Name: CCSM Control Run Data Management

Vision:
   Define and implement a policy for managing CCSM control run data on NCAR's Mass Storage
   System (MSS).  This includes managing data location, account numbers, file passwords, 
   data pruning, the removal of unimportant control runs, and making particularly 
   important control run data available to the general CCSM community or the general 
   public.  This includes control runs from CCSM1.0 forward, but not necessarily control 
   runs of limited interest (eg. only of interest to specific working groups).  This 
   project DOES NOT include running control runs or the post processing of data.

Goals:
   1) Manage pertinent CCSM control run data stored on NCAR's MSS...
      * Identify CCSM control runs that CSEG is tasked with managing
      * Relocate this data into the mss:/CCSM/csm directory structure
      * Gather information on the worth of each case and prune cases accordingly 
        to save space and gau charges.
      * Create uniform password and insure MSS charges go to the proper accounts
   2) Manage any disk space made available for local convenience copies of CCSM control 
      run data, eg. the  /ccsm/data  disk nfs-mounted to NCAR/SCD supercomputers
   3) Manage CCSM control run data made available to the general public,
      eg. the CCSM3.0 data made available on the Earth System Grid (ESG)
   4) Assist in writing related CCSM data management policies.

Motivation:
   1) Often the location and storage of CCSM control run data is disorganized -- we 
      don't know where data is located, what accounts are being charged for data storage, 
      what accounts should be charged, and what data is unnecessary and should be deleted.
      This is unacceptable for our critically important CCSM control run data.
   2) CSEG receives various requests for CCSM data -- the data itself must be organized
      in order to meet these requests.

Authority:
   Mariana Vertenstein

Project Lead:
   Brian Kauffman

Implementation Plan:
   I)   Clean up /ccsm/data to make room for CCSM2.0 and CCSM3.0 data
   II)  Put convenience copies for select cases on /ccsm/data and the ESG
   III) ID important CCSM runs and collect a basic set of meta-data on all cases
   IV)  Determine and publish a formal data management policy regarding meta-data,
        passwords, location, account numbers, retention periods, and class-of-service 
   V)   Modify passwords, location, account numbers, retention periods, and
	class-of-service according to the policy
   VI)  Prune data or delete entire cases in /CCSM/csm as appropriate.