1.- Schema change requests: #101 (P. Lombard): Change documentation of AssocArO.delta to specify units as Km, not degrees. ----------------------------------------------------------------- It appears that both SC and NC are assigning values to AssocArO.delta as if the units were Km, which are appropriate for local and regional quakes. Documentation should be consistent with usage. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Approved. ------------------------------------------------------------------------ #61 (P. Lombard): Units table: "spectral peak amplitude" is not a meaningful description. ----------------------------------------------------------------- The description of the unit labeled "spa" needs to specify the exact units; as it is now users have no idea if this is acceleration or velocity, let alone whether it is m/sec, %g, etc. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Discussed. Caltech tasked to find out what are the exact units. One option is to ask Hiroo Kanamori. ------------------------------------------------------------------------ #60 (P. Lombard): Units table: "integral of velocity squared" is not a meaningful description. ----------------------------------------------------------------- Several different length and time combinations could be used for "integral of velocity squared". Is the velocity in cm/sec, or m/sec? Is the integral with respect to time, or distance? ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Discussed. Caltech tasked to find out what are the exact units. One option is to ask Hiroo Kanamori. ------------------------------------------------------------------------ #112 (E. Yu): Move stacorrections from parametric schema to application schema. ----------------------------------------------------------------- I am not sure if stacorrections is properly categorized as part of the parametric schema. All other tables in the schema describe seismic event parameters are are "computed" values. This table holds information used to compute these values. ----------------------------------------------------------------- ------------------------------------------------------------------------ ==> Approved. ------------------------------------------------------------------------ 2.- Possible use of svn for tracking schema related documentation: * DDL scripts (SQL): a) Schema creation (PI,WF,HT,IR,SIS): - Should we just store the logical model of the schemas? NC & SC physical models are different. b) Alternate tables (RT, post processing): - Does SC already store them in svn? - NC should do the same (ChannelMap, AssocWfRc, ...). c) Views: - NC & SC have different versions of some views (md_magparms_view, ...). d) Packages: - Does SC already store them in svn? - Berkeley should do the same (Truetime, ...). * ER/Studio files (HTML). ------------------------------------------------------------------------ 2008/03/21 We decided in a 1st pass to store only the logical views of the DDL scripts. Ellen volunteered to come up with a draft for the SVN structure. 2008/04/25 Ellen came up with a strawman for the repository structure. ----------------------------------------------------------------- I just spoke with Rae Yip concerning using SVN to store the database creation scripts. Rae tells me that the scope of this SVN repository is to store source code and not site-specific configurations. So it seems that we would only check scripts concerning relational properties (and not physical or table properties) into this repository. Here is a strawman for these scripts. Current SVN repository structure for database scripts: DB ->trunk ->branches (there is a leap second dev branch - currently only storedprocedures is under this branch) Under "->trunk" ->storedprocedures ->tables ->types ->views ->snapshots Other scripts that are site-specific: 1. sequences 2. users 3. grants 4. table site-specific storage parameters ----------------------------------------------------------------- ------------------------------------------------------------------------