2022-08-04 Metadata Management Meeting notes

Notetaker

Jennifer Eustis

Announcements

• WOLFcon 2022: List of metadata management related sessions in the session planner (Sched): https://wolfcon2022.sched.com/overview/subject/MM

Now there is a large list of metadata sessions. Is there a note saying which sessions are hybrid, in-person or virtual? Felix will ask this.

• Update 2022-08-08: Notes from an e-mail to all speakers/presenters/session organizers:

4.                 Zoom/Hybrid/Virtual
·        Each room will have a dedicated zoom link that will be available within the session information in Sched.
·        If your session is in the Hall, there is IT support and there will be 3rd party live captioning provided
·        For all other rooms, you will be responsible for the online experience
o   Start the zoom
o   Check to make sure the session is recorded
o   Enable live-transcriptions (automated)
o   Consider assigning someone to monitor the chat

• Most sessions will be hybrid. Felix will follow-up about the procedure of providing Zoom links on the session pages.

PC update

• 2022-08-04 Meeting notes

This was discussing WOLFcon planning. There is a note about sprint reviews and how to share information since these reviews no longer take place.

@Jennifer Eustis 

MM SIG Release Note & Other Highlights

Mark instance for deletion. homework

@Felix Hemme 

Homework from last week:

Should there be one permission to "mark"/"unmark" or should there be two separate permissions? → If we want separate permissions, we have to come up with a use case in order to justify the development effort. HOMEWORK for August 4th: If you have a use case for two separate permissions, please indicate in this minutes, via Slack or contact Charlotte.

Perhaps we can start with just having the one permission for mark/unmake. Down the road, if we have use cases for separate permissions, then we can work on that later. We also need to think about the API permissions for the hard delete and then having a separate permission for a thing that is really deleted. Deleting through the API can have consequences such as not looking at dependencies and create unexpected things to happen. We also need to think about how other Apps work. An example is moving POLs to another instance and then mark something for deletion where the instance stays connected to the POL (UXPROD-3619 In review for Morning Glory). Inventory doesn't talk to the Orders App. At this time, if you update the record where the title is also updated and changed (for instance CIP to full record), then you won't be able to find that title in the Orders App. These interactions were throughtful designs and as more institutions go live then we can review those interactions. The connection in this case isn't broken. 

People in the meeting agree that one permission is easier for now until we have use cases to have separate permissions.

Data Import PO update

@Ann-Marie Breaux (Deactivated) 

PowerPoint Slides

Morning Glory Release - Folijet Team

There are a number of features being worked on: refine data import field protection, match on POL or VRN, stability, reliability, performance, log enhancements, MARC orders, and permissions enhancements.

Permissions: Added for Morning Glory to view only, can do everything in settings and/or DI, and then delete logs.  For existing users, permissions won't break. You will be able to add the new permissions.

Field protections: When protecting MARC fields that are repeatable, field protections need to be thought of differently than the non-repeatable MARC field. 

Flow control: This will push the single record imports to the top of the queue. 

Update Inventory records via POL/VRN Match: This can be used as a match point in Morning Glory. This is particularly good for shelf ready processing. 

Log Enhancements: You can delete logs. There is a filter, a summary, and style updates. There's a new status: stopped by user. 

Administrative note field: Support was added for this field in Morning Glory for instances, holdings, items. This field isn't controlled by the marc srs if present. 

Nolana Upcoming Features

Create orders and order lines based on MARC data (UXPROD-185). 

There isn't the ability to create invoices based on MARC data. This exists with EDIFACT files. 

Refine existing "Update individual fields" functionality: Logic will be added to take into account repeatable and non-repeatable MARC fields. 

Data Import UI cleanup: This is to clean up and make DI easier to read such as removing grayed-out selections in the matching profile. 

Prep work for Orchid features and dealing with instances that are marked for deletion or dealing with multiple holdings and items.