OpenDocProject:DC CollectionPolicy/2010/09/13

{| width="800"
 * style="background-color: #EEE"|[[Image:owwnotebook_icon.png|128px]] Project name
 * style="background-color: #F2F2F2" align="center"|  |Main project page
 * style="background-color: #F2F2F2" align="center"|  |Main project page


 * colspan="2"|
 * colspan="2"|

Report

 * Nic Weber 11:40, 13 September 2010 (EDT):One of our (my) main objectives is to draft a Collection Policy report which summarizes best practices in data centeres and archives. This was the motivation for a number of my observations last week.

I've started to outline what that document might look like. (see google doc)


 * Nic Weber 11:45, 13 September 2010 (EDT): I'd also like to take a closer look at the layered collection policy of ADS and the levels of service, as defined by NSIDC.

NSIDC presents the following service categories

1. Archival – Levels of service in this area reflects the relative amounts of work required in order to ingest and archive a data set.

2. Metadata – Levels of service in this area reflect the amount of work required to develop and maintain metadata not just for the data set as a whole; but also for any data element or service associated with the data set.

3. Documentation – Levels of service in this area reflect the amount of work required to document the data set and any associated web pages.

4. Distribution – Levels of service in this area reflect the amount of work required to support data distribution or distribution-related services.

5. USO Infrastructure – In order to provide any level of USO support, a base level of infrastructure support is required in order to prepare USO systems for the data set. This is a one-time setup that is not affected when levels of service change.

6. USO Support – Levels of service in this area reflect the amount of work required to support human-human requests for information about or help with a data set (via any mechanism – phone, email, etc.)


 * }