Refine Assets editor & metadata implementation
(MGNLDAM-186)
|
|
| 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 approach is to use JCR/MGNL properties where available as the DC properties. ie: dc:identifier is set to the jcr:UUID field. 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. One option would be to create two fields for these:
|