In-Line attachments (i.e. links to Sakai entities in HTML based Sakai entities) need to be specially transferred when the entity is transferred or archived
GENERAL
TESTING
GENERAL
TESTING
Description
Now that more of Sakai entities have HTML parts, and now that we have the ability to make "inline" attachments, i.e. links in the HTML, when we archive / import and transfer these entities we must take special care of these links.
This same care must be taken for any entity attachments, but attachments are already dealt with (correctly?) and are all in one place; inline attachments are trickier because they may be in any HTML part of an entity (file in content hosting, body of announcement, etc).
Links may be to content (such as images, etc) outside Sakai. These links would archive/import and transfer without change.
Links may be to content inside Sakai, but outside the context of the entity (i.e. to another site or public area). When the entity is archived, the content for these links should be part of the archive package, which is re-established if needed on import. The attached content may or may not be there at import. For a transfer/copy of the entity to another context, the links can be left alone.
Links may be to content in Sakai, in the same context as the entity. In these cases, the link content should be part of the archive package, and when imported, the content needs to be re-established in the new context, and the links updated (if not relative). For a transfer, the linked content should also be transferred to the new context, and the links updated (if not relative).
We might want to leave the links to the original site on a transfer, making a cross-context reference. But this could cause problems with permissions, etc.
We might want to leave the links in the original Sakai instance on an archive/import to an new Sakai, but again, this could cause problems with permissions, etc.
If this is not done properly, archive/imported or transferred entities will have broken or inaccessable links.
This effects many Sakai applications, such as:
ContentHosting
Announcements
Assignments
etc.
Any application that supports HTML and inine links / attachments.
Also, it is worth checking that the same logic is still being done in all these cases for regular attachments.
Activity
Neal Caidin August 14, 2017 at 2:00 PM
Bulk closing issues that have not been updated since 2014 and earlier. Please reopen if this is still an issue and you have new information.
Now that more of Sakai entities have HTML parts, and now that we have the ability to make "inline" attachments, i.e. links in the HTML, when we archive / import and transfer these entities we must take special care of these links.
This same care must be taken for any entity attachments, but attachments are already dealt with (correctly?) and are all in one place; inline attachments are trickier because they may be in any HTML part of an entity (file in content hosting, body of announcement, etc).
Links may be to content (such as images, etc) outside Sakai. These links would archive/import and transfer without change.
Links may be to content inside Sakai, but outside the context of the entity (i.e. to another site or public area). When the entity is archived, the content for these links should be part of the archive package, which is re-established if needed on import. The attached content may or may not be there at import. For a transfer/copy of the entity to another context, the links can be left alone.
Links may be to content in Sakai, in the same context as the entity. In these cases, the link content should be part of the archive package, and when imported, the content needs to be re-established in the new context, and the links updated (if not relative). For a transfer, the linked content should also be transferred to the new context, and the links updated (if not relative).
We might want to leave the links to the original site on a transfer, making a cross-context reference. But this could cause problems with permissions, etc.
We might want to leave the links in the original Sakai instance on an archive/import to an new Sakai, but again, this could cause problems with permissions, etc.
If this is not done properly, archive/imported or transferred entities will have broken or inaccessable links.
This effects many Sakai applications, such as:
ContentHosting
Announcements
Assignments
etc.
Any application that supports HTML and inine links / attachments.
Also, it is worth checking that the same logic is still being done in all these cases for regular attachments.