Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

correctReponsesPattern target identifier inconsistency and SCORM 1.2 errors #199

Open
danielghost opened this issue Nov 12, 2024 · 2 comments
Labels

Comments

@danielghost
Copy link

danielghost commented Nov 12, 2024

The correctResponsesPattern of getInteractionObject() is inconsistent with the cmi.interactions.n.response data and can also cause a 405 error when using SCORM 1.2.

The pattern uses both the item and option indexes for the target identifier, but this doesn't align with the getResponse() identifier which just uses the option index for the target part of its pattern. Using different identifiers for the target makes it unclear when comparing this data. For example, the following shows how the data can looks different for a correctly answered question:

  • 1.2,2.4,3.2 - response
  • 1.1_2,2.2_4,3.3_2 - correctResponsePattern

I understand the item identifier was added to the target so that each one would be unqiue when accounting for a question with more than one dropdown, but I think the target identifier should be consistent when referenced. The addition of the item identifier also breaks the CMIFeedback data type for this pattern as only a single letter or number is allowed for each identifier. The Rustici SCORM 1.2 Engine raises a 405 LMSGetLastError() when using the current pattern structure.

This would need amending if including correct_responses elements for SCORM 1.2 in adaptlearning/adapt-contrib-spoor#281.

@oliverfoster
Copy link
Member

@oliverfoster
Copy link
Member

Any idea what the solution would look like? @danielghost

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants