The CAS File Manager is a great data archive tool that is extremely flexible, but sometimes that flexibility can lead to confusion since you can perform a single task (like defining metadata elements) in various ways. This page's focus is to capture the 'Best Practices' people have found on their projects/experience when creating policy.

To try and keep the confusion to a minimum we will start with a Taxonomy to define some key terms, then jump into some Operational Scenarios. The scenario for all the Ops Scenario's will be built around the idea of cataloging and archiving MEDIA (audio, video, images) since most everyone can relate to these items. Some of the simple examples will focus on a single media format, while the more complex examples will show how to deal with an ever changing media library.

Taxonomy

File Manager Policy - All the *.xml files that the filemanager will use to define metadata

Data Set -

Product Type -

Virtual Product Type -

Metadata Elements -

Operational Scenarios

Simple File Manager Policy

• One set of File Manager Policy
• All of the Data Sets are homogenous

Example: You want to catalog and archive music files. They are logically grouped together by some album, but every song you archive has the same metadata elements. In this case we have a single Data Set called Music, which will be mapped to the default Product Type: GenericFile.

Sample Policy Overview

NOTE: Items that are bold/italic are default policy that come pre-installed with the File Manager and do not need to be edited.

product-types.xml

• GenericFile

elements.xml

• CAS.ProductId
• CAS.ProductName
• CAS.ProductReceivedTime
• Filename
• FileLocation
• ProductType
• ProductStructure
• MimeType
• Album
• Artist
• Track_Number
• Year
• Title

product-type-element-map.xml

• type=GenericFile
• * Filename

File Manager Policy with Inheritance

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

Example:

Sample Policy Overview