Scorm Cloud and Delivery Control 'Objective Set by Content attribute' parser error

[Tou Lee]

Hi All,

I just tried out the Pipwerks Javascript SCORM API wrapper, and am able to upload the test course (2004) up to SCORM Cloud to test. Course passes, and completion status is set, but I for some reason I am getting the following parser error. Additionally, I am not receiving the usual "manifest looks great" (something to that line) about the manifest file. I'm fairly new to SCORM, so any suggestions, or comments would be greatly appreciated. Thank you!

• The Delivery Control 'Objective Set by Content attribute' was detected on a cluster node, but is only applicable to leaf nodes.
• The Delivery Control 'Completion Set by Content attribute' was detected on a cluster node, but is only applicable to leaf nodes.

[John Campbell]

The <item> element is nested.  Your content can only set success and completion for itself (the SCO).  The SCO is a leaf node of the nested tree.  Don't stick those attributes on an item element that isn't a leaf node.  That is a "cluster" or group of SCOs.

<item>  <!-- CLUSTER -->

   <item>  <!-- SCO -->

    </item>

</item>

take care,

jpc

--
You received this message because you are subscribed to the Google Groups "eLearning Technology and Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elearning-technology-and...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Tou Lee]

Thank you for the response. I apologize for the late late late reply, as I never received an e-mail alert about somebody replying back. Thank you. 

So, what you're saying in your response is that the <item> element should not be nested? I guess I am still a bit confused on what I should do to resolve this. Take the <item> out of <organization>? This e-learning only has one SCO — the main file itself. This is the basic SCORM 2004 manifest. 

<?xml version="1.0" standalone="no"?>

<manifest   identifier="completionExample" version="1.0"

xmlns="http://www.imsglobal.org/xsd/imscp_v1p1"

xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"

xmlns:adlseq="http://www.adlnet.org/xsd/adlseq_v1p3"

xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"

xmlns:imsss="http://www.imsglobal.org/xsd/imsss"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd

http://www.imsglobal.org/xsd/imsss imsss_v1p0.xsd

http://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsd

http://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsd

http://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsd" >

<metadata>

<schema>ADL SCORM</schema>

<schemaversion>2004 3rd Edition</schemaversion>

</metadata>

<organizations default="org_pipwerks">

<organization identifier="org_pipwerks">

<title>COURSE TITLE</title>

<item identifier="pipwerks_SCORM2004_item01" identifierref="pipwerks_SCORM2004_item01_resource">

<title>COURSE TITLE</title>

</item>

<imsss:sequencing>

<imsss:controlMode choiceExit="true" flow="true"/>

<imsss:deliveryControls completionSetByContent="true" objectiveSetByContent="true"/>

</imsss:sequencing>

</organization>

</organizations>

<resources>

<resource identifier="pipwerks_SCORM2004_item01_resource" adlcp:scormType="sco" href="index.html" type="webcontent">

<file href="index.html"/>

<file href="SCORM_API_wrapper.js"/>

</resource>

</resources>

</manifest>

take care,

jpc

To unsubscribe from this group and stop receiving emails from it, send an email to elearning-technology-and-development+unsubscribe@googlegroups.com.

[Ethan Estes]

Move the <imsss:sequencing>  element inside your <item> element. Then the sequencing will be targeting the leaf/item and not the cluster which in this case is the root of the course.

Tou Lee wrote:

To unsubscribe from this group and stop receiving emails from it, send an email to elearning-technology-and...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
-EÆ

[Tou Lee]

I appreciate the fast response eestes1. I took your suggestion and moved the <imss:sequencing> element inside my <item> element. It did get rid of those two errors in SCOMR Cloud, but I was faced with three new ones (see below). Does the main <organization> need a <imss:sequencing> child as well (http://scorm.com/scorm-explained/technical-scorm/content-packaging/manifest-structure/#)? 

• An item was encountered that does not have an identifierref or any children.
• The Sequencing Control Mode 'Flow' was detected on a leaf node, but is only applicable to cluster nodes.
• The file referenced by the href attribute could not be found. href = index.html

For more options, visit https://groups.google.com/d/optout.

--
-EÆ

[Lis Tao]

I was able to get a clean / good manifest file when I moved the <imss:sequencing> into the file, and removed the flow attribute. The one that was marked good by SCORM Cloud is as follows. Thanks again!

<?xml version="1.0" standalone="no"?>

<manifest   identifier="completionExample" version="1.0"

xmlns="http://www.imsglobal.org/xsd/imscp_v1p1"

xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3"

xmlns:adlseq="http://www.adlnet.org/xsd/adlseq_v1p3"

xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3"

xmlns:imsss="http://www.imsglobal.org/xsd/imsss"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd

http://www.imsglobal.org/xsd/imsss imsss_v1p0.xsd

http://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsd

http://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsd

http://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsd" >

<metadata>

<schema>ADL SCORM</schema>

<schemaversion>2004 3rd Edition</schemaversion>

</metadata>

<organizations default="org_pipwerks">

<organization identifier="org_pipwerks">

<title>Building Inclusive Skills: Introduction to Diversity</title>

<item identifier="pipwerks_SCORM2004_item01" identifierref="pipwerks_SCORM2004_item01_resource">

<title>Building Inclusive Skills: Introduction to Diversity</title>

<imsss:sequencing>

<imsss:controlMode choiceExit="true"/>

<imsss:deliveryControls completionSetByContent="true" objectiveSetByContent="true"/>

</imsss:sequencing>

</item>

<!-- <imsss:sequencing>

<imsss:controlMode choiceExit="true" flow="true"/>

<imsss:deliveryControls completionSetByContent="true" objectiveSetByContent="true"/>

</imsss:sequencing> -->

</organization>

</organizations>

<resources>

<resource identifier="pipwerks_SCORM2004_item01_resource" adlcp:scormType="sco" href="index.html" type="webcontent">

<file href="index.html"/>

<file href="SCORM_API_wrapper.js"/>

</resource>

</resources>

</manifest>

On Thursday, February 12, 2015 at 3:17:08 PM UTC-6, eestes1 wrote:

For more options, visit https://groups.google.com/d/optout.

--
-EÆ

[Ethan Estes]

Yeah, flow is used on a cluster to state that the system should eval the seq rules to find the next valid child item to launch in the cluster. That may  occur when a user clicks on LMS provided controls or possibly via nav commands from sent from within the content.

You need to go look at the Sequencing and Navigation spec at http://adlnet.org/ to see what can be used on what type of element. They also have zip examples of various sequences that you can study.

Tou Lee wrote:

To unsubscribe from this group and stop receiving emails from it, send an email to elearning-technology-and...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
-EÆ

[Lis Tao]

Thanks for the clarification. I'll take further look at that resource you provided and study up a bit more. Your help and expertise is very much appreciated!