Product Council decided that a small group will work on the agenda setting process for the Product Council. Laura is checking with other conveners as to how they set agendas in other SIGs
Informing the user that there is a conflict and how to resolve it. Kahlilah presented the group with some scenarios:
Scenario - User is not aware that someone else or the system is editing the same record until try to close it. When the user hits Saved/Close, this message could appear: Option 1: You cannot override what was most recently saved with your update. View latest version would allow you to view the latest version of the record. This would take user to Inventory
Option 2: Two options, close or continue to save. "Override" includes if an item is getting checked out.
Asking PO's to review and consider.
Jennifer Eustis: "Are there distinctions made between single record update and other data imports?" Ann-Marie - "No"
Marmot Office: "How about another option for save as a new record?"
Felix: "Option 2 seems dangerous because the other person does not get any information that their edits are now gone." - Charlotte said, almost all POs were leaning towards Option
Jennifer Eustis: "What about changes through the API?" - Also commented that there are various possibilities of conflicts.
Rita Albrecht: "The ideal solution would be that the changes of both editing processes would be merged together. Some Systems are able to act like this but because we are discussing I guess FOLIO does not provide such an Option?"
Marmot Office: "I want to be able to save my changes in another record. Then I can look at the two records and figure out which to use, or merge them manually."
Jennifer and Ann-Marie thought record transfer should be considered as another action that would or should touch optimistic locking scenarios. Scenarios are in link above.
Feedback needed:
By Tuesday, September 14
Of the two options listed on the wiki and above, which is acceptable for the first version of optimistic locking? If neither works, it will not be in Kiwi.
Ann-Marie: "I think it's important to keep in mind that Kiwi is mainly surfacing the processes that are currently happening, and have not been identified in the UI previously. Once we can be aware of what's happening, then we can refine it."
Laura: Will Option 1 break anything, or is there a compelling reason for Option 2?
It will require adding option for saving Holdings UUIDs on the Inventory Holdings tab – similarly to Saving Instance UUIDs on the Inventory Instance tab
Do we need to preserve Saving Instance UUIDs on all tabs?
This will be possible once the SRS work is complete
NOTE:
Distinction between Custom mapping profiles and Default mapping to help group assess the spreadsheets accurately. The two processes are very distinct from each other:
mapping-preferences - spreadsheet that defines custom mapping profiles in data export. - These come into play when the user defines custom profiles in Settings/Data Export. A custom mapping. The fields seen when the user clicks on "Transform" is driven by the Custom mapping spreadsheet.
recommended mapping - spreadsheet covers the properties that are part of the default mapping profile. Common use case for default mapping profile: Select records in Inventory > Actions - export Instances (MARC). The MARC record appears in the Data Export app directly from that action. The resulting default record has a 999 field with UUIDs from Source Storage, another from Inventory Storage
.png?version=1&modificationDate=1631197862000&cacheVersion=1&api=v2&width=342&height=250)
