Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


No Product Council Update

PC did not meet this week (pre-empted by stakeholders' meeting)

Re-ranking (Capacity Planning Review) debriefLaura Wright

Consistent definition of "Go live" is desirable. 

Does go live mean "deal-breaker" or is a separate "deal-breaker" flag needed? What are we all considering "go-live" to mean?

Jennifer Eustis said at 5-colleges "Go Live" means "deal-breaker". Cornell was not necessarily thinking this way. They were considering work-arounds, if a work-around is available then they were not assigning a "go-live" status. 

Ann Kardos - Commented that this is an opportunity to rethink what they are doing completely.

Patty - "Go-live" was chosen instead of "deal breaker" to convey a concept of a "pioneer spirit". 

Jason - Some institutions are more risk adverse than others. Jason pointed out the concept of the MVP is a different construct than a "Go-live"

Suggestion: This should go to product council to define.

Christie Thomas - "Go-live" should be deal-breakers. At Chicago they are trying to be accommodating to contribute, however, even if a workaround is possible, it is not necessarily feasible. We should assume best intentions - everyone is trying their best. 

Sara - The Jira tickets are not as clear as they could be. They are easily interpreted in different ways. The review may need to be done multiple times, possibly looking at issues in a holistic way. 

Subgroup Updates and Other Updates

Batch Editing in FOLIO

Use cases for batch editing needs both within and across apps:

1) Identification & selection of records to be acted on

2) Definition of edits to be made (and implementing those changes)

e.g., find/replace; delete field

serverFOLIO Issue Tracker

Where/how should the identification & selection occur?

Where/how should the editing occur?


Multiple Graphical Representations

STILL ON HOLD for future meeting (possibly with representative members from Tech Council)

working document:


  • If multiple forms of the value are represented in a single JSON object, both scripts have to be included in a single value cell. This limits the search function.
  • Chicago is testing graphical representation in FOLIO. Here is an example:

  • See MARC record:
  • See JSON sample: (Christie will provide)
  • Functional requirements need to be built so developers can understand the issues. What would we like to have happen in FOLIO?
  • Proposed solution:
    • Single JSON object for the property, e.g., Title, with the ability to have an array of values for display (labels).

    • Values should allow for a property that identifies the script.

    • This would allow for the ability to configure displays to include multiple representations or a selection of representations.

Functional requirement: Create an instance record and be able to have multiple graphical representations of the language, or be able to put a non-transliterated title that can be searched in other scripts.

Note: Charlotte has added following feature description (UXPROD) in Jira: 

serverFOLIO Issue Tracker

Christie expressed hesitation about being too prescriptive about what the JSON should look like. She suggested spending time on the Functional Requirements. Suggestions for additional functional requirements were added to the Google doc: DRAFT - Multiple graphical representations in FOLIO. (Also linked above.) 

The group also would like to make recommendations as to what this should look like in the FOLIO interface. Example systems that work well?

Future meeting topics

Source of truth (SRS). Review the FOLIO metadata flow based on test of the newly implementation of edit freeze of records in Inventory when having only SRS and Inventory installed. Is the freeze to happen between SRS and Inventory, or freeze of Inventory is only when there is a MARCcat equivalent of the Inventory record?

Rename the Notes accordion in Instance, Holdings, Item and Container record to be renamed, in order to distinguish between the new Notes app ( and the notes we have in the metadata records.

Inventory Permissions (

serverFOLIO Issue Tracker

Search enhancements - possible also look at more general requirements for defining search, e.g. when to use: Phrase search, Truncating (left and/or right), Stemming, Nested search, Boolean search, etc. (TC and MM task)

Authority Data and Inventory Vision (small group work first)

Discovery – need to clarify sources of data for discovery vs. data needed for operations; this needs to be documented for the entire FOLIO community and direction should come from Product Counil

Item record statuses and the apps that affect them

Music / Maps / Media cataloging review of data elements in Inventory

Felix (via chat) "@charlotte: I could ask a colleague (from one of the 180 network libraries) if she/he could review the beta elements from a 'musical' point of view."

Texas A&M may have a music cataloger that can help.

Christie offered to load cartographic and music data from other libraries into their test FOLIO instance.

Jennifer (via chat): We should also look at video as well. Videos have other standard numbers EAN for instance and fields that people like to search and discovery them by




xAaron TrehubAuburn
      Alice Krim
xAnn-Marie BreauxEBSCO
xAnn KardosUMass Amherst


Charlotte WhittIndex Data

Christie Thomas

Colin Van AlstineSmith (FC)

Damian Biagi

Dennis BridgesStacks

Dennis ChristmanDuke University

Dracine HodgesDuke University


Filip Jakobsen

Jacquie SamplesDuke University

Jason Kovari

Jenn Colt

Jennifer EustisUMass Amherst

Jessica JaneckiDuke University

Kristen WilsonIndex Data
xLaura WrightCornell

Lisa FurubottenTexas A&M

Lisa McCollLehigh University

Lisa Sjögren

Lynn Whittenberger

Martina Schildt


xMary AlexanderUniv. of Alabama

Nancy Lorimer


Natascha Owens

Niels Erik Nielsen

Patty Wanninger
xRita AlbrechtHeBIS-Verbundzentrale

Sara ColglazierMHC/5C

Sarah RossCornell

Sarah SchmidtDuke University

Tiziana Possemato

Theodor Tolstoy

Wayne Schneider

Index Data