Considerations when using the BIB_TEXT table in Voyager Prepackaged Access Reports
- Product: Voyager
- Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare
Question
Some considerations when using the BIB_TEXT table in Voyager Prepackaged Access Reports.
Answer
The BIB_TEXT table is one of the major cataloging tables in Voyager Prepackaged Access Reports, along with BIB_INDEX, MFHD_MASTER, ITEM, ITEM_BARCODE, ITEM_TYPE, and ITEM_STATUS.
- If you need data from a bib record that are not available in BIB_TEXT, check to see if they are in BIB_INDEX (for fields in left-anchored indexes) or ELINK_INDEX (for URLs in the 856, 583, 563, etc.). All of these are more efficient than using the BLOB functions.
- If you need data from a fixed field, some of them are found here. Some are in the MARC*_VW tables. The 007/0 (Category of Materials) is in the BIB_MEDIUM table. Other fixed fields can be extracted from FIELD_008 in BIB_TEXT using the Mid function. Just remember that most fixed fields are specific to a record type so you’ll need to check bib_format, and that MARC calls the first byte “0” whereas Mid calls the first byte “1”.
- If you’re thinking of using begin_pub_date in a criterion, consider using the indexed version of this field. It’s in the BIB_INDEX table, in the normal_heading field when index_code=008D.
- If you’re thinking of using language in a criterion, consider using the indexed version of this field. It’s in the BIB_INDEX table, in the normal_heading field when index_code=008L.
- If you’re thinking of using place_code in a criterion, consider using the indexed version of this field. It’s in the BIB_INDEX table, in the normal_heading field when index_code=008P
For repeatable fields, the first occurrence is used. When both the 260 and 264 are present, the 260 is used.
The following displays how MARC tags map to fields in BIB_TEXT:
Leader bytes 5 record_status
Leader bytes 6-7 bib_format
Leader bytes 17 encoding_level
Leader bytes 18 descrip_form
008 field_008
008 byte 6 date_type_status
008 bytes 7-10 begin_pub_date
008 bytes 11-14 end_pub_date
008 bytes 7-10 - bytes 11-14
pub_dates_combined
008 bytes 15-17 place_code
008 bytes 22-23 map_projection
008 bytes 35-37 language
010 abz8 lccn
020 a isbn
022 a issn
024 a other_std_num
027 a stdtech
028 all subfields publisher_number
030 a coden
035 a network_number
037 a stock_number
074 a gponum
100 abcdkq author
110 abcdgkn author
111 acdegkn author
130 adfgklmnoprs uniform_title
240 adfgklmnoprs uniform_title
243 adfgklmnoprs uniform_title
245 abcfghknps title
245 ab title_brief
250 all subfields edition
255 abc map_math_data
260 abc imprint
264 abc imprint
260 a pub_place
264 a pub_place
260 b publisher
264 b publisher
260 c publisher_date
264 c publisher_date
440 anpv series
490 av series
The starred fields in the following list are UTF-8:
bib_id number
*author character 255
begin_pub_date character 4
bib_format character 2
*coden character 6
date_type_status character 1
descrip_form character 1
*edition character 100
encoding_level character 1
end_pub_date character 4
field_008 character 40
*gponum character 20
*imprint character 200
*isbn character 50
*issn character 20
language character 3
*lccn character 20
*map_math_data character 255
map_projection character 2
*network_number character 30
*other_std_num character 30
place_code character 3
pub_dates_combined character 9
*pub_place character 100
*publisher character 150
*publisher_date character 25
*publisher_number character 40
record_status character 1
*series character 255
*stdtech character 30
*stock_number character 50
*title character 255
*title_brief character 150
*uniform_title character 255
Additional Information
Sample query using BIB_TEXT that returns BIB_ID, title, and the first instance of the OCLC number:
Constructing custom SQL queries by request and troubleshooting unexpected results from customer-created SQL queries falls outside the scope of Support. The above has been posted for informational purposes. Voyager-L and Developer Network are useful resources for finding helpful custom SQL or obtaining assistance from peers in troubleshooting custom queries.
- Article last edited: 18-Jan-2021