RPT00 Views
This section describes each of the views that belong to the RPT00 schema.
PNX-Related Information
This section describes the views that display information that is associated with the PNX data.
PNX View
This view contains the PNX records that are harvested into Primo for local search. PNX records that are stored from remote search sources are accessed via the PNX_REMOTE view. Various extensions to the PNX record are stored externally to the PNX table, including tags, reviews, various types of full text and calculated popularity. These records are associated with the PNX record via the PNX record ID.
Column Name | Type | Index | Description |
---|---|---|---|
PNX_ID
|
NUMBER
|
Yes
|
The Unique ID of the row
|
MATCH_ID
|
NUMBER
|
Yes
|
The ID that uniquely identifies deduplication groups
|
GROUP_ID
|
NUMBER
|
Yes
|
The ID that uniquely identifies FRBR groups
|
SECONTROL
|
NUMBER
|
Yes
|
The Primo Publishing Platform status
|
SECONTROL_DESC
|
VARCHAR2
|
The Primo Publishing Platform status description:
|
|
TYPE
|
NUMBER
|
Yes
|
Type of record
|
TYPE_DESC
|
VARCHAR2
|
The Type description:
|
|
RECORD_ID
|
VARCHAR2
|
Yes
|
The Unique Primo Record ID
|
PIPE_NAME
|
VARCHAR2
|
The name of Pipe that is used to harvest the record
|
|
PUBLISHING_
WORK_ID |
NUMBER
|
Yes
|
The ID of the Pipe instance used to harvest the record
|
DATA_SOURCE_
CODE |
VARCHAR2
|
Yes
|
The Code that uniquely identifies the data source from which the record was harvested
|
SOURCE_ID
|
VARCHAR2
|
The unique ID of the record in the source system
|
|
EXTENSION_
EXISTS |
NUMBER
|
The PNX Extensions exist for this record
|
|
PNX
|
CLOB
|
The PNX XML
|
|
CREATION_DATE
|
DATE
|
The Date that the record was stored in the DB
|
|
UPDATED_DATE
|
DATE
|
The date of the last update
|
|
UPDATED_BY
|
VARCHAR2
|
The user who performed the last update
|
PNX_REMOTE View
This view displays the PNX remote search records that Primo stores. Primo only stores remote search records that are saved to e-Shelf, or records that are needed for long-term reference for some other reason.
Column Name | Type | Index | Description |
---|---|---|---|
PNX_ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
SECONTROL
|
NUMBER
|
Yes
|
The Primo Publishing Platform status
|
SECONTROL_DESC
|
VARCHAR2
|
The Primo Publishing Platform status description:
|
|
RECORD_ID
|
VARCHAR2
|
Yes
|
The unique Primo Record ID
|
EXTENSION_EXISTS
|
NUMBER
|
The PNX Extensions exist for this record
|
|
PNX
|
CLOB
|
The PNX XML
|
|
CREATION_DATE
|
DATE
|
The date that the record was stored in the DB
|
|
UPDATED_DATE
|
DATE
|
The date of the last update
|
|
UPDATED_BY
|
VARCHAR2
|
The user who performed the last update
|
PNX_TAGS View
This view displays the Tags that are associated with PNX records.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
RECORD_ID
|
VARCHAR2
|
Yes
|
The unique Primo Record ID
|
USER_ID
|
VARCHAR2
|
The ID of the user that added the Tag
|
|
STATUS
|
NUMBER
|
The status of the extension record
|
|
STATUS_DESC
|
VARCHAR2
|
The status description:
|
|
TAG
|
VARCHAR2
|
The tag text
|
|
CREATION_DATE
|
DATE
|
The date that the record was stored in the DB
|
|
UPDATED_DATE
|
DATE
|
The date of the last update
|
|
UPDATED_BY
|
VARCHAR2
|
The user who performed the last update
|
PNX_REVIEWS View
This view displays the reviews that are associated with PNX records.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
RECORD_ID
|
VARCHAR2
|
Yes
|
The unique Primo Record ID
|
USER_ID
|
VARCHAR2
|
The ID of the user that wrote the review
|
|
STATUS
|
NUMBER
|
The status of the extension record
|
|
REVIEW
|
CLOB
|
The text of the review
|
|
RATING
|
NUMBER
|
The rating of the review
|
|
CREATION_DATE
|
DATE
|
The date that the record was stored in the DB
|
|
UPDATED_DATE
|
DATE
|
The date of the last update
|
|
UPDATED_BY
|
VARCHAR2
|
The user who performed the last update
|
PNX_FULL_TEXT Views
This view displays the full-text information.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
RECORD_ID
|
VARCHAR2
|
Yes
|
The unique Primo Record ID.
|
FULL_TEXT_TYPE
|
VARCHAR2
|
The type of full-text:
TOC
ABSTRACT (or summary)
FICTION
FULL_TEXT—for future use
|
|
FULL_TEXT
|
CLOB
|
The text
|
|
CREATION_DATE
|
DATE
|
The date that the record was stored in the DB
|
|
UPDATED_DATE
|
DATE
|
The date of the last update
|
|
UPDATED_BY
|
VARCHAR2
|
The user who performed the last update
|
PNX_POPULARITY View
This view displays the popularity for a PNX record that Primo has calculated, based on various usage events that are included in the Full Display and Get It.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
Unique ID of the row
|
RECORD_ID
|
VARCHAR2
|
Yes
|
Unique Primo Record ID.
|
CALCULATED_POPULARITY
|
NUMBER
|
The popularity that was calculated by Primo.
This data is used by the Sort by Popularity option. The popularity rank is a total of the number of times a record was clicked, multiplied by the popularity boost for the type of click. Three types of clicks are counted: e-Shelf, Full display, and GetIt!.
The boosts are defined in the Popularity Sort Boosts mapping table in the Publishing subsystem.
|
|
CREATION_DATE
|
DATE
|
The date that the record was stored in the DB
|
|
UPDATED_DATE
|
DATE
|
The date of the last update
|
|
UPDATED_BY
|
VARCHAR2
|
The user who performed the last update
|
Search-Related Information
SEARCH_PROBLEMS View
This view displays logging of search related problems.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
Unique ID of the row
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The type of Event: Search Problem
|
PROBLEM_DESC
|
VARCHAR2
|
The description of the problem
|
|
'IP
|
VARCHAR2
|
The IP of the computer from which the search request originated
|
|
HOST_NAME
|
VARCHAR2
|
The server name running the search request
|
|
VIEW
|
VARCHAR2
|
The Primo View in which the Event occurred
|
|
INSTITUTION
|
VARCHAR2
|
The active user Institution at the time of the Event
|
|
ON_CAMPUS
|
VARCHAR2
|
The location of the user at the time of the Event (true/false)
|
|
USER_GROUP
|
VARCHAR2
|
The User Group of the user as returned by PDS
|
SEARCH_STATISTICS View
This view displays Search statistics information.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
SCOPE_NAME
|
VARCHAR2
|
The name of the Primo Scope of the request
|
|
SCOPE_TYPE
|
VARCHAR2
|
The Type: Local/Remote
|
|
SEARCH_COUNT
|
NUMBER
|
The number of searches in the monitored period.
This period is determined by the following parameters:
These parameters are set in Advanced Configuration > General Configuration > Statistics page in the Back Office. Primo uses the first limit that is reached.
|
|
AVERAGE_RESULTS
|
NUMBER
|
The average number of records in the result set
|
|
AVERAGE_SEARCH_
TIME_MILLISEC |
NUMBER
|
The average elapsed time for the search.
|
|
AVERAGE_FULL_
TIME_MILLISEC |
NUMBER
|
The average total elapsed time required to process the search request, including the search response time.
|
|
SOURCE_VIEW
|
VARCHAR2
|
The Primo view in which the search was done
|
|
INSTITUTION
|
VARCHAR2
|
The active user institution
|
|
ON_CAMPUS
|
VARCHAR2
|
The location of the user at the time of the search (true/false)
|
|
USER_GROUP
|
VARCHAR2
|
The User Group of the user as returned by PDS
|
|
CREATION_DATE
|
DATE
|
Yes
|
The date that the record was stored in the DB
|
SEARCH_STRINGS View
This view displays Search strings information.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
SEARCH_STRING
|
VARCHAR2
|
The search string
|
|
SCOPE_NAME
|
VARCHAR2
|
The name of the Primo Scope of the request
|
|
SCOPE_TYPE
|
VARCHAR2
|
The Scope Type:
|
|
SEARCH_COUNT
|
NUMBER
|
The number of searches in the monitored period.
This period is determined by the following parameters:
These parameters are set in the Advanced Configuration > General Configuration > Statistics page in the Back Office. Primo uses the first limit that is reached.
|
|
AVERAGE_RESULTS
|
NUMBER
|
The average number of rows in the result set
|
|
AVERAGE_SEARCH_
TIME_MILLISEC |
NUMBER
|
The average elapsed time for search portion only of handling the search requests
|
|
AVERAGE_FULL_
TIME_MILLISEC |
NUMBER
|
The average total elapsed time need to handle the search requests
|
|
VIEW
|
VARCHAR2
|
The Primo View in which the Event occurred
|
|
INSTITUTION
|
VARCHAR2
|
The active user Institution at the time of the Event
|
|
ON_CAMPUS
|
VARCHAR2
|
The location of the user at the time of the Event (true/false)
|
|
USER_GROUP
|
VARCHAR2
|
The User Group of the user as returned by PDS
|
|
CREATION_DATE
|
DATE
|
Yes
|
The date that the record was stored in the DB
|
User-Related UI Usage Events
CLICK_EVENTS View
This view displays click events, which contain accumulative usage information that pertains to UI actions that end users perform. Among the UI events tracked are Add Tags, Add a review, Add to e-Shelf, Advanced Search, and so forth.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the statistics were stored
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The type of Event: Search Problem
|
CLICK_VALUE
|
VARCHAR2
|
In some cases there is additional information:
|
|
CLICK_COUNT
|
NUMBER
|
In Primo Version 1, the system creates a single entry in the table for all events of the same type that occur per hour. For Primo Version 2 and later releases, the system creates a separate entry for every event.
|
|
VIEW
|
VARCHAR2
|
The Primo View in which the event occurred
|
|
INSTITUTION
|
VARCHAR2
|
The active user Institution at the time of the event
|
|
ON_CAMPUS
|
VARCHAR2
|
The location of the user at the time of the event (true/false)
|
|
USER_GROUP
|
VARCHAR2
|
The User Group of the user as returned by PDS
|
System Monitoring Events
Primo schedules all system-monitoring events every 15 minutes.
FILE_SYSTEM_EVENTS View
This view contains monitoring information related to the space allocated to files system of monitored servers. The values are calculated using the df -k command output.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The Type of Event: File System
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource that is being monitored: Server
|
|
SEVER_NAME
|
VARCHAR2
|
The name of the server
|
|
MOUNT_POINT
|
VARCHAR2
|
The mount point that is being monitored. The following message may display for old data in this column:
File System Name
|
|
USED_PCT
|
NUMBER
|
The percent of space used
|
|
USED_MB
|
NUMBER
|
The used space in MBs
|
|
TOTAL_MB
|
NUMBER
|
The total allocated space in MBs
|
ORACLE_INDEX_EVENTS View
This view contains monitoring information related to the validity of Oracle
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The type of Event: Indexes
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource that is being monitored: Oracle
|
|
ORACLE_
CONNECTION |
VARCHAR2
|
The Oracle connection that is being monitored
|
|
INDEX_NAME
|
VARCHAR2
|
The Index name. If there are no invalid indexes, the following message displays:
No Invalid Indexes
|
|
INDEX_STATUS
|
VARCHAR2
|
The status: Valid/Invalid
|
ORACLE_TABLESPACE_EVENTS View
This view contains monitoring information related to the space allocations of Oracle Table Spaces.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The type of Event: Indexes
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource being monitored: Oracle
|
|
ORACLE_
CONNECTION |
VARCHAR2
|
The Oracle connection monitored
|
|
TABLE_SPACE_NAME
|
VARCHAR2
|
The Table Space Name
|
|
FREE_PCT
|
NUMBER
|
The percent of free space
|
|
FREE_MB
|
NUMBER
|
The free space in MBs
|
|
TOTAL_MB
|
NUMBER
|
The total allocated space in MBs
|
ORACLE_FULL_TABLE_SCAN_EVENTS View
This view contains a log of SQL statements that performed full table scans.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The Type of Event: Indexes
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource being monitored: Oracle
|
|
ORACLE_
CONNECTION |
VARCHAR2
|
The Oracle connection monitored.
|
|
SQL_STATEMENT
|
VARCHAR2
|
The SQL_ID and the first 240 characters of the SQL text.
|
|
EXECUTION_COUNT
|
NUMBER
|
The execution count.
|
ORACLE_AVERAGES View
This view contains information concerning average execution of SQL statements.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row.
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored.
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The Type of Event: Indexes
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource being monitored: Oracle
|
|
ORACLE_
CONNECTION |
VARCHAR2
|
The Oracle connection monitored.
|
|
SQL_STATEMENT
|
VARCHAR2
|
The SQL_ID and the first 240 characters of the SQL text.
|
|
EXECUTION_COUNT
|
NUMBER
|
The execution count.
|
|
AVERAGE_
EXECUTION_ MILLISEC |
NUMBER
|
The average execution time in milliseconds.
|
SYSTEM_IOWAIT_EVENTS View
This view contains monitoring information related to the IO Waits of the servers being monitored. The IO Wait is captured using the UNIX sar command.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row.
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored.
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The Type of Event: Indexes
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource being monitored: Server
|
|
HOST_NAME
|
VARCHAR2
|
The name of the server that is being monitored.
|
|
IOWAIT_PCT
|
NUMBER
|
The IO Wait percent.
|
SYSTEM_LOAD_EVENTS View
Description: This view contains monitoring information related to the CPU Load of the servers being monitored. The load is captured using the UNIX uptime command.
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row.
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored.
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The Type of Event: Indexes
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource being monitored: Server
|
|
HOST_NAME
|
VARCHAR2
|
The name of the server that is being monitored.
|
|
LOAD
|
NUMBER
|
The load
|
SYSTEM_MEMORY_EVENTS View
This view contains monitoring information that is related to the Linux memory of the servers being monitored. Memory usage is captured by using the following UNIX commands:
-
Linux: free -lm
-
Solaris: vmstat and prtconf
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER
|
Yes
|
The unique ID of the row.
|
EVENT_DATE
|
DATE
|
Yes
|
The date that the monitored information was stored.
|
EVENT_TYPE
|
VARCHAR2
|
Yes
|
The Type of Event: Indexes
|
RESOURCE_TYPE
|
VARCHAR2
|
The resource being monitored: Server
|
|
HOST_NAME
|
VARCHAR2
|
The name of server that is being monitored.
|
|
FREE_MB
|
NUMBER
|
The free memory in MBs.
|
|
USED_MB
|
NUMBER
|
The used memory in MBs.
|
|
TOTAL_MB
|
NUMBER
|
The total allocated memory in MBs.
|
PRIMO_BO_AUDIT_TABLE View
This view allows you to generate reports regarding database activity in the Back Office. The following table lists the valid columns:
Column Name | Type | Index | Description |
---|---|---|---|
ID
|
NUMBER(15)
|
Yes
|
The ID of the record that has been modified.
|
SCHEMA_NAME
|
VARCHAR2(11)
|
Yes
|
The name of the schema.
|
TABLE_NAME
|
VARCHAR2(30)
|
Yes
|
The name of the table has been updated.
|
ACTION
|
VARCHAR2(10)
|
The action taken on the table (insert, update, or delete).
|
|
MODIFICATION_DATE
|
DATE
|
The date the change was made.
|
|
MODIFIED_BY
|
VARCHAR2(255)
|
The name of the staff user that made the change to the record.
|
|
ROLE
|
VARCHAR2(255)
|
The role of the staff user that made the change to the record.
|
|
INSTITUTION_CODE
|
VARCHAR2(255)
|
The institution code.
|
|
INSTITUTION_NAME
|
VARCHAR2(255)
|
The institution name.
|
|
AUDITED_FIELDS
|
VARCHAR2(4000)
|
The fields that have been modified. For insert and delete actions, all of the records fields are written. For update actions, only the changed fields are written.
For example:
ID=4800001;TABLE_OF_TABLE_ID=2105416;MAPPING_TABLE_NAME=Datasource Index Extensions;SOURCE_CODE_1=marc_exchange;TARGET_CODE=Index If Exists;ENABLED=1;CREATION_DATE=06-APR-10;UPDATED_DATE=06-APR-10;UPDATED_BY=Admin
|
The following table lists the tables that are audited for each menu:
Menu | DB Table Name |
---|---|
Monitor Primo Status:
|
|
Pipe Monitoring
|
RT_PIPE_CONFIGURATION
|
Scheduler:
|
|
RT_SCHEDULE
|
|
Ongoing Configuration Wizards:
|
|
Institution Wizard
|
C_I_INSTITUTION
C_I_INSTITUTION_IP
C_I_LIBRARY
|
Ongoing Configuration Wizards > Pipe Configuration Wizard:
|
|
Data Sources Configuration
|
C_N_DATA_SOURCE
|
Scope Values Configuration
|
C_N_SCOPES
|
Normalization Rules Set
|
C_N_MAPPING_TARGET
C_N_MAPPING_TRANSFORMATION
C_N_MAPPING_SOURCE
C_N_SOURCE_CONDITION
C_N_MAPPING_SET
|
Enrichments Sets Configuration
|
C_N_ENRICHMENT_MAPPING
C_N_ENRICHMENT_SET
|
Ongoing Configuration Wizards > Restrictions and Delivery Configuration Wizard:
|
|
Search Scopes
|
C_I_RESTRICTION
|
Ongoing Configuration Wizards > Views Wizard:
|
|
Views List
|
C_V_VIEWS
C_V_LAYOUT_SET
C_V_LAYOUT_SET_PAGES
C_V_PAGES
C_V_PAGE_TILES
C_V_TABS
C_V_TAB_SCOPE
C_V_UICOMPONENTS
C_V_VIEW_LAYOUT_SET
C_V_VIEW_TILE_CONFIG
|
View Scopes
|
C_V_SCOPES
|
View Scope Values
|
C_V_SCOPE_VALUES
|
Tiles
|
C_V_TILES
|
Ongoing Configuration Wizards > Staff Configuration Wizard:
|
|
R_STAFF
|
|
Advanced Configuration:
|
|
General Configuration Wizard
|
C_G_CONFIGURATION
|
All Code Tables
|
C_C_CODE_TABLES
C_C_TABLE_OF_TABLES
C_C_CODE_COLUMN_NAMES
|
All Mapping Tables
|
C_C_MAPPING_TABLES
C_C_TABLE_OF_TABLES
C_C_CODE_COLUMN_NAMES
|