Refine Assets editor & metadata implementation (MGNLDAM-186)

[MGNLDAM-188] Asset Editor: Decide and implement how to handle DC metadata fields that overlap with JCR and MGNL fields. Created: 28/Mar/13  Updated: 12/Mar/21  Resolved: 12/Mar/21

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

Type: Sub-task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:

 Description   

Decisions must be made about how to best handle DC metadata fields that potentially coorespond to Asset JCR fields.

Current DAM API implementation specified here: http://wiki.magnolia-cms.com/display/DEV/Concept+-+DAM+Asset+Metadata
The gist of this spec been followed in the asset editor to maintain consistancy, and avoid confusion.

The approach is to use JCR/MGNL properties where available as the DC properties. ie:

dc:identifier is set to the jcr:UUID field.
dc:creator <= jcr:createdBy
dc:date <= mgnl:created

But there are problems with this approach. For example, one can imagine that a user would want to specify or import the original creator of a photo, rather then using the id of the magnolia author who uploaded the jpeg file.
Maybe they want to specify their own identifier.
Maybe they want to specify or import the creation date of the photo - not the upload date into JCR. On the other hand - it could be useful to use the Asset upload date.

One option would be to create two fields for these:

  • one for jcr/mgnl
  • one for free entry.

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