Page Comparison

Summary: A breakdown of FOLIO apps and record structures as they pertain to TS work, and a mapping of Sierra record fields to FOLIO record fields, created for TS staff learning to navigate FOLIO.

FOLIO apps

FOLIO breaks out traditional TS functions into very specific "applications" within the FOLIO software suite. This is similar to Sierra's drop-down menu of functions, but the FOLIO apps are even more specific.

FOLIO record structures

We are accustomed to the Sierra way of storing records (bib records with attached orders and items, free-standing authority records, and check-in records all accessible from various Sierra modules). FOLIO significantly departs from this structure. 

Orders

The Orders app stores order information in a nested way. 

• Order (Purchase order or PO) = an entry for one or more items included in a single purchase
• Order line (Purchase order line or POL) = an entry for one individual title included in a larger order

Examples: 

Instances, holdings, and items

The Inventory app stores bibliographic information about our resources. There are three interrelated types of records in the Inventory app.

• Instance = the high-level description of any single title, including typical data points like titles, subtitles, creators and contributors, subject headings, classification, etc.  In most cases, for MSU, every FOLIO Instance will have an underlying MARC Bibliographic record as its source data. This MARC data resides in a layer called Source Record Storage (SRS). This will be the data that catalogers interact with.
   
  • Holdings
    • More localized data like call number, location, copies, notes, and more
    • Must be attached to an Instance record
      
      
    • Item
      • The most specific level of local data, including barcode, volume enumeration, etc.
      • Must be attached to a Holdings record

Image Added