Unicorn

Library Level Availability

Not in use.

A special enrichment program, Unicorn Availability Enrichment, merges and maps the availability information from the Enrichment/Availability fields to this field.

Refer to the Primo Interoperability Guide for more information on this enrichment program.

Backlink

$$Tunicorn_backlink

Note that the template itself requires the 'pcnum' script developed by Vanderbilt University. Documentation concerning this script is available from Ex Libris support.

LinktoHoldings

$$Tunicorn_holdings

Note that the template itself requires the 'pcnum' script developed by Vanderbilt University. Documentation concerning this script is available from Ex Libris support.

Creator/contributor

In addition to the fields used in Generic Marc also:

CR100, CR700, CR110, CR111, CR710, CR711

The CRnnn fields are cross-references that are added during the extract.

Subject

In addition to the fields used in Generic Marc also:

CR650, CR651, CR600, CR610, CR611, CR630.

In addition, the subfields with '=' and '?' are removed.

The CRnnn fields are cross-references that are added during the extract.

Collection

999 subfields 1 and m using the ILS Library Codes.

This adds all libraries as collections. The libraries are based on subfields l and m from the 999 field. Every 999 field represents an item that is added during the extract.

Top-level

The 'online resource' facets are created same as for Generic MARC.

Available in Library – records will be tagged as "Available in Library" if enrichment/availablility $$S is available or check_holdings.

Institution

The institution should be added as a constant and should be updated locally.

Availability

The purpose of these rules is to take the 852 (from linked holdings records) and 999 fields (one field per linked item) and convert them to the format of the Library Level Availability field from the display section. In the enrichment section, the mapping process creates a separate field for every 852 and 999 field, and then the Unicorn Availability enrichment program merges these fields into a single Library Level Availability field per location.

The rules give precedence to 852 over 999 on the assumption that only multivolume records have a holding record.

The first 5 rules deal with 852:

Rule 1 – creates $$I - the Primo institution. This is a constant which is updated locally

Rule 2 – creates $$L - the Primo library based on subfields b and c. Since the order of the elements differs from the order for the 999 equivalent fields, subfield l and m, use a special mapping table, ILS Library Codes2. Note that you should add all possible combinations to this mapping table.

For example:

BIOMEDICAL DOC-DELIV BIOMEDICAL

BIOMEDICAL FAMRESCTR BIOMEDICAL

Rule 3 – creates $$1 - the sublocation based on subfield c (unless the content is a hyphen).

Rule 4 – creates $$2 - the call number based on subfields: h, i, j, and z.

Rule 5 – creates $$S - the status. For multi-volumes, this is always "check_holdings"

The remaining rules apply to 999, which are activated only if the record does not have an 852 field (hence the condition checking for the presence of 852 in every rule).

Rule 6 – creates $$I - the Primo institution. This constant is updated locally.

Rule 7 – creates $$L - the Primo library based on subfields l and m and uses the ILS Library Codes mapping table that is automatically created from the Institution configuration defined in the Institution Wizard.

Rule 8 – creates $$1 - the sublocation based on subfield l.

Rule 9 – creates $$2 - the call number. This is based on subfield a.

Rule 10, 11, 12 – create $$S - the status. This is based on a combination of either subfields k and m or l and m using the Library Avail Codes mapping table that matches the combinations to one of the following statuses: available, unavailable, or check_holdings.

For example:

LOST MUSIC unavailable

ON-ORDER MUSIC check_holdings

LCC

Created also from 999 subfield a.