[MGNLDAM-912] Improve support for custom asset metadata Created: 18/Nov/20  Updated: 23/Aug/22

Status: Open
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: metadata
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDAM-411 Support custom metadata Closed
relation
is related to MGNLDAM-902 AssetPreviewProvider throws exception... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Team: AuthorX

 Description   

Since MGNLDAM-411, one may implement a custom AssetMetadataDefinition. These implementations are bound to the AssetMetadataRegistry via @Multibinding.

However, both JcrAsset and JcrAssetProvider limit their support to MagnoliaAssetMetadata and DublinCore, plain hard-coded.

  • AssetProviders should be able to configure which metadata they support (in similar way they can configure mediaTypes)
  • Assets may then implement #supports(AssetMetadata) according to their own media-type (for media-type-dependent metadata), and Assets app should respect those dynamically. Should return Optional<AssetMetadata> by now.

Side note: Magnolia's DublinCore support effectively corresponds to the historic, limited and openly outdated DC Element Set 1.1 +/- a few arbitrary elements Tika 1.x judged universal enough.
Nowadays, DCMI encourages adoption of the DCMI Metadata Terms spec instead, and Tika 2.x slightly improves the split of metadata classes (for parser's extraction), but still doesn't fully embrace DC Metadata Terms.


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