Dam API refactoring. Do not expose JCR nodes to third parties. (MGNLDAM-94)

[MGNLDAM-105] Create the Metadata Interfaces and class hierarchy Created: 05/Feb/13  Updated: 18/Feb/13  Resolved: 14/Feb/13

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.0

Type: Sub-task Priority: Neutral
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: bl-145
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLDAM-127 Enable developers to add additional m... Closed
Template:
Date of First Response:

 Description   

Create a Main AssetMetadataInterface and two sub interfaces. One for Magnolia Metadata and one for Dublin Metadata. Create also classes that implement these interfaces.

Create a MetadataBuilder Interface definition and an Internal Builder responsible to create the Metadata Pojo stored into JCR node.



 Comments   
Comment by Christopher Zimmermann [ 18/Feb/13 ]

Review:
Some of the implementation is hardcoded to "magnolia" and "dublin core". It should not be.

Comment by Christopher Zimmermann [ 18/Feb/13 ]

Created followup ticket (DAM-127 linked) to make it that developers can add other standards. Currently its hard-coded to DublinCore and Magnolia standards only. Closing this ticket though - as the API is correct.

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