MARC authority app

Current Capabilities (as of Orchid release)

Search / Browse authority records
- Powered by Open Search
- Search options: Personal name, Corporate/Conference name, Name-title, Subjects, Children's subject, Geographic name, Genre
- Advanced search: Supports Boolean
- Search Sort | Relevance (default), Authorized/Reference , Heading/Reference, Type of heading
- Search Facets | Authority source , Type of heading, Thesaurus, Exclude See also, Exclude See from, Date created, Date updated
- Browse options: Personal name, Corporate/Conference name, Name-title, Subjects, Children's subject, Geographic name, Genre
- Browse Facets | Authority source , Type of heading, Exclude See from,
Edit MARC authority records via quickMARC
- Shortcut keys to edit, save record, and navigate subfields across a text field box
Manual link MARC bib fields to authority headings
- Edit authority record will also update linked MARC bib fields too
Export authority records (.mrc - full MARC records) / (csv - just UUIDs)
Delete authority records via UI
Data import: Create and update MARC authority records
Authority control report: Authority headings change report (.csv)

Data import use

DO NOT load the same record twice. Unlike Sierra, FOLIO does not have separate indexes.
To create MARC authority records
- You may use the default job profile: Default - Create SRS MARC Authority
  - To prevent duplicates, create and attach a match profile to the job profile
  - AND attach the Create SRS MARC authority record action profile to Non-matches section
- OR you can create a new job profile and do not change - default job profile: Default - Create SRS MARC Authority
To update MARC authority records > Create your own job profile
- Create a match profile (can match on any field i.e. 010 $a or 001 or 999 ff $s/$i).
Authority control
- Data import authority 1XXs updates will also update linked bib fields
  - Depending on the change, it may unlink the bib fields
    - Example 1: Updated Authority 100 removed subfield t thus bib field 240 (which requires a subfield t) will no longer be linked
  - It should not significantly impact data import as it is using a different service to update bib records.
- Data import authority 010 $a updates > will also update linked bib fields $0 (SEE Rules for handling 010 (MARC authority - 1XX)
- Data import linked bib field updates
  - If $0 is removed then bib field will be unlinked
  - If $0 is edited then bib field will be unlinked
  - Possibility that duplicate bib fields are created for repeatable fields

Migration considerations

Import LoC authority records
- To support the authority source file facet and authority control, we need to know if the authority record comes from Library of Congress.
- Populate 010 $a with the LCCN
- 001 can also be populated with LCCN
Import non-LC authority records
- For MeSH authority records populate 010 $a OR 001 with the MeSH authority record identifier
- For FAST populate 001 with the FAST authority record identifier
- Art & architecture thesaurus populate unique identifier 010 $a OR 001
- Rare Books and Manuscripts Section populate unique identifier 010 $a OR 001
- GSAFD Genre Terms populate unique identifier 010 $a OR 001
- Thesaurus for Graphic Materials populate unique identifier 010
Import local authority records
- Via API create and update a local authority file with the following information
  - Whether 010 $a and 001 is populated with authority unique identifier
    - The alpha prefix to identify authority unique identifier
  - Authority file name
  - Authority type (i.e. Subjects)
  - Base URL to be used to populate bib field $0 for authority linking
Additional details regarding global and local authority source files
For any library that wants an authority source file to be global, please contact Khalilah Gambrell via slack.
Authority linking AND bib field $9 handling
- For bib fields that are eligible to be linked to an authority record, do not import $9.
- $9 is used to populate the linked authority record UUID
Authority 001 handling
- No HRID generation
- Populate with authority file unique identifier or your library's defined system control number

Release upgrades considerations

Authority record upgrades
- If mapping rules changes were made then existing records will not reflect changes with release upgrade UNLESS the records are updated
  - A standalone application can be used to update these records but it should be
    - run off hours
    - and it may take several days to complete
    - the script may require manual restart
  - Long term solution for handling such updates UXPROD-4082 - Getting issue details... STATUS
Nolana release requires this upgrade
Orchid release does not require this upgrade