Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-44810

Support ResouceLink.id.history subsitution variables

    XMLWordPrintable

    Details

    • 21 Status:
      Verified
    • 20 status:
      Verified
    • Conversion Script Required:
      Yes
    • Test Plan:
      Hide

      Install an LTI 1.3 app store.  Make sure the "Allow External Tool to store setting data" is not checked for the tool.  

      Make a site with Lessons + Gradebook.  Add an LTI tool to the site.   Launch the tool in debug mode and look at the data for something like:

      resourcelink_id_history":""

      The make another site and copy in the Lessons from the first site.  The tool should be in lessons and ready to launch.  When you launch it you should see something like this in the debug data:

      resourcelink_id_history":"content:12"

      The make another site and copy in the Lessons from the second site.  The tool should be in lessons and ready to launch.  When you launch it you should see something like this in the debug data:

      resourcelink_id_history":"content:12,content:13"

       

      Show
      Install an LTI 1.3 app store.  Make sure the "Allow External Tool to store setting data" is not checked for the tool.   Make a site with Lessons + Gradebook.  Add an LTI tool to the site.   Launch the tool in debug mode and look at the data for something like: resourcelink_id_history":"" The make another site and copy in the Lessons from the first site.  The tool should be in lessons and ready to launch.  When you launch it you should see something like this in the debug data: resourcelink_id_history":"content:12" The make another site and copy in the Lessons from the second site.  The tool should be in lessons and ready to launch.  When you launch it you should see something like this in the debug data: resourcelink_id_history":"content:12,content:13"  

      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

       

       
       

        Gliffy Diagrams

          Zeplin

            Attachments

            1. tool_settings.gif
              tool_settings.gif
              33 kB
            2. site_import_3x_no_lti_tool.mp4
              7.55 MB
            3. SAK-44865-Background.png
              SAK-44865-Background.png
              2.71 MB
            4. SAK-44810-Working.png
              SAK-44810-Working.png
              459 kB
            5. SAK-44810-unchecked.png
              SAK-44810-unchecked.png
              46 kB
            6. lessons_sites.gif
              lessons_sites.gif
              60 kB
            7. lessons_import_from_site2_failing.mp4
              19.13 MB
            8. announcements_lti_tool.gif
              announcements_lti_tool.gif
              64 kB
            9. announcements_lti_site_import.mp4
              10.35 MB
            10. 16Jan2021_imports.gif
              16Jan2021_imports.gif
              23 kB

              Issue Links

                Activity

                  People

                  Assignee:
                  csev Charles Severance
                  Reporter:
                  csev Charles Severance
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration