[MAGNOLIA-5381] Change the link API/Functionalities in order to support 'LinkProviders' Created: 14/Oct/13  Updated: 04/Mar/19

Status: Open
Project: Magnolia
Component/s: core
Affects Version/s: 5.0, 5.1
Fix Version/s: None

Type: Task Priority: Major
Reporter: Eric Hechinger Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDAM-296 Add a migration task for images uploa... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

The current link implementation assume that every 'documents' are stored into a JCR repository.
In order to access the document, the UUID and workspace informations of the link are used to retrieve the Document.

Unfortunately, for example in DAM Assets, the UUID is a composite key 'provider:uniqueAssetIdentifier' and in order to create a proper link, the following steps should be followed:

  • Get the corresponding Asset provider
  • Provider.getRendition().getLink() --> generate a proper link.

We will also need this for the forum module.



 Comments   
Comment by Eric Hechinger [ 12/Nov/13 ]

This should be done within M5.3, together with the introduction of the new DAM functionality (Create an Asset, get an Asset from an external provider...).

Comment by Tobias Mattsson [ 04/Dec/13 ]

I'm assuming the need for this comes from the fact that we're storing links in rich text fields in a format fed to the Link API. So for embedding links to assets in such fields the Link API would need to be extended to accept links to assets in that format.

I could be wrong though, or not see the full picture. Anyway, there's big room for alternative solutions here.

Generated at Mon Feb 12 04:04:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.