2022-11-03 Metadata Management Meeting notes

Owned by Charlotte Whitt
Last updated: Nov 03, 2022 by Raegan Wiechert
7 min read

Date

Charlotte Whitt Raegan Wiechert Jacquie Samples Jennifer Eustis 


Recordings of meetings can be found in the Metadata_Management_SIG > Recordings folder on AWS from 2022 onwards: https://recordings.openlibraryfoundation.org/folio/metadata-management-sig/

Discussion items

Notetaker

Caitlin Stewart 

Announcements


From Jana Freytag: I wanted to bring the CDL-Subgroup to your attention again. We are a subgroup of the RA SIG and are looking for input by MM folks on Controlled Digital lending processes in FOLIO. We have a new and hopefully better fitting meeting slot (Tuesdays 12 - 1 pm EST). We have the slack channel #cdl-subgroup and agendas here: https://folio-org.atlassian.net/wiki/display/RA/2022-11-08+CDL+Sub-group+Meeting+Notes


November 24 meeting will be cancelled because of Thanksgiving in the U.S.

PC update

Sharon Wiles-Young 

  • Onboarding working group- to help new members and institutions implementing FOLIO to introduce and join the community, to provide a sense of belonging in community, understand community needs and resource needs
  • Bugfest starting and also the Implementers SIG will devote their meeting time to testing 
  • FOLIO China announced 2 new members to bring a total of 18 implementing libraries
  • SIG meetings: discussed summarizing the notes and concerns from all the SIGS and finding critical needs and trying to take action
  • Community Council summarized comments from institutions about what could be better in FOLIO and provided an overview slides of comments and action items that need to be addressed by the FOLIO governance teams
    • Discussion of what PC should address. Onboarding, roadmap/priorities, resourcing and development contributions to the project



Jennifer Eustis 


MM SIG Release Note & Other Highlights

  • Check MM dashboard
  • Please sign up for Bugfest




Inventory UX

Charlotte Whitt 

Raegan Wiechert 

Discuss simple vs advanced search

Simple Search

Search on Locations - tricky because locations are hierarchical structure

Decision: add ability to search on null value in simple search interface

Need to be able to do an exact title search e.g. "starts with" / left-anchored

Need to be able to filter on an exact title search

Tradeoffs - if we add browse capability then we lose filters

Could we add way to search for invalid UTF-8 filters

Question: what is the best way to display results? Maybe be more a question of how to display results (rather than what's returned)

Include numbers / identifiers in simple search?

How will authority records be handled? How will we know which LCCN we are searching against?

  • Right now MARC Authority goes against MARC authority app - need examples of different types of prefixes and different types of normalization


Advanced search

  • Should include all simple search options plus additional items
  • Suggestion: have a dropdown for each of the 3 record types and then a second dropdown for the element we are looking for (e.g. permanent location in holdings, material type in item, and statistical code in Instance)
  • Idea - save query then combine with filters
  • Need ability to search by Note types
  • Need ability to save and share queries
    • If there is a query manager, need a way to track last time used, share notes on it etc to prevent clutter in large orgs
    • This would be a new app
      • As an intermediary step you could download a query from the query manager and load into an app to run query or edit it
    • Need fuzzy and near searching
    • Question: how does elastic search handle "And" from "Romeo and Juliet"
    • Wildcards
      • exists in simple search
      • have a ticket in to mask characters in advanced search (not yet implemented)
      • Should also be able to use wildcard in advanced search
      • Is there a way to escape the asterisk in search? Some collection names have asterisks.

Capture notes: UI Search Enhancements

Action Item: Please review and contribute use cases to  UI Search Enhancements by  

Charlotte Whitt provide list of reserved characters in search interface  







Chat:

10:34:21 From  Laura (she/they)  to  Everyone:
    thank you, Caitlin, for joining MM and for taking minutes!
10:51:20 From  Lynne Fors  to  Everyone:
    I would also like to filter on Library.  We have locations associated with specific branch library
10:52:04 From  Lynne Fors  to  Everyone:
    both simple and advanced search would be beneficial
10:52:47 From  Alissa Hafele  to  Everyone:
    +1 We would also like to be able to facet on library or campus.
10:52:56 From  Alissa Hafele  to  Everyone:
    (Stanford)
10:56:04 From  Kimberley Nohr (she/hers)  to  Everyone:
    is it possible to be able to search by field through this simple search?
10:56:12 From  Kimberley Nohr (she/hers)  to  Everyone:
    MARC field.
10:56:29 From  Laura (she/they)  to  Everyone:
    MARC data is not indexed here
10:56:32 From  Kimberley Nohr (she/hers)  to  Everyone:
    Ahh.
10:56:49 From  Laura (she/they)  to  Everyone:
    the search is for the instance data (or holdings or items), not underlying source
10:57:02 From  Kimberley Nohr (she/hers)  to  Everyone:
    Ah. Thanks Laura.
10:57:53 From  Lynne Fors  to  Everyone:
    Simple searching Instance notes and admin notes
10:58:46 From  Jacquie Samples -- Duke  to  Everyone:
    Searching for results with the Boolean NOT can be so useful!
10:58:54 From  Sharon Wiles-Young  to  Everyone:
    sorry have to run to another meeting thanks
10:59:08 From  Jennifer Eustis (she/her)  to  Everyone:
    +1 to being able to search blanks
11:01:18 From  Christie Thomas (she/her)  to  Everyone:
    Boolean searching is definitely necessary.
11:01:52 From  Christie Thomas (she/her)  to  Everyone:
    I think that limiting Boolean operators to the advanced search is okay.
11:01:52 From  Robert rscheier@nelib.org  to  Everyone:
    +1 for searching on NULL or Empty
11:03:05 From  Stewart, Caitlin  to  Everyone:
    +1 for searching on NULL or Empty
11:03:36 From  Laura (she/they)  to  Everyone:
    "does not exist"
11:03:49 From  Jacquie Samples -- Duke  to  Everyone:
    Maybe "Is Not" in the filter?
11:04:01 From  Jacquie Samples -- Duke  to  Everyone:
    Is not XX value I meant
11:04:24 From  Laura (she/they)  to  Everyone:
    YES to the "blanks" filter analogy
11:04:33 From  Robert rscheier@nelib.org  to  Everyone:
    Love that filter
11:04:35 From  Stewart, Caitlin  to  Everyone:
    I am not a Search expert but I'm pulling this from our search reqs: "Call number browse must support a mechanism to display holdings where MARC 852 Indicator 1 is null or blank."
11:04:53 From  Jacquie Samples -- Duke  to  Everyone:
    I think that is an excellent example, Christie.  I find the unexpected (needed) cleanups in that way. all too often.
11:05:09 From  Natascha Owens (she/her)  to  Everyone:
    I would like to be able to search by exact phrase in simple search
11:05:19 From  Jennifer Eustis (she/her)  to  Everyone:
    Yes!!! to cross elements
11:05:48 From  Christie Thomas (she/her)  to  Everyone:
    +1 to searching across elements and +1 to exact phrase searching.
11:05:53 From  Jackie Magagnosc  to  Everyone:
    Thank you for bringing this up Laura!
11:06:55 From  Jacquie Samples -- Duke  to  Everyone:
    +1 Christie and Laura!
11:09:58 From  Lynne Fors  to  Everyone:
    A way to search for invalid UTF8 characters!  It's a problem we have recently found and have no way to find them currently or know what the invalid character is.
11:10:45 From  Kara Hart (she/hers)  to  Everyone:
    It would be nice if the browse could be filtered too
11:12:03 From  Bausenbach, Ardie  to  Everyone:
    does folio differentiate between left-match "starts with" vs browse (given that browse lists are generally not filterable since browse implies a continuous listing
11:12:59 From  Laura (she/they)  to  Everyone:
    yes to what Colin just said -- all types of titles need to be included!
11:18:36 From  Jacquie Samples -- Duke  to  Everyone:
    We also use the LCCN in searches, too. So, having it in Simple Search would be helpful.
11:20:57 From  Bausenbach, Ardie  to  Everyone:
    we use info:lccn normalization for prefixes
11:22:33 From  Bausenbach, Ardie  to  Everyone:
    Ardie Bausenbach (abau@loc.gov)
11:24:49 From  Lynne Fors  to  Everyone:
    I'd like to have a dropdown for each of the 3 record types and then a second dropdown for the element we are looking for.
11:25:21 From  Jennifer Eustis (she/her)  to  Everyone:
    I like that idea Lynne
11:25:23 From  Lynne Fors  to  Everyone:
    Like search for permanent location in holdings, material type in item, and statistical code in Instance
11:25:28 From  Jacquie Samples -- Duke  to  Everyone:
    I agree that all of the Simple Searches should be included in the Advanced options.  Plus multiple record types.
11:25:43 From  Kimberley Nohr (she/hers)  to  Everyone:
    +1 to Lynne's suggestion.
11:26:03 From  Jacquie Samples -- Duke  to  Everyone:
    Or, should we have the dropdown include all the types, then the AND part of the modal will pick everything up.
11:26:07 From  Bausenbach, Ardie  to  Everyone:
    Does "advanced search" imply keyword - or does it also include "starts with" and/or browse?
11:26:24 From  Amanda Scott  to  Everyone:
    For advanced search: Perhaps search by uniform title, although an exact phrase search on all titles in simple search might be sufficient.
11:27:00 From  Bausenbach, Ardie  to  Everyone:
    how will advanced search control nesting?
11:31:05 From  Lynne Fors  to  Everyone:
    A way to save your advanced search query if you need it at a later date
11:32:02 From  Lynne Fors  to  Everyone:
    Should be able to search unique note types created and used by specific tenants
11:39:14 From  Lisa F. (Cataloging)  to  Everyone:
    'retain last search' is something that OCLC lets you select or not.  is that also what you would like?
11:40:02 From  Jennifer Eustis (she/her)  to  Everyone:
    Yes to sharing. You could do it on the dashboard
11:40:37 From  Lynne Fors  to  Everyone:
    +1 to Lloyd and Jacquie
11:41:35 From  Kara Hart (she/hers)  to  Everyone:
    But if you could upload it in advanced search and then edit that might work
11:47:10 From  Jacquie Samples -- Duke  to  Everyone:
    I think it is looking promising, too, Charlotte!
11:55:50 From  Kara Hart (she/hers)  to  Everyone:
    Will wildcards be in advanced search?
11:57:06 From  Kara Hart (she/hers)  to  Everyone:
    Thank you!
11:58:05 From  Laura (she/they)  to  Everyone:
    sorry, need to drop off; thank you, Charlotte
11:58:58 From  Jacquie Samples -- Duke  to  Everyone:
    Thanks Charlotte and everyone!  I have a 1PM and have to go.
11:59:30 From  Stewart, Caitlin  to  Everyone:
    I also need to go - I added notes to the wiki page. Thanks everybody!
12:00:31 From  Lynne Fors  to  Everyone:
    Thank you Charlotte and everyone for a great discussion
12:00:34 From  Jennifer Eustis (she/her)  to  Everyone:
    Thank you so much Charlotte!