Database Schema

A content reuse widget was here but the content was missing. The reused content is Media_Repository/Primo/Primo_VE_Doc_Note

Return to menu

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.

Primo Database Tables
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_C_TABLE_OF_TABLES—contains metadata information for the C_C_MAPPING_TABLES and C_C_CODE_TABLES tables.
  • C_C_CODE_COLUMN_NAMES—contains metadata information on each column for the C_C_MAPPING_TABLES and C_C_CODE_TABLES tables.
  • C_C_MAPPING_TABLES—contains the records of the generic tables (each table has six columns).
  • C_C_CODE_TABLES—contains the records of code tables (for internalization support).

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_I_INSTITUTION

  • C_I_INSTITUTION_IP

  • C_I_LIBRARY

  • C_I_RESTRICTION

C_N Tables

Normalization Configuration Tables. Tables that contain global normalization rules for the publishing process.

  • C_N_BASIC_ROUTINES

  • C_N_ENRICHMENT

  • C_N_ENRICHMENT_MAPPING

  • C_N_ENRICHMENT_SET

  • C_N_MAPPING_SET

  • C_N_MAPPING_SOURCE

  • C_N_MAPPING_TARGET

  • C_N_MAPPING_TRANSFORMATION

  • C_N_SCOPES

  • C_N_SOURCE_CONDITION

  • C_N_TRANSFORMATION_GROUP

  • C_N_DATA_SOURCE

  • C_N_PROCESS_CONFIGURATION

C_V Tables

Viewing Configuration Tables. Tables that contain end user viewing information.

  • C_V_LAYOUT_SET

  • C_V_LAYOUT_SET_PAGES

  • C_V_PAGES

  • C_V_PAGE_TILES

  • C_V_SCOPES

  • C_V_SCOPE_VALUES

  • C_V_TABS

  • C_V_TAB_SCOPE

  • C_V_TILES

  • C_V_VIEWS

  • C_V_VIEW_LAYOUT_SET

  • C_V_VIEW_TILE_CONFIG

M_P Tables

Pipe Monitoring Configuration Tables. Tables that contain pipe monitoring information.

  • M_P_BULK_CONTEXT

  • M_P_FAILED_RECORDS

  • M_P_PROCESS_CONTEXT

  • M_P_WORK

  • M_P_PROC_EXE

R Tables

Parameters Configuration Tables. Tables that contain user parameters.

  • R_ROLE

  • R_STAFF

  • R_STAFF_ROLE_MAPPING

S Tables

Statistics Configuration Tables. Tables that contain accumulated system statistics. The Primo reporting system uses these tables as its data source.

  • S_CLICK_SUMMARIES

  • S_SEARCH_SUMMARIES

U Tables

User Configuration Tables. Tables that contain end user customization and personal parameters.

  • U_BASKET—contains the electronic basket.

  • U_PREFERENCE—contains user preferences.

  • U_RSS—contains RSS information.

  • U_SAVED_SEARCH—contains user-saved searches.

P Tables

PNX Configuration Tables. PNX-related tables.

  • P_PNX—contains all the PNX records. For a full description of this table, refer to P_PNX Table.

  • P_PNX_EXTENSION—contains additional information on PNX records, where required. For example, tags, reviews, and syndetics (an external knowledge base that holds extra information about the record, for example, the TOC of a book).

  • P_SOURCE_RECORD—contains original source records for renormalization, if required.

  • P_DEDUP_VECTOR—contains information to support the dedup process.

  • P_FRBR_KEYS—contains information to support the FRBR process.

  • P_FRBR_MATCHES—temporary table for use during FRBR processing.

  • P_DEDUP_COMPONENT

  • P_PNX_CLICK

  • P_PNX_XREF

  • P_RPNX

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.

P_PNX Table Fields
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.

PERSISTCONTROL

The current processing stage of the record. Possible values:

  • 1 – NEW_STATUS – A new record has been added to the system.
  • 2 – UPDATED_STATUS – An existing record has been updated at least once.
  • 3 – AFTER_DEDUPED_STATUS – A record has been added to a dedup group and assigned a MATCHID. Single records that are not added to a dedup group are also assigned this status during this stage.
  • 4 – AFTER_DEDUPED_MERGE_STATUS – A dedup record has been added to a merged record. Single records that are not part of a merged group are also assigned this status after completing this stage.
  • 5 – AFTER_FRBR_STATUS – A record has been added to a FRBR group and assigned a GROUPID. Single records that are not added to a FRBR group are also assigned this status during this stage.
  • 6 – AFTER_FRBR_MERGE_STATUS – A FRBR record has been added to a merged record. Single records that are not part of a merged group are also assigned this status after completing this stage
  • 7 – DELETED_STATUS – A record has been logically deleted.

SECONTROL

The current indexing status. Possible values:

  • 1 – SE_CONTROL_NEW_STATUS – A new record has been indexed.
  • 2 – SE_CONTROL_UPDATED_STATUS – An existing record has been indexed.
  • 3 – SE_CONTROL_DELETED_STATUS – A record's indexing has been removed from the SE.

The following values are applied to dedup records, which are not indexed:

  • 101 – INTERNAL_SE_CONTROL_NEW_STATUS – A new dedup record has been processed, but not indexed.
  • 102 – INTERNAL_SE_CONTROL_UPDATED_STATUS – An existing dedup record has been processed, but not indexed.
  • 103 – INTERNAL_SE_CONTROL_DELETED_STATUS – A dedup record has been removed from the SE.

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:

  • 1 - REGULAR_TYPE
  • 2 - DEDUP_MEMBER_TYPE
  • 3 - DEDUP_SINGLE_TYPE
  • 4 - DEDUP_MERGE_TYPE
  • 5 - FRBR_MEMBER_TYPE
  • 6 - FRBR_SINGLE_TYPE
  • 7 - FRBR_MERGE_TYPE

EXTENSION_EXISTS

Indicates whether an extension exists.

PUBLISHING_WORK_ID

Pipe ID.