[MGNLDAM-127] Enable developers to add additional metadata standards Created: 18/Feb/13 Updated: 28/Feb/13 Resolved: 27/Feb/13 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | BL-145 | ||
| 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)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
In the current implementation the metadata-standards are hard coded. It must be possible to add and change the available metadata standards. For example a registry of metadata standards. Here is for example some code that must go: if (SupportedMetaDataType.MAGNOLIA.name().equals(metadataType)) { return createMagnoliaMetadata(source); }else if (SupportedMetaDataType.DUBLIN_CORE.name().equals(metadataType)) { return createDublinCoreMetadata(source); } else { |
| Comments |
| Comment by Eric Hechinger [ 27/Feb/13 ] |
|
Solved by |