Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-186 Refine Assets editor & metadata implementation
  3. MGNLDAM-188

Asset Editor: Decide and implement how to handle DC metadata fields that overlap with JCR and MGNL fields.

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Obsolete
    • Neutral
    • None
    • 1.0
    • None
    • None

    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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            czimmermann Christopher Zimmermann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: