Attendees

Charlotte Whitt

~36

Note taker: Laura Daniels, Lynne Fors, Alissa Hafele, Natascha Owens

Recordings

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

Announcements		WOLFcon: Felix will submit a MM SIG working meeting as standard (50 minute) session. Content will be worked out later. A reporter from the quickMARC Group is needed. If you are attending quickMARC and MM SIG and would be willing to regularly report back to MM SIG please reach out.
Custom fields for Inventory	Björn Muschall	Leipzig University with small dev team are in process of getting custom fields added to apps - Orders in process (2 sprints left), next is Inventory. Already implemented in Users Khalilah is feature owner for Custom Fields Inventory tickets UXPROD-2211 and UXPROD-2848 Custom fields setup in Settings - App. See Users as example Type of field, e.g. single select or radio button field label and help text hidden and required (default) options Search Plan all custom fields will be available in the filters and searchable via keyword and all shown as single search option from dropdown. Is that desirable? Laura: suspects we wouldn't agree to what to add to keyword search - limited right now. Should be in separate index, not keyword Could be added to All index? Yes Laura: Cornell doesn't have it turned on Custom fields added at end of filter list - not customizable Query search? should work but will look into. Data not part of actual records. Stored in separate table. Available in metadb? Will ask about this and List app availablity. Where should the fields be in the records? In settings? Any thing added to item records should involve input from RA SIG Laura: should probably be put at bottom, MM SIG could consult with colleagues. Will start at end of list and then bring to MM SIG for review. Custom fields accordion will display even if nothing configured? Yes Deletion of custom fields if you delete a custom field in settings that is used in a record you are deleting the settings AND the values stored in records. Warning modal if records exist. Any development will be available across all apps Questions from group Would you want it implemented for all Inventory record types? Charlotte: makes sense to implement for all while doing the work. +1 from others LOC wrote some desired specs for custom Instance fields - Library of Congress local fields requirements Can MARC data be mapped to custom fields? Available via api but question for data import group In inventory using elastic search so different from Orders app searching - accounted for in search ticket? Will require mod-search work. Is there a limit for how many custom fields which can be added? 5+ not sure, will ask dev team. Can only have 1 custom fields accordion per area, e.g. instances, holdings, or items Need way to identify the records even if search is not implemented yet to review e.g. before field deletion At minimum would want "has custom field" yes or no filter, e.g. suppress from discovery Each custom field will have a filter and those should be used. Will be implemented alongside the addition of custom fields to Inventory Any UX alignment possible with ERM solution? done in completely different approach Is there a way to use Lists App to find custom fields? Or can these custom fields be added to the Lists App?
Multiple graphical representations continued	Laura E Daniels	Continuation of discussion during 2024-01-25 Metadata Management Meeting notes Slide deck with proposal and outstanding questions Postponed to next week
PC updates	Charlotte Whitt	No PC meeting today
BELA (Bulk Edit and Lists App)	Jennifer Eustis	Magda Zacharska is collecting UAT feedback until Friday, March 29th. For this round of testing we are going to use FOLIO snapshot environment. Test data and test scenarios are located in the Bulk edit Google drive. If you have any questions, please feel free to reach out here or directly to Magda. Any feedback you can provide will be helpful and highly appreciated!
Data Import Working Group	Jennifer Eustis

Chat

08:30:55 From Felix Hemme to Everyone:
Today's agenda: https://folio-org.atlassian.net/wiki/x/AQDXAw
08:34:06 From Lynne Fors to Everyone:
+1 Laura
08:37:50 From Laura Daniels to Everyone:
not everyone in MM may be familiar with Users!
08:38:00 From Laura Daniels to Everyone:
so a quick overview might be helpful
08:38:13 From Sara Colglazier to Everyone:
Yes, please. some broader background
08:39:15 From Lynne Fors to Everyone:
https://folio-org.atlassian.net/browse/UXPROD-2211
08:39:35 From Lynne Fors to Everyone:
https://folio-org.atlassian.net/browse/UXPROD-2848
08:40:47 From Sara Colglazier to Everyone:
Reacted to "https://folio-org.at..." with 🙂
08:41:45 From Laura Daniels to Everyone:
So all custom fields appear in the same accordion?
08:42:10 From Felix Hemme to Everyone:
That is how it works in Users, but not sure about Orders
08:42:14 From Sara Colglazier to Everyone:
And how does it work with updates (flower to flower, etc)
08:42:22 From Charlotte Whitt to Everyone:
Can costom fields be added to existing accordions
08:42:33 From Laura Daniels to Everyone:
Reacted to "That is how it works..." with ✅
08:42:44 From Laura Daniels to Everyone:
Reacted to "Can costom fields be..." with 👆
08:43:32 From Lynne Fors to Everyone:
Reacted to "Can costom fields be..." with 👆
08:43:33 From Laura Daniels to Everyone:
Some examples of how libraries are using custom fields in other apps might be useful also
08:43:47 From Gerhard, Jeffery to Everyone:
Hi Björn, Library of Congress wrote up some desired specs for custom Instance fields that are NOT currently part of our Ebsco development plan. Can I share them with you in case it gives your team any ideas?
08:43:53 From Christie Thomas (she/her) to Everyone:
What are the implications for for the marc to instance map? Can marc data be mapped to inventory custom fields?
08:44:10 From Laura Daniels to Everyone:
Reacted to "What are the implica..." with ➕
08:44:16 From Lynne Fors to Everyone:
Reacted to "What are the implica..." with ➕
08:45:08 From Laura Daniels to Everyone:
Replying to "Hi Björn, Library of..."

if you're able to share these with MM, I'm sure they would be of interest to many of us
08:45:21 From Gerhard, Jeffery to Everyone:
Reacted to "if you're able to sh..." with 👍🏻
08:45:27 From Felix Hemme to Everyone:
Reacted to "if you're able to sh..." with 👍🏻
08:45:30 From Gerhard, Jeffery to Everyone:
Replying to "Hi Björn, Library of..."

yes we can share
08:45:48 From Sara Colglazier to Everyone:
Can you have the component more than once within an app?
08:45:59 From Laura Daniels to Everyone:
Replying to "Hi Björn, Library of..."

👍
08:46:43 From Magda Gad to Everyone:
Reacted to "if you're able to sh..." with 👍🏻
08:46:50 From Laura Daniels to Everyone:
My biggest concern is making sure we don't create problems with import/export... but I love the idea of custom fields
08:48:58 From Christie Thomas (she/her) to Everyone:
Reacted to "My biggest concern i..." with ➕
08:49:14 From Laura Daniels to Everyone:
I also think it would be valuable to have the option to create them, even if we couldn't (yet) search by them
08:49:21 From Lynne Fors to Everyone:
Reacted to "My biggest concern i..." with ➕
08:49:43 From Charlotte Whitt to Everyone:
Reacted to "I also think it woul..." with 👍🏻
08:49:50 From Charlotte Whitt to Everyone:
Reacted to "My biggest concern i..." with ➕
08:50:15 From Christie Thomas (she/her) to Everyone:
Reacted to "I also think it woul..." with 👍🏻
08:50:27 From Charlotte Whitt to Everyone:
Reacted to "Hi Björn, Library of..." with 🌸
08:50:30 From Charlotte Whitt to Everyone:
Reacted to "if you're able to sh..." with 👍🏻
08:51:18 From Felix Hemme to Everyone:
+1 Laura. I would not want custom field added to keyword search
08:51:26 From Lynne Fors to Everyone:
Reacted to "+1 Laura. I would no..." with ➕
08:51:28 From Kalli Mathios to Everyone:
Reacted to "+1 Laura. I would no..." with ➕
08:51:43 From Felix Hemme to Everyone:
And in the All index
08:52:16 From Laura Daniels to Everyone:
Replying to "And in the All index"

Yes, I tend to forget about "All" because we don't have it turned on
08:52:55 From Laura Daniels to Everyone:
Reacted to "And in the All index" with 👍
08:52:55 From Kalli Mathios to Everyone:
Reacted to "And in the All index" with ➕
08:52:57 From Magda Gad to Everyone:
Reacted to "And in the All index" with ➕
08:52:58 From Laura Daniels to Everyone:
Reacted to "And in the All index" with ➕
08:53:00 From Sara Colglazier to Everyone:
All should be all!
08:53:14 From Charlotte Whitt to Everyone:
Reacted to "All should be all!" with 👍🏻
08:53:21 From Kalli Mathios to Everyone:
Reacted to "All should be all!" with 👍🏻
08:53:40 From Magda Gad to Everyone:
Reacted to "All should be all!" with 👍🏻
08:54:15 From Sara Colglazier to Everyone:
What about Query search?
08:54:22 From Charlotte Whitt to Everyone:
Is there a limit for how many custom fields which can be added
08:54:38 From Laura Daniels to Everyone:
Replying to "What about Query sea..."

I believe Query search depends on what is indexed
08:55:57 From Laura Daniels to Everyone:
if it's stored in a separate table, we need to consider how that impacts export options
08:56:32 From Felix Hemme to Everyone:
Reacted to "if it's stored in a ..." with 👍
08:57:41 From Laura Daniels to Everyone:
I see a lot of potential here for, e.g., tracking productivity stats
08:59:34 From Charlotte Whitt to Everyone:
Reacted to "if it's stored in a ..." with 👍
08:59:57 From Sara Colglazier to Everyone:
Po & POL ?
09:02:59 From Gerhard, Jeffery to Everyone:
Sure. I will share our document to the MM Slack channel
09:03:24 From Laura Daniels to Everyone:
Yes, if we implement it, it would be best to do so for all record types
09:03:30 From Gerhard, Jeffery to Everyone:
And happy to discuss it at a future SIG meeting
09:03:38 From Charlotte Whitt to Everyone:
Reacted to "Yes, if we implement..." with 🌸
09:03:41 From nancy lorimer to Everyone:
Reacted to "Yes, if we implement..." with 🌸
09:03:45 From Felix Hemme to Everyone:
Reacted to "And happy to discuss..." with 👍
09:03:46 From Charlotte Whitt to Everyone:
Reacted to "And happy to discuss..." with 👍
09:04:09 From Sara Colglazier to Everyone:
Reacted to "And happy to discuss..." with 👍
09:04:10 From Laura Daniels to Everyone:
Reacted to "And happy to discuss..." with 👍
09:04:12 From Kalli Mathios to Everyone:
Reacted to "And happy to discuss..." with 👍
09:04:37 From Magda Gad to Everyone:
Reacted to "And happy to discuss..." with 👍
09:04:46 From Charlotte Whitt to Everyone:
Maybe also take a quick look at Settings > Inventory and talk about where it should be listed in the sub menus
09:07:22 From Laura Daniels to Everyone:
ideally, of course, the order of elements could be customized locally!
09:09:33 From Laura Daniels to Everyone:
I like the "save & lose data" option as a model in settings
09:09:47 From Charlotte Whitt to Everyone:
Reacted to "I like the "save & l..." with 😅
09:09:53 From Felix Hemme to Everyone:
Replying to "I like the "save & l..."

With its own dedicated permission I hope ;)
09:10:16 From Laura Daniels to Everyone:
Replying to "I like the "save & l..."

absolutely, a dangerous but useful option
09:10:25 From Charlotte Whitt to Everyone:
Reacted to "With its own dedicat..." with 💯
09:10:29 From Laura Daniels to Everyone:
Reacted to "With its own dedicat..." with 💯
09:10:33 From Felix Hemme to Everyone:
Reacted to "absolutely, a danger..." with 👍
09:12:06 From Sara Colglazier to Everyone:
Ah, yes, Lists … we should talk to BELA then to be able to get at the info then
09:12:38 From Lynne Fors to Everyone:
Reacted to "Ah, yes, Lists … we ..." with ➕
09:18:23 From Lynne Fors to Everyone:
So like how Suppress from Discovery has yes/no as your filter option
09:19:50 From Laura Daniels to Everyone:
Re: deletion, an institution could always just not give anyone permission to save & lose data
09:27:07 From Bob Scheier (Holy Cross) to Everyone:
And LDP and MetaDB
09:27:19 From Charlotte Whitt to Everyone:
Reacted to "And LDP and MetaDB" with 💯
09:27:34 From Bob Scheier (Holy Cross) to Everyone:
Reacted to "And LDP and MetaDB" with 💯
09:27:36 From Bob Scheier (Holy Cross) to Everyone:
Removed a 💯 reaction from "And LDP and MetaDB"

Browser not supported