Refer to the summary table for estimates of data volumes by type. Although our data fall into broad classes as described in sections 2.1-2.7, data come in many forms. In order to preserve forward compatibility, there should be no limitation imposed by the data base on the data formats that can be stored.

• documents
  In this category fall writeups, copies of talks and slides, manuals, memos, lists of names and addresses and the like. In general, documents are envisioned to reside 'on the web'. We need a Phenix-specific search engine to locate info by header, keyword, content. Portions of this (e.g. project management docs) need to be able to be roped off to all but authorized readers.

• drawings
  These are CAD models, engineering drawings and the like. Since CAD files can only be viewed by experts with the appropriate expensive software, there is probably no need to have these generally accessible. However, they should be catalogued. Postscript files can be derived from CAD models, and we should consider having a fairly complete set of these available online. Engineering drawings come in a variety (?) of formats (PDF, ps..). In principle they can be stored for general access, but we might consider only storing in the data base a catalog of such drawings. Again, we should consider having postscript copies available online.

• photographs
  Some subsystems are taking (MUT) or plan to take (MVD) copious digital photographs during construction. They should be archived and organized in a way similar to 'documents', and linked to them.

• sub-system constuction data
  Inventory
  Component test results
  Internal wiring and cabling & piping
  QA & QC information
  

• integration - configuration and performance
  Description of geometry
  Nomenclature - Channel naming (numbering)
  Electronics configuration and mapping
  HV & LV to channel mapping
  Wiring and cabling & piping