[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: |
|
||||||||
| 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. 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:
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. |