Page Comparison

• Bugfest is next week – designate MM meeting time as Bugfest testing time?
• Plea from Anton E: please claim tests if you haven't yet (and are planning on testing)
• Other ways we (SMEs) can help our POs???

Ann-Marie via chat: In happy news, all 3 scenarios for Single record import (new Instance and SRS MARC, updated Instance and new SRS MARC, updated instance and updated SRS MARC) all seem to be working in the pre-Bugfest Kiwi environment

Jenn Colt via chat: Data import people are going to look at test rails in lab today if anyone wants pointers

Important - record updates get saved. Currently in FOLIO, if two people are editing the same item record, the person who saves first will loose their changes. Another scenario is that two system actions could occur at the same time, or a system and a user action on the same record. System action example: status of an item being checked out changes.

FOLIO is planning on implementing optimistic locking. 

Charlotte via chat: "Right now Optimistic locking is implemented for apps interacting with Inventory. Then next step will be to roll is out for all apps, including Agreements. "...optimistic locking is to be solving SRI and Data Import as well. SRI and Data Import collisions/conflicts as well"

Jenn (via chat): "It’s not really the collision I’m concerned about, it’s passing the messaging through a multi-step process and reporting the result to the user"

With optimistic locking, FOLIO will make the user aware that the record has changed as the user has had it in edit mode and made changes themselves.

The code is present in Kiwi but not "turned on". More testing is needed.

User messaging JIRA 

This will be tested with Inventory first, then other apps are considering. 

Screenshot messaging:

"View latest version" will return them to Instance, Holding, or Item and user will able to see the latest changes made. 

Jenn Colt asked how this will translate to more complex cases like single record import overlays or batch updates. 

Khalilah - We do have to test workflows and see the outcome. This is one of the reasons it will not be released in Kiwi - need to test these complex cases. That is part of the plan so it can be released for Lotus.

Ann-Marie (via chat) - "I think part of the Single Record Import messaging issue is that the UI messaging you see in Inventory was a first iteration, and needs to be worked on in general. Maybe we can use Kiwi Bugfest as a venue for trying to refine those current messages."

Tim Watters (via chat) - ""Close = closes the modal and keeps user on the record in edit mode"  Does that keep your edits alive then?"

Laura suggested a new tab would open. When you click on "View latest button" it could open the latest version in a new tab or window to give the user the chance to copy edits to the record that will be saved.  Desire for temp screen and permanent record to be obvious. 

Tim (via chat) - "We are in a consortial setting and never know when someone else is editing for all kinds of reasons. People blame that *other person* at *that other library* if they lose their work. Not good for relationships."

Jenn - Language is important. Not "old version" - maybe more like, unsaved changes. 

Janet Ewing (via chat) - "Does the system know if/when the Edit screen is opened?  If so, can it alert a user who clicks Edit that someone else has already started editing the same record?"

Suggestion, agreed by Khalilah that the record not open in "edit" but "view" mode to let the user decide what is needed. 

Khalilah will work on a mock-up with suggested changes, come back to MM meeting, get response, then move forward from there.

Next week's meeting will be BugFest testing