Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Important notes about local fields and holdings statements (paired and textual)

  • Field 908 (was H08 in Aleph) is no longer a required field. You only need to add this field if you do NOT want holdings set in OCLC. To prevent holdings being set in OCLC, add 908 $$ap. 
    • Some units may continue to require 908 for statistical purposes. 
  • Fields 866, 867, 868 (textual holdings statements) will automatically be generated by Alma when a record is saved and there are paired enum/chron fields (863, 864, 865).
    • When enum/chron paired fields are updated and you re-save a record, Alma will regenerate the 866, 867, 868. 
    • You should not modify 866, 867, 868 fields. 
    • This system is configured to generate these fields for the purposes of Primo display. 
  • Fields 966, 967, 968 are designated for use by staff for manually creating textual holdings statements (in lieue of 866, 867, 868). 
    • These fields will display in Primo. 
    • Aleph holdings fields 866, 867, 868 migrated as 966, 967, 968. 
  • Additional fields are automatically generated (and updated) when saving a holding, for the purposes of Primo display:
    • 994 : Copy of 977 Bound-with for Primo use (displays with a hyperlink for the user to click on)
    • 995 : Copy of 008 receipt status for Primo use (displays as On Order or Currently Received, when applicable)
      • Migrated data have some encoded data in this field. This should be ignored. (Data will be removed when the record is saved.)
    • 996 : Copy of 561/1 or 561/_ for Primo use (indexed and displayed when note is not marked private)
    • 997 : Copy of 541/1 for Primo use (indexed and display when note is marked as public)
  • All Harvard defined fields are documented at https://wiki.harvard.edu/confluence/x/2zgWDQ

852 changes

  • For holdings field 852, we no longer having the option of leaving both indicators blank. Most library/locations have been configured to have a default 1st indicator appropriate for that location. If no other default has been set, the 1st indicator will default to 8. If there is no $h/$i, no entry will appear in call number browses or shelf listing tools. 

Authorities and authority control

Authorities and Authority Control Task List

Every heading in Alma bib records will be run through two jobs. Both those jobs run every night on new and changed records:

  1. Heading will get linked to an authority with the same string (whether that is your entity or not)

  2. Heading will get flipped to the 1XX of that entity, if your string matches a 4XX (except if the record is in the Community Zone)

A note about the "binoculars" icon in the Alma metadata editor:

  • Presence of this icon indicates only that the heading string is linked to either the 1XX or the 4XX of an authority record. The icon does not indicate that the form of the heading shown is the authorized form. Preferred Term Correction flips linked headings to the authorized form.

New best practice for name headings issued by Metadata Standards:

New policies for local authority records:

  • ITS no longer creates local authority records

  • Local units are discouraged from creating local authorities

  • All units, shared or local, are encouraged to create NACO records

 

Read more at Authorities and Authority Control Task List

 

  • No labels