Refine Assets editor & metadata implementation (MGNLDAM-186)

[MGNLDAM-193] Asset Editor: Evaluate if language field should be a dropdown and how it should be configured. Created: 02/Apr/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   

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?)


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