Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-411

Support custom metadata

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Neutral
    • 2.1
    • 2.0
    • DAM API

    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)

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                rsiska Robert Šiška
                gjoseph Magnolia International
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoR