2022-02-10 Metadata Management Meeting notes

• We are looking for volunteers who could take over the SIG convenership on an interim basis from end of May till mid July. Please contact Raegan or Felix if you are interested or have any questions.

MM SIG Release Note & Other Highlights

Martina Schildt 

Charlotte Whitt 

Presentation

Inventory related use cases: https://docs.google.com/spreadsheets/d/18-QIbq1DjjWABgkjI0nbNO9I4-XeqtRQ66aUkINUu9g/edit?usp=sharing

**New:** Use cases in a Google Form: https://forms.gle/TRiYPNNbn1R5CNmB8. More than one person from an institution can participate in the survey, it does not have to be a collected answer. Please fill in the form until 18 Feb 2022 

• Cross app data sync working group is visiting various SIGs and is interested in feedback on the time that is approriate for data changes in one app to be made available to other apps
• Error handling: What happens when a change in one app does not trigger the change in the other app? How do we find out? If the consuming app is not able to process the event, it should provide a way to tell that a change has not been processed (log etc.). 
• The main focus is not on solving possible issues with data sync, but to get feedback on the appropriate time span.
• Does the working group consider other data corruption issues that we want to avoid with optimistic/pessimistic locking? 
• It is not always obvious where the source of truth is, e.g. the barcode a user enters during receiving in the Receiving app is stored in the Inventory item record 
• There is a difference in waiting for the change to appear in an app and being aware that there is a change that is not yet reflected in the record.
• If the submission is going through a queue, does that mean that the time a change needs to be available in another app could be variable, depending on the time the change is made (e.g. in the moring it takes longer because more user are active in the system)
• SC: already experiencing performance issues when an app is loading data from another app. This impacts day-to-day work. 
• FOLIO is a modular LSP and not an integrated ILS what makes it challenging
• Should the messages be prioritized, so that one type of changes is more important than others and be made available ASAP? MS is asking the working group if this is something that we need to consider.

Felix Hemme

Theodor Tolstoy