When replacing an existing SCORM package, the LMS checks whether the identifier inside the new package matches the identifier in the existing package. The Identifier setting, located beneath Package File in the SCORM activity settings, determines whether a replacement with a different identifier can be saved.
Important: This setting does not change the identifier inside your SCORM package, and selecting an option does not delete historical learner records. It only controls whether the LMS accepts the replacement package.
What Is a SCORM Identifier?
A SCORM package contains an identifier in its imsmanifest.xml file, typically generated by the authoring tool or content provider. The LMS uses identifiers to associate learner attempts, progress, scores, and reporting information with SCORM content.
When a replacement package is uploaded, the LMS compares its identifier with the existing package's identifier. If they match, this setting does not prevent the replacement. If they differ, the setting determines whether saving is allowed.
Understanding the Two Settings
Do not allow changes to the identifier (default)
If the new package has a different identifier, the LMS warns you and prevents the replacement from being saved. The existing package and its historical learner records remain unaffected.
To proceed, request a package that retains the existing identifier from your content provider, or deliberately choose the option below after considering the reporting consequences.
Allow changes to the identifier
If the new package has a different identifier, the LMS allows you to save the replacement. It does not modify the identifier in the file.
Historical learner data is not deleted. However, previous attempts, progress, and scores may no longer appear in standard SCORM reports for the updated package because they are associated with the previous identifier. This can make data appear to be lost even though the underlying records remain stored.
Only choose this option if you understand and accept the potential impact on historical reporting.
Example
Suppose 200 learners have completed a SCORM activity and your provider supplies an updated package.
-
Identifier unchanged: The replacement can be saved regardless of the Identifier setting.
-
Identifier changed; changes not allowed: The LMS warns you and refuses to save the replacement. The existing package and records are unaffected.
-
Identifier changed; changes allowed: The replacement can be saved. The 200 learners' records are not deleted, but some or all of their earlier results may no longer appear in standard SCORM reports.
Why Might the Identifier Change?
The identifier is defined in the package itself, usually by the authoring software or content provider. It may change when a package is republished, recreated, or substantially revised.
For routine changes such as spelling corrections, updated images, formatting, accessibility improvements, or repaired links, the identifier should generally remain unchanged.
Significant structural changes, such as reorganizing slides, SCOs, navigation, or assessments, may justify a different identifier. However, retaining the same identifier after major structural changes can also cause problems for learners attempting to resume previously started activities.
Impact on incomplete attempts: A learner who started a SCORM activity but has not finished it may be unable to resume after significant structural changes. They may encounter a blank screen when reopening the activity. In such cases, an administrator may need to delete the learner's in-progress SCORM attempt so the learner can start again. Deleting that attempt removes the progress recorded in that attempt.
Ask your content provider to assess whether an identifier should be retained or changed when republishing content.
Who Is Responsible for the Identifier?
Dual Code does not automatically change, generate, or correct identifiers within client-supplied SCORM packages. The identifier is part of the package provided by your content provider or authoring tool. The LMS setting only controls whether a replacement with a different identifier is accepted.
If you are unsure why the identifier changed, contact your content provider before proceeding. Dual Code can assist with SCORM content modifications under a separate Professional Services agreement; this work is not included in standard hosting and support fees.
Key Takeaways
-
The setting does not change the identifier inside the SCORM package.
-
The default setting blocks a replacement when the identifier differs.
-
Allowing the replacement does not delete historical learner data, but historical results may disappear from standard SCORM reports.
-
Significant structural changes can disrupt in-progress attempts, even when the identifier remains the same.
-
When in doubt, retain the default setting and consult your content provider.