HOME
UP
The CERA-2 Software Name Structure of Tables and Views
Numbers of tables and their names in CERA-2 Base and in the PIK's Loading Layer
CERA Core + Module DATA_ACCESS (other modules are not included).
CAPITALS refer to the actual table names, lower case to example names.
| CERA Base | Loading Layer |
|---|
| tables | views | tables | views |
| Entities | List of Values | 22+1 lov | - | 23 NEW_lov | 23 BOTH_lov |
| like LOV | 3+1 entity | 3+0 entit | 4 NEW_entity | 4 BOTH_entit |
| other | 6+2 | 1+0 GET_ENTRY | 1 LOAD_ENTRY | - |
| Relations | 11+0 relation | 11+1 GET_relat | 8 LOAD_relat | - |
Sum (tables/views): CERA Base: 46/16, CERA Loading Layer: 36/27, all in all: 125.
Description of the names
- entit:
For tables Citation, Institute, and Person views (Citat, Insti, Perso) have been created.
They offer among others an attribute (c_name, i_name, p_name) which combines the most important
attributes of the parent tables (e.g., p_name concatenates last_name, first_name, and institute
from Person). This can be used in pull down menues.
Names are shortened to 5 letters.
- GET_relat, GET_ENTRY:
These views simply join the information from tables related to the relation tables of CERA.
Sometimes inner, sometimes outer joins are used - sorry.
GET_ENTRY joins some tables to the CERA Entry table.
Names are shortened to 9 letters.
- GETF_relat, GETF_ENTRY:
... do exactly the same as GET_relat and GET_ENTRY - just they are used for foreign access,
i.e., they only select data, where the Access_Constraint is unrestricted.
Names are shortened to 10 letters.
- LOAD_relat, LOAD_ENTRY:
Every input to CERA is held in the loading layer for checking, before it is transferred
to the CERA tables.
So for most relations and most of their accompanying data LOAD_relat holds the information
in the meantime. Practically, the relations mostly correspond to the CERA Blocks.
Names are shortened to 10 letters.
- NEW_lov, NEW_entity:
Every input to CERA is held in the loading layer for checking, before it is transferred
to the CERA tables.
So for all LOV and some other Entities (Citation, Institute, Person, and STORAGE)
the tables have doubles in the loading layer, to catch the new input data before
checking and transferring them.
- BOTH_lov:
BOTH_lov unifies the lov from CERA Base with NEW_lov from the loading layer.
- BOTH_entit:
BOTH_entit has the same structure as entit, but unifies entity and NEW_entity.
Names are shortened to 10 letters.
Additionally, the following views for convenience belong to the CERA Base
- Views, belonging to CERA Block Contact. They select certain contact information
from the bulk of all Contact records, joining it with Person and Institute
information.
- COPYRIGHT_CON
- DISTRIBUTOR
- INHOUSE_CON
- INVESTIGATOR
- METADATA_CON
- ORIGINATOR
- OWNER
- TECHNICAL_CON
- Views, belonging to CERA Block Coverage. They join and layout the information
connected to the Spatial_Coverage and Temporal_Coverage tables.
Pages are optimized for NETSCAPE.
For comments and suggestions contact CERA Admin.
Last change: Tue Jul 26 12:53:54 NFT 2000