Details
-
Type:
Bug
-
Status: CLOSED
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 21.0 [Tentative]
-
Fix Version/s: 20.3 [Tentative], 21.0 [Tentative], 22.0 [Tentative]
-
Component/s: BasicLTI
-
Labels:None
-
21 Status:Verified
-
20 status:Verified
-
Conversion Script Required:Yes
-
Test Plan:
Description
IMS LTI has a concept that tracks the "provenance" of content across site copies and content import from site. This JIRA will be used to add this feature to Sakai.
This also renames the lti_content field lti_allowsettings to be lti_allowsetings_ext because not setting this checkbox actually breaks some of Sakai's internal use of the settings field. Hence the need for a database conversion.
From this page:
http://www.imsglobal.org/spec/lti/v1p3/#lti-context-variable
ResourceLink.id.history | A comma-separated list of URL-encoded resource link ID values representing the ID of the link from a previous copy of the context; the most recent copy should appear first in the list followed by any earlier IDs in reverse chronological order. If the link was first added to the current context then this variable should have an empty value. |
From Moodle: https://youtu.be/c7vt7ClGTRM