2316909 - Naming Convention of SCORM and Documents Content Objects uploaded - [LMS]

Naming convention of the Documents and SCORM Content Objects uploaded to the iContent via the Depolyment Location in LMS.

SuccessFactors LMS

1) If it is a document(pdf, video or audio files, txt, docx, xlsx etc) that you are uploading, the file name would be considered as the Content Object "Object ID". For example: if you upload "TestPDF.pdf" the Object ID would be "TestPDF".

2) When you upload a SCORM content which would be usually zipped, we could find a file named "imsmanifest.xml" that is responsible for filling the details of content objects of a content package. The two main parameter responsible for the naming convention is "manifest identifier"(first 15 characters or lesser) and "identifierref" and a sequence number generated by SuccessFactors LMS to keep the Content Object's IDs unique whereas the Content Package would get you the name that you give for it when you import the content. All the additional information related to the content could be found in this imsmanifest file easily, like the SCORM type in "schemaversion" SCORM 1.2 or SCORM 2004 etc.,

For Example, consider the following imsmanifest file, this would help the LMS system create two Content objects: "manifest identifier"_"identifierref"_"RandomValue"

1) CABELAS-1-MANIF_SCO1_RandomValue
2) CABELAS-1-MANIF_SCO2_NextRandomValue

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

<manifest identifier="CABELAS-1-MANIFEST" version="1.0"
  xmlns="http://www.imsproject.org/xsd/imscp_rootv1p1p2"
  xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_rootv1p2"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.imsproject.org/xsd/imscp_rootv1p1p2 imscp_rootv1p1p2.xsd
                        http://www.imsglobal.org/xsd/imsmd_rootv1p2p1 imsmd_rootv1p2p1.xsd
                        http://www.adlnet.org/xsd/adlcp_rootv1p2 adlcp_rootv1p2.xsd" >

<metadata>
 <schema>ADL SCORM</schema>
 <schemaversion>1.2</schemaversion>
 <adlcp:location>imsmetadata.xml</adlcp:location>
</metadata>
 
<organizations default="TOC1">
 <organization identifier="TOC1">
  <title>Gearing Up For Camping</title >
  <item identifier="I_SCO1" identifierref="SCO1">
   <title>Introduction To Camping</title>
  </item>
  <item identifier="I_SCO2" identifierref="SCO2">
   <title>Cabela's Tents, Sleeping Systems, and Packs</title>
  </item>
 </organization>
</organizations>

<resources>
 <resource identifier="SCO1" type="webcontent" adlcp:scormtype="sco" href="camping_01/main.htm">
  <file href="camping_01/main.htm" />
  <file href="interface.swf" />
 </resource>
 <resource identifier="SCO2" type="webcontent" adlcp:scormtype="sco" href="camping_02/main.htm">
  <file href="camping_02/main.htm" />
  <file href="interface.swf" />
 </resource>
</resources>
</manifest>
----------------------------------------------------------------------------------------------------------------------------------------

Content Object, naming convention, SCORM Content Object ID, Content Object ID, documents, iContent, Deployment Location , KBA , LOD-SF-LMS-CNT , Content , How To