2021-01-05 Meeting Notes
Date
Attendees
@jessica Janecki
@Andrew Clark
@Mary?'
jackie.gottlieb@duke.edu (Deactivated)
Ann-Marie Breaux (Deactivated)
Goals
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Optimistic Locking | Jakub Skoczen & Holly Mistlebauer | Not be able to handle update conflicts has been an issue for over a year and a half - Issue# 2027 Was discussed as a Tech Debt item at last WOLFCon and Optimistic Locking was selected as best strategy - UXPROD-1752 - This ticket is mostly about the backend development This feature has been ranked as R1 by most institutions There is no silver bullet for solving this problem - all have pros & cons
- RMB-719Getting issue details... STATUS R1 2021: OL platform support implementation
R2 rollout:
AMB: If it will be added to Inventory, then I think Data Import would have to make some changes to deal with those reports, when the conflict is caused by Data Import and a User making changes to the same record at once. There is nothing now in JIRA that reflects the work and size of work to be done. OL in Inventory: - UIIN-1245Getting issue details... STATUS Tod: how do we get these out of RMB and into issues? Source Record Storage, for example. R2 would be clearer if we can get R1 to give report - Jakub, yes, want this for R1. Code freeze is mid-Feb Is there a specific team of people who need to look for these issues? or an institution? - Cornell would be interested, Chicago will see if anyone has time for this. This will be important for consortia where maybe 5 libraries are sharing a record- rate of collisions will increase. OL may not be the best solution for frequent collisions. Enabling this for R1 to collect frequency data could help us make a better solution AMB- trickiest part will be the flag in R1 - just now moving places to Honeysuckle and Iris work us just starting. Seems to be a little late to implement a Juniper solution. Jakub - yes, this is a big challenge. Hopeful that the institutional testing will help us. Tod - maybe can look at our experience with current systems - where are the collisions happening. FOLIO won't change that number. AMB - anything patron-facing will be more high-cost, could affect someone trying to checkout, for example Ian will check with Koha to see how they handle and what the volume is | |
Future topics | January 12 - Receiving demo | ||