[MGNLDAM-764] Add "alternative" to asset meta data DCMI Created: 04/Oct/18  Updated: 03/Sep/20  Resolved: 03/Sep/20

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM Core
Affects Version/s: 2.4.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLREST-266 NodeWriter & Asset writer should be m... Open
duplicate
duplicates MGNLDAM-650 Offer a convenient way to specify the... Open
relation
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)

 Description   

Expand the coverage of the DCMI by adding "alternative" to Asset metadata. See https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/alternative



 Comments   
Comment by Richard Gange [ 03/Sep/20 ]

After closer investigation we can see that we use whatever Tika is providing us. See https://tika.apache.org/1.16/api/org/apache/tika/metadata/DublinCore.html. Really "alternative" is not part of the core group of properties which is widely supported. The concern from their side is to have it consistent across a super wide variety of file formats & parsers. In other words, we may declare/support alternative, but we would/might not be able to extract it from uploaded assets

For both related support tickets the issue could also be resolved with MGNLREST-266. So we will focus there and close this issue as "Won't do".

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