...
Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
After the transition to Primo VE, some information in this document is no longer current. Please refer to the documentation on local fields in Primo VE.
Background
Procedures for adding local fields in Alma. Document also outlines local data in Alma and Primo . To be used in conjunction with the policy: Local FieldsVE.
Procedures
Methods Two methods for adding local fields (now called Extensions) in Alma:
First Method: Adding Local
...
Extensions using the
...
Metadata Editor (MDE)
- Click Edit on a bibliographic record result or Push Selected records to the MDE.
- Within the MDE, navigate to the Editing Actions > Add Local Extension (Ctrl+L) command
...
- . After selecting this command, Alma creates a field with a gray institution icon to the left of the MARC field number and an invisible subfield $9 containing the string "local" (all lower case).
- This subfield $9 is used by Alma to mark fields as local, i.e., they are stored in an institution's Institution Zone and are not lost when the master bib record in the NZ is overlaid. Although this subfield $9 is not displayed in Alma
...
- , it is present in local fields when bib records are exported.
Second Method: Adding Local Fields using Norm Rules.
...
Use a normalization rule to add a local
...
extension one-at-a-time in the
...
MDE or to batch-add a local
...
extension to a set of
...
bibliographic records. The normalization rule
...
MUST include the addSubfield command as shown below:
then
addField "590.a.Gift of John Doe."
addSubField "590.9.local" if (not exists "590.9.local")
end
Note: Using "local" or "LOCAL" in a subfield $9 both work in Alma when creating normalization rules. However, be consistent! Be sure to test for the presence of either string before adding a new subfield $9. Alma Analytics will consider local or Local or LOCAL as different instances.
How NOT to Add Local Fields.
...
Do NOT navigate to Editing Actions > Add
...
Local Extension (Ctrl+L) command and then add the "$$9local" subfield in the
...
field afterward. The field will be a normal field in the NZ and will be lost when the NZ bib record is overlaid. Similarly, adding the "$9 local" subfield in OCLC Connexion before downloading the bib record into Alma will also NOT work, and the new field will again be lost when the NZ bib record is overlaid.
- IZ-only records
Please see Display of Local Fields from IZ Records in Primo for additional metadata required for local fields in IZ-only records.
...