| mechtype |
| Base Entity | eventprefmec |
| Attribute Name | mechtype |
| Logical Rolename | |
| ColumnName | mechtype |
| RoleName | |
| Definition | Mechanism type |
| Note | Range: mechtype = {FP | MT}
FP = Fault plane solution
MT = Moment tensor |
| evid |
| Base Entity | eventprefmec |
| Attribute Name | evid |
| Logical Rolename | |
| ColumnName | evid |
| RoleName | |
| Definition | Event identifier. Each event is assigned a unique integer which identifies it in a database. It is possible for several records in the Origin relation to have the same evid. This indicates there are several opinions about the location of the event. The evid does not have to be identical to the local network’s event identifier, which is stored in the Origin table. This allows merging data for a single event from multiple sources without insisting that database evid is identical to the source’s local event identifier |
| Note | Range: evid > 0 |
| mecid |
| Base Entity | eventprefmec |
| Attribute Name | mecid |
| Logical Rolename | |
| ColumnName | mecid |
| RoleName | |
| Definition | Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database |
| Note | Range: mecid > 0 |
| lddate |
| Base Entity | eventprefmec |
| Attribute Name | lddate |
| Logical Rolename | |
| ColumnName | lddate |
| RoleName | |
| Definition | Load date. Date and time that the record was created, in Oracle date datatype |
| Note | Range: Any valid date between January 01, 4712 BC and January 01, 4712 AD Units: YYYY/MM/DD HH24:MI:SS |