2021-1-26 Meeting Notes

Optimistic Locking - this group sees issues with this solution.  It's too late, though, to make a change in the system. 

Still uncertainty about logging - how will this work?  Will have to coordinate with hosting provider.  The error would be signaled at the time and would have to get with person in charge of the log.

AMB- just starting to work on error reporting with data import.  Will be able to identify that there was a problem.  How to resolve still has to be figured out. 

Jacquie - in Aleph get pessimistic locking, person gets a note that someone else is working on the record.  Not knowing how this will be handled in FOLIO, especially since their people see these notices frequently, maybe daily.

Ian - would like to lock a record while someone is editing it, but have to remember to unlock

Tod - with OL you might get the message that someone else has edited.  No kind of locking solves all problems.

Jacquie - not sure we need something sophisticated.  Wiki & Google doc for example let you know that someone else is editing the page.

Tod - that kind of resolution is expensive

Jacquie - there doesn't seem to be a way for X and Y to know they're working on the same record at the same time

Chrisitie - Person A saves a record, how is Person B to know that changes have occurred while B had it open and some changes may be overwritten.

Jacquie - has never seen a system that doesn't tell you these things

Tod - "this record has been saved, do you want to continue" - this is optimistic locking

Does this rely on PubSub? No, not connected at all

Volume of collisions - Koha - sees it in training when a lot of people working on the same record, doesn't seem to come up elsewhere

Jacquie - see collision avoidance notices a lot

Jenn - are they going to apply this to Inventory first, can they do this in SRS also?

AMB - it's a little tricky while this is theoretical, need to see it in action

Christie - FOLIO doesn't need to fix the collisions, just needs to avoid them.  Ex - batch loading/editing and someone is actively editing one of them, needs to skip that record and report that it was not updated

Tod- yes, just need to know which record failed.  Whoever saves first, the next person needs to know

AMB - if someone's checking out an item, do they get a note "record in use, cannot check this out"

Christie - we'll probably implement before this is available, how do we handle the problems that come up?  What is the risk?

Tod - need to know when the basic logging will be available

Jenn - yes and what it's covering, seems like it will only cover Inventory.

AMB - Users is another big area

Tod - this will happen in RMB

Optimistic Locking issues in JIRA:

Can we ask Jakub where development stands for Iris?  Can we set up a situation in Bugfest?

Tod - this would be the best way to test

AMB - we'll need to remember this to write up a test case for Iris

Jacquie - do we need to let Jakub know about the other modules we're concerned about?

ACTION - Paula will contact Jakub and get Iris update, refer him to Jan 29 & 26 discussions, and update him on areas of concern