Versions Compared


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


Product Council Update

There was a presentation from the Capacity Planning Team regarding the MVP and the prioritization of feature. The Council tentatively approved the recommendation from the Capacity Planning Team. Goal - identify what libraries will be able to implement based on the Capacity Planning Team's recommendations. By August 27

Subgroup Updates and Other Updates

Metadata Export Group: Magda reported: This new group will meet on Thursdays between 2:00 and 3:00 pm. Meetings will be recorded. The first meeting will be scheduled for August 29th. 

Christie and Laura joined the first part of today's RA meeting to speak with the group about bound-with materials. Laura will work on a mock-up.

Feature ranking/new features?

UXPROD-1922  Item. Easy copy of barcode and make barcode a link in item list

UXPROD-1923  Settings > Inventory > Item: Implement material type category

UXPROD-1924  Item. Copy should not be a repeatable element

UXPROD-1889  Instance: Delete warning when deleting format or contributor type

UXPROD-1890  Instance: Additional controlled vocabularies for Instance menus

UXPROD-1891  Instance: Lookup by code (contributor type, resource type and format)

UXPROD-1892  Instance: Add related instances data element

UXPROD-1893  Instance: Implement preceding and succeeding titles

UXPROD-1894  Settings > Inventory > Instance: Implement format category

PO-MVP/MVP and Capacity Planning updateLaura WrightInventory features - CWFeaturesByEpic
Search in Inventory update, mock-upCharlotte WhittSlide deck - Search in Inventory - UXPROD-140 (Misc. UX) –  (smile) and not completely done (time was running too fast)

Multiple Graphical Representations

Laura, Christie, and Jacquie met with Tech Council Aug. 7 – still some work to be done around ideal display options and sample data

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.

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

Ann-Marie BreauxEBSCO

Ann KardosUMass Amherst


Charlotte WhittIndex Data
xChristie ThomasChicago
xColin Van AlstineSmith (FC)

Damian Biagi

Dennis BridgesStacks
xDennis ChristmanDuke University
xDracine HodgesDuke University

Filip Jakobsen
xJacquie SamplesDuke University
xJason KovariCornell
xJenn ColtCornell
xJennifer EustisUMass Amherst
xJessica JaneckiDuke University

Kristen WilsonIndex Data
xLaura WrightCornell
xLisa FurubottenTexas A&M
xLisa McCollLehigh University

Lisa SjögrenChalmers
xLynn Whittenberger

Martina Schildt


Mary AlexanderUniv. of Alabama

Nancy Lorimer


Natascha OwensChicago

Niels Erik Nielsen

Patty WanningerEBSCO
xRita AlbrechtHeBIS-Verbundzentrale
xSara ColglazierMHC/5C

Sarah RossCornell

Sarah SchmidtDuke University

Tiziana Possemato

Theodor Tolstoy


Wayne Schneider

Index Data