[MGNLDAM-411] Support custom metadata Created: 03/Mar/14  Updated: 18/Nov/20  Resolved: 04/Jun/15

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM API
Affects Version/s: 2.0
Fix Version/s: 2.1

Type: Task Priority: Neutral
Reporter: Magnolia International Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: architecture
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDAM-418 Improve handling of supported metadat... Closed
relates to MGNLDAM-912 Improve support for custom asset meta... Open
dependency
is depended upon by MGNLDAM-546 AssetQuery: add sorting capabilities Closed
is depended upon by MGNLDAM-564 Create new asset app module liberated... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: DAM / CMIS

 Description   

In the DAM 1.x API, it was possible to do Asset.getCustomProperty(). This doesn't sit well with the idea that Asset instances should be "disconnectable". (Since we'd have to copy all properties of an asset to support this method - and for all providers)

a) One way around this is to use AssetMetadata; define the custom properties you'd want in there. But that requires more implementation code than necessary.

b) We can also think about "meta metadata", where this Metadata would be described in configuration, rather than coded.

c) Another possibility would be to support something like this only in MagnoliaMetadata, and implement support for it only on the JcrAssetProvider.

To be able to pick the best approach of these 3, we'd need real, concrete use-cases. (a and c being the easiest for us; b probably the most flexible but also the most complex for us)


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