Use of the MARC*_VW tables in Voyager Prepackaged Access Reports
- Product: Voyager
- Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare
Question
Using the MARC*_VW tables in Voyager Prepackaged Access Reports.
Answer
The MARC*_VW tables make it easier to get at some of the fixed fields. They rely on record type and bib level in your BIB records, so quality of cataloging is important if you want to use these tables.
These tables parse out many of the fixed fields from bibliographic records. Remember that some of the fixed fields are also available in BIB_INDEX and BIB_TEXT and that using those tables may be easier.
Remember: Voyager uses the record type and bib level fields to decide which records are included in each view (see examples that follow).
For each MARC* table, the Access field name and the label from a WorldCat display are given.
Examples:
MARCBOOK_VW
Includes these record type/bib level pairs: aa, ac, ad, am, ha, hc, hd, hm, ta, tc, td, tm.
audience: Audn 008 byte 22
biography: Biog 008 byte 34
conferencepub: Conf 008 byte 29
governmentpub: GPub 008 byte 28
itemform: Form 008 byte 23
literaryform: LitF 008 byte 33
bib_id number
audience character 1
biblevel character 1
bibtype character 1
biography character 1
conferencepub character 1
governmentpub character 1
itemform character 1
literaryform character 1
MARCSERIAL_VW
Includes these record type/bib level pairs: ab, as, bb, bs, cb, cs, db, ds, eb, es, fb, fs, gb, gs, hb, hs, ib, is, jb, js, kb, ks, mb, ms, nb, ns, ob, os, pb, ps, rb, rs, tb, ts
conferencepub: Conf 008 byte 29
entirenature: EntW 008 byte 24
frequency: Freq 008 byte 18
governmentpub: GPub 008 byte 28
itemform: Form 008 byte 23
originalform: Orig 008 byte 22
regularity: Regl 008 byte 19
type: SrTp 008 byte 21
bib_id number
biblevel character 1
bibtype character 1
conferencepub character 1
entirenature character 1
frequency character 1
governmentpub character 1
itemform character 1
originalform character 1
regularity character 1
type character 1
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: 21-Jul-2021