Skip to end of banner
Go to start of banner

2023-09-21 Metadata Management Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Date

Charlotte Whitt Felix Hemme Raegan Wiechert Ann-Marie Breaux (Deactivated) Jennifer Eustis Adam Cottle Amanda Scott Amanda Sprochi Robert Scheier Catherine Tuohy Dwayne Swigert emily.semenoff@colorado.edu Jackie Magagnosc Kara Hart Laura E Daniels Linda Turney Lloyd Chittenden Lynne Fors Mary Aycock morganm@gvsu.edu Natascha Owens Nicole Smeltekop, Paulina Czyzewics, Former user (Deleted) Amanda Ros Ryan Tamares Sara Colglazier Seth Huber, Sheila Torres-Blank, Thomas Trutt 


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

NotetakerNatascha Owens 
Announcements

As your Product Council members, we are both in search of 3 people’s opinions on “Things that could be better about FOLIO”. Please DM Charlotte Whitt or Jennifer Eustis on Slack if you’d like to help us, identify topics which you'd like us to bring back to the Community Council (CC), Technical Council (TC) and Product Council) and add to the list started by Tom Cramer. Big thanks for all help/input/comments/concerns in advance

Thomas Trutt - new PO for Item States

PC update

PC meeting minutes 9/21/2023

PC meetings has introduced a new schedule: Thursdays 10 am - 10:55 am EST

3 new subgroups:

  1. Re-architecting impacts: Wiki Page. The working group has had 2 meetings. Purpose: evaluate the proposal for Re-achitecting the FOLIO as product. This proposal was presented by Vince Bareau and Craig McNally at a couple of sessions at WOLFcon.
  2. SIG Updates: Wiki Page. 4 members. Reviewing the monthly SIG reports while there is a sense that the current isn't surfacing problems and we want to restructure this. This group is also trying to think how this ties in with the Roadmap. The subgroup will also look at the scope, and model for the Re-architecting work presented by Vince Bareau. This new work need to be anchered in one of the existing SIG. Kristin Martin suggest that the PC do a regular SIG report in one of the upcoming meetings in October.   J. Eustis: Group is creating a template to submit issues to PC. 2nd meeting is tomorrow.
  3. Meeting Hygiene: Meet first time yesterday, and will meet every 2 weeks. Converted the ideas from the PC shoulder meeting on 8/25/2023, and converted it to a spread sheet: a) structure, ...

      Meeting times to be more inclusive for people not is Europe and US. 

List App: This app was approved by the PC, but the TC review is still in process. Will meet tomorrow for final decision.

Quesnelia release: Proposal to set the initial date for the planned Quesnelia release until April 29th - [draft] Quesnelia (R1 2024) - The date is picked to avoid conflict with Easter Holiday and Spring Breaks. 



TestRails

Creating/Updating TestRails Presentation slides:

If folks in MM SIG have time or inclination–it would be fantastic to have help with writing some of the cases that pertain to existing JIRA's or tests that relate to workflows, etc. that we work with in day-to-day life. 

View presentation slides for: key terminology used by TestRails; how to get started contributing to TestRails; how to find (and/or create) tests to work on; sample TestRail cases.  For guidance on navigating TestRails it may be useful to watch recording of today's meeting.

Removing blank spaces from some data elements

UXPROD-3473 - Getting issue details... STATUS

Continuation of discussion from last week's meeting.  JIRA for adding copy icon to Instance Classification: UIIN-2580 - Getting issue details... STATUS

UXPROD-3473 : Strip leading, trailing, and double spaces out of data in some elements (instance, holdings, items)

Spaces get saved and are indexed that way

WolfCon conversation just discussed leading and trailing spaces

We should think about which elements we want this for (or for which we would NOT want this)

Leading and trailing spaces should not be stored - can't think of a use case where we would want whitespace retained

Container RecordsSara Colglazier 

https://wiki.folio.org/x/5wISC - if you have use cases not currently covered, add to this page for App Interaction to discuss

Updates from App Interaction - do we still need container records or do these updates cover all of our use cases?

Sara Colglazier - Package POL has not actually changed since the beginning; would like to see some enhancements to the functionality of the "Package POL"; would also like to rename Package POL since it is misleading (perhaps "Container POLs"?)

"Packages" are not only useful for e-resources:

Sara thinks Package POL's are useful for ongoing orders, approval plans - demonstrated creating a Package POL in Orders App; linking titles to Package POL; Analyzed or Monographs Classed Separately titles–all on separate Instance records but can be linked to one Package POL

Right now, links to Packages can only be made at the Instance level; don't need separate PO's created for each item rec'd on an Approval plan (or titles that are lumped together under one payment)

Demonstrated linking to an Inventory search from Package POL to list all titles included in Package (used Keyword search using "Container code" which is added locally to an 035 in MARC record)–a way to manage e-resources by creating sets

Also useful for print + online subscriptions; e-book collections



MM Dashboard with Bulk Edit


  • No labels