Database Schema
The Primo database consists of many tables used to store data, system information, process states, and more.
The following is a list of the table types in the Primo database. The prefix of each table describes its major function.
Schema | Description | Tables |
---|---|---|
C_C Tables
|
Common Configuration Tables. Tables with common fields are grouped together into a single table to improve processing speed. One of the fields of a common table is the name of the table to which each record belongs. This group of tables contains configuration data for these common tables and all the records of the tables.
|
|
C_G Tables
|
Global Configuration Tables. Tables that contain global system configuration parameters.
|
C_G_CONFIGURATION—contains global system configuration parameters. |
C_I Tables
|
Institution Configuration Tables. Tables that contain configuration parameters concerning the institution providing bibliographical services.
|
|
C_N Tables
|
Normalization Configuration Tables. Tables that contain global normalization rules for the publishing process.
|
|
C_V Tables
|
Viewing Configuration Tables. Tables that contain end user viewing information.
|
|
M_P Tables
|
Pipe Monitoring Configuration Tables. Tables that contain pipe monitoring information.
|
|
R Tables
|
Parameters Configuration Tables. Tables that contain user parameters.
|
|
S Tables
|
Statistics Configuration Tables. Tables that contain accumulated system statistics. The Primo reporting system uses these tables as its data source.
|
|
U Tables
|
User Configuration Tables. Tables that contain end user customization and personal parameters.
|
|
P Tables
|
PNX Configuration Tables. PNX-related tables.
|
|
All default data created by the Primo system is noted as updated by Primo.
P_PNX Table
The P_PNX table contains the Primo PNX records. The following table lists and describes the fields in the P_PNX table.
Field Name | Description |
---|---|
ID
|
The internal identification number of the record.
|
RECORDID
|
The source system record identification number of the record.
|
PART_1, PART_2,PART_3, PART_4, PART_5, STRING_CLOB
|
The PNX xml code of the record.
|
CREATION_DATE
|
The date on which the record was created in Primo.
|
UPDATED_DATE
|
The date on which the record was updated in Primo.
|
UPDATED_BY
|
The name of the user who ran the pipe that created the record.
|
MATCHID
|
The dedup match identification number of the record.
|
GROUPID
|
The FRBR match identification number of the record.
|
The current processing stage of the record. Possible values:
|
|
The current indexing status. Possible values:
The following values are applied to dedup records, which are not indexed:
|
|
PIPE_NAME
|
The name of the pipe from which the record was loaded.
|
PREVIOUS_TYPE
|
For dedup and dedup merge purposes.
|
SOURCE_ID
|
The name of the source from which the record was loaded.
|
DATA_SOURCE_CODE
|
The code name of the data source associated with the pipe.
|
BULK_ID
|
The name of the bulk from which the record was loaded.
|
TYPE
|
The type of the record. Possible values:
|
EXTENSION_EXISTS
|
Indicates whether an extension exists.
|
PUBLISHING_WORK_ID
|
Pipe ID.
|