- Request #149 (E. Yu): Add a new netmag.magtype of r
-----------------------

Add a new magtype = r, as a valid magnitude type. This magnitude is based on
the Ml magnitude but it has been adjusted to be closer to the Mw calculation.
The SCSN would like to apply this adjustment to Mls >=3, and would like to
distinguish them from the original Ml calculation by magtype.  

==> Request approved.
    This magnitude is a linear adjustment to Ml and will be labeled 'Mlr' (reduced).
    Caltech will implement the software changes.
    Jiggle & Trimag need to be updated. Possibly Ampgen, TMTS & Alarming.
    Constraints on Netmag, EventPrefMag & MagPrefPriority tables need to be updated.

==> Allan implemented the changes in Trimag & Jiggle.
    Currently, no amplitudes are associated with Mlr magnitudes; the ones associated
    with the Ml are used. Group suggests that the observables should be stored in the
    database as well.

==> Associations between amplitudes and Mlr are now stored in the DB.


- Request #150 (S. Zuzlewski): PDL product submission information
------------------------------

==> Request approved.
The following tables will be added to the AP schema:

- PDL_PRODUCT Table:

FIELD    TYPE    DEFINITION
-----------------------------------------------------------------------------
evid     NUMBER  Event Identifier
prodtype VARCHAR Product Type: origin, phase-data, moment-tensor,
                 focal-mechanism, nearby-cities, shakemap
dest     VARCHAR Destination: Recent_event_PDL, ComCat_PDL, dev-ComCat_PDL,
                 dev-Recent_event_PDL
source   VARCHAR Source: System that submitted the information
time     DATE    Time of Action
action   VARCHAR PDL action (called "status" in PDL docs): 
                 U (update) or D (delete)
dbsetid  NUMBER  Database Id's of main elements of the product: orid & magid
                 for Origin, Shakemap & Phase-data products; mecid for
                 Moment-tensor & Focal-mech products; orid for  
                 Nearby-cities product.
                 Foreign key to PDL_IDS.dbsetid
lddate   DATE    Load date
-----------------------------------------------------------------------------
Primary Key: (evid, prodtype, action, dest, time, source)

- PDL_IDS Table:

FIELD    TYPE    DEFINITION
-----------------------------------------------------------------------------
dbsetid  NUMBER  DB Set of Id's Identifier
tname    VARCHAR Table name: ORIGIN, NETMAG, MEC
id       NUMBER  Identifier Value
lddate   DATE    Load date
-----------------------------------------------------------------------------
Primary Key: (dbsetid, tname)

==> PL Implemented apps for the following products:
	- Origin
	- Phase data
	- Focal mechanism
	- Moment tensor


- Request #151 (S. Zuzlewski): Modify cosmos tables
------------------------------

In the cosmos schema, we currently use the sensor name as a primary key to find
out the VperG and MaxG values but since a given sensor can have multiple settings,
we have to overload the sensor names with that information, e.g.
"Episensor (4 g max 5.0 v/g)". This is definitely not ideal.

The same is also true for datalogger attributes (number of bits, full scale value).

The proposal we have is to specify those attributes on a per channel basis rather
than on a per equipment basis. It can be easily implemented by merging the tables
C_ChannelData, C_LoggerData & C_SensorData into one table. The resulting C_ChannelData
table would look like:

C_ChannelData:
  net         VARCHAR2(8)
  sta         VARCHAR2(6)
  seedchan    VARCHAR2(3)
  location    VARCHAR2(2)
  ondate      DATE
  offdate     DATE
  netId       NUMBER(5)
  lgrName     VARCHAR2(48)
* LGRID       NUMBER(5)
* LGRBITS     NUMBER(2)
* LGRFSV      NUMBER(5,2)
  snsName     VARCHAR2(48)
* SNSID       NUMBER(5)
* MAXG        NUMBER(6,4)
* VPERG       NUMBER(6,4)
  siteId      NUMBER(5)
  orntId      NUMBER(5)
  timeId      NUMBER(5)
  datumId     NUMBER(5)
  staVs30     NUMBER(5,2)
  staGeoId    NUMBER(15)
  chan_number NUMBER(3)
  description VARCHAR2(60)
  lddate      DATE
  ref_azi     FLOAT

==> Approved.