Page Comparison

MARC Authority example (what a FOLIO librarian/cataloger sees/expects to see when using FOLIO)

Figure 1. Name authority record for Apple Computer, Inc. (Source: screenshot of the MARC record retrieved from Classweb.org) - from https://journal.code4lib.org/articles/15014

Commonly used MARC fields (See - https://www.loc.gov/marc/uma/pt8-11.html#pt8) 

1XX, 3XX - Headings Information Fields

• 1XX - Main heading (authorized name) (see box 1)
  • 100 - Heading - Personal Name
  • 110 - Heading - Corporate Name
  • 111 - Heading - Meeting Name
  • 130 - Heading - Uniform Title
  • 147 - Heading - Named Event
  • 148 - Heading - Chronological Term
  • 150 - Heading - Topical Term
  • 151 - Heading - Geographic Name
  • 155 - Heading - Genre/Form Term
  • 162 - Heading - Medium of Performance Term
  • 180 - Heading - General Subdivision
  • 181 - Heading - Geographic Subdivision
  • 182 - Heading - Chronological Subdivision
  • 185 - Heading - Form Subdivision 
• 3XX - Additional information related to the heading (see box 2)

4XX: See from tracings

• Fields 400-485, the See From tracing fields, are used to identify unauthorized forms of headings and other variants not chosen as an authorized form (see box 3)

5XX: See also from tracings

• Fields 500-585, the See Also From tracing fields, are used to identify different authorized forms of headings related to the authorized form in the 1XX field. (see box 4)

667-68X - Notes-General Information 
General notes are contained in field 667 (Nonpublic General Note) or 680 (Public General Note). The remaining 667-68X fields are used for specialized information. Except for fields 678 and 680, these notes often are not written in a form adequate for public display.

670 - Source Data Found ; citations

680 - Public General Note (R) | Note that provides general information about a 1XX heading for which a specialized note field has not been defined. The note is written in a form adequate for public display.678 - Biographical or Historical Data

• Summary of the essential biographical, historical, or other information about the 1XX heading in an established heading record, an established heading and subdivision record, or a subdivision record.

670 - Source Data Found ; citations

7XX - Heading Linking Entries-General Information

• 700 - Established Heading Linking Entry-Personal Name (R)
  • Personal name heading that is equivalent to the heading contained in the 1XX field or the same record. It links headings within a system or from different thesauri or authority files.

1. For more details - please check out Slides 34 to 36
2. Examples 
3. Additional details

What a library user sees - Browse Subject Headings 

What a library sees - View title record 

FOLIO Requirements #1 - Store the Authority record   (UXPROD-2322) 

• DEV Work 
  • mod-data-import > Create MARC Authorities
  • Store MARC authority record 
    • Record Source = MARC 
    • Future, Future phase we may support Record Source = FOLIO and possibly other Record Source = TBD
  • Performance testing 
  • Unit Testing 
  • API testing 

Questions Questions NOT just for this requirement

1. Does the MARC Authority record indicate it is an Authority record ? 
2. Should we indicate the Authority controlled vocabulary used?
3. Can we support different Authority records with different Authority controlled headings 
4. What Authority MARC fields are required?
5. With current ILS which MARC fields are the most challenging to manage? (e.g. data corruption) 
6. Follow up on overlay support? 
7. Follow up on ORCID too. 
8. Would it make more sense to support just pulling LC authority files versus users loading these files?
9. Do we need to create a 999 f f <<tbd subfield delimiter>> for displaying record via MARC Authority app or GET MARC authority record API
10. Should we consider any punctuation in regards to validation?
11. What are the most important MARC tags we must validate?
12. Which MARC fields cannot be edited? 

FOLIO Requirements #2 - Retrieve/GET an Authority record for the Authority app (UXPROD-2969) 

• For the authority app, we need a way to retrieve an Authority record.
• For initial implementation we can use either <<TBD>> UUID. Not sure if it is SRS or the MARC Authority app UUID to retrieve the record. 
• OR we can use the value contained in MARC Tag 001 to return View MARC authority record 
• This record (see mockup to the right) will display in the  third pane
• Depending on estimate have this API endpoint support retrieving multiple records; this will allow libraries who need to develop their own scripts/etc. 

View MARC Authority Record (Rough draft) 

FOLIO Requirements #3 - Search/Get Authority records for the Authority app (UXPROD-2942)

• TO support the Authority app, we need a way to 
  • Search and Retrieve MARC Authority records 
• We need a way to support 
  • searching by Identifiers (MARC 001, 035, ???) 
  • Searching by Main heading types (MARC 1XX) 
  • Keyword search 
• User expectations for searching 
  • Allow search to return (MARC 4XX and 5XX)when searching just for authority records, I need to be able to search the following MARC Authority Format fields: 100 Personal name, 110 Corporate name, 111 Conference name, 130 Uniform or series title, 150 Subject, 151 Geographic place, 155 Genre. I also need to retrieve authority records based on the cross-references, i.e. the 4XX  and 5XX versions of all these fields. It is also useful to be able to search on the LCCN (Library of Congress Control number, field 010) and a system identifier, if possible.

Add a rough mockup 

Image Added

FOLIO Requirements #4 - MARC Authority results list display

• Support the ability to display 

  • Distinguish between established access points (1XX) and references (4XX)/(5XX) when searching.

• Apply new pagination component (will be available with Juniper release) - STRIPES-701
• Spike Results List Hierarchy (

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key STRIPES-739

  )
  Support the ability to display 
  • Main headings
    • See from 
    • See also 
  • Apply new pagination component (will be available with Juniper release) - STRIPES-701

Add a rough mockup 

• • (1XX) (aka access/authorized points) 
    • See from (4XX) (aka See references)  
    • See also (5XX) (aka See also from references)
• Implement shortcut keys

Add a rough mockup 

Example from another system - Hierarchy display

Image Added

Example from another system - how to distinguish MARC 1XX from MARC 4XX/5XX

Image Added

FOLIO Requirements #5 - Edit/ PUT an Authority record (

• Depending on estimate, PUT endpoint should support sending multiple IDs in support of batch editing editing
• Implement shortcut keys 

Rough mockup 

FOLIO Requirement #6 - Export Authority records 

• First phase will be to support export all results returned 
• A future phase will be to allow a user to select results to export 
• Export is important as we will not support bulk/batch editing via UI. 

ROUGH mockup 

Image Removed

FOLIO Requirement #7 - Browse Authority records Browse Authority records (

• Catalogers like to browse Authority records in order to identify errors, duplicates. etc. 

Example from another system

Image Added