Previous slide	Up to slide index	Next slide

---

1. Accessibility

2. Data types
   

3. Miscellaneous considerations
   • OO
     We as a group do not clearly understand the requirements made by OO databases. GEANT 4.x might actually impose an OODB on the users. The GEANT folks' policy is to go with the OODB (but it will definitely be an OODB) which RD45 ensorses. So we might be in this business if we want to or not.
     Since ONCS will produce oo products, ONCS strongly prefers that their data reside in an OODB.
     Most of our data types do not require a specific data base type. Products that offer a mix of types are particularly attractive.

   • hardware
     Database products and tools should be available on a variety of platforms Currently, these would be the Unix platforms supported by Phenix (HP, SUN, SGI, IBM). , but it is likely that other platforms and operating systems will join this list in the future. A special problem is posed by data currently residing on non-supported platforms (PCs, Macs). [WHAT TO DO ABOUT THIS?]

   • timing
     This is the timing of the data base acquisition. It appears that the greatest needs at this moment is in the area of documntation, and in the area of construction and QA data being collected.
     Next will be ONCS and offline, who will need to integrate the data base into their products.
     Large volume calibrations will arrive last.

   • coordination
     Coordination with STAR and RHIC is essential.

   • manpower
     Who will maintain the database and provide access applications for users? What group supports the DB? -- Should there be a DB manager?

   • reliability for critical applications
     ONCS must have data base services available at all times. Mechanism should be available to ensure that ONCS can have access to its domain at any time. This might include mechanisms for prioritizing data base requests.

---