Skip to end of metadata
Go to start of metadata


please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!


Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on Google Drive:

Discussion items

Product Council Update

Dracine gave the update on today's meeting. Cate Boeremagave an update on Product Owners. She introduced Lucy Lu who will be working with the Shanghai Libraries as a Product Owner. Lucy speaks Mandarin and English. Todd Olsen will be the new PO for SSO. Cate spoke about release notes based on feedback from Chalmers. Kirstin  and Maike ZBW and WDR broadcasting will be going live with FOLIO.  Chair elections for Chair and Vice Chair of Product Councils. 

Subgroup & other updates?

Data Import: MARC Holdings-to-Inventory Holdings working group will meet next week to finalize the default map. If any libraries besides Alabama, Duke, and Texas A&M plan to store MARC Holdings in FOLIO, please tell Ann-Marie BreauxASAP.

Upcoming meetings:

Cross-app searching use cases: search and results expectations?

See use cases for pre-order searching

Are there additional use cases for cross-app searching?

  • What fields would you expect to be able to search on?
  • Action: Add use cases to the pre-order searching document, but specify that a different use case.

Other use cases discussion

  • needing to use all the ways we have access to a resource. 
  • Searching MARC data from the UI. Is this a place for cross app searching?
  • Cross-app searching needed because we you don't want to have to create dummy inventory records just to assist in searching.
  • More to the point is "cross-app results" as opposed to just searching. 
  • Use case: Searching invoices and agreements
  • Keyword search in a cross app search tool, what do we expect to be indexed? 
  • Phase 2 of tags - being able to see where a tag is used across apps. Not yet implemented, but sorted out. 
  • Are there any apps that will not have a core set of elements? Example: SRS because MARC data has many unique properties. 
  • Finding commonalities of records between apps is difficult. 

How would you expect results to display? (What/how much information?)

  • Depends on what is being searched. Flexibility is key. 
  • Ability to drill down from results to origination of full record desired. 
  • Icons to label origin of info? Maybe be an accessibility issue
  • Difficult to have a result screen because of disparate data underlying apps. Maybe this is for a later phase.
  • Bento results list? 
  • Would IDs help display relationships? Relationships are important.
  • In discussion - create and agreement line for something in Inventory - right now this is possible for e-holdings. 

Cross-app Use Cases

Knowing all of the versions of an owned or accessible resource.

Need to search outside of FOLIO for owned or accessible resources.

Any place dummy records would be created could lead to a use case. 

Crossing between levels of bibliographic data, like records for a series. This was discussed in relation to having container records. 

Search results that show which institution in a consortium environment owns the resource. Consortia SIG? 

Action: App Interaction SIG meets tomorrow. If you have other thoughts, message Laura or add info here so Laura can convey ideas.

Feature review (ongoing)

MARC authority & holdings data



Where will MARC holdings data be stored, where will authority data be stored? SRS for non-bibliographic MARC data? 

Holdings: If a library chooses to store MARC Holdings, they will load into SRS. A default map will be used to populate Inventory Holdings. There are fields in Inventory Holdings not controlled by MARC.  Not part of QuickMARC editor, yet. Expectation is that they are editable in MARCCat. MARCCat may be needed for complex serials, but QuickMARC should suffice for most use cases. Note that at the moment there is no way to create in QuickMARC, only edit. Duke has holdings records for all physical monograph resources. Nice to create FOLIO Inventory holdings, initiating an underlying MARC Holdings record. 

Authorities: Do not manifest in Inventory in any way. They will be stored in SRS. They will be able to edit and create them in MARCCat. Some libraries do not store authorities locally. Duke does store MARC authorities locally. Cornell and Chicago store entire authority file locally, (Chicago, not stored in system currently, but Cornell does store in Voyager). They both use this for discovery. Discuss in Entities Management Working Group, as well as with Tiziana when she comes to our 6/18 meeting. Has needed work changed? Are architecture needs different? 

Note from chat: "There could be an advantage of having authority records in Inventory when it comes to searching on different names and headings."

Future MM meetings (ongoing)

Add ideas here




Aaron TrehubAuburn
xAnn-Marie BreauxEBSCO

Ann KardosUMass Amherst

Charlotte WhittIndex Data

Christie ThomasChicago
    Christin Seegerthbz

Colin Van AlstineSmith (FC)

Damian Biagi
xDennis BridgesStacks
xDennis ChristmanDuke University
     Douglas ChorpitaGoethe Uni Frankfurt
xDracine HodgesDuke University

Felix Hemme


Filip Jakobsen
xJacquie SamplesDuke University

Jason KovariCornell

Jenn ColtCornell

Jennifer EustisUMass Amherst

Jessica JaneckiDuke University

Kristen WilsonIndex Data
xLaura WrightCornell

Lisa FurubottenTexas A&M

Lisa McCollLehigh University

Lisa SjögrenChalmers

Lynn Whittenberger

Magda ZacharskaEBSCO

Martina Schildt


Nancy Lorimer


Natascha OwensChicago

Niels Erik Nielsen

Patty WanningerEBSCO
xRita AlbrechtHeBIS-Verbundzentrale

Sara ColglazierMHC/5C

Tiziana Possemato

Theodor Tolstoy


Wayne Schneider

Index Data

xLloyd ChittendenMarmot Library Network