Page History

...

• One set of File Manager Policy
• There are some standard elements common to ALL Data sets
• Data Sets are heterogeneous

Example: You want to catalog and archive music AND video files. Now both of these files can be grouped under the more generic title of MEDIA, and they do share some metadata elements like 'Title' and 'Year', but they start to diverge with format specific terms (i.e. 'sample rate' vs. 'resolution').

So we DO NOT want to repeat the elements that both data sets have in common, so we introduce the idea of PARENT product types within the product-type-element-map.xml file. Whatever elements a PARENT product type contains are inherited by the children. In the Sample Policy below you see that Title and Year are declared ONCE but 2 child product types (Music and Video) can use those elements during ingestion.

Sample Policy Overview

NOTE: Items that are default policy and listed in the first example have been replaced with CAS.DEFAULTS to save space.

product-types.xml

• GenericFile
• Music
• Video

elements.xml

• CAS.DEFAULTS
• Album
• Artist
• Track_Number
• Year
• Title
• Sample_Rate
• Resolution
• Chapters
• Aspect_Ratio
• Director

product-type-element-map.xml

• type=GenericFile
• +CAS.DEFAULTS
• +Year
• +Title

• type=Music parent=GenericFile
• +Album
• +Artist
• +Track_Number
• +Sample_Rate

• type=Video parent=GenericFile
• +Resolution
• +Chapters
• +Aspect_Ratio
• +Director