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.
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:
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: