* Automatic Caldb Update plan 
 
 The project delivers the data files and index files in the caldb 
 staging area. Each delivery consists in the following :

 - Calibration data file 
 - Index file
 - Send an email to the "caldbingest@legacy.gsfc.nasa.gov

* Calibration Data files 

 The data files are expected to be in FITS already checked and prepared to be
 made public. To ensure that the project should follow these steps
 when preparing the data for a CALDB delivery:
  
 - Verification.  The file should been already verified for integrity
   with no errors in their FITS file structure and possibly with no warning.
 
 - Chechsum datasum. All the files should contain the DATASUM and CHECKSUM 
   keywords added to each extention.

 - Directory. All files should be already in the final directory structure 

 *Index File

 With each data delivery an index file should be present for ecah of the 
 instruement. The index file should be updated with all files included 
 in caldb, even if the delivery includes only updates or new files 
 (see below Delivery section). Within the index file the QUALITY column 
 should be properly flagged for all data files in CALDB. 
 The delivery should include two identical caldb index files named as follows:
 - caldb.indx. This file is used by the caldb software to query caldb.
 - caldb.indxYYMMDD where YYMMDD is the delivery date. 
   This file will be moved in the public area in a directory named /index 
   where all the previous delivery of caldb.indexYYMMDD files are kept.
   Calibration files can change across the mission life time. Tagging the 
   index files with a date allow to recover information on what files were 
   present in CALDB and what was their quality setting.
   In this way files produced with a specific delivery of CALDB can be 
   reproduced by selecting the specific caldb.indexYYMMDD.

* Email content
 
 After data and index files are ready and copied in the CALDB staging area
 an email should be sent to "caldbingest@legacy.gsfc.nasa.gov"
 The subject of the e-mail should contain mission name and date of the
 delivery (YY/MM/DD) preceeded by the string "caldb update". 
 For example :

 Subject: caldb update ASCA 93/12/20

 indicates that the ASCA calibration data file were staged on 
 December 20 1993.
 
 The email should contain two keywords and the list of files included 
 between a set of markers. The keywords are 'instrument' and 'caldbfile' and
 should be set to the instrument name and the caldbindex file for that 
 instrument respectively. It should be one keyword per line.
 The strings for the markers are 'newfile' and 'endnewfile'. After  
 'newfile' starts the list of files given one per line with the directory 
 structure. The list should end with the string 'endnewfile'.
 If the delivery includes data file from different instrument of the same 
 mission the above structure should be repeted within the same e-mail 
 for each of the instrument.
 For example the email structure of a ASCA SIS and GIS calibration file
 delivery of ASCA data contains the following:

   instrument= GIS
   caldbindexfile= caldb.indx931220
   newfile
   gis/cpf/gis_center256.rmf
   gis/cpf/93dec20/g2_1p.arf
   endnewfile
   instrument= SIS
   caldbindexfile= caldb.indx931220
   newfile
   sis/cpf/s0c3g0p20e0_512_1c.rsp
   sis/bcf/sis0c3p40_290296.fits
   sis/bcf/bgd/s0bgd_14i.evt
   endnewfile


 * Delivery

  The first delivery should contain all the CALDB files.
  The updates either because a new version of the file has been released
  or because a new file has been added should contain ONLY the new data 
  file. The caldb index appropariate for that instrument should reflect 
  what is changed in caldb :
  - New file. The caldb index file should include a new line which the 
    characteristic of the new file
  - Update file. The caldb index file should include a new line with the
    update version of the file. The QUALITY value for the old file should be
    set to lower quality value.