Voyager Data Dictionary through Version V9.1.

1
Including Tricks for Using the Voyager Tables in Queries
June 1, 2015

This document is designed to be your first stop when you are looking for something in the Voyager tables.
Since it lists all the tables and fields, you might be able to locate what you want by searching the document
in Word or another text editor.

This document also serves as an index to the Voyager class diagrams (formerly called Entity-Relationship
diagrams). Ex Libris has provided a set of class diagrams on Doc Portal. Use the V9.1 version with page
numbers 1 through 41. CARLI has some additional diagrams, with page numbers 42-51, on the CARLI web
site. These are available at http://www.carli.illinois.edu/products-services/i-share/reports . The page
numbers following the table names in this document will point you to the relevant class diagrams.

Finally, this document includes tips about how the tables relate to each other and how to understand what
you find in the fields.

The fields for each table are listed in alphabetical order, except that the fields with “_id” in them are listed
first. The “_id” fields are important because you will often use them to link tables to each other.

Fields marked with a star (*) are encoded in UTF-8. To make the diacritics and special characters display
properly, you will need the utf8to16() function and a Unicode font.

This document highlights changes from V8.0 through V9.1 using yellow highlighting.

The tables that are grayed out are not present in the I-Share member libraries’ version of
CARLI_Reports*.mdb because it’s inadvisable to use them.

ACCESS_GROUP Data in this table are defined in the SysAdmin

Data in this table are defined in the SysAdmin client at System, Access Control Groups.
client at System, Access Control Groups, and
display at OPAC Configuration, Holding Sort There will be data in this table when
Groups, Access Control Groups tab. access_group_type in ACCESS_GROUP = D.

For access_group_type, D=Domain Name, I=IP access_group_domain_id number

Address, R=IP Range, and P=Patron Group. access_group_id number
domain_name character 256
access_group_id number
access_group_code character 8 ACCESS_GROUP_IP
access_group_name character 40 Data in this table are defined in the SysAdmin
access_group_type character 1 client at System, Access Control Groups.

ACCESS_GROUP_DATABASES There will be data in this table when

This table does not appear to be used for access_group_type in ACCESS_GROUP = I or R.
anything.
access_group_id number access_group_id number
db_id number access_group_ip_id number
db_code character 8 max_ip_addr number
max_ipv6_addr character 32
ACCESS_GROUP_DOMAIN min_ip_addr number

1
 min_ipv6_addr character 32
ACQ_PROFILE p. 36, 42
ACCESS_GROUP_PATRON_GROUP Data in this table are defined in the SysAdmin
Data in this table are defined in the SysAdmin client at Security, Acquisitions/Serials Profiles,
client at System, Access Control Groups.. Profile Values and Profile Values Cont. tabs, and
access_group_id number display at the Operator, Current Profiles tab.
patron_group_id number
The change_line_item_bib field is new in V7.0.
ACCESS_GROUP_SORT_GROUP
Data in this table are defined in the SysAdmin acq_profile_id number
client at System, Access Control Groups. acq_profile_name character 25
access_group_id number bind_edit_issue character 1
sort_group_id number bind_edit_vol character 1
bind_print character 1
ACCOUNT_LOCATION p. 50 bind_view_vol_issue character 1
account_id number change_fund_alloc character 1
account_location number change_line_item_bib character 1
currency_maintenance character 1
ACCOUNT_NOTE p. 50 edi_incoming character 1
account_id number edi_outgoing character 1
vendor_id number fiscal_close character 1
note character 1900 hold_ignore_ownership character 1
invoice_add_update character 1
ACQ_LOCATIONS p. 42 invoice_approve character 1
Data in this table are defined in the SysAdmin invoice_delete character 1
client at Acquisitions, Policy Definitions, invoice_view_only character 1
Locations tab. item_add_update character 1
acq_policy_id number item_delete character 1
location_id number item_view_only character 1
destination_loc character 1 ledger_add_update character 1
order_default_item_type number ledger_delete character 1
order_loc character 1 ledger_view_only character 1
order_opac character 1 modify_edi_outgoing character 1
print_location number mono_claims character 1
receive_default_item_type number order_add_update character 1
receive_loc character 1 order_approve character 1
order_delete character 1
ACQ_OPERATOR p. 36, 42 order_view_only character 1
Data in this table display in the SysAdmin client override_commit character 1
at Security, Acquisitions/Serials Profiles, override_expend character 1
Operator tab and display at the Operator, Current pattern_add_update character 1
Profiles tab. pattern_delete character 1
acq_profile_id number pattern_view_only character 1
operator_id character 10 problems_claims_view_only character 1
receive character 1
ACQ_POLICY_GROUP p. 42, 50 serial_checkin character 1
Data in this table are defined in the SysAdmin serial_claims character 1
client at Acquisitions, Policy Definitions, Policy serials_view_only character 1
tab. vendor_add_update character 1
acq_policy_id number vendor_delete character 1
dup_profile_id number vendor_view_only character 1
acq_policy_name character 40

2
ACQ_SECURITY_LOCS p. 36, 42 create_date date
Data in this table are defined in the SysAdmin update_date date
client at Security, Acquisitions/Serials Profiles,
Locations tab. AUTHORITY1XX4XX_VW
acq_profile_id number auth_id_1xx number
location_id number auth_id_4xx number
display_heading character 330
ACTION_TYPE p. 43, 44 index_type character 10
This table is used with the AUTH_HISTORY, opacbibs number
BIB_HISTORY, and MFHD_HISTORY tables. staffbibs number
action_type_id number
action_type character 20 AUTHORITY5XX1XX_VW
auth_id_5xx number
ADDRESS_TYPE p.23 display_heading character 300
This table is used with the PATRON_ADDRESS index_type character 10
table.
address_desc character 25 AUTHORITYDUPE_VW
address_type number auth_id number
display_heading character 330
ADJUST_REASON p. 2
Data in this table are defined in the SysAdmin AUTHORITYRECORDS_VW
client at Acquisitions, Adjust Reasons. auth_id number
reason_id number index_type character 10
vendor_id number reference_type_desc character 20
charge_or_credit character 1 display_heading character 300
reason_edi_code character 250 normal_heading character 300
reason_text character 50
AUTH_DATA p. 43
ALT_VENDOR_NAMES p. 3, 7, 8, 50 The starred field in this table is in UTF-8.
vendor_id number
alt_vendor_name character 60 When you are searching record_segment, it is
normal_alt_vendor_name character 60 helpful to know that CHR(31) is the subfield
delimiter, CHR(30) is the end of field delimiter,
AUTHBLOB_VW and CHR(29) is the end of record delimiter.
This view does not work for authorities longer
than 4000 characters, so the GetAuthBlob function auth_id number
is more reliable. *record_segment character 990
auth_id number seqnum number
marc_record character 4000
AUTH_HEADING p. 26, 43
AUTHHEADING_VW The starred field in this table is in UTF-8.
auth_id number auth_id number
heading_id_pointee number heading_id_pointee number
heading_id_pointer number heading_id_pointer number
reference_type character 20 *display_heading character 330
reference_type character 1
AUTHHISTORY_VW scope_note_present character 1
auth_id number
create_location_id number AUTH_HISTORY p.43
create_operator_id character 10 There’s an error in some versions of the E-R
update_location_id number diagrams. Action_type_id has a value between 1
update_operator_id character 10

3
and 6 and it is interpreted by linking to the BASE_CURRENCY
ACTION_TYPE table. Data in this table are defined in the SysAdmin
client at System, Base Currency.
When an authority record is deleted, its base_country_name character 25
AUTH_HISTORY records are deleted too. base_currency_code character 3
base_currency_name character 25
action_type_id number base_decimals number
auth_id number decimal_delimiter character 1
location_id number
operator_id character 10 BIBBLOB_VW
action_date date This view does not work for bibs longer than 4000
encoding_level character 1 characters, so the GetBibBlob function is more
reliable.
AUTH_INDEX p. 34, 43 bib_id number
The starred fields in this table are in UTF-8. marc_record character 4000

This is the table that Voyager uses to index the BIBCOMPOSITEINDEX_VW

010 and 035 fields in authorities. The index_code composite_searchcode character 4
tells you what fields and subfields are being component_searchcode character 4
indexed. A10A indexes 010$a, A10Z indexes
010$z, A350 and A35A both index 035$a, but they BIBHISTORY_VW
are formatted differently, and A35Z would index bib_id number
035$z, but it appears that the LC authority create_location_id number
records do not include this subfield. If you want create_operator_id character 10
to know more about what is indexed, take a look update_location_id number
at the indexrules field in the SEARCHPARM update_operator_id character 10
table. create_date date
auth_id number update_date date
*display_heading character 150
index_code character 4 BIBLOC_VW
*normal_heading character 150 bib_id number
marcloccode character 3
AUTH_MASTER p. 26, 34, 43, 47
If a record has not been modified, the BIBSORTING_VW
modify_date is null. This table provides a very convenient way to sort
auth_id number by author and/or title, but it is slow. If you need
export_ok_location_id number a faster solution, use BIB_INDEX.
export_ok_opid character 10 bib_id number
create_date date display_author character 150
export_date date display_title character 150
export_ok character 1 normal_author character 150
export_ok_date date normal_title character 150
update_date date pub_date character 4

AUTH_SUBDIVISION p. 26, 43 BIB_CARRIER p. 34, 44

The starred field in this table is in UTF-8. This table is part of RDA functionality.
auth_id number bib_id number
subdiv_id_pointee number carrier character 2
subdiv_id_pointer number
*display_subdiv character 330 BIB_CONTENT p. 34, 44
reference_type character 1 This table is part of RDA functionality.
bib_id number

4
 content character 3
The encoding_level and suppress_in_opac are the
BIB_DATA p. 44 values after the transaction.
The starred field in this table is in UTF-8.
action_type_id number
When you are searching record_segment, it is bib_id number
helpful to know that CHR(31) is the subfield location_id number
delimiter, CHR(30) is the end of field delimiter, operator_id character 10
and CHR(29) is the end of record delimiter. action_date date
encoding_level character 1
bib_id number suppress_in_opac character 1
*record_segment character 990
seqnum number BIB_INDEX p. 44
The starred fields in this table are in UTF-8.
BIB_FACET
This table is part of Voyager’s Geospatial module. This is the table that Voyager uses for left
We’re not using this module yet, so the table is anchored searches and limits, so it is very useful
not useful. for bibliographies. Titles, subjects, dates,
languages, and many other fields are indexed
The starred fields in this table are in UTF-8. here. The index_code gives you a clue as to what
fields and subfields are being indexed. If you
bib_id number want to know precisely what is indexed, take a
*facet1 character 20 look at the indexrules field in the SEARCHPARM
*facet2 character 20 table. Note that the language code in the 008L
*facet3 character 20 index is lower case in both of the heading fields.
index_code character 4
If you need data from a bib record that are not
BIB_FORMAT_DISPLAY available in BIB_TEXT, check to see if they are
Data in this table are defined in the SysAdmin available here. Using BIB_INDEX and BIB_TEXT
client at Search, Title List Material Type Display. is more efficient than using the BLOB functions.
bib_format character 2
bib_format_display character 20 The OCLC control number is indexed in
BIB_INDEX in 2 ways. If index_code is 0350,
BIB_HEADING p. 26, 44 normal_heading is “OCOLC 12345678”. If
The starred field in this table is in UTF-8. index_code is 035A, normal_heading is
bib_id number “12345678”.
heading_id number
*display_heading character 330 bib_id number
suppress_in_opac character 1 *display_heading character 150
index_code character 4
BIB_HISTORY p. 44 *normal_heading character 150
There’s an error in some versions of the E-R
diagrams. Action_type_id has a value between 1 BIB_ITEM p. 27, 44
and 6 and it is interpreted by linking to the This table is not completely reliable, particularly
ACTION_TYPE table. for “bound withs”. It is safer to use BIB_MFHD
and MFHD_ITEM instead.
When a bib record is deleted, its BIB_HISTORY
records are deleted too. Don’t use this table in queries that include the
MFHD_MASTER or BIB_MFHD tables, or you’ll
Voyager’s marcexport utility uses the create_date probably get redundant rows and bad counts.
and update_date in BIB_MASTER, not the
action_date in BIB_HISTORY. add_date date

5
 bib_id number BIB_SUBDIVISION p. 26, 44
item_id number The starred field in this table is in UTF-8.
operator_id character 10 bib_id number
subdiv_id number
BIB_LOCATION p. 44 *display_subdiv character 330
This table provides mapping from bibs to the
locations in the MFHDs, but it’s not very reliable, BIB_TEXT p. 34, 44, 47, 51
so you’re better off using BIB_MFHD, The starred fields in this table are in UTF-8.
MFHD_MASTER and LOCATION.
bib_id number If you need data from a bib record that are not
location_id number available in BIB_TEXT, check to see if they are in
BIB_INDEX (for fields in left-anchored indexes)
BIB_MASTER p. 5, 26, 27, 34, 44 or ELINK_INDEX (for URLs). All of these are
DPS is Ex Libris’ Digital Preservation System. more efficient than using the BLOB functions.

Voyager’s marcexport utility uses the create_date If you need data from a fixed field, some of them
and update_date in BIB_MASTER, not the are found here. Some are in the MARC*_VW
action_date in BIB_HISTORY. tables. The 007/0 (Category of Materials) is in the
BIB_MEDIUM table. Other fixed fields can be
If a record has not been modified, the extracted from FIELD_008 in BIB_TEXT using the
modify_date is null. Mid function. Just remember that most fixed
fields are specific to a record type so you’ll need
bib_id number to check bib_format, and that MARC calls the first
export_ok_location_id number byte “0” whereas Mid calls the first byte “1”. For
export_ok_opid character 10 example, to get Nature of Contents (008 bytes 24-
library_id number 27 for bibs): SELECT Mid([bib_format],1,1) AS
create_date date RecType, Mid([field_008],25,4) AS 008_24to27
exists_in_dps character 1 FROM BIB_TEXT WHERE
exists_in_dps_date date (((Mid([bib_format],1,1)) In ('a','h','t')));
export_date date
export_ok character 1 If you’re thinking of using begin_pub_date in a
export_ok_date date criterion, consider using the indexed version of
suppress_in_opac character 1 this field. It’s in the BIB_INDEX table, in the
update_date date normal_heading field when index_code=008D.

BIB_MEDIA p. 34, 44 If you’re thinking of using language in a criterion,

This table is part of RDA functionality. consider using the indexed version of this field.
bib_id number It’s in the BIB_INDEX table, in the
media character 1 normal_heading field when index_code=008L.
Note that the value “n/a” appears as “N/A” in
BIB_MEDIUM p. 44 that table.
The medium field holds the first byte of the 007
from a bib record. Voyager uses this table to limit If you’re thinking of using place_code in a
searches by “medium” in the staff clients or criterion, consider using the indexed version of
“additional format specification” in Web Voyage. this field. It’s in the BIB_INDEX table, in the
bib_id number normal_heading field when index_code=008P.
medium character 1
Here’s how MARC tags map to fields in
BIB_MFHD p. 14, 27, 41, 44 BIB_TEXT. For repeatable fields, the first
bib_id number occurrence is used. When both 260 and 264 are
mfhd_id number present, the 260 is used.:
Leader bytes 5 record_status

6
Leader bytes 6-7 bib_format encoding_level character 1
Leader bytes 17 encoding_level end_pub_date character 4
Leader bytes 18 descrip_form field_008 character 40
008 field_008 *gponum character 20
008 byte 6 date_type_status *imprint character 200
008 bytes 7-10 begin_pub_date *isbn character 50
008 bytes 11-14 end_pub_date *issn character 20
008 bytes 7-10 - bytes 11-14 language character 3
pub_dates_combined *lccn character 20
008 bytes 15-17 place_code *map_math_data character 255
008 bytes 22-23 map_projection map_projection character 2
008 bytes 35-37 language *network_number character 30
010 abz8 lccn *other_std_num character 30
020 a isbn place_code character 3
022 a issn pub_dates_combined character 9
024 a other_std_num *pub_place character 100
027 a stdtech *publisher character 150
028 all subfields publisher_number *publisher_date character 25
030 a coden *publisher_number character 40
035 a network_number record_status character 1
037 a stock_number *series character 255
074 a gponum *stdtech character 30
100 abcdkq author *stock_number character 50
110 abcdgkn author *title character 255
111 acdegkn author *title_brief character 150
130 adfgklmnoprs uniform_title *uniform_title character 255
240 adfgklmnoprs uniform_title
243 adfgklmnoprs uniform_title BIB_TEXT_DISPLAYFIELD
245 abcfghknps title Data in this table are defined in the SysAdmin
245 ab title_brief client at Search, Title List Column Names.
250 all subfields edition bib_text_field character 30
255 abc map_math_data display_name character 40
260 abc imprint
264 abc imprint BIB_USAGE_LOG
260 a pub_place The starred fields in this table are in UTF-8.
264 a pub_place
260 b publisher Records are written in this table and the
264 b publisher OPAC_SEARCH_LOG table when OPAC Bib
260 c publisher_date Usage logging is turned on. The table is
264 c publisher_date documented in the Voyager Technical Users
440 anpv series Guide.
490 av series
A client_type of G or W indicates WebVoyage.

bib_id number bib_id number

*author character 255 location_id number
begin_pub_date character 4 operator_id character 10
bib_format character 2 session_id character 16
*coden character 6 client_ip character 40
date_type_status character 1 client_type character 1
descrip_form character 1 *stat_string character 15
*edition character 100 use_date date

7
 use_type character 1 issue_id number
sequence_number number
BIB_VW
bib_id number BOOKING_RESULT
create_location_id number This table is part of Voyager’s Media Scheduling
mfhd_id number module.
mfhd_create_location_id number booking_result_id number
mfhd_location_id number booking_result character 20
call_no character 300
call_no_type character 1 BROWSE_STATS
create_date date The starred fields in this table are in UTF-8.
create_operator character 10
mfhd_create_date date This table is used by Voyager as a shortcut for
mfhd_create_operator character 10 left-anchored searches. It’s not very useful for
mfhd_location character 25 queries
mfhd_location_code character 10
normalized_call_no character 300 stat_id number
sort_title character 150 *stat_sample character 50
title character 150 stat_type character 1
sub_type character 12
BINDERY_COPY p. 1 subsub_type number
bindery_copy_id number
component_id number CACHE_MAPS
copy_id number This table is used by Voyager as a shortcut for
left-anchored searches. It’s not very useful for
BINDERY_COPY_DATA p. 1 queries.
bindery_copy_id number cache_id number
bindery_data_id number arg character 60
bindery_data_type_id number bits number
bindery_data character 1000 code character 4
date_updated date
BINDERY_COPY_DATA_TYPE p. 1 segsize number
bindery_data_type_id number
bindery_copy_data_type_desc char 25 CACHE_SEGS
This table is used by Voyager as a shortcut for
BINDERY_VOLUME p. 1 left-anchored searches. It’s not very useful for
bindery_copy_id number queries.
bindery_volume_id number cache_id number
item_id number record_segment long raw 0
bind_on_date date seqnum number
caption character 256
chron character 80 CALENDAR p. 46
freetext character 256 Data in this table are defined in the SysAdmin
item_enum character 80 client at Circulation, Calendars.
other_volume_data character 200
volume_note character 200 calendar_id number
year character 20 circ_cluster_id number
calendar_begin_date date
BINDERY_VOLUME_ISSUES p. 1 calendar_desc character 25
bindery_volume_id number calendar_end_date date
component_id number fixed_due_date date
copy_id number friday_closehour number

8
 friday_hourly_effect number CALL_NO_TYPE p. 45
friday_loan_due number The data in this table are defined by the Ex Libris
friday_open character 1 and cannot be changed.
friday_openhour number
monday_closehour number This table is used for call number processing
monday_hourly_effect number during bulk imports. It is not a complete list of
monday_loan_due number values in CALL_NO_TYPE in MFHD_MASTER.
monday_open character 1
monday_openhour number call_no_code character 16
saturday_closehour number call_no_desc character 25
saturday_hourly_effect number call_no_type character 1
saturday_loan_due number indexrules character 300
saturday_open character 1 map_code character 1
saturday_openhour number
sunday_closehour number CALL_SLIP p. 14, 41
sunday_hourly_effect number The print_group_id field can be linked to the
sunday_loan_due number group_id field in
sunday_open character 1 CALL_SLIP_GROUP_LOCATION and
sunday_openhour number CALL_SLIP_PRINT_GROUP.
thursday_closehour number
thursday_hourly_effect number If status_opid is blank, the last action (most likely
thursday_loan_due number a cancel) was done via Web Voyage.
thursday_open character 1
thursday_openhour number The rest of the information about this table is
tuesday_closehour number relevant only for sites using UB.
tuesday_hourly_effect number
tuesday_loan_due number The patron_db_id field give the affiliation of the
tuesday_open character 1 patron. For patrons of your library, it may be
tuesday_openhour number either zero or –1 or null. For patrons of other
wednesday_closehour number libraries, use the VOYAGER_DATABASES table
wednesday_hourly_effect number to translate.
wednesday_loan_due number
wednesday_open character 1 The pickup_db_id can also be translated with
wednesday_openhour number VOYAGER_DATABASES. For requests that will
be picked up at your library, it will be either zero
CALENDAR_TERM_DATE p. 46 or null.
Data in this table are defined in the SysAdmin
client at Circulation, Calendars. When a call slip is archived, none of the dates in
the record are changed. When a call slip is
calendar_id number promoted to another library, the call_slip record
end_of_term_date date is archived immediately. The STATUS is set to 9.
lead_days number Otherwise, CALL_SLIP records are archived by
the nightly circjob8 after the archive interval set in
CALL_NO_HIERARCHY p. 45 SysAdmin has passed.
Data in this table are defined in the SysAdmin
client at Cataloging, Call Number Hierarchy. The DATE_PROCESSED field is null if STATUS is
call_no_hierarchy_id number 1, 2, or 3. Otherwise, it’s the same as the
call_no_type character 1 STATUS_DATE field. It’s easier to use
code character 8 STATUS_DATE so you don’t have to remember
name character 25 this.
use_as_default character 1

9
If a call slip is neither filled nor unfilled before the patron_id number
expire period for this call slip queue, the nightly pickup_db_id number
circjob8 changes its status to Expired, which pickup_location_id number
makes it eligible for promotion by circjob32. print_group_id number
status_opid character 10
For UB requests that have been promoted to this date_processed date
library, date_requested is the date on which the date_requested date
call slip arrived here, not the date on which the item_chron character 80
patron placed the request. You can find out item_enum character 80
where the request has been previously and get a item_year character 20
closer approximation of the date the patron made no_fill_reason number
the request by looking at the not_needed_after number
REQUEST_HISTORY table. note character 100
reply_note character 100
For call slips that were promoted to this library by status number
circjob 32, item_id=0 until the call slip is filled. status_date date

bib_id number CALL_SLIP_GROUP_LOCATION p. 14, 41

call_slip_id number Data in this table are defined in the SysAdmin
item_id number client at Call Slips, Rules.
location_id number
mfhd_id number The group_id field can be used to link to
patron_db_id number print_group_id in CALL_SLIP and
patron_group_id number CALL_SLIP_ARCHIVE.
patron_id number
pickup_db_id number group_id number
pickup_location_id number item_type_id number
print_group_id number location_id number
status_opid character 10 temp_item_type_id number
date_processed date call_no_max_display character 144
date_requested date call_no_max_norm character 112
item_chron character 80 call_no_min_display character 144
item_enum character 80 call_no_min_norm character 112
item_year character 20 call_no_type character 1
no_fill_reason number perm_location number
not_needed_after number rule_rank number
note character 100 temp_location number
reply_note character 100 year_max character 20
status number year_min character 20
status_date date
CALL_SLIP_MSG
CALL_SLIP_ARCHIVE Data in this table are defined in the SysAdmin
When a call slip is archived, the call_slip_id gets client at OPAC Configuration, Call Slip Request
copied to archive_id. You can use archive_id to Messages.
link to request_history. message_id number
archive_id number active character 1
bib_id number message_code character 10
item_id number message_name character 25
location_id number suspension_message character 1
mfhd_id number
patron_db_id number CALL_SLIP_PRINT_GROUP p. 14, 41
patron_group_id number

10
Data in this table are defined in the SysAdmin If you get the message, “Type mismatch in
client at Call Slips, Queues. expression”, when you use this table, see
Appendix A for a solution.
There is a record in this table for each call slip call_slip_id number
queue. patron_stat_id number

The group_id field can be used to link to CALL_SLIP_STATUS_TYPE p. 14

print_group_id in CALL_SLIP and status_desc character 25
CALL_SLIP_ARCHIVE. status_type number

The values for process_method are CAMBRIDGEDEPTCLASS_VW

C=automatically charge to the patron, H=place in This table parses call numbers in a Cambridge
On Hold status, and T= place in In Transit On University-specific classification. It’s not useful to
Hold status us, so CARLI staff have removed it from the
CARLI_reports.mdb.
default_item_type_id number mfhd_id number
group_id number class character 6
location_id number
archive_interval character 1 CAMBRIDGEMAINCLASS_VW
archive_period number This table parses call numbers in a Cambridge
cat_review character 1 University-specific classification. It’s not useful to
circ_review character 1 us, so CARLI staff have removed it from the
default_group character 1 CARLI_reports.mdb.
expire_interval character 1 mfhd_id number
expire_period number class character 6
group_code character 10
group_name character 25 CAMBRIDGEMEDICALCLASS_VW
patron_info character 1 This table parses call numbers in a Cambridge
process_method character 1 University-specific classification. It’s not useful to
us.
CALL_SLIP_REASSIGN… Tables mfhd_id number
When a call slip is reassigned to a different queue, class character 6
this table shows the queue that it used to be in
and who reassigned it. The status of the call slip CAT_CONTROL_BARCODE p. 45
is 3=Reassigned until the slip is filled, unfilled, Data in this table are defined in the SysAdmin
expired, or canceled. The reassignment record is client at Cataloging, Bulk Import Rules, Barcode
archived when the call slip is archived. tab.
import_rule_id number
CALL_SLIP_REASSIGNMENT field character 3
call_slip_id number indicator1 character 1
operator_id character 10 indicator2 character 1
print_group_id number sequence number
reassign_date date subfield character 1

CALL_SLIP_REASSIGN_ARCHIVE CAT_CONTROL_CALL_NO p. 45
archive_id number Data in this table are defined in the SysAdmin
operator_id character 10 client at Cataloging, Call Number Hierarchy, Call
print_group_id number Number tab.
reassign_date date call_no_hierarchy_id number
cutter_subfield character 1
CALL_SLIP_STATS field character 3
indicator1 character 1

11
 indicator2 character 1 CAT_POLICY_DUP p. 45
main_subfield character 1 Data in this table display in the SysAdmin client
sequence number at Cataloging, Policy Definitions.
cat_policy_id number
CAT_CONTROL_ITEM_STATUS p. 33 dup_profile_id number
import_rule_id number
bindery character 1 CAT_POLICY_GROUP p. 45
cat_review character 1 Data in this table are defined in the SysAdmin
circ_review character 1 client at Cataloging, Policy Definitions.
damaged character 1
in_process character 1 The opac_display field does not appear to be used
lost_lib_app character 1 for anything.
missing character 1 cat_policy_id number
withdrawn character 1 cat_policy_name character 40
nuc_code character 15
CAT_CONTROL_ITEM_TYPE p. 45 opac_display character 1
Data in this table are defined in the SysAdmin
client at Cataloging, Bulk Import Rules, Item CAT_POLICY_HIERARCHY p. 45
Type tab. Data in this table are defined in the SysAdmin
client at Cataloging, Policy Definitions, Default
The fixed_start and fixed_end fields do not Policies tab.
appear to be used for anything. call_no_hierarchy_id number
import_rule_id number cat_policy_id number
field character 3
fixed_end number CAT_POLICY_LOCS p. 45
fixed_start number Data in this table are defined in the SysAdmin
indicator1 character 1 client at Cataloging, Policy Definitions, Locations
indicator2 character 1 tab.
sequence number
subfield character 1 The circ_location field does not appear to be used
for anything.
CAT_CONTROL_MULTI_ITEMS p. 33 cat_group_id number
import_rule_id number location_id number
barcode_subfield character 1 call_no_type character 1
chron_subfield character 1 cataloging_location character 1
collapse_mfhds character 1 circ_location character 1
enum_subfield character 1 default_item_type number
item_type_subfield character 1 nuc_code character 15
location_subfield character 1 routing_location character 1
main_field character 3
main_ind1 character 1 CAT_PROFILE p. 37, 45
main_ind2 character 1 Data in this table are defined in the SysAdmin
note_subfield character 1 client at Security, Cataloging Profiles, Profile
year_subfield character 1 Values and Profile Values Cont. tabs.

CAT_OPERATOR p. 37, 45 cat_profile_id number

Data in this table display in the SysAdmin client auth_add character 1
at Security, Operator Profiles, Current Profiles auth_delete character 1
tab. auth_export_ok character 1
cat_profile_id number auth_update character 1
operator_id character 10 auth_view_only character 1
bib_add character 1

12
 bib_delete character 1
bib_export_ok character 1 The gov_item_type fields are the item’s current
bib_update character 1 type, in other words, the temp item type, if there
bib_view_only character 1 is one, otherwise the item type. Similarly, the
cat_profile_name character 25 gov_location fields are the item’s temp location, if
change_ownership character 1 there is one, otherwise the perm location.
global_replace character 1
hold_add character 1 The charge_date_time field is the date and time
hold_delete character 1 the item was charged. The charge_date_only
hold_ignore_ownership character 1 field is just the date of the charge. Access treats
hold_update character 1 this as if the charge were done at 12:00 a.m.
hold_view_only character 1 bib_id number
item_add character 1 charge_oper_id character 10
item_delete character 1 item_id number
item_update character 1 mfhd_id number
item_view_only character 1 patron_group_id number
marcauth_add_update character 1 charge_date_only date
marcauth_view_only character 1 charge_date_time date
marcbib_add_update character 1 charge_location number
marcbib_view_only character 1 charge_location_code character 10
marchold_add_update character 1 charge_location_name character 25
marchold_view_only character 1 gov_item_type character 25
mfhd_export_ok character 1 gov_item_type_code character 10
use_template character 1 gov_location character 25
gov_location_code character 10
CAT_SECURITY_LOCS p. 37 notice_count number
Data in this table display in the SysAdmin client patron_group_code character 10
at Security, Cataloging Profiles, Locations tab. patron_group_name character 25
cat_profile_id number perm_item_type character 25
location_id number perm_item_type_code character 10
perm_location character 25
CHARACTER_SET p. 33 perm_location_code character 10
char_set_id number renewal_count number
char_set_code character 1
char_set_name character 30 CIRCRENEW_VW
This view has a number of quirks and it is not
CHRON chron_type_id number efficient. Consider using the tables directly
chron_seq number instead.
chron_value character 20
If an item has been deleted since it circulated, its
CHRON_TYPE p. 51 renewals are not available in this view.
chron_type_id number
chron_name character 40 The gov_item_type fields are the item’s current
chron_type_code character 2 type, in other words, the temp item type, if there
is one, otherwise the item type. Similarly, the
CIRCCHARGES_VW gov_location fields are the item’s temp location, if
This view has a number of quirks and it is not there is one, otherwise the perm location.
efficient. Consider using the tables directly
instead. The charge_date_time field is the date and time
the item was charged. The charge_date_only
If an item has been deleted since it circulated, its field is just the date of the charge. Access treats
charges are not available in this view.

13
this as if the charge were done at 12:00 a.m. The CIRC_ALERT_TYPES p. 15
two renew_date fields function similarly. Data in this table are defined in the SysAdmin
client at Circulation, Policy Definitions, Alerts tab.
bib_id number
charge_oper_id character 10 alert_type number
item_id number alert_type_desc character 100
mfhd_id number
patron_group_id number CIRC_BLOCKS p. 38
renew_oper_id character 10 Data in this table are defined in the SysAdmin
charge_date_only date client at Security, Circulation Profiles, Patron
charge_date_time date Blocks and Item Blocks tabs.
charge_location number
charge_location_code character 10 block_id number
charge_location_name character 25 block_display_name character 100
gov_item_type character 25 block_name character 30
gov_item_type_code character 10 block_type character 6
gov_location character 25
gov_location_code character 10 CIRC_BLOCK_OVERRIDE p. 38
location_name character 25 Data in this table are defined in the SysAdmin
patron_group_code character 10 client at Security, Circulation Profiles, Patron
patron_group_name character 25 Blocks and Item Blocks tabs.
perm_item_type character 25
perm_item_type_code character 10 block_id number
perm_location character 25 circ_profile_id number
perm_location_code character 10
renew_date_only date CIRC_CLUSTER
renew_date_time date Data in this table are defined in the SysAdmin
renew_location_code character 10 client at Circulation, Cluster Maintenance.
renewal_count number
circ_cluster_id number
CIRC_ALERTS p. 15 circ_cluster_code character 10
alert_id number circ_cluster_name character 100
alert_name character 30 default_pickup_location number
alert_text character 100
alert_type number CIRC_GROUP_CALENDAR p. 46
Data in this table display in the SysAdmin client
CIRC_ALERT_CONDITIONS p. 15 at Circulation, Policy Definitions, Calendar tab.
Data in this table are defined in the SysAdmin
client at Circulation, Policy Definitions, Alerts tab. calendar_id number
circ_group_id number
If you get the message, “Type mismatch in
expression”, when you use this table, see CIRC_OPERATOR p. 38, 46
Appendix A for a solution. Data in this table display in the SysAdmin client
alert_id number at Security, Operator Profiles, Current Profiles
loc_id number tab.
alert_display number circ_profile_id number
alert_use_patron_barcode character 1 operator_id character 10
alert_use_patron_name character 1
alert_use_patron_phone character 1 CIRC_POLICY_GROUP p. 46
Data in this table are defined in the SysAdmin
client at Circulation, Policy Definitions, Policies
tab.

14
 print_fine_receipts character 1
circ_cluster_id number print_hold_slips character 1
circ_group_id number print_location number
circ_group_name character 40 print_routing_slips character 1
closed_days_for_fines character 1 recall_life number
closed_days_for_loans character 1 shelving_interval character 1
early_pickup_window number shelving_period number
extend_recall_due_date character 1 suppress_fly_items character 1
fixed_due_time character 1 transit_period number
in_transit_fulfilled character 1
lost_credit_trans_type number CIRC_POLICY_MATRIX p. 46
lost_process_fee character 1 Data in this table are defined in the SysAdmin
lost_remove_overdue character 1 client at Circulation, Policy Definitions.
lost_remove_proc_fee character 1
lost_remove_repl_fee character 1 The value of loan_interval may be M=minutes,
lost_update_patron_counter character 1 H=hours, D=days, T=term, or I=indefinite. For
max_fine_fee_for_lost character 1 Term loans and Indefinite loans, the value of
process_fee number loan_period does not matter and it may be zero.
renew_if_hold character 1 For all other intervals, if loan_period=0, then the
renew_if_overdue character 1 item does not circulate.
renew_if_recall character 1
title_level_no_items_circ character 1 If the value of item_type_id and patron_group_id
title_level_no_items_opac character 1 is zero, this matrix entry applies to all item types
unclaimed_interval number and patron groups, in this circ policy group.

CIRC_POLICY_LOCS p. 15 Hold_shelf_life is the number of days a local item

Data in this table are defined in the SysAdmin can sit on the hold shelf waiting for the patron to
client at Circulation, Policy Definitions, Locations pick it up. Don’t confuse this with hold_life in
tab. CIRC_POLICY_LOCS.

Hold_life is how long the patron will wait for an Lost_notice_interval is the number of days
item charged to another patron to become overdue after which the item is given the “Lost-
available. For UB items, it is also the length of System Applied” status.
time the item will remain on the hold shelf before
being expired by circjob 19. Don’t confuse it with circ_group_id number
hold_shelf_life in CIRC_POLICY_MATRIX. circ_policy_matrix_id number
item_type_id number
circ_group_id number patron_group_id number
location_id number advanced_loan_warning_interval character 1
automated_storage character 1 advanced_loan_warning_period number
circ_location character 1 allow_bookings_on_overdues character 1
collect_fines character 1 always_due_next_open_day character 1
courtesy_discharge character 1 charge_limit number
default_item_type number charge_limit_apply character 1
default_location number charge_renew character 1
hold_life number courtesy_notice_interval number
opac_circ_desk character 1 courtesy_notice_min_loan number
patron_avail_items_alert character 1 fine_interval character 1
patron_fine_fee_alert character 1 fine_rate number
pickup_location character 1 first_overdue_interval number
print_date_dues character 1 grace_period number
print_discharge_receipts character 1 hold_shelf_life number

15
 hold_shelf_life_interval character 1 lost_remove_repl_fee character 1
loan_interval character 1 lost_update_patron_counter character 1
loan_period number manually_map_patron character 1
lost_notice_interval number mfhd_delete character 1
max_fine number mfhd_update character 1
max_recall_fine number modify_fines character 1
other_notice_count number patron_add_update character 1
other_notice_interval number patron_counters character 1
place_call_slip character 1 patron_delete character 1
place_hold character 1 patron_mask_ssn character 1
place_recall character 1 patron_proxy_maintain character 1
place_ub_request character 1 patron_view_only character 1
recall_fine_interval character 1 pay_fines character 1
recall_fine_rate number pg_restrict_circ character 1
recall_grace_period number pg_restrict_maint character 1
recall_min_loan number pg_restrict_view character 1
recall_notice_count number recahold_add_update character 1
recall_notice_interval number recahold_resequence character 1
recall_return_period number reserve_add_update character 1
renew_from_due_date character 1 update_pin character 1
renewal_count number view_patron_circ_history character 1
renewal_interval character 1
renewal_period number CIRC_SECURITY_LOCS p. 38
Data in this table are defined in the SysAdmin
CIRC_PROFILE p. 38, 46 client at Security, Circulation Profiles, Locations
Data in this table are defined in the SysAdmin tab.
client at Security, Circulation Profiles and display circ_profile_id number
at Operator, Current Profiles. location_id number

circ_profile_id number CIRC_SECURITY_PG p. 38

add_fines character 1 Data in this table are defined in the SysAdmin
bib_delete character 1 client at Security, Circulation Profiles, Patron
change_discharge_date character 1 Groups tab.
change_due_date character 1 circ_profile_id number
charge_renew character 1 patron_group_id number
circ_profile_name character 25
discharge character 1 CIRC_TRANS… Tables
distribution_item_create character 1 Circulation transactions are recorded in
distribution_item_delete character 1 CIRC_TRANSACTIONS until the item is
distribution_item_distribute char discharged, after which they are moved to
distribution_item_order character 1 CIRC_TRANS_ARCHIVE. Consequently, the
distribution_item_receive character 1 discharge… fields in CIRC_TRANSACTIONS are
distribution_item_update character 1 always blank.
distribution_item_view character 1
edit_stub_patron character 1 When a transaction is archived, the value of
forgive_fines character 1 circ_transaction_id is changed. In both tables,
hold_ignore_ownership character 1 circ_transaction_id is assigned sequentially as a
item_add_update character 1 record is added. Nonetheless, you can join either
item_delete character 1 table to REQUEST_HISTORY by
item_status character 1 circ_transaction_id.
lost_remove_overdue character 1
lost_remove_proc_fee character 1

16
The db_id field gives the affiliation of the patron.
It can be translated using the charge_oper_id character 10
VOYAGER_DATABASES table. For patrons circ_policy_matrix_id number
affiliated with your library, db_id may be either circ_transaction_id number
zero or null. db_id number
discharge_oper_id character 10
For items charged at another library, item_id number
charge_location=0 and charge_oper_id=’SYS-UB’. patron_group_id number
For items discharged at another library, patron_id number
discharge_location=0 and patron_id_proxy number
discharge_oper_id=’SYS-UB’. charge_date date
charge_due_date date
For many circ statistics, you will want to combine charge_location number
data from these two tables. Voyager provides an charge_type character 1
Access query called “Circulation Transactions courtesy_notice_date date
(Charges)” which does this for you. From an Add current_due_date date
Tables window in Access, click the Queries tab discharge_date date
and you’ll find it. discharge_location number
discharge_type character 1
The charge_type and discharge_type fields have 2 over_recall_notice_count number
values, N for Normal and O for Override. over_recall_notice_date date
overdue_notice_count number
If patron_id_proxy is neither zero nor null nor overdue_notice_date date
equal to the patron_id, then the charge was done recall_date date
by a proxy patron. The patron_id is the sponsor’s recall_due_date date
patron_id and patron__id_proxy is the proxy’s recall_notice_count number
patron_id. recall_notice_date date
renewal_count number
When circulation staff do an on-the-fly charge,
that is, when they charge an item that is not in the CIRC_TRANSACTION_STATS p. 16
database, Voyager creates an item, a MFHD and, This table may be linked to
if needed, a bib record. When the item is CIRC_TRANS_ARCHIVE, but not to
discharged, these records are retained unless circ CIRC_TRANSACTIONS. Refer to the notes on
staff do something to delete them, so they are the PATRON_STATS table.
available for circ statistics. However, if your circ
staff routinely delete these records and you want circ_transaction_id number
on-the-fly circ to be included in your circ patron_stat_id number
statistics, be sure to change the link properties on
the link from the circ transaction table(s) to the CIRC_TRANS_ARCHIVE p. 16
item table. Due_date is the due date at the time the item was
initially charged out. If the item was renewed,
CIRC_TRANSACTIONS p. 17 the new due date is not stored in this table.
The current_due_date is the due date that you
normally want to use. It is set when the item is The patron_id field will always be 0 unless you
initially charged and changed when the item is have checked Retain Patron ID for Circ History in
renewed or recalled. The charge_due_date field SysAdmin.
is the due date at the time the item was initially
charged; it never changes. If the item was charge_oper_id character 10
recalled, the new due date will be in circ_policy_matrix_id number
recall_due_date. If the item was renewed, the circ_transaction_id number
dates of each renewal will be in the RENEW* db_id number
tables. discharge_oper_id character 10

17
 item_id number normal_section_number character 10
patron_group_id number number_of_students number
patron_id number section_number character 10
patron_id_proxy number
charge_date date COMPLEX_COMP_PATTERN p. 51
charge_location number ccp_id number
charge_type character 1 component_id number
courtesy_notice_date date cp_id number
discharge_date date end_issue_id number
discharge_location number start_issue_id number
discharge_type character 1 end_cp_issue number
due_date date end_date date
over_recall_notice_count number
over_recall_notice_date date COMPLEX_PATTERN p. 51
overdue_notice_count number If a record has not been modified, the
overdue_notice_date date modify_date is null.
recall_date date cp_id number
recall_due_date date create_location_id number
recall_notice_count number update_location_id number
recall_notice_date date create_date date
renewal_count number create_opid character 10
pattern_name character 40
CIRC_TRANS_EXCEPTION pattern_name_norm character 40
Unusual circulation activity is recorded here update_date date
during the day. The table is cleared out nightly update_opid character 10
when the circ transactions exception report (Circ
Job 24) is run. COMPONENT p. 1, 9, 10, 11, 51
circ_trans_except_id number The values of predict are: Y=yes, the component
item_id number uses a predictive pattern, N=the component uses
patron_id number a non-predictive pattern, S=the pattern has been
trans_except_oper_id character 10 closed, M=the pattern has yet to be set, C=the
item_location number component uses a complex pattern.
trans_except_date date
trans_except_location number component_id number
trans_except_type number item_type_id number
next_issue_id number
CIRC_TRANS_EXCEPT_TYPE subscription_id number
exception_desc character 50 category number
exception_type number claim_interval number
component_name character 100
CLAIM_TYPES p. 7, 10 component_name_norm character 100
Data in this table are defined in the SysAdmin create_items character 1
client at Acquisitions, Claim Types. note character 256
predict character 1
claim_type number unit_title number
claim_type_desc character 70
edi_code character 11 COMPONENT_ALTCHRONDAY p. 9
component_id number
CLASS_SECTION p. 18 chron_day number
This table is part of Reserves functionality. type_of_day character 3
circ_cluster_id number
section_id number COMPONENT_CHRONDAY p. 9

18
 component_id number begin_date date
chron_day number course_name character 40
type_of_day character 3 course_number character 10
end_date date
COMPONENT_ISSUES_ROUTED p. 11 normal_course_name character 40
component_id number normal_course_number character 10
issue_id number
routing_list_id number The CP… Tables
These tables are part of the implementation of
COMPONENT_ISSUE_DAY p. 9 complex serial patterns in the acquisitions
component_id number module.
expected_day number
type_of_day character 3 CP_CELL p. 51
cp_issue_id number
COMPONENT_PATTERN p. 9, 51 cp_level_id number
component_id number level_increment character 80
end_issue_id number
pattern_id number CP_DOMAIN_TYPE p. 51
start_issue_id number If domain=c, then enum_chron_type_id can be
alt_lvl1_inc_at number linked to CHRON_TYPE. If domain=e, then
alt_lvl2_inc_at number enum_chron_type_id can be linked to
end_date date ENUMERATION_TYPE.
frequency_code character 1 cp_domain_type_id number
lvl1_inc_at number enum_chron_type_id number
lvl2_inc_at number domain character 1
lvl3_inc_at number
lvl4_inc_at number CP_ISSUE p. 51
lvl5_inc_at number cp_id number
lvl6_inc_at number cp_issue_id number
regularity character 12 cp_issue number
regularity_marc character 50 expected_date_inc number
time_unit_code character 1
COMPONENT_ROUTING p. 11
component_id number CP_LEVEL p. 51
routing_list_id number cp_domain_type_id number
cp_id number
CONTROL_TABLE cp_level_id number
This table is part of patron self-registration. caption character 50
control_name character 50 cp_level number
control_value character 2000 is_constant character 1
print_order number
CONVERSION_RATE_AUDIT reg_or_alt character 1
audit_id number
currency_id number CURRENCY_CONVERSION
rate_create_operator_id character 10 create_operator_id character 10
conversion_rate number currency_id number
rate_create_date_time date rate_create_operator_id character 10
conversion_rate number
COURSE p. 18 country_name character 75
This table is part of reserves. create_date date
circ_cluster_id number currency_code character 3
course_id number currency_name character 75

19
 decimal_delimiter character 1
decimals number A set of techniques for producing statistics by
normal_country_name character 75 more precise call number ranges is given in
normal_currency_code character 3 “Reports with Call Number Ranges: How to
normal_currency_name character 75 Request Then and How to Write Them” at
rate_create_date_time date http://www.carli.illinois.edu/products-
services/i-share/reports/secure/callnumrange
DATABASE_ADDRESS
Data in this table are defined in the SysAdmin mfhd_id number
client at Search, Database Definitions, Definitions class character 3
tab. longclass character 300
db_id number
application_type character 20 DISTRIBUTION_ITEM p. 19
db_addr character 255 create_location_id number
db_port number create_opid character 10
item_id number
DATABASE_LICENSE modify_location_id number
Ex Libris says that this table keeps track of active modify_opid character 10
connections to Voyager. It is not used to track vendor_id number
simultaneous user licenses. It could be used for active character 1
this, but Oracle does it instead. When a create_date date
connection times out, its record is deleted. historical_distributions number
license_id number modify_date date
session_id number on_hand_quantity number
db_code character 8 order_quantity number
init_date date reorder_automatic character 1
module character 20 reorder_point number

DEPARTMENT p. 18 DISTRIBUTION_ORDER p. 19
This table is part of reserves. distribution_order_id number
circ_cluster_id number item_id number
department_id number order_location_id number
department_code character 10 order_opid character 10
department_name character 40 vendor_id number
normal_dept_code character 10 expected_date date
normal_dept_name character 40 not_yet_received number
order_complete character 1
DEWEYCLASS_VW order_date date
There’s an entry in this table for every call order_quantity number
number encoded as Dewey (MFHD 852 first
indicator = 1) even if that encoding is wrong. DISTRIBUTION_RECEIPT p. 19
CLASS is the first 3 characters of 852$h. distribution_order_id number
LONGCLASS is the entire 852$h. distribution_receipt_id number
receipt_location_id number
If you want to sort a report (not a query, a report) receipt_opid character 10
by longclass, you will have to use the Left receipt_date date
function to truncate it to less that 255 characters. receipt_quantity number

To add a description of each Dewey class to your DISTRIBUTION_TRANSACTION p.19

queries, link the class field in DEWEYCLASS_VW distribution_location_id number
to the DeweyNum field in the DeweyDetailed distribution_opid character 10
table and show the Description field. distribution_transaction_id number

20
 item_id number
patron_group_id number dup_profile_id number
patron_id number fieldoverride character 3
distribution_date date indicator_1 character 1
indicator_2 character 1
DSL_DIALECT p. 12 searchcode character 4
dsl_clob clob seqnum number
dsl_name character 200 subfieldoverride character 10
weight number
DUPE_PROFILE_MERGE p. 45
The starred field in this table is in UTF-8. DUP_PROFILE_QUALITY p. 45
dup_profile_id number Data in this table are defined in the SysAdmin
marc_field character 3 client at Cataloging, Authority Duplicate
marc_ind1 character 1 Detection Profiles, Quality Hierarchy tab, and at
marc_ind2 character 1 Cataloging, Bibliographic Duplicate Detection
*nuc5 character 15 Profiles, Quality Hierarchy tab, and at Cataloging,
Bibliographic Duplicate Detection Profiles, Merge
DUP_DETECTION_PROFILE p. 45 Data tab.
Data in this table are defined in the SysAdmin
client at Cataloging, Authority Duplicate The starred fields in this table are in UTF-8.
Detection Profiles, Profile tab, and at Cataloging, dup_profile_id number
Bibliographic Duplicate Detection Profiles, Profile desc_conventions 12
tab, and at Search, Indexes, Bibliographic Record encoding_level character 1
Linking, and at Search, Hook to Holdings. *modifying_agency character 15
*nuc_code character 15
The discard_unmatched field indicates that an record_type character 2
incoming bib record should be discarded if it does seqnum number
not match a record in the database.
EDI_CODE_REF
dup_profile_id number code character 3
discard_unmatched character 1 descr character 70
cancellation character 1 usage number
displayfield1 character 30
displayfield2 character 30 EDI_CODE_USAGES
displayfield3 character 30 data_element character 4
dup_handling character 1 descr character 70
dup_profile_code character 8 usage number
dup_profile_name character 25
dup_replace number EDI_CONNECTION_PROFILE
dup_warn number If a record has not been modified, the
record_type character 1 modify_date is the same as the create_date.
sortfield1 character 30 create_opid character 10
sortfield2 character 30 location_id number
sortfield3 character 30 profile_id number
update_opid character 10
DUP_PROFILE_FIELDS p. 45 vendor_id number
Data in this table are defined at Cataloging, create_date date
Authority Duplicate Detection Profiles, Field library_envelope_address character 55
Definitions tab, and at Cataloging, Bibliographic library_inside_address character 2
Duplicate Detection Profiles, Field Definitions tab, update_date date
and at Search, Indexes, Bibliographic Record use_iv character 1
Linking. use_mc character 1

21
 use_mr character 1 If a record has not been modified, the
use_po character 1 modify_date is the same as the create_date.
use_sc character 1 create_op_id character 10
use_sr character 1 db_ref_id number
use_vendor_account character 1 file_id number
use_xm character 1 location_id number
vendor_envelope_address character 55 msg_id number
vendor_inside_address character 25 update_op_id character 10
vendor_id number
EDI_CURSOR create_date date
cursor_id number create_loc number
file_id number data_present character 1
msg_id number doc_msg_code character 3
file_name character 30 file_end_pos number
file_position number file_start_pos number
msg_delimiters character 6 group_index number
line_item_count number
EDI_EVENT_TYPES load_or_append_date date
event_desc character 25 matching_profile number
event_type number msg_date date
msg_delimiters character 6
EDI_FILE msg_direction character 1
If a record has not been modified, the msg_number character 35
modify_date is the same as the create_date. msg_status number
create_op_id character 10 msg_type character 6
file_id number msg_type_code number
update_op_id character 10 msg_version_code number
create_date date receiver_code character 55
file_name character 30 receive_items character 1
file_size number sender_code character 55
file_status number total_amount number
file_type character 1 trans_index number
file_update_date date update_date date
group_count number update_loc number
message_count number
trans_count number EDI_MISSING_LINE_ITEM
update_date date exception_id number
line_id number
EDI_HISTORY print_std_num character 2
If a record has not been modified, the problem_code number
modify_date is the same as the create_date. std_number character 40
create_op_id character 10 title character 100
event_id number vendor_ref_num character 35
file_id number vendor_ref_qual character 3
msg_id number vendor_title_num character 40
update_op_id character 10
create_date date EDI_NOTE
event_type number event_id number
update_date date note_code number
position number
EDI_MESSAGE
EDI_SECTION

22
 msg_id number Record_type is supposed to be interpreted by the
section_id number ELINK_RECORD_TYPE table, but there are some
section_ordinal number errors. Actual values for record_type are A for
section_type character 3 Authority, B for Bibliographic, E for Electronic
seg_count number item, and M for MFHD. (ELINK_RECORD_TYPE
segments long raw 0 has a row, I for Item, but you can’t have a URL in
an item.)
EITEM p. 18, 47
This table is part of Reserves functionality. The record_id is either an auth_id, a bib_id, an
eitem_id, or a mfhd_id, depending on the value
The starred field in this table is in UTF-8. of record_type.

An electronic item has a MFHD and a bib, which As a general rule, the link field is 856$u and the
you can link to just as you would link physical link_text field is subfields $z and $3. See
items. Appendix B for more details. It also holds bib
subfields 505$u, 506$u, 514$u, 520$u, 530$u,
If a record has not been modified, the 540$u, 545$u, 552$u, 583$u, and 856$g, as well as
modify_date is null. MFHD subfields 563$u and 583$u.
create_location_id number
create_opid character 10 elink_id number
eitem_id number record_id number
mfhd_id number update_opid character 10
update_location_id number check_date date
update_opid character 10 check_status character 1
caption character 255 *link character 2048
chronology character 80 link_subtype character 10
create_date date *link_text character 1024
enumeration character 80 *link_text_normal character 1024
*link character 2048 link_type character 3
reserve_list_update_date date parse_status character 1
sequence number record_type character 1
update_date date seqnum number
year character 20 update_date date
*url_host character 255
EITEM_NOTES p. 18 url_port number
This table is part of Reserves functionality.
eitem_id number ELINK_RECORD_TYPE p. 47
eitem_note_type_id number record_type_id character 10
note character 2000 record_type character 25

EITEM_NOTE_TYPE p. 18 ENUMERATION_TYPE p. 51
This table is part of Reserves functionality. enumeration_type_id number
note_desc character 25 code char 2
note_type number name character 40

ELINK_INDEX p. 47 ENUM_CHRON_TYPES_VW
The starred fields in this table are in UTF-8. If you get the message, “Type mismatch in
expression”, when you use this table, see
ELINK_INDEX is a very handy place to find Appendix A for a solution.
URLs from various types of records.
chron_type_id number
cp_domain_type_id number

23
 enumeration_type_id number status_date date
code character 2
domain char 1 EQUIPMENT_BARCODE_STATUS p. 31
domain_desc character 13 equip_barcode_sts_id number
name character 40 barcode_sts character 25

EQUIPMENT… Tables EQUIPMENT_MEDIA_TYPE

These tables are part of the media scheduling equip_type_id number
module. media_schedule_policy_id number
media_type_id number
EQUIPMENT p. 29, 30, 31 priority number
create_location_id number
create_opid character 10 EQUIPMENT_NOTES p. 31
equip_id number equip_id number
equip_type_id number equip_note_type_id number
group_equip_id number op_id character 10
media_room_id number note character 2000
temp_room_id number update_date date
update_location_id number
update_opid character 10 EQUIPMENT_NOTE_TYPE p. 31
create_date date equip_note_type_id number
date_purchased date type character 15
dealer character 100
dealer_normalized character 100 EQUIPMENT_STATUS p. 30, 31
equip_format character 25 equip_id number
equip_format_normalized character 25 equip_sts_type_id number
equip_no character 15 op_id character 10
equip_no_normalized character 15 note character 100
historical_bookings number update_date date
historical_maintenance number
is_group character 1 EQUIPMENT_STATUS_TYPE p. 30, 31
last_inventoried date equip_sts_type_id number
manufacturer character 100 block_booking character 1
manufacturer_normalized character 100 block_charge character 1
model character 100 discharge_message character 50
model_normalized character 100 discharge_message_show character 1
next_maintenance date display_priority number
part_no character 100 message character 50
part_no_normalized character 100 sts_type character 40
part_supplier character 100 warn_on_booking character 1
part_supplier_normalized character 100 warn_on_charge character 1
serial_no character 100
serial_no_normalized character 100 EQUIPMENT_TYPE p. 30, 31
update_date date equip_type_id number
value_purchase number cleanup_time number
value_replacement number is_group character 1
replacement_default number
EQUIPMENT_BARCODE p. 31 setup_time number
equip_barcode_sts_id number type character 50
equip_id number type_code character 10
barcode_no character 25
barcode_no_normalized character 25

24
EVENT When a fine is paid, the fine_fee_balance goes to
Beginning with V9, browse and UB browse zero, but the record is not deleted from this table.
transactions are logged here. Other events may
be logged here in the future. The db_id field is not maintained by Voyager, so
circ_location_id number don’t use it. If you need to know the affiliation of
event_id number the patron who owes you a fine, use the db_id
event_type_id number field in the PATRON table.
item_id number
item_location_id number The fine_fee_location may be zero if the item was
oper_id character 10 returned at a library other than its home library.
patron_id number In this case, the operator_id may be null or “SYS-
event_date date UB”.
event_xml blob
item_type_code character 10 The create_date field is not filled in for manually
patron_group_code character 10 applied fines and fees. Some libraries manually
apply most fines and fees, even those for overdue
EVENT_ITEM_STATUS and lost items. For overdue fines created by a
event_id number back-dated discharge, the create_date is the actual
item_status number date of the discharge, not the back-date.

EVENT_TYPE db_id number

event_type_id number fine_fee_id number
retain_patron_id character 1 item_id number
event_type_code character 10 modify_loc_id number
event_type_desc character 250 modify_oper_id character 10
retain_event character 1 operator_id character 10
patron_id number
EXCEPTION_CALENDAR p. 46 create_date date
Data in this table are defined in the SysAdmin discharge_date date
client at Circulation, Calendars. due_date date
fine_fee_amount number
calendar_id number fine_fee_balance number
exception_closehour number fine_fee_location number
exception_date date fine_fee_note character 1000
exception_hourly_effect number fine_fee_notice_date date
exception_loan_due number fine_fee_type number
exception_open character 1 orig_charge_date date
exception_openhour number modify_date date

EXCEPTION_TYPES FINE_FEE_TRANSACTIONS p. 22
exception_type number fine_fee_id number
exception_type_desc character 20 fine_fee_trans_id number
operator_id character 10
FIELDWEIGHTS trans_amount number
Data in this table are defined in the SysAdmin trans_date date
client at Search, Indexes, Field Weighting. trans_location number
trans_method number
fieldcode character 4 trans_note character 1000
fieldweight number trans_type number

FINE_FEE p. 22 FINE_FEE_TRANS_METHOD p. 22
method_desc character 25

25
 method_type number To get to the parent fund, add a second FUND
table to your query, linking ledger_id to ledger_id
FINE_FEE_TRANS_TYPE p. 22 and parent_fund_id to fund_id.
Data in this table are defined in the SysAdmin
client at System, Fines/Fees, Payment tab. If a record has not been modified, the
modify_date is the same as the create_date.
transaction_desc character 25
transaction_type number create_opid character 10
type_demerit character 1 fund_id number
type_fine character 1 institution_fund_id character 50
ledger_id number
FINE_FEE_TYPE p. 22 update_opid character 10
Data in this table are defined in the SysAdmin allocation_decrease number
client at System, Fines/Fees, Payment tab. allocation_increase number
begin_date date
fine_fee_code character 10 category number
fine_fee_desc character 25 commit_freeze date
fine_fee_type number commit_pending number
commitments number
FISCAL_PERIOD p. 4 create_date date
Data in this table are defined in the SysAdmin end_date date
client at Acquisitions, Fiscal Periods. expend_freeze date
expend_only character 1
The fiscal_period_id field in FISCAL_PERIOD expend_pending number
can be used to link to fiscal_year_id field in expenditures number
LEDGER. This isn’t obvious from the names. fund_code character 10
end_date date fund_name character 25
fiscal_period_id number fund_type number
fiscal_period_name character 25 normal_fund_code character 10
start_date date normal_fund_name character 25
original_allocation number
FREQUENCY p. 9 overcommit character 1
freq_calc_type character 1 overcommit_percent number
freq_increment number overcommit_warn number
frequency_code character 1 overexpend character 1
frequency_desc character 25 overexpend_percent number
overexpend_warn number
FUND… Tables parent_fund number
Remember that a fund_id does not uniquely undercommit_percent number
identify a fund. It’s the combination of fund_id underexpend_percent number
and ledger_id that uniquely identifies a fund. update_date date
Consequently, you need to link by both of these
fields when you are linking among the FUND…, FUNDLEDGER_VW
PO_FUNDS and LINE_ITEM_FUNDS tables. fiscal_period_id number
fund_id number
FUND p. 2, 4 institution_fund_id character 50
There's no table that translates the values in the ledger_id number
category field. The values are 0=Summary, parent_fund_id number
1=Allocated, 2=Reporting. begin_date date
cash_balance number
commit_pending number
commitments number

26
 current_allocation number ledger_id number
end_date date operator_id character 10
expend_pending number amount number
expenditures number note character 1900
fiscal_period_end date reference_no character 25
fiscal_period_name character 25 statistical_fund number
fiscal_period_start date trans_date date
free_balance number trans_type number
fund_category character 9
fund_name character 25 FUND_TYPE p. 4
fund_type character 25 Data in this table are defined in the SysAdmin
fundline character 255 client at Acquisitions, Fund Types.
ledger_name character 40
normal_fund_name character 25 fund_type_id number
normal_ledger_name character 40 commit_warning number
original_allocation number expend_warning number
parent_fund character 25 fund_type_name character 25
policy_name character 40 overcommit_limit number
overexpend_limit number
FUND_NOTE p. 4 undercommit number
The ledger_id field is always set to 0. underexpend number
Consequently, a fund note persists from fiscal
year to fiscal year. GDC_OPERATOR p. 39
fund_id number gdc_profile_id number
ledger_id number operator_id character 10
fund_note character 1900
GDC_PROFILE p. 39
FUND_PAYMENT p. 2 gdc_profile_id number
fund_id number authload_job_kill 1
ledger_id number data_change_job_kill character 1
payment_id number data_change_rule_add character 1
amount number data_change_rule_delete character 1
percentage number data_change_rule_update character 1
split_fund_seq number data_change_rule_view character 1
gdc_profile_name character 25
FUND_TRANSACTION p. 4 index_job_kill character 1
The operator_id is sometimes null. If you look at job_auth_data_change character 1
other fund transactions done at about the same job_auth_remove_logfile character 1
time, you might be able to discern the job_auth_remove_marc_file character 1
operator_id. job_auth_scan character 1
job_auth_view_history character 1
If trans_type=4 (commitment) then reference_no job_authload 1
is a PO number. If trans_type=5 (expenditure) job_authload_view_history 1
then reference_no is an invoice number. job_authload_remove_logfile 1
job_authload_remove_marc_file 1
If trans_type=6 then fund_id is the fund from job_bib_data_change character 1
which the transfer came. If trans_type=7 then job_bib_remove_logfile character 1
fund_id is the fund to which the money was job_bib_remove_marc_file character 1
transferred. Be sure you link on ledger_id too. job_bib_scan character 1
job_bib_view_history character 1
audit_id number job_index_only char 1
fund_id number job_mfhd_data_change character 1

27
 job_mfhd_remove_logfile character 1 The starred field in this table is in UTF-8.
job_mfhd_remove_marc_file character 1
job_mfhd_scan character 1 This table is part of Voyager’s Geospatial module.
job_mfhd_view_history character 1 Until we begin using that module, the table will
record_set_auth_add character 1 not be useful.
record_set_auth_delete character 1 *coord_name character 25
record_set_auth_delete_rule character 1 coord_type number
record_set_auth_preview character 1
record_set_auth_update character 1 GEO_FORMAT_TYPE
record_set_auth_view character 1 The starred field in this table is in UTF-8.
record_set_bib_add character 1
record_set_bib_delete character 1 This table is part of Voyager’s Geospatial module.
record_set_bib_delete_rule character 1 Until we begin using that module, the table will
record_set_bib_preview character 1 not be useful.
record_set_bib_update character 1 coord_type number
record_set_bib_view character 1 *format_name character 30
record_set_mfhd_add character 1 format_type number
record_set_mfhd_delete character 1
record_set_mfhd_delete_rule character 1 GEO_SEARCH
record_set_mfhd_preview character 1 The starred field in this table is in UTF-8.
record_set_mfhd_update character 1
record_set_mfhd_view character 1 This table is part of Voyager’s Geospatial module.
scan_job_kill character 1 Until we begin using that module, the table will
scan_rule_add character 1 not be useful.
scan_rule_delete character 1 *search_name character 25
scan_rule_update character 1 search_type number
scan_rule_view character 1
GEO_UNITS
GDC_SAVED_SEARCHES The starred field in this table is in UTF-8.
search_id number
browse_find_flag character 1 This table is part of Voyager’s Geospatial module.
browse_scan_flag character 1 Until we begin using that module, the table will
heading_type_filter character 20 not be useful.
hit_count number *unit_name character 25
keyword_headings_flag character 1 unit_type number
keyword_search_type number
limits character 750 GLOBAL_PARM
location_filter character 10 In the SysAdmin client, there’s a Miscellaneous
search_argument character 700 section under Circulation, OPAC Configuration,
search_code character 20 and System. Some of the data on these screens is
search_name character 200 stored in GLOBAL_PARM, some is in
search_option character 20 MISCELLANEOUS. Some data from
search_view character 700 GLOBAL_PARM doesn’t appear in the Voyager
send_search character 700 clients at all.
subdivision_filter character 300
tab_key character 20 The parms are:
AdvanceShortLoan
GDC_SECURITY_LOCS p. 39 AllowCallslipBibSelect (Might be obsolete)
gdc_profile_id AllowCallslipReassign (Might be obsolete)
location_id CALLNOPREFIXSUFFIX (If set to Y, then
852$km are included in
GEO_COORD_TYPE mfhd_master.display_call_no; otherwise not.)

28
CITATION_CALL_SLIP heading_queue_id number
DeletePatronHistFines change_date date
DisplaySubfieldSeparators index_type character 1
EmailFineFeeNotice *new_heading character 330
EmailStatementOfFineFee process_flag character 1
ILLCutOffDays
PACKAGE (Used to enable various optional HEADING_CHANGE_FIELDS
modules) The starred fields in this table are in UTF-8.
ShortLoansIncrement
ShortLoansStart This table has a row for each bib to be changed.
ShortLoansTimeBuffer
StopCRProcessing heading_change_id number
UBPatronUpdate (Obsolete. Deleted with 7.2.2.) rec_id number
demerits change_date date
demeritsdisplay marc_ind1 character 1
saved_records_display1 marc_ind2 character 1
saved_records_display2 marc_tag character 3
saved_records_display3 *new_field character 330
*old_field character 330
parm character 25 rec_type character 1
value character 50
HEADING_CHANGE_QUEUE
HEADING p. 26, 43 This table has a row for each entry in the change
The starred fields in this table are in UTF-8. queue.
heading_id_new number
If a record has not been modified, the heading_id_old number
modify_date is null. heading_queue_id number
rec_id number
heading_id number change_date date
create_date date index_type character 1
*display_heading character 300 process_flag character 1
heading_type character 12 rec_type character 1
index_type character 1
*normal_heading character 300 HEADING_SUBDIVISION p. 26, 43
opacbibs number heading_id number
opacrefs character 5 subdiv_id number
staffbibs number
staffrefs character 5 HEADING_TYPE p. 26, 43
update_date date Most of the data in this table are set by Ex Libris
and cannot be changed by the customer, but the
HEADING_CHANGE staffsuppress can be set in the SysAdmin client at
The starred field in this table is in UTF-8. Search, Heading Filters.

This tables links HEADING_CHANGE_FIELDS The starred fields in this table are in UTF-8.
and HEADING_CHANGE_QUEUE.
*heading_code character 20
There are some extra records in the table. If they heading_type character 12
cause catjob 13 to bomb, change the process_flag *heading_type_desc character 50
to Y. (See Knowledge Base 16384-1315.) index_type character 1
heading_change_id number staffsuppress character 1
heading_id_new number
heading_id_old number HEADING_VW

29
 auth_id number The values of hold_recall_type are H=Hold and
heading_id number R=Recall.
create_date date
display_heading character 300 The request_item_count is the number of items in
heading_type character 50 HOLD_RECALL_ITEMS that could fill this hold
index_name character 30 or recall. If the value is –1, then the hold or recall
normal_heading character 300 has been cancelled.
opacbibs number
reference_type character 20 If the item on hold belongs to another library, the
call_slip_id will be the call_slip in the item’s
HEAD_SUBDIV_LIST home database, not your own.
heading number
subdivision number The patron_group_id is null for UB transactions
where the item is on hold someplace other than
HOLD_RECALL… Tables its home library.
These tables are used for two distinct purposes.
If the item on hold belongs to another library, the
If a hold or recall is placed for a patron, record of HOLD_RECALL record is created when the item
it appears in these tables from the time the hold is discharged to the hold shelf. An available item
or recall is placed. In this case, call_slip_id is notice is sent next time circjob5 runs. The
zero. create_date is the date of the patron’s request, not
the date the HOLD_RECALL is created. The
If a call slip or a UB request is made for a patron, expire_date is set to the date the HOLD_RECALL
record of it appears in these tables for the pick up is created plus the hold_shelf_life set in your
library from the time the item is routed to the pick library’s sys admin settings.
up library. In this case, call_slip_id will not be
zero. A HOLD_RECALL that is not picked up is
archived by circjob6 when the expire_date has
HOLD_RECALL p. 20 passed.
If holding_db_id is zero or null, then the item or
title belongs to your library. In this case, If a record has not been modified, the
call_slip_id will point to a call slip in your modify_date is null.
database. If holding_db_id is neither zero nor
null, the item or title belongs to another library. If you get the message, “Type mismatch in
You can use VOYAGER_DATABASES to find out expression”, when you use this table, see
what library it belongs to. In this case, Appendix A for a solution.
call_slip_id will NOT point to a call slip in your
database. bib_id number
call_slip_id number
When a hold or recall is archived, it is moved create_location_id number
from HOLD_RECALL to create_opid character 10
HOLD_RECALL_ARCHIVE and any items are hold_recall_id number
moved from HOLD_RECALL_ITEMS to holding_db_id number
HOLD_RECALL_ITEM_ARCHIVE. When this modify_location_id number
happens, the hold_recall_id changes. This modify_opid character 10
number is assigned sequentially as records are patron_group_id number
added to HOLD_RECALL and patron_id number
HOLD_RECALL_ARCHIVE. request_group_id number
available_notice_count number
The values of request_level are C=Copy Level available_notice_date date
and T=Title Level. create_date date
expire_date date

30
 hold_recall_type character 1 HOLD_RECALL_ITEM_ARCHIVE p. 21
modify_date date hold_recall_id number
patron_comment character 100 item_id number
pickup_location number hold_recall_status number
request_item_count number hold_recall_status_date date
request_level character 1 hold_recall_type character 1

HOLD_RECALL_ARCHIVE p. 21 HOLD_RECALL_STATS
If you get the message, “Type mismatch in hold_recall_id number
expression”, when you use this table, see patron_stat_id number
Appendix A for a solution.
bib_id number HOLD_RECALL_STATUS p. 20, 21
call_slip_id number hr_status_desc character 25
create_location_id number hr_status_type number
hold_recall_id number
holding_db_id number IMPORT_RULE p. 33, 45
modify_location_id number Data in this table are defined in the SysAdmin
modify_opid character 10 client at Cataloging, Bulk Import Rules, Rules tab.
patron_group_id number auth_dup_profile_id number
patron_id number bib_dup_profile_id number
request_group_id number char_set_id number
available_notice_count number import_rule_id number
available_notice_date date import_rule_po_id number
create_date date library_id number
create_opid character 10 bib_dup_exist character 1
expire_date date bib_to_mfhd character 1
hold_recall_type character 1 cat_review character 1
modify_date date code character 8
patron_comment character 100 create_mfhds_items character 1
pickup_location number create_mfhds_only character 1
request_item_count number create_multi_items character 1
request_level character 1 create_multi_mfhds character 1
ignore_opac_suppress character 1
HOLD_RECALL_ITEMS p. 20 loc_field character 3
For a copy-level hold, there will be a row in loc_ind1 character 1
HOLD_RECALL_ITEMS to identify the specific loc_ind2 character 1
item. loc_subfield character 1
mag_media_field character 3
If the item on the hold shelf belongs to another I- mag_media_ind1 character 1
Share library, the item_id will be the item_id in mag_media_ind2 character 1
the item’s home library, not yours. You can tell mag_media match character 50
what library the item belongs to by checking mag_media_subfield character 1
holding_db_id in the corresponding name character 25
HOLD_RECALL record. order_create character 1
sensitize_field character 3
hold_recall_id number sensitize_ind1 character 1
item_id number sensitize_ind2 character 1
hold_recall_status number sensitize match character 50
hold_recall_status_date date sensitize_subfield character 1
hold_recall_type character 1 suppress_in_opac character 1
queue_position number update_mfhds_items character 1

31
IMPORT_RULE_BIBTOMFHD p. 45 ledger_default number
Data in this table display in the SysAdmin client ledger_field character 3
at Cataloging, Bulk Import Rules, Rules tab. ledger_ind1 character 1
ledger_ind2 character 1
import_rule_id number ledger_subfield character 1
mfhd_field character 3 line_item_type_default number
line_item_type_field character3
IMPORT_RULE_COPY_NUMBER p. 33, 45 line_item_type_ind1 character1
Data in this table display in the SysAdmin client line_item_type_ind2 character1
at Cataloging, Bulk Import Rules, Item line_item_type_subfield character1
Information tab, Copy Numbers button. notes_field character3
notes_ind1 character1
import_rule_copynum_id number notes_ind2 character1
copy_number_field 3 notes_subfield character1
copy_number_subfield 1 one_po_per_bib character 1
copy_number_ind1 1 order_type number
copy_number_ind2 1 piece_field character3
copy_number_start number piece_ind1 character1
copy_number_method number piece_ind2 character1
piece_subfield character1
IMPORT_RULE_PO p. 45 po_number_field character 3
Data in this table display in the SysAdmin client po_number_ind1 character 1
at Cataloging, Bulk Import Rules. po_number_ind2 character 1
po_number_subfield character 1
Earlier versions of import rule mappings are not price_default number
deleted, so watch for obsolete data in this table. price_field character3
price_ind1 character1
account_id number price_ind2 character1
import_rule_po_id number price_subfield character1
location_id_order number requester_field character 3
vendor_id number requester_ind1 character 1
automatic_approval character 1 requester_ind2 character 1
copy_default number requester_subfield character 1
copy_field character3 title_ind1 character1
copy_ind1 character1 title_ind2 character1
copy_ind2 character1 title_no_field character3
copy_subfield character1 title_no_subfield character1
currency_code character3 vendor_ref_field character 3
fiscal_period_default number vendor_ref_ind1 character 1
fiscal_period_field character 3 vendor_ref_ind2 character 1
fiscal_period_ind1 character 1 vendor_ref_subfield character 1
fiscal_period_ind2 character 1
fiscal_period_subfield character 1 INDEX_TYPE p. 43
fund_code character10 index_name character 30
fund_field character3 index_type character 1
fund_ind1 character1
fund_ind2 character1 INSTRUCTOR p. 18
fund_subfield character1 This table is part of reserves.
instruction_field character3 circ_cluster_id number
instruction_ind1 character1 instructor_id number
instruction_ind2 character1 first_name character 40
instruction_subfield character1 last_name character 50

32
 normal_last_name character 50 This is the table that lets you move between a PO
title character 10 and its invoice.

INTERVAL_TYPE If a record has not been modified, the

interval_desc character 25 modify_date is null.
interval_type character 1
create_opid character 10
INVOICE p. 2, 3, 4 inv_line_item_id number
The total field is reliable; the invoice_total is not. invoice_id number
account_id number line_item_id number
create_location_id number update_opid character 10
create_opid character 10 create_date date
invoice_id number edi_ref number
update_location_id number line_price number
update_opid character 10 piece_identifier character 500
vendor_id number prepay_amount number
adjustments_subtotal number quantity number
bill_location number unit_price number
check_number character 40 update_date date
conversion_rate number
currency_code character 3 INVOICE_LINE_ITEM_FUNDS p. 2
edi_ref number copy_id number
expend_date date fund_id number
invoice_create_date date inv_line_item_id number
invoice_date date ledger_id number
invoice_number character 25 allocation_method 1
invoice_quantity number amount number
invoice_status number percentage number
invoice_status_date date split_fund_seq number
invoice_total number
invoice_update_date date INVOICE_NOTE p. 3
line_item_count number invoice_id number
line_item_subtotal number note character 1900
normal_check_number character 40
normal_invoice_number character 25 INVOICE_STATUS p. 3
total number invoice_status number
voucher_number character 25 invoice_status_desc character 25

INVOICE_FUNDS p. 4 INV_LINE_ITEM_NOTES
This table sometimes gets out of synch with inv_line_item_id number
reality. A FullFundRepair will fix this. The invoice_id number
INVOICE_LINE_ITEM_FUNDS table is more note character 1900
reliable.
fund_id number IN_CLAUSE_LIST
invoice_id number member number
ledger_id number
commit_pending number ISSUES_RECEIVED p. 9, 11
commitments number To uniquely identify an issue, you need both
expend_pending number issue_id and component_id.
expenditures number
In the opac_suppressed field, 0=suppressed,
INVOICE_LINE_ITEM p. 2, 3 1=not suppressed.

33
 them. Consequently, the only way to get browse
component_id number statistics for a time period is to take a count at the
copy_id number beginning and end of the period and subtract.
issue_id number CARLI collects historical browse data
item_id number periodically; documentation is at
location_id number http://www.carli.illinois.edu/products-
collapsed character 1 services/i-share/reports/secure/histbrowstat
note character 256
opac_suppressed number The historical_charges field is incremented when
receipt_date date the item is discharged. It includes reserves
charges and short loan charges. It may include
ISSUES_VW transaction counts from your previous ILS. All
This view is dropped in V7.0. CARLI libraries migrated counts from their
previous systems except COD, CSC, IEC, KEN,
This view has a number of quirks and it is not LAC, MMC, MRT, NBY, NPU, ONU, RSH, SFM,
efficient. Consider using the tables directly SIM, SVC, and USF.
instead.
component_id number The reserve_charges field is incremented by each
issue_id number charge while an item is on reserve. It is zeroed
enumchron character 256 out when the item goes off reserve. Reserve
expected_date date charges are also counted in all the ways that
receipt_date date normal charges are counted.
received number
The various enumeration fields are in
ITEM 14, 16, 17, 18, 19, 20, 21, 22, 25, 27, 28, 29, MHFD_ITEM, not ITEM.
41, 44, 47, 48
The perm_location and temp_location fields can The short_loan_charges field is the historical
both be used to link to the location_id in the count of short loans. It is incremented when the
LOCATION table. Remember that there are item is charged. Short loan charges are also
locations in MFHDs as well as items, and that counted in all the ways that normal charges are
Voyager lets you change one without the other. counted.
The locations in ITEM determine the circulation
policies; the location in MFHD_MASTER controls It may be that modify_date is not reset for all item
limiting and the call slip queue. If you want to changes. It seems that giving an item a temp
count materials by location, remember that some location and item type may not reset the date.
of your bibs (e-resources, for example) may have
MFHDs but not items. If a record has not been modified, the
modify_date is null.
The historical_browses count is incremented
whenever an item that is not charged gets
discharged. This happens in these situations: The copy_number field comes from the MFHD
when items picked up from desks in the library 852$t.
are discharged (true browses) and when UB items
are routed around the consortium (not true create_location_id number
browses). So the historical_browses field is not an create_operator_id character 10
accurate count of browses (for libraries that use item_id number
UB), but it still gives a general indication of how item_type_id number
frequently an item is used. media_type_id number
modify_location_id number
By the way, historical_browses is never reset back modify_operator_id character 10
to zero. Browses are not recorded anywhere else perm_location number
in the system and there’s no date associated with temp_item_type_id number

34
 temp_location number To spell out item statuses, link from item_status
copy_number number to the item_status_type field in the
create_date date ITEM_STATUS_TYPE table.
historical_bookings number item_id number
historical_browses number item_status number
historical_charges number item_status_date date
holds_placed number
item_sequence_number number ITEM_STATUS_TYPE p. 28, 48
magnetic_media character 1 item_status_desc character 25
modify_date date item_status_type number
on_reserve character 1
pieces number ITEM_STAT_CODE p. 16, 17, 28, 48
price number Data in this table are defined in the SysAdmin
recalls_placed number client at System, Statistical Categories, Item tab.
reserve_charges number
sensitize character 1 item_stat_id number
short_loan_charges number item_stat_code character 3
spine_label character 25 item_stat_code_desc character 25

ITEM_BARCODE p. 48 ITEM_TYPE p. 28, 46, 48

Before you use this table, consider: Are all your Data in this table are defined in the SysAdmin
items barcoded? What about AV, microforms, or client at System, Item Types.
bound serials?
item_id number item_type_id number
barcode_status number item_type_code character 10
barcode_status_date date item_type_display character 40
item_barcode character 30 item_type_name character 25

ITEM_BARCODE_STATUS p. 48 ITEM_TYPE_MAPPING p. 45
barcode_status_desc character 25 Data in this table are defined in the SysAdmin
barcode_status_type number client at Cataloging, Bulk Import Rules, Mapping
tab.
ITEM_NOTE p. 14, 16, 18, 20, 22, 25, 28, 48
item_id number call_no_hierarchy_id number
item_note character 1000 import_rule_id number
item_note_type number item_type_id number
last_modified date location_id number
marc_item_type character 50
marc_location character 50
ITEM_NOTE_TYPE p. 14, 16, 18, 20, 22, 25, 48
1=regular, 2=charge, 3=discharge ITEM_TYPE_POLICY
note_type number Data in this table are defined in the SysAdmin
note_desc character 20 client at Circulation, Policy Definitions, Items tab.
circ_group_id number
ITEM_STATS p. 16, 17, 28, 48 item_type_id number
item_id number circ_hold_lost_library character 1
item_stat_id number circ_hold_lost_system character 1
date_applied date circ_hold_missing character 1
circ_recall_lost_library character 1
ITEM_STATUS p. 28, 48 circ_recall_lost_system character 1
circ_recall_missing character 1
opac_hold_lost_library character 1

35
 opac_hold_lost_system character 1 operator_id character 10
opac_hold_missing character 1 actual_start_date date
opac_recall_lost_library character 1 current_bulk_num number
opac_recall_lost_system character 1 deleteall_hierarchy_count number
opac_recall_missing character 1 error_record_count number
order_quantity_number number job_status number
reorder_point number job_type number
replace_cost number modify_date date
short_loan character 1 name character 200
parameter_ptr clob
ITEM_VW parameter_string character 2000
This view has a number of quirks and it is not records_deleted number
efficient. Consider using the tables directly records_processed number
instead. records_to_process number
record_type number
The gov_item_type fields are the item’s current scheduled_start_date date
type, in other words, the temp item type, if there
is one, otherwise the item type. Similarly, the JOB_STATUS p. 12
gov_location fields are the item’s temp location, if This table is part of Voyager’s Global Data
there is one, otherwise the perm location. Change rule management functionality.
create_opid character 10
item_id number 0=pending, 1=running, 2=done, 3=kill, 4=killed,
mfhd_id number 5=failed.
barcode character 30
call_no character 300 id number
call_no_type character 1 description character 20
caption character 256
chronology character 80 JOB_TYPE p. 12
create_date date This table is part of Voyager’s Global Data
enumeration character 80 Change rule management functionality.
gov_item_type character 25
gov_item_type_code character 10 1=DBSCAN, 2=GDCPROCESS.
gov_location character 25
gov_location_code character 10 id number
historical_bookings number description character 20
historical_browses number
historical_charges number LCCLASS_VW
holds_placed number This table parses LC class numbers, which makes
media_type character 50 statistics by call number ranges really slick.
media_type_code character 10 Consider the class number, ML410. Class=ML,
normalized_call_no character 300 classnumber=410, firstletter=M,
perm_item_type character 25 longclass=MLbb410. Those b’s are blanks.
perm_item_type_code character 10 Longclass is padded with blanks so that numbers
perm_location character 25 sort nicely. When a class number has a decimal
perm_location_code character 10 point and digits following, these are not included
recalls_placed number in longclass.
year character 20
Since V7.1, this table works correctly for classes
JOB_DATA p. 12 that begin with 3 letters, such as LC law numbers.
This table is part of Voyager’s Global Data
Change rule management functionality.
id number

36
If you want to sort a report (not a query, a report) overcommit character 1
by class, you will have to use the Left function to overcommit_percent number
truncate it to less that 255 characters. overcommit_warn number
overexpend character 1
If you are doing statistics by the first letter of the overexpend_percent number
LC class code, you can easily add a description of overexpend_warn number
the class to your results. Link firstletter in undercommit_percent number
LCCLASS_VW to ClassLetter in LCClassBrief and underexpend_percent number
show the Description field. update_date date

If you are doing statistics by the alphabetic part of LEDGER_LOCATIONS p. 4

the LC class code, you can easily add a ledger_id number
description of the class to your results. Link location_id number
firstletter in LCCLASS_VW to ClassLetters in
LCClassDetailed and show the Description field. LEDGER_NOTE p. 4
ledger_id number
A set of techniques for producing statistics by note character 1900
more precise call number ranges is given in
“Reports with Call Number Ranges: How to LIBRARY p. 27
Request Then and How to Write Them” at Data in this table are defined in the SysAdmin
http://www.carli.illinois.edu/products- client at System, Owning Libraries.
services/i-share/reports/secure/callnumrange
The starred field in this table is in UTF-8.
mfhd_id number
class character 300 library_id number
classnumber number library_display_name character 80
firstletter character 1 library_name character 50
longclass character 300 *nuc_code character 15

LEDGER p. 4 LIBRARY_ADDRESS_DEFAULT
The fiscal_year_id field in LEDGER can be used Data in this table are defined in the SysAdmin
to link to fiscal_period_id in FISCAL_PERIOD client at System, Default Address.
and ROLLOVER_RULES. This isn’t obvious from
the names. address_line1 character 50
address_line2 character 50
If a record has not been modified, the address_line3 character 50
modify_date is the same as the create_date. address_line4 character 50
address_line5 character 50
acq_policy_id number city character 30
create_opid character 10 contact_name character 50
fiscal_year_id number country character 20
ledger_id number email character 50
new_ledger_id number library_name character 50
rule_id number san character 10
update_opid character 10 state_province character 7
commit_freeze date zip_postal character 10
create_date date
expend_freeze date LINE_ITEM… Tables
ledger_name character 40 These tables are part of purchase orders.
new_ledger_name character 40
normal_ledger_name character 40 LINE_ITEM p. 2, 3, 5, 7, 8, 9, 10, 51
normal_new_ledger_name character 4 bib_id number

37
 create_opid character 10 LINE_ITEM_COPY_MFHD_HISTORY p. 6
line_item_id number audit_id number
po_id number copy_id number
update_opid character 10 create_opid character 10
cancel_interval number mfhd_id number
claim_interval number create_date date
create_date date
donor character 50 LINE_ITEM_COPY_STATUS p. 2, 3, 6, 7, 8
edi_ref number Both the line_item_status and the
line_item_number number invoice_item_status field can be interpreted by
line_item_type number linking to the line_item_status field in
line_price number LINE_ITEM_STATUS.
piece_identifier character 50 copy_id number
prepay_amount number item_id number
print_std_num character 2 line_item_id number
quantity number location_id number
requestor character 50 mfhd_id number
rush character 1 invoice_item_status number
standard_num character 50 line_item_status number
unit_price number status_date date
update_date date
vendor_ref_num character 35 LINE_ITEM_FUNDS p. 2
vendor_ref_qual character 3 Remember that a fund_id does not uniquely
vendor_title_num character 25 identify a fund. It’s the combination of fund_id
and ledger_id that uniquely identifies a fund.
LINE_ITEM_BIB_HISTORY p. 5 Consequently, you need to link by both of these
fields when you are linking among the FUND…,
audit_id number PO_FUNDS and LINE_ITEM_FUNDS tables.
bib_id number copy_id number
create_opid character 10 fund_id number
line_item_id number ledger_id number
create_date date amount number
allocation_method 1
LINE_ITEM_COPY p. 3, 8 percentage number
To determine the fund that is being used to prepay number
purchase this item, link to FUND with use_fund prepay_percentage number
linked to fund_id and use_ledger linked to split_fund_seq number
ledger_id.
line_item_id number LINE_ITEM_NOTES p. 8
location_id number line_item_id number
copy_count number po_id number
ship_to_location number note character 1900
use_fund number print_note character 60
use_ledger number
LINE_ITEM_STATUS p. 3
LINE_ITEM_COPY_HISTORY p. 3, 7, 8 line_item_status number
audit_id number line_item_status_desc character 25
copy_id number
inv_line_item_id number LINE_ITEM_TYPE p. 8
line_item_status number line_item_type number
status_date date line_item_type_desc character 25

38
LOADLINK
This table is created as part of a library’s LOCATION_LIMIT
conversion into Voyager. It has no use after that. Data in this table are defined in the SysAdmin
bibid number client at System, Location Limit Groups.
libid number
originalid character 25 This table is used for WV and client searching to
itemtype character 2 control location limiting in searches.

LOCATION p. 4, 11, 17, 20, 21, 22, 27, 28, 29, 31, location_limit_id number
32, 36, 37, 38 ,39, 42, 44, 45, 48, 49, 50 limit_code character 10
Data in this table are defined in the SysAdmin limit_name character 60
client at System, Locations. suppress_in_opac character 1

Don’t use mfhd_count in statistics. It’s not at all LOCATION_LIMIT_LOCS

reliable. Data in this table are defined in the SysAdmin
client at System, Location Limit Groups.
The location_opac field is not used for anything.
This table is used for WV and client searching to
library_id number control location limiting in searches.
location_id number
location_code character 10 location_id number
location_display_name character 60 location_limit_id number
location_name character 25
location_opac character 1 LOCATION_PHONE
location_spine_label character 25 Data in this table are defined in the SysAdmin
mfhd_count number client at System, Locations, Address tab.
suppress_in_opac character 1
address_id number
LOCATION_ADDRESS phone_id number
Data in this table are defined in the SysAdmin phone_number character 25
client at System, Locations, Address tab. phone_type number

address_id number LOGIN_AUDIT_TRAIL p. 35

location_id number login_user_id character 10
address_line1 character 50 operator_id character 10
address_line2 character 50 workstation_id character 40
address_line3 character 50 invalid_attempt_time date
address_line4 character 50 lockout_counter number
address_line5 character 50 lockout_time date
bill_to_address character 1
campus_address character 1 MAINTENANCE p. 30
circ_desk_address character 1 This table is part of the media booking module.
city character 30 create_location_id number
contact_name character 50 create_opid character 10
country character 20 equip_id number
email character 50 maint_id number
other_address character 1 update_location_id number
san character 10 update_opid character 10
ship_to_address character 1 create_date date
state_province character 7 date_in date
street_address character 1 date_out date
zip_postal character 10 update_date date

39
 map_index_id number
MAINTENANCE_DETAIL p. 30 *east_longitude_display character 1
This table is part of the media booking module. east_longitude_normal number
maint_dtl_id number *north_latitude_display character 1
maint_id number north_latitude_normal number
maint_type_id number *south_latitude_display character 1
detail_comment character 100 south_latitude_normal number
*west_longitude_display character 1
MAINTENANCE_NOTE p. 30 west_longitude_normal number
This table is part of the media booking module.
maint_id number MAP_INDEX_G_RING
op_id character 10 The starred fields in this table are in UTF-8.
note character 2000
update_date date This table is part of Voyager’s Geospatial module.
Until we begin using that module, the table will
MAINTENANCE_QUEUE not be useful.
This table is at least a partial record of when
indexes were regenerated for this database. map_index_id number
The causation_comment field is always set to *g_ring_latitude character 12
“upgrade” which isn’t true. Routine index regens g_ring_latitude_normal number
should create records with maintenance_code set *g_ring_longitude character 12
to K (=Keyword) and T (=TurboBibText). Other g_ring_longitude_normal number
values are H=Heading, M=MFHDIndex, seqnum number
E=BibTextTable, B=BibLeftAnchored,
G=Geospatial, F=FacetedBib (part of geospatial), MAP_INDEX_SCALE
S=StatSampler, X=Bib856Links, Y=Auth856Links, This table is part of Voyager’s Geospatial module.
Z=MFHD856Links. Until we begin using that module, the table will
not be useful.
The enqueue_date is the date when Voyager map_index_id number
somehow determined that an index regen was map_scale number
needed. The process_date is the date on which scale_type character 1
the regen occurred.
causation_comment character 2000 MARC… Tables
enqueue_date date These tables parse out some of the fixed fields
maintenance_code character 1 from bibliographic records. Remember that some
process_date date of the fixed fields are also available in BIB_INDEX
release_processed character 30 and BIB_TEXT. Voyager uses the record type and
bib level fields to decide which records are
MAINTENANCE_TYPE p. 30 included in each view.
This table is part of the media booking module.
maint_type_id number For each MARC* table, the Access field name and
type character 50 the label from a WorldCat display are given.
type_code character 10
MARCBOOK_VW
MAP_INDEX Includes these record type/bib level pairs: aa, ac,
The starred fields in this table are in UTF-8. ad, am, ha, hc, hd, hm, ta, tc, td, tm.
audience: Audn 008 byte 22
This table is part of Voyager’s Geospatial module. biography: Biog 008 byte 34
Until we begin using that module, the table will conferencepub: Conf 008 byte 29
not be useful. governmentpub: GPub 008 byte 28
itemform: Form 008 byte 23
bib_id number literaryform: LitF 008 byte 33

40
 bib_id number
audience character 1 MARCSERIAL_VW
biblevel character 1 Includes these record type/bib level pairs: ab, as,
bibtype character 1 bb, bs, cb, cs, db, ds, eb, es, fb, fs, gb, gs, hb, hs, ib,
biography character 1 is, jb, js, kb, ks, mb, ms, nb, ns, ob, os, pb, ps, rb,
conferencepub character 1 rs, tb, ts
governmentpub character 1 conferencepub: Conf 008 byte 29
itemform character 1 entirenature: EntW 008 byte 24
literaryform character 1 frequency: Freq 008 byte 18
governmentpub: GPub 008 byte 28
MARCCOMPUTER_VW itemform: Form 008 byte 23
Includes these record type/bib level pairs: ma, originalform: Orig 008 byte 22
mc, md, mm regularity: Regl 008 byte 19
audience: Audn 008 byte 22 type: SrTp 008 byte 21
filetype: File 008 byte 26 bib_id number
governmentpub: GPub 008 byte 28 biblevel character 1
bib_id number bibtype character 1
audience character 1 conferencepub character 1
biblevel character 1 entirenature character 1
bibtype character 1 frequency character 1
filetype character 1 governmentpub character 1
governmentpub character 1 itemform character 1
originalform character 1
MARCMAP_VW regularity character 1
Includes these record type/bib level pairs: ea, ec, type character 1
ed, em, fa, fc, fd, fm
cartographictype: CrTp 008 byte 25 MARCVISUAL_VW
governmentpub: GPub 008 byte 28 Includes these record type/bib level pairs: ga, gc,
indexed: Indx 008 byte 31 gd, gm, ka, kc, kd, km, na, nc, nd, nm, oa, oc, od,
projection: Proj 008 bytes 22-23 om, ra, rc, rd, rm
bib_id number audience: Audn 008 byte 22
biblevel character 1 governmentpub: GPub 008 byte 28
bibtype character 1 runningtime: Time 008 bytes 18-20
cartographictype character 1 technique: Tech 008 byte 34
governmentpub character 1 visualtype: TMat 008 byte 33
indexed character 1 bib_id number
projection character 2 audience character 1
biblevel character 1
MARCMUSIC_VW bibtype character 1
Includes these record type/bib level pairs: ca, cc, governmentpub character 1
cd, cm, da, dc, dd, dm, ia, ic, id, im, ja, jc, jd, jm runningtime character 3
audience: Audn 008 byte 22 technique character 1
compositionform: Comp 008 bytes 18-19 visualtype character 1
itemform: Form 008 byte 23
musicformat: FMus 008 byte 20 MARKED_ISSUE p. 10
bib_id number component_id number
audience character 1 copy_id number
biblevel character 1 issue_id number
bibtype character 1 location_id number
compositionform character 2 marked_id number
itemform character 1 op_id character 10
musicformat character 1 subscription_id number

41
 mark_date date security character 1
mark_reason number security_view character 1
marked_comment character 250 system_definitions character 1
system_defs_view character 1
MARKED_LINE_ITEM p. 7
copy_id number MASTER_SECURITY_LOCS p. 49
line_item_id number Data in this table are defined in the SysAdmin
location_id number client at Security, Master Profiles, Locations tab.
marked_id number
op_id character 10 location_id number
mark_date date master_profile_id number
mark_reason number
marked_comment character 250 MEDIA… Tables
These tables are part of the Voyager media
MARK_REASON p. 7, 10 scheduling module.
Data in this table are defined in the SysAdmin
client at Acquisitions, Mark Reasons. MEDIA_BOOKING_EXCEPTION
equip_id number
mark_reason_id number equip_sts_type_id number
claim_type number item_id number
mark_reason_name character 25 location_id number
media_booking_exception_id number
MASTER_OPERATOR p. 49 media_room_id number
Data in this table are defined in the SysAdmin op_id character 10
client at Security, Master Profiles, Operator tab patron_id number
and display at Operator, Current Profiles. room_sts_type_id number
action character 1
master_profile_id number item_status_type number
operator_id character 10 update_date date

MASTER_PROFILE p. 49 MEDIA_BOOKING_EXCEPTION_TYPE
Data in this table are defined in the SysAdmin media_booking_exception_id number
client at Security, Master Profiles, and display at media_booking_exception character 25
Operator, Current Profiles
. MEDIA_BOOKING_TYPE
master_profile_id number media_booking_type_id number
acq_policies character 1 type character 20
acq_policies_view character 1
cat_policies character 1 MEDIA_OPERATOR
cat_policies_view character 1 patron_id number
circ_policies character 1 update_location_id number
circ_policies_view character 1 update_opid character 10
cluster_create character 1 status character 1
cluster_delete character 1 update_date date
cluster_edit character 1
cluster_view character 1 MEDIA_POLICY_DELIVERY_CALENDAR
currency_tables character 1 calendar_id number
currency_view character 1 media_schedule_policy_id number
master_profile_name character 25
media_policies character 1 MEDIA_POLICY_EQUIPMENT_MATRIX
patron_group_edit character 1 equip_type_id number
patron_group_view character 1 matrix_id number

42
 media_schedule_policy_id number warning_interval number
patron_group_id number warning_interval_scale character 1
settings_id number
MEDIA_POLICY_ITEM_MATRIX
MEDIA_POLICY_EQUIPMENT_TYPE matrix_id number
equip_type_id number media_schedule_policy_id number
media_schedule_policy_id number media_type_id number
cleanup_time number patron_group_id number
replacement_default number settings_id number
request_equip_using_opac character 1
setup_time number MEDIA_POLICY_ITEM_SETTINGS
settings_id number
MEDIA_POLICY_EQUIP_SETTINGS booking_interval character 1
settings_id number booking_period_max number
booking_interval character 1 booking_renew number
booking_period_max number booking_renew_count number
booking_renew number can_deliver character 1
booking_renew_count number can_pickup character 1
can_deliver character 1 fine_grace_period number
can_pickup character 1 fine_interval character 1
fine_grace_period number fine_max number
fine_interval character 1 fine_rate_delivery number
fine_max number fine_rate_pickup number
fine_rate_delivery number recall_for_booking character 1
fine_rate_pickup number settings_name character 40
settings_name character 40 usage_fee number
usage_fee number usage_rate number
usage_rate number usage_rate_interval character 1
usage_rate_interval character 1 usage_rate_period number
usage_rate_period number
MEDIA_POLICY_LOCATION
MEDIA_POLICY_GROUP location_id number
media_schedule_policy_id number media_schedule_policy_id number
block_interval number print_location_id number
block_interval_scale character 1 booking character 1
cancel_unclaimed_booking number collect_fines character 1
charge_warning_interval number courtesy_discharge_equipment char
charge_warning_interval_scale character 1 courtesy_discharge_item character 1
delivery_count_closed character 1 courtesy_discharge_room_key char
delivery_count_closed_fees character 1 delivery character 1
overdue_conflict_list_interval number delivery_slip_print character 1
overdue_first_interval number delivery_time number
overdue_lost_fee character 1 equip_restricted character 1
overdue_lost_fee_amt number fly_item_location number
overdue_lost_interval number fly_item_suppress character 1
overdue_lost_max_fine character 1 fly_item_type number
overdue_notice_count number item_shelving_interval character 1
overdue_notice_interval number item_shelving_period number
overdue_renew character 1 item_transit_period number
pickup_count_closed character 1 pickup character 1
pickup_count_closed_fees character 1 pickup_slip_print character 1
schedule_policy character 40 print_confirmation character 1

43
 return_time number can_book character 1
settings_name character 40
MEDIA_POLICY_MEDIA_TYPE usage_fee number
media_schedule_policy_id number usage_rate number
media_type_id number usage_rate_interval character 1
replacement_default number usage_rate_period number
request_item_using_opac character 1
MEDIA_POLICY_ROOM_TYPE
MEDIA_POLICY_PATRON_GROUP media_room_type_id number
media_schedule_policy_id number media_schedule_policy_id number
patron_group_id number can_deliver character 1
booking_limit character 1 room_scheduled character 1
booking_max number
cancelled_booking_limit character 1 MEDIA_POLICY_ITEM_STATUS_ALERT
cancelled_booking_max number item_settings_id number
early_pickup number alert_item_status_type number
early_pickup_interval character 1
equip_booking_limit character 1 MEDIA_ROOM p. 31, 32
equip_booking_max number create_location_id number
fees_apply character 1 create_opid character 10
fines_apply character 1 location_id number
item_booking_limit character 1 media_room_id number
item_booking_max number media_room_type_id number
late_return_limit character 1 update_location_id number
late_return_max number update_opid character 10
outstanding_balance_limit character 1 capacity number
outstanding_balance_max number create_date date
overdue_notice_apply character 1 historical_bookings number
overlapping_bookings character 1 room_name character 40
request_patron_using_opac character 1 room_name_normalized character 40
unclaimed_booking_limit character 1 room_no character 15
unclaimed_booking_max number room_no_normalized character 15
storage character 1
MEDIA_POLICY_PICKUP_CALENDAR update_date date
calendar_id number
media_schedule_policy_id number MEDIA_ROOM_DETAILS p. 32
media_room_details_id number
MEDIA_POLICY_ROOM_CALENDAR media_room_dtl_type_id number
calendar_id number media_room_id number
media_schedule_policy_id number room_dtl character 100

MEDIA_POLICY_ROOM_MATRIX MEDIA_ROOM_DETAIL_TYPE p. 32
matrix_id number media_room_dtl_type_id number
media_room_type_id number repeatable character 1
media_schedule_policy_id number type character 50
patron_group_id number type_code character 10
settings_id number
MEDIA_ROOM_KEY
MEDIA_POLICY_ROOM_SETTINGS media_room_id number
settings_id number media_room_key_id number
booking_interval character 1 key_no character 15
booking_period_max number

44
MEDIA_ROOM_NOTES p. 32 confirm_no character 77
media_room_id number create_date date
media_room_note_type_id number operator_delivery number
op_id character 10 operator_pickup number
note character 2000 sched_comment character 1000
update_date date update_date date
wizard character 1
MEDIA_ROOM_NOTE_TYPE p. 32
media_room_note_type_id number MEDIA_SCHEDULE_ARCHIVE
type character 15 create_location_id number
create_opid character 10
MEDIA_ROOM_STATUS p. 32 media_booking_type_id number
media_room_id number media_schedule_id number
media_room_sts_type_id number media_schedule_policy_id number
op_id character 10 patron_group_id number
note character 100 patron_id number
update_date date patron_id_picked_up number
staging_location_id number
MEDIA_ROOM_STATUS_TYPE p.32 update_location_id number
media_room_sts_type_id number update_opid character 10
block_booking character 1 admin_booking character 1
display_priority number booking_cleanup number
message character 50 booking_end date
sts_type character 40 booking_result number
warn_on_booking character 1 booking_setup number
booking_start date
MEDIA_ROOM_TYPE p. 32 confirm_date date
media_room_type_id number confirm_no character 77
equip_storage character 1 create_date date
type character 50 operator_delivery number
type_code character 10 operator_pickup number
sched_comment character 1000
MEDIA_SCHEDULE p. 29 update_date date
create_location_id number wizard character 1
create_opid character 10
media_booking_type_id number MEDIA_SCHEDULE_EQUIPMENT p. 29
media_schedule_id number count_id number
media_schedule_policy_id number equip_id number
patron_group_id number equip_type_id number
patron_id number fine_fee_id number
patron_id_picked_up number location_id number
staging_location_id number media_schedule_id number
update_location_id number media_schedule_trans_type_id number
update_opid character 10 op_id character 10
admin_booking character 1 fulfill_item character 1
booking_cleanup number in_room character 1
booking_cleanup_date date update_date date
booking_end date
booking_setup number MEDIA_SCHEDULE_EQUIP_ARCHIVE
booking_setup_date date count_id number
booking_start date equip_id number
confirm_date date equip_type_id number

45
 fine_fee_id number room_key_id number
location_id number trans_location_id number
media_schedule_id number capacity_needed number
media_schedule_trans_type_id number capacity_operator number
op_id character 10 update_date date
fulfill_item character 1
in_room character 1 MEDIA_SCHEDULE_ROOM_ARCHIVE
update_date date count_id number
fine_fee_id number
MEDIA_SCHEDULE_FINE location_id number
fine_fee_id number media_room_id number
media_schedule_id number media_room_type_id number
media_schedule_id number
MEDIA_SCHEDULE_FINE_ARCHIVE media_schedule_trans_type_id number
fine_fee_id number op_id character 10
media_schedule_id number room_key_id number
trans_location_id number
MEDIA_SCHEDULE_ITEM p. 29 capacity_needed number
bib_id number capacity_operator number
count_id number update_date date
fine_fee_id number
item_id number MEDIA_SCHEDULE_TRANS_TYPE
location_id number media_schedule_trans_type_id number
media_schedule_id number type character 15
media_schedule_trans_type_id number
media_type_id number MEDIA_SECURITY_LOCATION
mfhd_id number location_id number
op_id character 10 media_profile_id number
update_date date
MEDIA_SECURITY_OPERATOR
MEDIA_SCHEDULE_ITEM_ARCHIVE media_profile_id number
bib_id number operator_id character 10
count_id number
fine_fee_id number MEDIA_SECURITY_PROFILE
item_id number media_profile_id number
location_id number booking_add character 1
media_schedule_id number booking_cancel character 1
media_schedule_trans_type_id number booking_charge character 1
media_type_id number booking_discharge character 1
mfhd_id number booking_renew character 1
op_id character 10 booking_update character 1
update_date date booking_view character 1
booking_view_historical character 1
MEDIA_SCHEDULE_ROOM p. 29 change_discharge_date character 1
count_id number equip_add character 1
fine_fee_id number equip_booked_move character 1
location_id number equip_delete character 1
media_room_id number equip_maint_add character 1
media_room_type_id number equip_maint_delete character 1
media_schedule_id number equip_maint_update character 1
media_schedule_trans_type_id number equip_maint_view character 1
op_id character 10 equip_update character 1

46
 equip_view character 1 *record_segment character 300
fees_add character 1 seqnum number
fees_adjust character 1
fees_pay character 1 MFHD_HISTORY
item_add character 1 There’s an error in some versions of the E-R
item_delete character 1 diagrams. Action_type_id has a value between 1
item_update character 1 and 6 and it is interpreted by linking to the
item_view character 1 ACTION_TYPE table.
media_profile_name character 25
override_item_block character 1 When a MFHD is deleted, its MFHD_HISTORY
override_other_block character 1 records are deleted too.
override_patron_block character 1
patron_add character 1 The encoding_level and suppress_in_opac are the
patron_counters character 1 values after the transaction.
patron_delete character 1
patron_update character 1 action_type_id number
patron_view character 1 location_id number
room_add character 1 mfhd_id number
room_delete character 1 operator_id character 10
room_update character 1 action_date date
room_view character 1 encoding_level character 1
suppress_in_opac character 1
MEDIA_TYPE p. 29, 48
media_type_id number MFHD_ITEM p. 14, 27, 28, 41, 48
type character 50 The chron field comes from serials check-in. It
type_code character 10 will match the value in enumchron in the
SERIAL_ISSUES table.
MFHDBLOB_VW
This view does not work for MFHDs longer than The item_enum field comes from the MFHD
4000 characters, so the GetMfhdBlob function is 853/863 interaction.
more reliable.
mfhd_id number item_id number
marc_record character 4000 mfhd_id number
caption character 256
MFHDHISTORY_VW chron character 80
create_location_id number freetext character 256
create_operator_id character 10 item_enum character 80
mfhd_id number year character 20
update_location_id number
update_operator_id character 10 MFHD_MASTER p. 6, 27, 47, 48
create_date date The starred fields in this table are in UTF-8.
update_date date
Call_no_type is usually the same as the 852 first
MFHD_DATA p. 48 indicator, but there are exceptions. If there’s no
The starred field in this table is in UTF-8. 852$h, call_no_type will be blank. If the indicator
shows that the call number should be LC, Dewey,
When you are searching record_segment, it is SuDoc, or NLM, but the call number in 852$h
helpful to know that CHR(31) is the subfield cannot be parsed by Voyager according to its
delimiter, CHR(30) is the end of field delimter, rules for the class scheme, then call_no_type will
and CHR(29) is the end of record delimiter. be set to 8. If the 852 first indicator is 7 and
subfield $2 is not a classification scheme that
mfhd_id number Voyager recognizes, then call_no_type will be set

47
to 8. If the 852 first indicator is 7 and subfield $2 is report) you will need to use the Left function to
empty, then call_no_type will be set to blank. cut them to fewer than 255 characters.

For most libraries, the display_call_no includes If a record has not been modified, the
852 subfields $k, $h, $i, and $m in that order. The modify_date is null.
normalized_call_no contains only $h, $i, and $m.
Since call number prefixes are in 852$k, you’ll export_ok_location_id number
find them only in display_call_no. However, export_ok_opid character 10
when your library came up on Voyager, a location_id number
decision may have been made not to include 852 mfhd_id number
$k and $m. You can see this decision in the call_no_type character 1
GLOBAL_PARM table, but you can’t see it in the create_date date
SysAdmin client and you can’t change your mind. *display_call_no character 300
CARLI libraries IIT and TIU do not have 852 $k encoding_level character 1
and $m in display_call_no and export_date date
normalized_call_no. export_ok character 1
export_ok_date date
Generally, call numbers are sorted by *field_007 character 23
normalized_call_no. However, in staff client *field_008 character 32
searches with location limiting, the sort is by *normalized_call_no character 300
display_call_no. record_status character 1
record_type character 1
The value of display_call_no is NULL when there source_module character 1
is no 852$h. The value of normalized_call_no is suppress_in_opac character 1
NULL when 1) there is no 852$h, or 2) there is an update_date date
852$h but it’s empty, or 3) 852 Ind1=blank, or 4)
852$h cannot be parsed by Voyager according to MISCELLANEOUS
the rules for the classification indicated by Ind1. In the SysAdmin client, there’s a Miscellaneous
section under Circulation, OPAC Configuration,
For Dewey numbers, normalized_call_number and System. Some of the data on these screens is
begins with the Dewey class (including the stored in MISCELLANEOUS, some is in
decimal), one space, followed by the book GLOBAL_PARM. Some data in
number, which may have spaces embedded. For MISCELLANEOUS doesn’t appear in the
LC numbers, normalized_call_number begins Voyager clients at all.
with the class code, followed by the whole
number portion of the class code right justified in For the auto_retrieve_system field, N=ARS is not
a 5-character field. If the class code includes available, Y=ARS is available and only the item
decimals, the decimal digits follow (without the barcode is exported, C=ARS is available and the
decimal point). Then comes some spaces, item barcode, call#, author, and title are exported.
followed by the rest of the book number, which
may include embedded space. Examples using authreadonly character 1
carets to show spaces: KFH1396.2 = KFH^13962, auto_retrieve_system character 1
F868=F^^868, DA5=DA^^^^5. bibreadonly character 1
call_slip_item_required character 1
Remember that there are locations in ITEM as custom_1 character 1
well as MFHD_MASTER, and that Voyager lets databaselanguage character 30
you change one without the other. The locations distribution_patron_id_retain char 1
in ITEM determine the circulation policies; the media_patron_id_retain character 1
location in MFHD_MASTER controls limiting. mfhdreadonly character 1
on_shelf_hold character 1
If you want to sort by display_call_no or opac_item_sort character 1
normalized_call_no in a report (not a query, a patron_expire_date date

48
 patron_expire_offset character 5
patron_id_retain character 1 MONO_SUPPLIER_REPORT p. 7
patron_purge_date date audit_id number
patron_purge_offset character 5 claim_id number
ubpaging character 1 action_date date
unique_id_field character 6 action_quantity number
unique_id_offset number edi_ref number
use_default_policy character 1 note character 512
report_date date
The MONO_CLAIM Tables report_type number
A claim is uniquely identified by copy_id,
claim_thread, and claim_id. MY_OPAC_DB
db_id number
The claim_count tells you which claim this is patron_id number
(first, second, etc.). For the most recent claim,
claim_status=1; otherwise claim_status=0. MY_OPAC_PREFERENCES
patron_id number
The claim_type may be interpreted using the search_preferences character 50
CLAIM_TYPES table.
NALCLASS_VW
The claim_date is the date when the order should If you want to sort a report (not a query, a report)
be claimed. If it has been overridden, the new by longclass, you will have to use the Left
date is in override_claim_date. function to truncate it to less that 255 characters.
mfhd_id number
MONO_CLAIM p. 7 class character 3
claim_id number longclass character 300
copy_id number
op_id character 10 NLMCLASS_VW
vendor_id number This table parses NLM class numbers, which
claim_count number makes statistics by call number ranges really slick.
claim_date date The parsing algorithm is the same one used for
claim_status number LC numbers. Consider the class number, QS110.
claim_thread number Class=QS, classnumber=110, firstletter=Q,
claim_type number longclass=QSbb110. Those b’s are blanks.
edi_ref number Longclass is padded with blanks so that numbers
note character 256 sort nicely. Be warned that this table does not
override_claim_date date work correctly for classes that begin with 3 letters,
such as the 19th century class schedule.
MONO_CLAIM_ARCHIVE
claim_id number If you want to sort a report (not a query, a report)
copy_id number by class, you will have to use the Left function to
op_id character 10 truncate it to less that 255 characters.
vendor_id number
archive_date date A set of techniques for producing statistics by
claim_count number more precise call number ranges is given in
claim_date date “Reports with Call Number Ranges: How to
claim_status number Request Then and How to Write Them” at
claim_thread number http://www.carli.illinois.edu/products-
claim_type number services/i-share/reports/secure/callnumrange
edi_ref number
note character 256 mfhd_id number
override_claim_date date class character 300

49
 classnumber number suppress_in_opac character 1
firstletter character 1 voucher_end number
longclass character 7 voucher_last_used number
voucher_prefix character 4
NOTE_TYPE p. 23 voucher_start number
This table is used with PATRON_NOTES.
note_desc character 25 OPAC_FORM_DATABASES
note_type number Data in this table are defined in the SysAdmin
client at OPAC Configuration, Request Forms,
NO_FILL_REASON p. 14, 41 Select Form tab.
Data in this table are defined in the SysAdmin
client at Call Slips, No-Fill Reasons. db_id number
form_id number
This table is part of call slip processing. db_code character 8

reason_id number OPAC_FORM_FIELDS

reason_code character 10 Data in this table are defined in the SysAdmin
reason_desc character 50 client at OPAC Configuration, Request Forms,
suppress character 1 Data tab.

OLDYALECLASS_VW In opac_change, 1=No edit/no display, 2=No

This table parses call numbers in a Yale edit/display, 3=Editable.
University-specific classification. It’s not useful to
us. form_id number
mfhd_id number clio_tag character 20
class character 6 field_label character 20
field_required character 1
OPAC_CHANGE_TYPE field_sequence number
opac_change_desc character 25 mapping character 10
opac_change_type number opac_change number

OPAC_CIRC_SETTINGS OPAC_FORM_PATRON_GROUP
Data in this table are defined in the SysAdmin Data in this table are defined in the SysAdmin
client at OPAC Configuration, Patron Self- client at OPAC Configuration, Request Forms,
registration. Patron Group tab.

patron_purge_period number form_id number

self_reg_dflt_patron_grp number patron_group_id number

OPAC_FORM OPAC_FORM_REQUEST_FILE
Data in this table are defined in the SysAdmin bib_id number
client at OPAC Configuration, Request Forms. form_id number
form_id number item_id number
blank_form character 1 mfhd_id number
email character 100 patron_group_id number
form_code character 10 patron_id number
form_name character 40 request_id number
form_type character 1 date_requested date
instructions character 1000 email_text character 2000
login character 15 expire_date date
output_type character 1 free_text1 character 100
password character 15 free_text2 character 100

50
 free_text3 character 100 type and bib level of the bibs: am=books,
free_text4 character 100 as=magazines/journals, gm=films/videos,
free_text5 character 100 c?=scores, j?=music recordings, i?=spoken word
free_text6 character 100 recordings, e?=maps, m?=computer files, o?=kits,
note character 100 rm=3D objects.
voucher_number number
The search_string field has the search argument
OPAC_FORM_TYPE (e.g. GONE WITH THE WIND), which is often
Data in this table are defined in the SysAdmin preceded by a search code. You can look up a
client at OPAC Configuration, Request Forms. search code in the SEARCHPARM table.

form_type character 1 The search_tab field has values of 1=quick search,

form_type_desc character 25 2=guided keyword, 3=course reserves.

OPAC_MESSAGES The values of the client_type field should be

line_number number W=Web Voyage, G=Web Voyage, Z=Z39.50, and
opac_line character 70 A=ASCII OPAC (which is no longer supported by
tab_number number Ex Libris.) However, bug 88568 in Voyager
2001.2 says that other values may be found here
OPAC_SEARCH_LOG that oughtn’t.
When OPAC logging is turned on in Voyager,
Web Voyage searches done against your database session_id character 16
are logged in this table and in BIB_USAGE_LOG. client_ip character 40
The table is documented in the Voyager Technical client_type character 1
Users Guide. The values are not completely dbkey character 100
consistent, so try to find what you want in several hits number
ways. Here are some additional comments: hyperlink character 1
index_type character 1
The client_ip field is the IP address of one of limit_flag character 1
CARLI’s Web Voyage servers, not the user's limit_string character 250
workstation, so it's not very useful. However, at redirect_flag character 1
other Voyager sites it might be the address of the relevance character 1
workstation. search_date date
search_string character 250
The index_type field has values of A=Authority search_tab character 1
search, B=Browse, K=Keyword, and L=Left- search_type character 25
anchored, but the field is often blank or null at stat_string character 15
times when search_string or search_type indicate
an authority, browse, keyword, or left-anchored OPERATOR p. 35, 36, 37, 38, 39
search. CARLI has not allowed access to this table by
library staff because operator passwords are
The limit_flag field is set to Y or N. Usually, if stored here. Remember that operator_id is a text
limit_flag is N, then limit_string is null, but there field, not a number. If you choose operator_id’s
are exceptions, so think twice about which field that are reasonably mnemonic, you can probably
you trust. get by without the operator’s name, which is the
most useful field in this table. File a work
For browse searches, hits=-1. request if you need other information from this
table.
The limit_string field lists the limits were in effect
for a search: DATE, LANG, LOCA, MEDI Data in this table are defined in the SysAdmin
(medium), PLAC (place), STAT (status), and client at Security, Operator Profiles, Operator tab.
TYPE. The values following TYPE are the record

51
If a record has not been modified, the in this field or with dates before today’s date are
modify_date is the same as the create_date. not suspended.

create_opid character 10 If a record has not been modified, the

modify_opid character 10 modify_date is the same as the create_date.
operator_id character 10
create_date date In name_type, 1=personal name, 2=institutional
first_name character 25 name.
invalid_login_time date
last_name character 25 The rest of the comments about this table are
lockout_counter number relevant only for sites that use UB.
lockout_time date
manual_expire character 1 Patrons affiliated with your library have db_id=0.
middle_initial character 1 Stub patrons have a db_id greater than 1. Link
modify_date date db_id to VOYAGER_DATABASES to find the
never_expire character 1 patron’s affiliation.

OPERATOR_PASSWORD p. 35 Records for patrons affiliated with another library

operator_id character 10 are either stub records or child records. Stub
password character 1000 records have modify_operator_id=’SYS-UB’; they
password_date date are deleted nightly by circjob29 when they are no
longer needed. Child records have been modified
ORDER_TYPES by staff at your library, so the modify_operator_id
The values in this table are set by Ex Libris and is the ID of one of your staff; they are deleted
cannot be changed by the customer. In the nightly by circjob29 when they are no longer
SysAdmin client, they figure in Acquisitions, needed AND their purge_date has passed.
Policy Definitions, Vendor Policies tab and CARLI runs a script right before circjob29 runs to
Cataloging, Bulk Import Rules. changes children back to stubs so that they can be
order_type number deleted if they are no longer needed.
order_type_desc character 25
If you requested an SSN Purge from CARLI, the
PATCH_REGISTRY following fields may have been reset to zero at
This table can tell you when your Voyager the time of the purge: claims_return_ub,
upgrades were done. current_charges_ub, historical_charges_ub,
historical_requests_ub, lost_items_ub,
patch_opid character 30 requests_ub, self_shelved_ub, total_fees_due_ub.
patch_date date
patch_file character 30 The current_charges_ub and requests_ub
patch_status character 30 counters are reliable since V7.1.
release_processed character 30
The counters, historical*, lost_items,
PATRON p. 11, 14, 16, 20, 22, 23, 24, 29, 40, 41 claims_return, self_shelved, etc., may have been
The items_recalled field is the number of items initialized when your library migrated from your
currently charged to this patron which have been previous system to Voyager. The CARLI libraries
recalled for another patron. that migrated in 2002 initialized
historical_charges, claims_return, self_shelved,
For privacy reasons, avoid including SSN in and lost_items, although lost_items has since
reports. If you print reports with the SSN, be sure been reset. The CARLI libraries that migrated in
to dispose of them properly. 2012 initialized historical_charges.

The suspension_date is the date on which a counter_reset_oper_id character 10

patron’s suspension ends. Patrons with nothing create_operator_id character 10

52
db_id number self_shelved_ub number
institution_id character 30 sms_number character 50
media_counter_reset_opid character 10 ssan character 11
modify_location_id number suspension_date date
modify_operator_id character 10 title character 20
normal_institution_id character 30 total_demerits number
patron_id number total_demerits_due_ub number
patron_id_ub number total_fees_due number
birth_date date total_fees_due_ub number
cancelled_bookings number unclaimed_bookings number
claims_return number unclaimed_short_loans number
claims_return_ub number
counter_reset_date date PATRON_ADDRESS p. 23
create_date date The values of the address_type field are:
current_bookings number 1=permanent address, 2=temporary address,
current_call_slips number 3=email address.
current_charges number
current_charges_ub number Ex Libris says that type 2 addresses are not copied
current_hold_shelf number into stub patron records, but this seems to be true
current_short_loans number only sometimes.
department character 50
expire_date date The value of address_status is H=hold, N=no-
first_name character 50 hold.
historical_bookings number
historical_call_slips number When a patron record is updated by a batch
historical_charges number patron load, all its addresses are deleted and re-
historical_charges_ub number added. Consequently, the values in address_id
historical_distributions number grow faster than the _id fields in other patron
historical_requests_ub number tables.
historical_short_loans number
holds_placed number address_id number
home_location number modify_operator_id character 10
items_recalled number patron_id number
last_name character 50 address_line1 character 100
late_media_returns number address_line2 character 100
lost_items number address_line3 character 100
lost_items_ub number address_line4 character 100
major character 50 address_line5 character 100
media_counter_reset_date date address_status character 1
middle_name character 50 address_type number
modify_date date city character 40
name_type number country character 20
normal_first_name character 50 effect_date date
normal_last_name character 50 expire_date date
normal_middle_name character 50 modify_date date
note_count number protect_address character 1
patron_pin character 12 state_province character 7
purge_date date zip_postal character 10
recalls_placed number
registration_date date PATRON_BARCODE p. 14, 23, 24 ,25, 29, 40, 41
requests_ub number Records for patrons affiliated with another library
self_shelved number are either stub records or child records. Stub

53
records have modify_operator_id=’SYS-UB’; they demerits_applies character 1
are deleted nightly by circjob29 when they are no max_demerits number
longer needed. Child record have been modified patron_group_code character 10
by staff at your library, so the modify_operator_id patron_group_display character 40
is the ID of one of your staff; they are deleted patron_group_name character 25
nightly by circjob29 when they are no longer suspension_days number
needed AND their purge_date has passed.
PATRON_GROUP_ITEM_TYPE
The home_barcode_id and Data in this table are defined in the SysAdmin
home_patron_group_id are filled in for UB stub client at Circulation, Patron Groups, Global
patron records. They are values from the patron’s Borrowed Item Limits tab.
home database, so you can’t use them to link in
other databases. If you get the message, “Type mismatch in
expression”, when you use this table, see
When an item is charged to a UB patron, the Appendix A for a solution.
patron_group_id in PATRON_BARCODE is
ignored. Instead, the patron group is looked up item_type_id number
anew in UB_PATRON_GROUP_MAP using the patron_group_id number
db_id from the stub and home_patron_group_id charge_limit number
from PATRON_BARCODE. So, if you change the
UB patron group mapping, it’s possible to have PATRON_GROUP_POLICY
some items charged under the old patron group Data in this table are defined in the SysAdmin
and some under the new one. And a renewal of client at Circulation, Policy Definitions, Patrons
an item charged under the old patron group can’t tab.
be done in WV because an override is required.
The place_hold_outside_lib,
home_barcode_id number place_interlib_loan_req, place_purchase_req, and
home_patron_group_id number place_recall_outside_lib fields are obsolete.
modify_operator_id character 10
patron_barcode_id number circ_group_id number
patron_group_id number patron_group_id number
patron_id number call_slip_limit number
barcode_status number claim_return_limit number
barcode_status_date date courtesy_notice_applies character 1
patron_barcode character 25 day_short_loan number
email_cancellation_notice character 1
PATRON_BARCODE_STATUS p. 23 email_courtesy_notice character 1
barcode_status_desc character 25 email_item_available_notice char
barcode_status_type number email_overdue_notice character 1
email_overdue_notice_other character 1
PATRON_GROUP p. 14, 16, 17, 23, 24 ,38, 40, 46 email_overdue_recall_notice char
Data in this table are defined in the SysAdmin email_recall_notice character 1
client at Circulation, Patron Groups. fees_applies character 1
hold_request_limit number
The demerits_applies and max_demerits fields do include_hold_in_borrow_limit character 1
not appear to be used for anything. item_limit number
lost_limit number
circ_cluster_id number max_call_slips character 1
patron_group_id number max_claim_return_limit character 1
charge_limit number max_day_short_loan character 1
charge_limit_apply character 1 max_hold_request character 1
charged_status_display character 1 max_item_limit character 1

54
 max_lost_limit character 1
max_outstanding_balance number PATRON_STAT_CODE p. 16, 23
max_overdue_limit character 1 Data in this table are defined in the SysAdmin
max_overdue_recall_limit character 1 client at System, Statistical Categories, Patron tab.
max_recall_limit character 1 If an undefined stat code comes in on a batch
max_self_shelve_limit character 1 patron load, the code will be defined here
max_title_short_loan character 1 automatically. In this case, the patron_stat_code
max_total_short_loan character 1 and patron_stat_desc will be the same.
min_balance_for_notice number
overdue_limit number To count circulation by patron stat code for
overdue_notice_applies character 1 current charges, link from
overdue_recall_limit number CIRC_TRANSACTIONS via patron_id to
place_call_slips character 1 PATRON_STATS. To count circulation by patron
place_hold_inside_lib character 1 stat code for completed circ transactions, link
place_recall_inside_lib character 1 from CIRC_TRANS_ARCHIVE via
place_short_loan_in_lib character 1 circ_transaction_id to
recall_limit number CIRC_TRANSACTION_STATS. Either way, you
self_shelve_limit number can then use PATRON_STAT_CODE to translate
title_short_loan number patron_stat_id.
total_short_loan number
If any of your patrons have multiple patron stat
PATRON_NAME_TYPE p. 23 codes, be aware that their circ transactions will be
patron_name_desc character 25 counted multiple times.
patron_name_type number
patron_stat_id number
PATRON_NOTES p. 23 patron_stat_code character 3
address_id number patron_stat_desc character 25
modify_operator_id character 10
patron_id number PATTERN p. 9
patron_note_id number If a record has not been modified, the
modify_date date modify_date is null.
note character 1900 create_location_id number
note_type number create_opid character 10
pattern_id number
PATRON_PHONE p. 23 update_location_id number
When a patron record is updated by a batch update_opid character 10
patron load, all its addresses and phone numbers alt_chron1 number
are deleted and re-added. Consequently, the alt_lvl1 character 20
values in address_id and patron_phone_id grow alt_lvl1_scheme character 2
faster than the _id fields in other patron tables. alt_lvl2 character 20
alt_lvl2_max number
address_id number alt_lvl2_num_cont number
modify_operator_id character 10 alt_lvl2_scheme character 2
patron_phone_id number chron1 number
modify_date date chron2 number
phone_number character 25 chron3 number
phone_type number chron4 number
create_date date
PATRON_STATS p. 23 frequency_code character 1
patron_id number lvl1 character 20
patron_stat_id number lvl1_scheme character 2
date_applied date lvl2 character 20

55
 lvl2_max number The print_note field is called “Instructions to
lvl2_num_cont number vendor” in the acq client.
lvl2_scheme character 2 po_id number
lvl3 character 20 note character 1900
lvl3_max number print_note character 60
lvl3_num_cont number
lvl3_scheme character 2 PO_STATUS p. 8
lvl4 character 20 po_status number
lvl4_max number po_status_desc character 25
lvl4_num_cont number
lvl4_scheme character 2 PO_TYPE p. 8
lvl5 character 20 Data in this table are defined in the SysAdmin
lvl5_max number client at Acquisitions, PO Types.
lvl5_num_cont number
lvl5_scheme character 2 po_type number
lvl6 character 20 po_type_desc character 25
lvl6_max number
lvl6_num_cont number PO_TYPE_RULES
lvl6_scheme character 2 po_type_id number
pattern_name character 40 rule_id number
pattern_name_norm character 40 apl_increase number
update_date date approval character 1
blanket_order character 1
PHONE_TYPE p. 23 bo_increase number
This table may be used for both patron and mem_increase number
vendor phone numbers, but see the note on membership character 1
VENDOR_PHONE before you use it for vendors. mp_increase number
phone_desc character 25 multi_part character 1
phone_type number single_part character 1
so_increase number
PO_FUNDS p. 4 sp_increase number
This table contains fund info for POs that have standing_order character 1
not yet been invoiced or have rolled over as an sub_increase number
open order. subscription character 1

Remember that a fund_id does not uniquely PO_VENDOR_HISTORY

identify a fund. It’s the combination of fund_id account_id number
and ledger_id that uniquely identifies a fund. audit_id number
Consequently, you need to link by both of these po_id number
fields when you are linking among the FUND…, replace_opid character 10
PO_FUNDS and LINE_ITEM_FUNDS tables. vendor_id number
replace_date date
fund_id number replace_location number
ledger_id number
po_id number PRICE_ADJUSTMENT p. 2
commit_pending number The reason_id is interpreted by the
commitments number ADJUST_REASON table.
expend_pending number
expenditures number The values of method are 1=Amount (Line item
or PO total), 2=Per Copy, 3=Percentage.
PO_NOTES p. 8
If object_type=A, then object_id is a po_id.

56
If object_type=B, then object_id is a line_item_id. claim_interval number
If object_type=C, then object_id is an invoice_id. conversion_rate number
If object_type=D, then object_id is an currency_code character 3
invoice_line_id. edi_ref number
line_item_count number
object_id number line_item_subtotal number
payment_id number normal_po_number character 25
reason_id number not_needed_after date
adjust_amount number order_location number
method number po_approve_date date
object_type character 1 po_create_date date
sequence number po_number character 25
po_status number
PRIMO_AVAIL po_status_date date
bib_id number po_type number
deleted_YN character 1 po_update_date date
avail_hash number prepay_conversion_rate number
rush character 1
PRINT_LOCATION ship_location number
Data in this table are defined in the SysAdmin ship_via character 20
client at System, Print Locations. total number

print_location_id number RECORDCOUNT_VW

acq_global_printing character 1 To get an easy count of various types of records in
cat_global_printing character 1 your database, select all fields and all records
circ_global_printing character 1 from this view.
default_printing character 1
media_global_printing character 1 For most types of records, it’s a simple count; but
print_location_code character 10 for patrons, only those whose expire date has not
print_location_name character 25 passed are counted.

PROXY_PATRON p. 17, 24 count number

create_opid character 10 recordtype character 16
patron_barcode_id number
patron_barcode_id_proxy number RECORD_SET p. 12
create_date date This table is part of Global Data Change
create_location number functionality.
expiration_date date create_operator_id character 10
modify_operator_id character 10
PURCHASE_ORDER p. 2, 3, 4, 7, 8 record_set_id number
account_id number record_set_type_id number
approve_location_id number record_type_id number
approve_opid character 10 description character 2000
create_location_id number last_modify_date date
create_opid character 10 record_set_name character 200
po_id number
update_location_id number RECORD_SET_RECORDS p. 12
update_opid character 10 This table is part of Global Data Change
vendor_id number functionality.
adjustments_subtotal number record_id number
bill_location number record_set_id number
cancel_interval number record_set_bulk_num number

57
 item_barcode character 30
RECORD_SET_TYPE p. 12 message_type character 4
This table is part of Global Data Change sent character 1
functionality.
RENEW_ TRANS… Tables
1=EXPLICIT, 2=LOGICAL There is a renewal_count field in
CIRC_TRANSACTIONS and
record_set_type_id number CIRC_TRANS_ARCHIVE. If you just need
record_set_type_desc character 200 counts, use it. If you need to know when or how
the renewal occurred, you need the
RECORD_TYPE p. 12 RENEW_TRANS* tables.
This table is part of Global Data Change
functionality. RENEW_TRANSACTIONS has a record for each
time an item is renewed. When the item is
1=BIB_RECORD, 2=MFHD_RECORD, discharged, all of the renewal records get copied
3=AUTH_RECORD to RENEW_TRANS_ARCHIVE. If you want to
count renewals, you probably want to include
record_type_id number records from both tables. A technique for doing
record_type_desc character 200 this is given in the CARLI shared SQL space,
http://www.carli.illinois.edu/products-
REFERENCE_TYPE p. 26, 43 services/i-share/reports/secure/sql-loc-circ#08-
display_constant character 80 01b
reference_type character 1
reference_type_desc character 20 For non-UB transactions, renew_location and
renew_oper_id should contain a circ happening
REMOTE_CIRC_CLUSTER_CACHE location and a circ operator. However, if
This table is part of Universal Borrowing. It is not renew_location is not a circ happening location,
useful for reporting. It is populated by circjob33. check the renew_date. The renewal may have
db_id number come over in the conversion from your previous
remote_circ_cluster_id number ILS.
remote_circ_cluster_code character 10
remote_circ_cluster_name character 100 For UB transactions, the values of renew_location
update_date date and renew_oper_id vary depending on the
Voyager version on which the renewal was done.
REMOTE_PATRON_GROUP_CACHE
This table is part of Universal Borrowing. It is not For UB transactions in V2001.2, if renew_location
useful for reporting. It is populated by circjob33. is zero, the renewal was done at the circ desk of
It contains mapping for all patron groups, not just another library. If renew_location is not zero and
the UB-eligible groups. renew_oper_id is blank, then the renewal was
db_id number done in your Web Voyage. If renew_location is
remote_circ_cluster_id number not zero and renew_oper_id is SYS-UB, then the
remote_patron_group_id number renewal was done in another library’s Web
update_date date Voyage.

REMOTE_STORAGE_QUEUE For UB transactions in V6.1, if renew_oper_id is

This table is related to Voyager’s ARS product. OPAC or SYS-UB or null, then the renewal was
done someplace other than your circ desk. In this
item_id number case, renew_location is set to the item’s location.
location_id number
patron_id number RENEW_TRANSACTIONS p. 17
pickup_location_id number circ_transaction_id number
queue_id number renew_oper_id character 10

58
 renew_date date circ_cluster_id number
renew_due_date date circ_copy_level_hold character 1
renew_location number circ_copy_level_recall character 1
renew_type character 1 circ_title_level_hold character 1
circ_title_level_recall character 1
RENEW_TRANS_ARCHIVE p. 16 opac_copy_level_hold character 1
circ_transaction_id number opac_copy_level_recall character 1
renew_oper_id character 10 opac_title_level_hold character 1
renew_date date opac_title_level_recall character 1
renew_due_date date ws_copy_level_hold character 1
renew_location number ws_copy_level_recall character 1
renew_type character 1 ws_title_level_hold character 1
ws_title_level_recall character 1
REPORTING… Tables
These tables are part of Ex Libris’s REQUEST_GROUP p. 20, 21
implementation of the Cognos reporting tool, so it Data in this table are defined in the SysAdmin
is useful to only Meridian and Analyzer client at Circulation, Request Groups.
customers.
group_id number
REPORTING_LEVEL group_code character 10
reporting_level_id number group_name character 25
reporting_level_name character 50
REQUEST_GROUP_LOCATION p. 20, 21
REPORTING_OPERATOR Data in this table are defined in the SysAdmin
operator_id character 10 client at Circulation, Request Groups.
reporting_profile_id number
group_id number
REPORTING_PROFILE location_id number
reporting_level_id number
reporting_profile_id number REQUEST_HISTORY
acquisitions_serials character 1 For call slips that started in this database (i.e.
cataloging character 1 have not been promoted), sometimes there is no
circulation_call_slip character 1 REQUEST_HISTORY record and sometimes there
database_model character 1 is a REQUEST_HISTORY record that shows that
local_ub character 1 it started here. I don’t know the difference
media_scheduling character 1 between these cases, but count both if you want
opac character 1 to count requests without counting promoted
remote_storage character 1 requests multiple times.
reporting_profile_name character 2
sysadmin character 1 For UB requests that have been promoted to your
library, this table shows you where they’ve been
REPORT_TYPES p. 7, 10 previously, ordered by the sequence field. There
Data in this table are defined in the SysAdmin is also a row for your library.
client at Acquisitions, Vendor Reports.
If you get the message, “Type mismatch in
edi_code character 11 expression”, when you use this table, see
report_type number Appendix A for a solution.
report_type_desc character 70
call_slip_id number
REQUEST_CONFIG circ_cluster_id number
Data in this table are defined in the SysAdmin db_key character 100
client at Circulation, Request Configuration. promote_date date

59
 sequence number expire_date in RESERVE_ITEM_HISTORY is set.
Reserve circulation is also recorded in
RESERVE… Tables CIRC_TRANSACTIONS and
Reserves circ is much like regular circ. At the CIRC_TRANS_ARCHIVE in the same way that
time of charge, a CIRC_TRANSACTIONS record non-reserve circ transactions are. So, if you want
is created. At discharge, the record is moved to to count reserve circ separately from non-reserve
CIRC_TRANS_ARCHIVE and the circ, you need the RESERVE_ITEM_HISTORY
historical_charges counter in the ITEM record is table to tell you when the item was on reserve.
incremented. The RESERVE... tables keep track of
what is on your reserve lists. There are also some Now, consider the case of an item on multiple
counters that allow you to see how your reserves reserve lists. It has multiple records in
are used, but it gets complicated. RESERVE_LIST_ITEMS. Because an item is
turned on in the ITEM table, an item on multiple
There are 2 ways to count reserve circulation. reserve lists is turned on for all reserve lists or
One is by using the CIRC_TRANS_ARCHIVE none of them. So, if an item is on multiple reserve
table. You can do this if an item that is put on lists, you cannot distinguish the charges for list.
reserve is given a distinctive temp item type, or a
distinctive temp location, or if your reserve desk RESERVE_ITEM_HISTORY p. 18
has its own circ happening location. To do this, item_id number
link from CIRC_TRANS_ARCHIVE to effect_date date
CIRC_POLICY_MATRIX and from there to either expire_date date
ITEM_TYPE, LOCATION, or reserve_charges number
CIRC_POLICY_GROUP. The advantage of this
approach is that you can count reserves RESERVE_LIST p. 18
circulation even when items are no longer on If a record has not been modified, the
reserve. The disadvantage is that you cannot tell modify_date is null.
what reserve list the item was on. create_location_id number
create_opid character 10
The second way of counting reserve circulation reserve_list_id number
works only while an item is still on reserve, but update_location_id number
you can tell which reserve list or lists the item is update_opid character 10
on. If you use this strategy, you might want to create_date date
collect your statistics before you disperse your effect_date date
reserves at the end of the term. To do this, link expire_date date
from RESERVE_LIST to RESERVE_LIST_ITEMS list_title character 40
to ITEM and use reserve_charges in ITEM. Be normal_list_title character 40
aware that the circulation for items on multiple reserve_item_type number
reserve lists will be counted for all the lists that reserve_location number
they are on. update_date date

More detail: When an item is on a reserve list, RESERVE_LIST_COURSES p. 18

there's a record for it in RESERVE_LIST_ITEMS. course_id number
When an item is turned on on a reserve list, the department_id number
on_reserve field in ITEM is set to "Y" and an instructor_id number
open-ended record is written in reserve_list_id number
RESERVE_ITEM_HISTORY. While an item is section_id number
turned on on a reserve list, the circulation count is
collected in the reserve_charges field in ITEM. RESERVE_LIST_EITEMS p. 18
When an item is turned off of a reserve list, that eitem_id number
value is copied to the reserve_charges field in reserve_list_id number
RESERVE_ITEM_HISTORY and the field is
zeroed out in ITEM. At the same time, the RESERVE_LIST_ITEMS p. 18

60
The RESERVE_LIST_ITEMS table tells you which member_type character 1
items are on which reserve lists. rank number
item_id number
reserve_list_id number RULESET_RULEDOC p. 12
This table is part of Voyager’s Global Data
ROLLOVER_AUDIT Change rule management functionality.
audit_id number rule_doc_id number
parent_id number rule_set_id number
record_id number rule_order number
run_id number
other_info character 50 RULE_DOC p. 12
record_type number This table is part of Voyager’s Global Data
result_code number Change rule management functionality.
timestamp date rule_doc_id number
create_operator character 10
ROLLOVER_RESULT_CODES description character 2000
description character 256 dsl_name character 200
result_code number last_modify_date date
name character 200
ROLLOVER_RULES rules blob
The fiscal_period_id in ROLLOVER_RULES can type number
be used to link to fiscal_year_id field in LEDGER. update_operator character 10
This isn’t obvious from the names.
action_indicator character 1 RULE_SET p. 12
create_op_id character 10 This table is part of Voyager’s Global Data
fiscal_period_id number Change rule management functionality.
new_fiscal_period_id number rule_set_id number
rule_id number create_operator character 10
update_op_id character 10 description character 2000
create_date date last_modify_date date
initialize_type character 1 name character 200
normal_rule_name character 25 parameter_ptr clob
rule_name character 25 type number
update_date date update_operator character 10

ROUTING_LIST p. 11 SAVED_RECORDS_RESULTS
create_location_id number CARLI has not allowed access to this table by
create_opid character 10 library staff because of patron confidentiality
routing_list_id number concerns.
update_location_id number bib_id number
update_opid character 10 db_id number
create_date date patron_id number
name character 45 save_date date
normal_name character 45
note character 256 SAVED_SEARCHES
print_note character 1 The starred field in this table is in UTF-8.
update_date date
CARLI has not allowed access to this table by
ROUTING_LIST_MEMBERS p. 11 library staff because of patron confidentiality
member_id number concerns.
routing_list_id number patron_id number
add_date date saved_searches_id number

61
 sdi_interval_id number completely understand this field, but here’s what
index_type character 1 we do know: IX=A for authority indexes, B for
last_executed date bib indexes, K for keyword indexes, Q for MFHD
limit_flag character 1 indexes, S for special subject indexes, T for special
limit_string character 250 title indexes, U for call number indexes. AL= is a
number_hits number MARC field. SR= is used with a single,
relevance character 1 repeatable field and indicates that each
sdi_new_hits character 1 occurrence should generate an index entry; S+=
search_date date lists subfields that should be included in the
search_page character 3000 index. S-= lists subfields that should be excluded
*search_string character 700 from the index. NM= is the normalization rules.
search_tab character 1 NF tells the location of a non-filing indicator. HL
search_type character 250 indicates a hard limit, i.e., a limit that is always in
effect for this search key.
SDI_INTERVALS
sdi_interval_id number The ordering field does not appear to be used for
sdi_interval_code character 10 anything.
sdi_interval_days number
The acqcount, catcount, circcount, and
SEARCHFIELDS mediacount fields are incremented by Voyager
Data in this table are defined in the SysAdmin during searches in the staff clients. They never
client at Search, Indexes - Holding Keyword display in the clients, but they make the most
Definitions and Indexes - Holding Keyword frequently used searches appear first in the search
Definitions. window. Similarly, the opaccount field makes the
most frequently used keyword searches appear
This table holds the definition of keyword search first on the WebVoyage advanced search screen.
keys. The name of the search key is in
searchcode. The MARC fields and subfields that acqcount number
are indexed with this search key are in fieldcode. catcount number
The searchcode field is further defined in the circcount number
SEARCHPARM table. displayfield1 character 30
fieldcode character 4 displayfield2 character 30
searchcode character 4 displayfield3 character 30
indexrules character 300
SEARCHPARM p. 34 mediacount number
Data in this table are defined in the SysAdmin opaccount number
client at Search, Indexes - Composite Definitions opacsuppress character 1
and in Indexes- Headings and Left-Anchored ordering number
Definitions and in Indexes - Holding Keyword searchcode character 4
Definitions and in Indexes - Holding Keyword searchname character 40
Definitions. sortfield1 character 30
sortfield2 character 30
This table is cryptic, but it stores many of the sortfield3 character 30
indexing decisions that govern searching in staffsuppress character 1
Voyager. z3950_use_attribute number

The searchcode field can be used to link to SELF_REG_FIELDS

index_code in the BIB_INDEX and Data in this table are defined in the SysAdmin
AUTH_INDEX tables. client at OPAC Configuration, Patron Self-
Registration.
The indexrules field, if you can figure it out, tells field_code character 20
how each index in constructed. We don’t required character 1

62
 visible character 1 claim_thread number
claim_type number
SERIALS_VW edi_ref number
This view has a number of quirks and it is not note character 256
efficient. Consider using the tables directly override_claim_date date
instead.
SERIAL_CLAIM_ARCHIVE
If you get the message, “Type mismatch in claim_id number
expression”, when you use this table, see component_id number
Appendix A for a solution. copy_id number
bib_id number issue_id number
component_id number location_id number
issue_id number op_id character 10
mfhd_id number vendor_id number
next_issue_id number archive_date date
component_name character 100 claim_count number
component_name_norm character 100 claim_date date
enumchron character 256 claim_status number
expected_date date claim_thread number
note character 256 claim_type number
predict character 1 edi_ref number
receipt_date date note character 256
received number override_claim_date date

The SERIAL_CLAIM Tables SERIAL_ISSUES p. 1, 9, 10

To uniquely identify a serial issue, you need both To uniquely identify a serial issue, you need both
issue_id and component_id. To identify a copy, issue_id and component_id.
you need copy_id as well. To identify a claim,
you need claim_thread and claim_id too. With V7.0, data that used to be in the
UNPREDICTABLE_ISSUES table is moved here.
The claim_count tells you which claim this is component_id number
(first, second, etc.). For the most recent claim, issue_id number
claim_status=1; otherwise claim_status=0. alt_chron number
alt_lvl1 number
The claim_type may be interpreted using the alt_lvl2 number
CLAIM_TYPES table. chron1 number
chron2 number
The claim_date is the date when the order should chron3 number
be claimed. If it has been overridden, the new chron4 number
date is in override_claim_date. enumchron character 256
expected_date date
SERIAL_CLAIM p. 10 lvl1 number
claim_id number lvl2 number
component_id number lvl3 number
copy_id number lvl4 number
issue_id number lvl5 number
location_id number lvl6 number
op_id character 10 receipt_date date
vendor_id number received number
claim_count number
claim_date date SERIAL_SUPPLIER_REPORT p. 10
claim_status number audit_id number

63
 claim_id number item_id number
action_date date mfhd_id number
action_quantity number patron_group_id number
edi_ref number patron_id number
note character 512 short_loan_id number
report_date date short_loan_status_id number
report_type number update_opid character 10
create_date date
SHORT_LOAN… Tables create_location number
When an item is scheduled for a short loan, a end_time date
SHORT_LOAN record is created and an note character 100
ITEM_STATUS record is created. When the item pickup_location number
is charged to the patron, the SHORT_LOAN start_time date
record is archived, short_loan_charges in ITEM is status_date date
incremented, and all circ activity is recorded as it update_date date
is for any other charge. update_location number

SHORT_LOAN p. 25 SHORT_LOAN_STATS
If you get the message, “Type mismatch in If you get the message, “Type mismatch in
expression”, when you use this table, see expression”, when you use this table, see
Appendix A for a solution. Appendix A for a solution.
patron_stat_id number
bib_id number short_loan_id number
create_opid character 10
item_id number SHORT_LOAN_STATUS p. 25
mfhd_id number short_loan_status_id number
patron_group_id number short_loan_status_desc character 4
patron_id number
short_loan_id number SIMUL_MERGE_PROFILE
short_loan_status_id number Data in this table are defined in the SysAdmin
update_opid character 10 client at Search, Simultaneous Search De-
create_date date Duplicating.
create_location number
end_time date The pseudo_relevance field does not appear to be
note character 100 used for anything.
pickup_location number
start_time date bib_field1 character 30
status_date date bib_field2 character 30
update_date date bib_field3 character 30
update_location number citation_field1 character 30
citation_field2 character 30
SHORT_LOAN_ARCHIVE citation_field3 character 30
If you get the message, “Type mismatch in pseudo_relevance character 1
expression”, when you use this table, see
Appendix A for a solution. SNV_FIELDS p. 13
This table is related to the validation of standard
When a short loan is charged, the record is numbers in the bib 020, 022, and 024 fields.
archived, the status changes, but the status_date snv_field_id number
does not change. snv_id number
field character 3
bib_id number ind1 character 1
create_opid character 10 ind2 character 1

64
 norm_rules character 10 line_item_id number
record_type character 1 subscription_id number
snv_validation_type character 10 auto_renewal character 1
subfield character 1 length_type number
normal_sici character 45
SORT_GROUP normal_upc character 30
Data in this table are defined in the SysAdmin note character 256
client at OPAC Configuration, Holding Sort renewal_date date
Groups, Sort Groups tab. sici character 45
sequence_number number start_date date
sort_group_code character 8 subscription_length number
sort_group_default character 1 upc character 30
sort_group_id number
sort_group_name character 40 SUDOCCLASS_VW
If you want to sort a report (not a query, a report)
SORT_GROUP_LOCATION by class, you will have to use the Left function to
Data in this table are defined in the SysAdmin truncate it to less that 255 characters.
client at OPAC Configuration, Holding Sort
Groups, Locations tab. mfhd_id number
class character 300
location_id number longclass character 12
sort_group_id number
sequence_number number SUPPRESS_SYSTEM_CLAIMS p. 10
component_id number
STANDARD_NUMBER_VALIDATION p. 13 issue_id number
This table is related to the validation of standard
numbers in the bib 020, 022, and 024 fields. UB_CHARGE… Tables
snv_field_id number When a patron borrows an item from another
snv_code character 7 library, a record is created in UB_CHARGE in the
snv_name character 20 patron’s home database. When the item is
discharged, the record is moved to
SUBDIVISION p. 26, 43 UB_CHARGE_ARCHIVE in the patron’s
The starred fields in this table are in UTF-8. database. You can use these tables to count the
items charged by your patrons from other
If a record has not been modified, the libraries. To find out which library’s item they
modify_date is null. charged, use db_id to link to
VOYAGER_DATABASES.
subdiv_id number
authorized character 1 The circ_transaction_id matches a circ transaction
create_date date in the item’s database, not yours. Do not use this
*display_subdiv character 300 field to link to CIRC_TRANSACTIONS in your
heading_type character 12 database.
*normal_subdiv character 300
subdiv_type character 1 Between V7.1 and V7.2.2, circjob 43 puts bad data
update_date date in the due_date field.

SUBDIVISION_TYPE p. 26, 43 UB_CHARGE p. 40

The starred fields in this table are in UTF-8. circ_transaction_id number
subdiv_type character 1 db_id number
*subdiv_type_desc character 50 patron_id number
discharge_date date
SUBSCRIPTION p. 9, 10, 51 due_date date

65
 recall_date date This table is not very useful for Access reports
because it requires data from the databases of
UB_CHARGE_ARCHIVE other libraries. Patron_group_id_mapped is the
circ_transaction_id number patron_group_id from the database of the library
db_id number indicated by db_id. Patron_group_id is the
patron_id number patron group in your database.
discharge_date date
due_date date When patron_group_id_mapped=0,
recall_date date patron_group_id is the default mapping for
patrons from the library specified in the db_id.
UB_FINE_FEE p. 40
The value of fine_fee_total is incorrect about 10% circ_cluster_id number
of the time, so take this table with a grain of salt. db_id number
Here’s how it’s supposed to work: When one of patron_group_id number
your patrons owes a fine to another CARLI I- patron_group_id_mapped number
Share library, the fine amount is recorded in this remote_circ_cluster_id number
table. When your patron pays the fine, the manual_map character 1
fine_fee_total goes to zero, but the record is not
deleted. To find out which library is owed the UB_PATRON_RECORD
fine, use db_id to link to This table indicates when one of your patrons has
VOYAGER_DATABASES. a stub record in another database.
circ_cluster_id number
Patron blocks are implemented using db_id number
total_fees_due_ub in PATRON, not the values in patron_id number
this table. patron_stub_id number
create_date date
db_id number update_date date
patron_id number
demerits_total number UB_PG_HOME_POLICY p. 40
fine_fee_total number Data in this table are defined in the SysAdmin
update_date date client at Circulation, UB Policy Definitions.

UB_HOLD p. 40 There is a record in this table if UB eligible is

When an item is lent through UB, while it is on chcked now or if it was checked in the past.
the hold shelf at another library, there’s a
UB_HOLD record in the item’s home database. patron_group_id number
Not sure what this tells you, but there it is. claim_return_limit number
claim_return_limit_lclblock character 1
demerits_limit number
There may be multiple records with the same demerits_limit_lclblock character 1
pickup_db_id and hold_recall_id if there are fees_applies character 1
multiple items as part of the hold. item_limit number
item_limit_lclblock character 1
hold_recall_id number lost_limit number
item_id number lost_limit_lclblock character 1
patron_id number max_claim_return_limit character 1
pickup_db_id number max_demerits_limit character 1
max_item_limit character 1
UB_PATRON_GROUP_MAP max_lost_limit character 1
Data in this table are defined in the SysAdmin max_outstanding_balance number
client at Circulation, Patron Group Mapping. max_overdue_limit character 1
max_overdue_recall_limit character 1

66
 max_self_shelve_limit character 1
max_ub_requests character 1 The request_status field can be interpreted using
outstanding_balance_lclblock character 1 the UB_REQUEST_STATUS table, but note that
overdue_limit number circjob43 changes the status from 2=In Transit to
overdue_limit_lclblock character 1 5=Available for Pickup before the item arrives at
overdue_recall_limit number the pickup library.
overdue_recall_lclblock character 1
self_shelve_limit number For promoted requests, date_requested is the
self_shelve_limit_lclblock character 1 promote date, not the request date.
ub_eligible character 1
ub_request_limit number UB_REQUEST p. 40
ub_requests_limit_lclblock character 1 call_slip_id number
db_id number
UB_REQUEST… Tables holding_item_id number
When one of your patrons places a UB request, a patron_id number
record is written in the UB_REQUEST table in pickup_db_id number
your database. Also, when one of your patrons date_requested date
using the Universal Catalog’s Web Voyage made not_needed_after number
a request of your library (this capability was lost request_status character 25
with V6.1), a record was written in this table. In status_date date
these records, pickup_db_id and holding_db_id
both equal -1. However, if your patron places a UB_REQUEST_ARCHIVE
request in your database, and you no-fill it, and call_slip_id number
the request is then promoted, there will be no db_id number
UB_REQUEST record in your database. holding_item_id number
patron_id number
Generally, a UB_REQUEST record corresponds to pickup_db_id number
a CALL_SLIP record for one of your patrons in date_requested date
another database, but they are archived at not_needed_after number
different times. Each time the request is request_status character 25
promoted to another library, the old status_date date
UB_REQUEST is archived and a new
UB_REQUEST record is added. When the item is UB_REQUEST_STATUS
finally charged to the patron, the final status_desc_ub character 25
UB_REQUEST record will be moved to the status_type_ub number
UB_REQUEST_ARCHIVE in your database.
UB_ROUTING and UB_ROUTING_ARCHIVE
If you want to count UB requests made by your As UB items are routed from location to location,
patrons, you’ll be pretty close if you count all but records are written in these tables at the “from”
the ones with request_status=8 (promoted). and “to” libraries on each leg of the journey. The
Circjob 43 sometimes creates a second pairs of records have the same value in
UB_REQUEST record for the same call slip, so ub_routing_id; the value seems to be the max of
your counts will be about 10% high. If you want the next ub_routing_id in the 2 databases. While
to be really accurate, count the distinct an item is en route, there is a record in
call_slip_id’s. UB_ROUTING. When an item is received at its
destination, db_id_received and received_date
The db_id field is the database whose item your fields are filled in and the record is moved to
patron is requesting. The pickup_db_id is where UB_ROUTING_ARCHIVE.
your patron wants to pick up the item. Both can
be interpreted using the All of the db_id* fields in these tables can be
VOYAGER_DATABASES table, except that your translated using the VOYAGER_DATABASES
own database has a db_id of zero.

67
table, except the value 0 (zero) indicating your This table was dropped with Voyager V7.0 and
local database. the data are moved to SERIAL_ISSUES.
component_id number
Normally, if db_id_patron=0, this is your patron, issue_id number
and patron_id_ub links to patron_id in your enumchron character 256
patron table. And if db_id_patron is not zero, this expected_date date
is not your patron, but you have a stub patron receipt_date date
record which you can locate by linking received number
patron_id_ub to patron_id_ub in your patron
table. However, this field is incorrect on occasion, VENDOR p. 3, 7, 8, 10, 19, 50
so be flexible. create_opid character 10
federal_tax_id character 10
UB_ROUTING p. 40, 41 institution_id character 25
The db_id_received and received_date fields are update_opid character 10
never filled in in this table because, once the item vendor_id number
is received, the UB_ROUTING record moves to cancel_interval number
UB_ROUTING_ARCHIVE. claim_count number
db_id_from number claim_interval number
db_id_item number create_date date
db_id_patron number default_currency character 3
db_id_received number normal_vendor_code character 10
db_id_to number normal_vendor_name character 60
item_id_ub number normal_vendor_type character 2
location_id_to number ship_via character 20
patron_id_ub number update_date date
ub_routing_id number vendor_code character 10
received_date date vendor_name character 60
shipped_date date vendor_type character 2

UB_ROUTING_ARCHIVE VENDORINVOICE_VW
The db_id_received field is wrong about 1/3 of institution_fund_id character 50
the time. If it says that the item was received institution_id character 25
back at the library that sent it, it was probably invoice_id number
received at the right place. bill_to_location character 25
db_id_from number bill_to_location_code character 10
db_id_item number currency_code character 3
db_id_patron number currency_name character 35
db_id_received number expend_pending number
db_id_to number expenditures number
item_id_ub number fiscal_period_end date
location_id_to number fiscal_period_name character 25
patron_id_ub number fiscal_period_start date
ub_routing_id number fund_name character 25
received_date date invoice_date date
shipped_date date invoice_number character 25
invoice_status character 25
UDCCLASS_VW invoice_status_date date
mfhd_id number ledger_name character 40
class character 6 policy_name character 40
vendor_code character 10
UNPREDICTABLE_ISSUES vendor_name character 60
vendor_type character 40

68
 voucher_number character 25 payment_address character 1
return_address character 1
VENDORORDER_VW state_province character 7
institution_id character 25 std_address_number character 8
mfhd_id number zip_postal character 10
currency_name character 35
invoice_status character 25 VENDOR_BANK_INFO p. 50
line_price number modify_operator_id character 10
line_status_date date vendor_id number
order_location character 25 account_number character 25
order_location_code character 10 address_line1 character 50
po_line_status character 25 address_line2 character 40
po_number character 25 address_line3 character 40
po_status character 25 address_line4 character 40
po_status_date date address_line5 character 40
po_type character 25 bank_name character 60
quantity number city character 30
total number country character 20
unit_price number fax character 25
vendor_code character 10 modify_date date
vendor_name character 60 phone character 25
vendor_type character 40 state_province character 7
tax_id_number character 11
VENDOR_ACCOUNT p. 3, 8, 50 transit_number character 25
account_id number zip_postal character 10
vendor_id number
account_name character 25 VENDOR_NOTE p. 50
account_number character 25 vendor_id number
account_status number note character 1900
default_discount number
default_po_type number VENDOR_PHONE p. 50
deposit character 1 The values of phone_type are 0=primary,
status_date date 1=mobile, 2=fax, 3=other. These are one less than
the values in the PHONE_TYPE table. But you
VENDOR_ADDRESS p. 50 can effect a link between VENDOR_PHONE and
address_id number PHONE_TYPE by this devious means:
modify_operator_id character 10
vendor_id number SELECT VENDOR_PHONE.PHONE_NUMBER,
address_line1 character 50 PHONE_TYPE.PHONE_DESC
address_line2 character 40 FROM VENDOR_PHONE, PHONE_TYPE
address_line3 character 40 WHERE (((Val([phone_type].[phone_type]))=
address_line4 character 40 Val([vendor_phone].[phone_type])+1));
address_line5 character 40
city character 30 address_id number
claim_address character 1 modify_operator_id character 10
contact_name character 40 modify_date date
contact_title character 40 phone_number character 25
country character 20 phone_type number
email_address character 1
modify_date date VENDOR_TYPES p. 50
order_address character 1 Data in this table are defined in the SysAdmin
other_address character 1 client at Acquisitions, Vendor Types.

69
 connecttimeout number
vendor_type character 2 database_name character 50
vendor_type_desc character 40 db_code character 10
db_desc character 200
VENDOR_TYPE_DEFAULTS p. 50 db_key character 100
acq_policy_id number db_name character 100
cancel_interval number db_protocol character 1
claim_count number db_public character 1
claim_interval number db_subtype character 1
discount number db_type character 1
order_type number db_weight number
ship_via character 20 implementor character 5
vendor_type character 2 max_license number
maxhits number
VERSIONS opacsuppress character 1
This tables lists the version of each Voyager password character 50
module that is in place. It provides a way to public_highwater number
determine which patch sets have been applied. public_pool number
module character 20 retrievaltimeout number
syncpoint number searchtimeout number
version character 30 staff_highwater number
staff_pool number
VOYAGER_DATABASES p. 33, 41 staffsuppress character 1
Data in this table are defined in the SysAdmin ub_db character 1
client at Search, Database Definitions, Definitions userid character 50
tab.
WOPAC_PID_PATRON_KEYS
This table can be used to interpret database IDs This table is used for Voyager’s External Patron
that occur in all the other tables, with one Authentication functionality.
exception: In VOYAGER_DATABASES, your patron_key character 30
local database has db_id=1; in all the other tables, pid character 80
your local database is indicated by a value of zero
(or sometimes a mix of zero and null). Z3950_ATTRIBUTES
Data in this table are defined in the SysAdmin
The implementor, opacsuppress, retrievaltimeout, client at Search, Database Definitions, Attributes
and searchtimeout fields do not appear to be used tab.
for anything.
db_id number
The public_highwater and staff_highwater fields attrib_desc character 50
are filled in by Voyager as it runs and are not attributes character 40
displayed anywhere in the clients. boolean_enabled character 1
db_code character 8
db_id number lh_truncation character 1
dup_profile_id number rh_truncation character 1
action character 10 searchcode character 4
char_set_id number

70
Appendix A: The “Type mismatch in expression” message

The “Type mismatch in expression” message comes up occasionally when you run a new Access query or a
query that you have just changed. It means that the fields that you use in one of your links are of different
types. In other words, one field is a number and the other is a text string. It’s not your fault. This Data
Dictionary leads you to believe that they are both numbers, but that’s not quite true.

Detail for techies: The two fields are indeed defined as numbers in Voyager’s Oracle
database. There is a slight difference in the way that they are defined, however, that makes
Access treat them differently. It’s such a small difference that it doesn’t matter to Voyager.
One field is explicitly defined as an integer and the other is implicitly an integer. Most
numerical fields in Voyager are explicitly defined as integers. Access knows that Oracle
can handle larger integers than Access can. To protect itself from an integer value that
might be too large for it to handle, Access treats the field as if it were a text string. But if
Oracle defines a numerical string as an integer implicitly, Access treats it as a number.

Most fields that look like numbers are treated by Access as if they were text strings. But there are a few
exceptions, and these are the ones that trigger the “Type mismatch” error message. Here is a list of the
fields that Access treats as numbers:

Table Name Field Name

CALL_SLIP_STATS CALL_SLIP_ID
CALL_SLIP_STATS PATRON_STAT_ID
CIRC_ALERT_CONDITIONS LOC_ID
ENUM_CHRON_TYPES_VW CHRON_TYPE_ID
ENUM_CHRON_TYPES_VW ENUMERATION_TYPE_ID
HOLD_RECALL PATRON_GROUP_ID
HOLD_RECALL_ARCHIVE PATRON_GROUP_ID
HOLD_RECALL_ARCHIVE PATRON_ID
PATRON_GROUP_ITEM_TYPE ITEM_TYPE_ID
PATRON_GROUP_ITEM_TYPE PATRON_GROUP_ID
REQUEST_HISTORY CALL_SLIP_ID
REQUEST_HISTORY CIRC_CLUSTER_ID
SERIALS_VW ISSUE_ID
SHORT_LOAN BIB_ID
SHORT_LOAN CREATE_LOCATION
SHORT_LOAN ITEM_ID
SHORT_LOAN MFHD_ID
SHORT_LOAN PATRON_GROUP_ID
SHORT_LOAN PATRON_ID
SHORT_LOAN PICKUP_LOCATION
SHORT_LOAN UPDATE_LOCATION
SHORT_LOAN_ARCHIVE BIB_ID
SHORT_LOAN_ARCHIVE CREATE_LOCATION
SHORT_LOAN_ARCHIVE ITEM_ID
SHORT_LOAN_ARCHIVE MFHD_ID
SHORT_LOAN_ARCHIVE PATRON_GROUP_ID
SHORT_LOAN_ARCHIVE PATRON_ID
SHORT_LOAN_ARCHIVE PICKUP_LOCATION
SHORT_LOAN_ARCHIVE UPDATE_LOCATION
SHORT_LOAN_STATS PATRON_STAT_ID

71
So the problem that you need to solve involves a link between one of these fields and a like-named field in
another table. Here’s what to do:

1) In the design pane, delete the link in question. Do this by right-clicking near the middle of the link and
clicking on Delete.

2) Is the numeric field (i.e., the one listed above) in your list of fields? No? Then add it. If you don’t want it
in your query results, un-check the Show box.

3) Now you need to add a criterion underneath the numeric field. The criterion will use the table name and
field name of the text field. This is the field that was part of the link. The syntax for the criterion is:

= Val ( [tablename].[fieldname] )

For example, here is a query that counts hold and recalls by patron group:

But when I try to run it…

72
So I right-click near the middle of the link and select Delete:

The numeric field (i.e., the one list in the table above) patron_group_id in the hold_recall_archive table. So I
add that field to my list of fields:

73
It was linked to patron_group_id in the patron_group table, so I’ll put that field and table name in the
criterion:

I don’t want the patron_group_id to display, so I’ll un-check the Show box. Since this is a Totals query, I’m
also going to change the Group By to Where on this field.

Voila!

74
Appendix B: What’s in the LINK and LINK_TEXT fields of ELINK_INDEX?

The values in the LINK and LINK_TEXT fields in the ELINK_INDEX table are derived from the 856 field of
the corresponding bib, MFHD, or authority.

The value of the LINK field:

If there is a $u
then if $u has a valid prefix (e.g. http, telnet, ftp, file, etc)
then LINK = $u
else LINK = blank
else if there is a $g
then LINK = $g
else if $d and $f and $o are all present
then if there is a $2
then LINK = blank
else if $o = 'dos'
then LINK = $d, a backslash character, $f
else LINK = $d, a slash character, $f
else LINK = blank

The value of the LINK_TEXT field:

There are 4 cases, depending on whether $3 and $z are present.

1. If there is a $z and no $3
then LINK_TEXT = $z

2. If there is a $z and $3
then if there is $u or $g
then LINK_TEXT = $3 followed by $z
else LINK_TEXT = $z

3. If there is a $3 and no $z
then if there is $u or $g
then LINK_TEXT = $3
else if $d and $f and $o are all present
then LINK_TEXT = $3
else if $d and $f are both present
then LINK_TEXT = blank
else LINK_TEXT = all subfields of the 856 with subfield codes

4. If neither $3 nor $z is present and there’s something in the LINK field

then LINK_TEXT = LINK
else LINK_TEXT = all subfields of the 856 with subfield codes

75