Local Fields

Background

Ex Libris has developed Alma functionality that will allow a library to store local bibliographic information into local fields, referred to as “local extensions to bibliographic records.” These local extensions would display to users in both Alma and Primo as if they were part of the bibliographic record, but would be stored in the library’s Institution Zone (IZ). This protects the local fields in bibliographic records from being lost when master records in the Network Zone (NZ) are overlaid with an updated record. Local extensions remain in the record until deleted by the library.

Policy

• Use local fields for the uses defined in the table of Local Fields in Alma & Primo (Procedures). For a detailed list of local fields in Alma, see the document CSU Migration of Local Bibliographic Data to Alma Local Extensions to Bibliographic Records.
  
  
• Most local fields in Alma are designed to mimic a specific non-local MARC 21 field. The local and non-local field equivalencies are shown in the table of Local Fields in Alma & Primo (Procedures). It is essential that these local fields be formatted like those MARC 21 fields, including indicators and use of subfields, as the Primo normalization rules that control display and searchability are designed for the local fields to be formatted the same way as the relevant non-local field.
  
  
• If a library has data in a particular local field that does not have the desired characteristics display, searchability, and clickability, move the data to a different local field that has the desired characteristics rather than requesting changes to that field’s characteristics. This can be done by using a norm rule to change the field tag (using the ChangeField command) and, if not already present, add the subfield $9.

Procedures in Alma

Local Fields in Alma & Primo

Related Resources

Display of Local Fields from IZ Records in Primo

Action log