Project

General

Profile

Bug #491

scorm import: not fully imported

Added by Koen Favere almost 10 years ago. Updated over 8 years ago.

Status:
Bug resolved
Priority:
Normal
Assignee:
-
Target version:
Start date:
12/01/2010
Due date:
% Done:

0%

Estimated time:
Complexity:
Normal

Description

The higher level objects (the icon with two feet) are not completely imported. Only the title is imported, but not the content.
When you import the scorm package below, you should see a title for every 'two feet icon', with content (e.g. extra info concerning the exercise in the next (document/exercise) steps). This extra info is a plain html text or a plain html table, which shouldn't give any problems.


Files

Al-bar.zip (2.76 MB) Al-bar.zip Koen Favere, 12/01/2010 15:22

History

#1

Updated by Stefaan Vanbillemont almost 10 years ago

  • Target version set to 2
#2

Updated by Sven Vanpoucke almost 10 years ago

  • Category set to 4
  • Assignee set to Sven Vanpoucke
#3

Updated by Sven Vanpoucke over 9 years ago

  • Status changed from New to Needs more info
  • Assignee deleted (Sven Vanpoucke)

This is not a bug, this is a missing feature.
However this is a very big issue at the moment because our entire structure is built differently (sublearningpaths instead of chapters which are executable).

This means that not only our entire architecture of learning paths and chapters and items is wrong but also the way learning paths are executed on the system. This has a huge impact on the entire system.

The reason why we did it this way was because when we first started implementing scorm we started working with 2004, before making it backwards compatible with scorm 1.2. As far as we have read through the manual and several examples of scorm 2004 we never found anything about executable chapters.

I do not see a fast solution for this problem in the near feature without reworking the entire learning path.

#4

Updated by Sven Vanpoucke over 9 years ago

In addition to my previous comment i would like to add these resources to underline my statements

http://www.scorm.com/scorm-explained/technical-scorm/content-packaging/manifest-structure/

"<item>[1:many]Each item represents an activity in this course. Items can be nested to create a hierarchical structure. Items with child item nodes are called Aggregations. Items without children are called Leaf Nodes and represent a deliverable resource (SCO or Asset)."

"identifierref[0:1]Pointer to a resource that contains the content for this item. Should only be used on items that represent deliverable activities (SCO/Assets). Items that contain children (Aggregations) should not contain an identifierref attribute."

#5

Updated by Yannick Warnier over 9 years ago

  • Status changed from Needs more info to Assigned
  • Assignee set to Sven Vanpoucke

A few comments:

  • scorm.com is not the official resource for SCORM, and it is actually maintained by a commercial company (Rustici Software), which, by the way, provides a paying, non-open-source tool called the "SCORM cloud" which can integrate to Dokeos/Chamilo 1.8 to replace the current SCORM tool (when you know the efforts put into the SCORM tool as part of the Dokeos company's costs, I think it makes sense for them not to provide it for free)
  • Chamilo in 1.8, the idea was to provide one mother class (learnpath.class.php) to be extended by the various versions of SCORM (like scorm.class.php for SCORM v1.2 or aicc.class.php for AICC) in a distinct way. I still think this was an excellent idea. I don't know how it's been done in Chamilo 2.0, but I would recommend using the same kind of structure, with the base class allowing for directories (=nested items) to be executable.
  • I can't see a solution other than modifying the code to allow an element to be executable and have sub-elements

Extract from the SCORM 1.2 Content Aggregation Model's specification:

Multiplicity:  The <item> element may occur 0 or More times within the <organization> element and/or 0 or More times within an <item> element.  The <item> element can be nested any number of levels deep inside of another <item> element.

Attributes:
- identifier (required). An identifier that is unique within the Manifest.  Data type = ID.
- identifierref (optional). A reference to a <resource> identifier (within the same package) or a (sub)Manifest that is used to resolve the ultimate location of the file.  If no identifierref is supplied, it is assumed that there is no content associated with this entry in the organization.  Data type = String.
- isvisible (optional). Indicates whether or not the title of the item is displayed by the LMS navigation mechanism.  If not present, value is assumed to be “true”.  Data type = Boolean
- parameters (optional). Static parameters to be passed to the content file at launch time.  Data type = String.

In short, there is no mention that items with sub-items should not have an identifierref.

Another thing: in the glossary of SCORM 2.0, is there a specification of what "must" and "should" mean?

In the specification of identifierref, "Should only be used on items that represent deliverable activities (SCO/Assets). Items that contain children (Aggregations) should not contain an identifierref attribute." doesn't mean that it must be that way. It means it should. Sadly, there is a lot of possible interpretation in SCORM, and it seems you've fallen fool to one of them.

This finally means that there is no other solution than to "rework[ing] the entire learning path"...

#6

Updated by Sven Vanpoucke over 9 years ago

  • Status changed from Assigned to Needs more info
  • Assignee deleted (Sven Vanpoucke)

We decided to leave it as it is know and support scorm semi for the first release of 2.0

#7

Updated by Stefaan Vanbillemont over 9 years ago

  • Status changed from Needs more info to Bug resolved
#8

Updated by Stefaan Vanbillemont over 8 years ago

  • Project changed from Chamilo LCMS Connect to Repository
  • Category deleted (4)
#9

Updated by Stefaan Vanbillemont over 8 years ago

  • Target version changed from 2 to 1.0.0

Also available in: Atom PDF