Members of the task force:

Hubert van Hecke
Marzia Rosati
Edmond Desmond
Kenta Shigaki
Martin Purschke
Thomas K. Shea
Soren Sorenson (honorary member)

Complete addresses are in this address list, and just the email addresses here.

The job is defined by the charter:

The purpose of the database Task Force is to define the requirements for the ancillary data storage system for PHENIX. This includes all data to be stored electronically excepting the raw data stream from the particle detectors. The requirement should be defined as completely as is reasonable at this time. It is not the purpose of the present effort to define the database system itself or write a specification for such. However, the report of the Task Force will form the basis from which a specification will be written and products chosen that will serve PHENIX for the foreseeable future. It is expected that specification-writing and product selection will be done by experts in database technology. The Task Force should deliver its findings to Project Management in written form by the November, 1996 Collaboration meeting. The requirements should reflect the needs of all aspects of PHENIX, including all detector sub-system groups, service groups including ONCS, On-line, Off-line, Simulation, and Project Management, as well as individuals and groups who will analyze PHENIX data. Each requirement for data to be stored should be described, including the data type, estimated quantity (the size of the data set), the group(s) generating and requiring the data, entry and access requirements, and any relationships to other data sets. Correlations between similar data requirements should be noted, but full analysis of this aspect will be done while generation the database specification. Particular attention should be paid to required methods for entry and access. This aspect of the requirements will be important in choosing technologies. Methods for finding and retrieving information, from what platforms, and locations, and with what tools or interfaces should be discussed. So should requirements for hardware interfaces such as bar-code readers, portable workstations on factory floors etc. Just as important are requirements for automated access by various software in the areas of On-line, Off-line, and Simulation.

Subsystems to be addressed are:

The first 11 were taken from the alignment task force list, and are hardware systems; The last 6 are other project components that also need to keep databases on data, (simulated) run conditions, file inventories and documents.

Are any missing?

Each subsystem needs to have one of our names assigned to it.

Questionnaire

I tried to convert the charter into a questionnaire. You can use this for guidance in the first round of collecting information.

Archive of correspondence, files, etcetera:

Slides of Huberts talk to the DC during the Nov '96 Phenix week at BNL

---

to the phenix home page

---

corrections, additions, comments to hubert@lanl.gov