This is a template that can be used to collect first-round information about the data base requirements. Let me know if I missed something. Remember that we are covering detector-type collaborators, who are primarily thinking calibrations, as well as management-type colleagues, who are primarily thinking documents, so not all categories may be appropriate to your subsystem. 1 - WHAT KINDS OF DATA AND WHAT DATA VOLUMES ARE PRODUCED? ---------------------------------------------------------- For each type of data, please note its format, if it is produced/collected by small standalone systems ... 1.1 - ONE-TIME DATA ------------------- This would be for example data collected during contruction of a detector. - Detector component characterizations, identification, history ... - Detector mechanical data. Geometry, surveys, wire tensions ... - other? 1.2 - RUN-TIME DATA -------------------- These would be data that are produced on a regular basis once we are running. - Data returned from slow controls: temperatures, voltages ... - Data produced by calibration programs - Component swap/repair/replacement histories - other? 1.3 - DOCUMENTATION ------------------- - Writeups, technical drawings, minutes, photos ... - other? 2 - ACCESS ---------- This is more difficult to define, but also more important in that the requirements and wishes expressed here will drive decisions on what the actual implementations will be. Imagine an ideal situation, where we could dream up the nicest software tools and interfaces. If we get lucky, those things may already be out there... 2.1 - INPUT ----------- How are the data generated, and how would you like to see - from a users point of view - the data transported to the 'central' data base. - are they/will they be in some existing data base program? If so, which? - if they are/will be in some other computer form, what is it? Machine type, software application, format .... - do you want your program/application to write directly into the data bases? - other? 2.1 - OUTPUT ------------ How would you like to access this information. In the ideal world, what would the user interfaces look and feel like? Some of you might have good/bad experiences from previous experiments - lets hear them. - organization, searchability ... - graphing, manipulation, display ... - direct access from analysis programs - for documents: searching by title/keywords/content/date/author .... - are all documents accessible from the web? - other?