2021-03-11 Metadata Management Meeting notes

Agenda/minutes

• SIG Conveners gave their monthly updates.
• Laura mentioned the concerns about the barriers to developers contributing code back to the project.
• quickMARC - issue of MARC holdings and need for them was discussed. 
• MARC Holdings timeline? - Jacquie thought she saw it was decided for Kiwi. Universities that need MARC Holdings : Is it Duke, TAMU,, Alabama, Michigan State
• Holdings vs. Authority timeline - which order will and should the development occur? Jacquie noted that MARC Holdings import may not necessarily be needed. Jason noted that shelf ready items will need the import feature.
• Support SIG has a dashboard
• Reminder - Virtual WolfCon Dates set:  June 1-3
• See Dracine's section in the minutes concerning SIG charges
• How can SIG members support POs more? How will we keep track of responsibilities. Charlotte asked for help for writing test cases for upcoming BugFest test rails. Ann-Marie asked the same for data import. Reach out to Ann-Marie and Charlotte if you can contribute.
• Magda asked for assistance for the FOLIO Tips and Tricks for the Data Export page.
• "Pointing system for prioritization" for features. 
• Today and tomorrow are the last days to vote for community council. Outcomes should be shared on Monday around noon EST.

Homework

• Current terms got 1 "pro" but no vote.
• 3 votes for "old school" . Laura expressed concerns that this may not be useable by other schemas.
• Charlotte suggested asked Wayne Schneider who has done mapping work for the Library of Congress.
• Comparison tool for MARC to Bibframe - https://id.loc.gov/tools/bibframe/compare-id/full-rdf?find=5226
• Do we need to reconsider the RDA vocab we use for Resource Type
• Jacquie expressed hesitancy in creating a new vocabulary just for FOLIO
• Christie - We're putting a big burden on "mode of issuance". What do we really want this to do for us? What does mode of issuance need to do inside of FOLIO and outside of FOLIO. Mode of issuance is inflexible compared with other reference data. Several issues to work through. 
• Charlotte pointed out that it is tied to the data import. 
• Felix: When they run reports for national library statistics, they have a need to distinguish types of resources
• Ann K. "That’s correct—our front end folks have no idea what those formats mean" (Front end - circ folks) 
• Felix - They have identified this lack of format clarity as a gap. 
• Charlotte:
  • UXPROD-1634 (index title/title)
  • UXPROD-2667 (sort on contributor, when more than one contributor is listed)
  • UXPROD-2668 (Adding instance HRID)
  • UXPROD-2669 (Adding resource type)
  • UXPROD-2670 (Adding format)
  • UXPROD-2671 (Adding edition)
  • UXPROD-2703 (Adding publication date)
• Christie (via chat) - "I think it is a problem for end users. I find the filters really unusable. I agree with you that being able to change the labels would help this, but also having the limiters only include values that are relevant to the result set.  For instance, all formats are listed even if the results only include two or three of them. Having fewer formats to choose from when limiting a search would help."
• Ann K (via chat) - "+1 Christie—our access services, etc. people have found the filters unusable. Ditto for running a search and filtering to find results for a metadata task."
• Jacquie (via chat)  - "+1 Christie and Ann"
• Conclusion: Leave values as they are, focus efforts on ability to labels, values, reference data more readily.

(if time permits)

Cornell has made some changes, mapping most notes to "general note" and creating some specific custom note types for music (mapped from 382, 383, 384)

x

VZG

Stanford

Index Data

Missouri States University