Some Data Base Issues  (tks)
____________________________________________________________________

- Electronic Documentation currently planned to be done in View Logic must be
  available to On-Line and Off-Line, and probably Simulation. (see "Duplication
  of Data" below)
 
- Should drawings and pictures should be kept in the structured database or
  simply cataloged there.
 
- Can the on-line and off-line systems rely on a database server external to
  PHENIX control?

- Cost
  - Oricale is "free" (or is it? What is the real cost?)
  - How much would an OO DB cost?  - is it worth it?
   
- Performance
  - Can any commercial product, OO or otherwise, keep up with the ancillary
    data flow during running?
 
- Manpower
  - Who will maintain the database and provide access applications for users?
  - What group supports the DB? -- Should there be a DB manager? 

- Integration of independent sub-system data with the central data 
  - What goes in the central DB? - What stays independent
  - How does PHENIX determine this?

- Organization of Data
  - What are requirements of various groups for different organizations of the
    data, both at entry and retrieval? 
 
- OO or Not
  - We as a group do not understand the requirements made by OO databases
  - Is there a specific requirement for the On-Line system to use an OODB
  - Generally people in PHENIX do not understand what OO databases are,  	how to
      use them or what there advantages are.
  - Can a single OODB be used to support all scientific requirements?
  - What about administrative requirements? 
  - If not what about the duplication problem?
  - Can an OODB present data organized for different needs?
  - Relational databases do not deal with floating point numbers.

- Duplication of Data
  - Should the on line system depend on a separate DB server?
  - On-Line, Off-Line and Simulation will need access to consistent data sets.
    - At BNL and at PHENIX CC in Japan 
    - At various institutions
  - Is configuration data stored in ViewLogic duplicated in the DB.
  - What goes in the data stream and what in the DB.  How to control
    divergence of any common information.

__________________________________________________________________________

CATEGORIES OF DATA 
This list is organized by where and when the data in generated.

Sub-system Construction
	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
	Calibration constants
	Wiring and cabling & piping
	FPGA codes and the like

Running
	Survey and Alignment
	Trigger configuration
	Partitioning configuration
	Ancillary data from runs
	Calibration history	

Administrative
	Names & Addresses
	Indices of Notes and Papers