In most aspects, the Aleph danMARC2 mapping is the same as the Generic danMARC2 mapping. Only the exceptions are listed in this section.
|Normalized Record Field||Source/Content||Note|
ILS API ID
Created from the PNX control/sourceid merged with control/sourcerecorid
Required for OPAC via Primo.
Library level availability
The Availability subfields are created as follows:
$$I Institution – based on institution look-up table based on AVA$$a
$$L Library – based on library look-up table based on AVA$$b
$$1 Sublocation – from AVA$$c
$$2 Call number – from AVA$$d
$$S Availability status – based on AVA$$e
$$3 No. of items – from AVA$$f
$$4 No. of unavailable items – from AVA$$g
$$5 multi-volume flag – from AVA$$h
$$6 number of loans – from AVA$$i
$$9 – For more information, refer to section Adding $$9ONLINE to Library Level Availability.
$$P location priority – from AVA $$p
$$X source institution code (Aleph ADM) – from AVA $$a
$$Y source library code (Aleph sublibrary) – from AVA $$b
$$Z source sub-location code (Aleph collection) – from AVA $$j
|Type of Link||Source||Note|
For example, for a backlink to an Aleph source (OPAC):
Link to Holdings
In addition to the generic mapping also AUT (cross-references)
In addition to the generic mapping also SUB (cross-references)
Use mapping table "ILS library codes."
Generic mapping and:
AVA $$e IF "available" or "check_holdings
Delivery and Scoping
Delivery and Scoping Section
|Delivery Field||Source||Additional Normalization Notes|
AVA $$a or AVA $$b
Use mapping table ILS Institution.
The system can create multiple occurrences in separate fields.
|Browse field||Source||Additional normalization notes|
AVA $$d (for call number)
AVA $$a (for institution)
$$D (display form), $$E (normalized form), and $$I (institution) are created.