Guests: Oleksii Petrenko
|10 minutes||Status update|
Issue - Mod-source record storage. Needs a hotfix for Iris. A data consistency problem when importing data using external tools creates a bad record ID (duplicate record id's). A script is ready. A SQL script should run prior to Juniper upgrade to check for duplicates.
Solution, Apply this fix to Juniper. What are the next needed steps?
They will upgrade to hotfix for Juniper 1. Should include the the circ block/barcode fix.
Need to discuss with spitfire team 1st. Script should identify the data for libraries that they can be fixed by the customer at the database level.
ModInvstor - 523 should be included.
Script needs to identify the records. Discuss with Ann-Marie if import could be used to fix these.
Do we need protection from loading data directly to the database?
Teams will meet to discuss solution.
Timing for hotfix 1 for Juniper? Will check if it can be released this week. September 10th.
|5 minutes||Next Monday is a US Holiday||Holly Mistlebauer|
Should we skip our meeting or reschedule it? (BTW, I will be OOO September 1-8.)
Will skip meeting on September 6.
|FYI (no discussion needed)||Circulation Performance Proposal|
|15 minutes||Circulation Hotfix||Oleksii Petrenko|
Is it needed? If so, which release and when? (For what?–Holly)
If you are talking about https://issues.folio.org/browse/MODPATBLK-91 and https://issues.folio.org/browse/MODPATBLK-94, Cornell needs these fixes ASAP. We can't really wait for a planned hotfix. Cornell is experiencing 10-12 second checkouts that these tickets should fix. I am happy to do testing on BugFest so that we make sure these tickets don’t break anything else--Holly
|5 minutes||Plans for Zak||Holly Mistlebauer||Zak's last day as a community developer is September 24. Zak mentioned that he will spend part of his time doing community work. What will this entail?|
|10 minutes||Prokopovych Team Capacity|
As of September 27, when Zak is no longer on the Prokopovych team, we will have the following capacity:
Given the volume of issues assigned to the team, and expectations by the project, we need more devs.
In order to manage expectations, please note that...
Prokopovych priorities between now and September 17 code freeze (see our Scrum Board)...
|15 minutes||Institution Ranking||Holly Mistlebauer||We currently have 29 institutions with a Rank field in JIRA. Anya has requested that we add 33 more. The process we are using has become unwieldy. Our plan was to use the "points" to plan most work, but then use the "rankings" to determine what to do next when nothing is highly ranked for the team/epic. Perhaps the POs should work with the appropriate SIG to determine what to work on when nothing is highly pointed? Then we can eliminate the ranking process. Thoughts?|