An adopter has found that older integration data produces LTI links of the form https://my-oeq-url/null. Also, the current behavior has shown room for improvement.
Looking to make the following changes:
1
Turn off the deletion of data from the old integration building block. It should not affect the migrated link since it's now under a new handle (eg apereo/oeq), and deleting it may create unforeseen issues.
2
Implement the following logic flow:
if the equella content has the extendedData/Blob > entry > url of the form integ/gen/...attachment.uuid=..., use it.
else if the equella content body contains <!--item... attachments... selected="link-to-migrate"... then parse the attachments@selected value
else if (need to consider other edge cases)
otherwise, if the parser can't find an appropriate link-to-migrate, it'll log what extendedData and HTML it tried to parse, and skip that link, instead of trying to change it and creating a broken link.
3
Log that the script is ignoring the content id / handle if it DOESN'T match:
An adopter has found that older integration data produces LTI links of the form
https://my-oeq-url/null
. Also, the current behavior has shown room for improvement.Looking to make the following changes:
1 Turn off the deletion of data from the old integration building block. It should not affect the migrated link since it's now under a new handle (eg apereo/oeq), and deleting it may create unforeseen issues.
2 Implement the following logic flow:
integ/gen/...attachment.uuid=...
, use it.<!--item... attachments... selected="link-to-migrate"...
then parse the attachments@selected value3 Log that the script is ignoring the content id / handle if it DOESN'T match:
4 Review the migration of the link description.