Solar-B/EIS Catalog Requirements

EIS RDBMS Requirements CDS Database System
  1. Compatible with SQL
  2. OS independent
  3. Secure
  4. Import/Export flat ASCII files
  5. Handle over 1 million observations (over 3 year life)
  1. Yes, relational database but requires translation (PERL/C)
  2. Yes, Unix/Linux, Windows (95/98/2000...)
  3. Yes, can run on a secure server and password/write protected
  4. Yes, CDS remote planning is handled this way
  5. CDS catalog currently has over 100,000 records
   
EIS Interface Requirements CDS Catalog System
Administrator Interface
  1. Allow automatic updates from planning tool
  2. Allow manual editing
  3. Distinguish between planned and asrun
  4. Import/Export flat ASCII files
  5. Rigorous error checking and logging
  1. Automatic updating during FITS file generation
  2. Command and widget-based DB editing tools exist
  3. Planned and asrun entries kept in separate databases
  4. Import/Export files not actually used (done on the fly)
  5. Error checking performed (study/raster validity, modes, etc)
User Interface
  1. IDL GUI
  2. Allow user query, searching, and browsing
  3. Read, extract, & load FITS files
  4. Provide access to QL software
  5. Interface with other instrument catalogs
  1. IDL GUI exists - XCAT
  2. User query, searching, and browsing performed via point & click or text entry
  3. Linked to CDS file system for access to FITS files
  4. Linked to IDL QL software
  5. Interface with other instrument catalogs not implemented


Some additional info about CDS (aka, UIT) database system: