[MGNLDAM-912] Improve support for custom asset metadata Created: 18/Nov/20 Updated: 23/Aug/22 |
|
| Status: | Open |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | metadata | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||
| Team: | |||||||||||||||||
| Description |
|
Since However, both JcrAsset and JcrAssetProvider limit their support to MagnoliaAssetMetadata and DublinCore, plain hard-coded.
Side note: Magnolia's DublinCore support effectively corresponds to the historic, limited and openly outdated DC Element Set 1.1 +/- a few arbitrary elements Tika 1.x judged universal enough. |