Question

In whidh Oracle table is the "BAR", item barcode, index stored?
In moving to a shared single bib file for multiple ADM libraries, it seems that barcode data could be a problem. Actual barcodes (barcode labels) are probably unique, but system-created "barcodes" (B<number>) are not.

Answer

Unlike most other Aleph indexes the "BAR index" does not exist as a separate Aleph Oracle table. The z30_id1 Oracle index is built on the z30_barcode field:
Z30_ID1 VALID NORMAL NONUNIQUE Z30_BARCODE

When the user specifies that the BAR index should be searched, the system looks at the z30_id1/z30_barcode field.

In a multi-ADM situation, the system will retrieve all bib records (in the specified base) whose items contain the specified barcode.

Most of the time, users will be searching the local campus' base and will not retrieve bib records not held by their campus. But, if users are searching in the shared catalog, they *could* retrieve bib records from other campuses whose items share the same "B-nnnn" barcode as the item they are searching for.

The solution to this is to have users search for barcodes in the local base only.

• Article last edited: 2/12/2014