[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:
relation
is related to MGNLDAM-105 Create the Metadata Interfaces and cl... Closed
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:
InternalAssetMetadataBuilder

if (SupportedMetaDataType.MAGNOLIA.name().equals(metadataType))

{ return createMagnoliaMetadata(source); }

else if (SupportedMetaDataType.DUBLIN_CORE.name().equals(metadataType))

{ return createDublinCoreMetadata(source); }

else {
log.warn("Unsuported Metadata type '{}'", metadataType);
throw new AssetMetadataTypeNotSupportedException(metadataType + " is Not a supported Metadata Type.");
}



 Comments   
Comment by Eric Hechinger [ 27/Feb/13 ]

Solved by MGNLDAM-132

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