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

Asset Editor: Evaluate if language field should be a dropdown and how it should be configured.

    XMLWordPrintable

Details

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

    Description

      Language field should allow user to specify the language used in the asset. For example the language appearing in an image.
      Ideally this field would restrict entries to a language coding scheme like "en" "de-CH" etc. Perhaps with a dropdown.

      Decisions need to be made about this implementation:

      Should we create a new language field that is pre-populated with the language defined for the webiste?
      Should we make the current dropdown field more flexible by enabling it to point elsewhere in the tree to get its options?
      Do we rather need a programatic way to configure dropdowns?

      Or is it to limiting to have a dropdown - what about a website that needs to serve up assets with many different languages? (Or in that case should they rather use tags for all the languages?)

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: