Page History

Date

20 Sep 2021

Attendees

• Anya Arnold
• Debra Howell
• Elizabeth German
• Zak_Burke
• Charlotte Whitt
• Anton Emelianov

• Philip Robinson

Discussion items

• Discussion of the barcode index rebuild

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODINVSTOR-741

   Impacts probably most libraries.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODINVSTOR-740

   Ditto. We marked them as P2 and assigned to the Core Platform team for now.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key UICAL-159

   Calendar issue - UI - should be Vega team.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODINVOICE-299

    Cornell will try again to reproduce; if it can't be reproduced then we'll close it.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODDATAIMP-546

    Has a priority, assignee, and team, looks like it's in process.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key UIU-2183

   Index Data is aware of it. Might be a data-related bug. Dev team is now Thor; no assignee yet.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key UICIRC-430

   An old bug from early 2020. We are thinking it's browser-related.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key UICHKOUT-726

   A lot of investigation is going on with this check-in speed Spike (and check-out as well). We think they should be put back into an active sprint for more visibility. 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODPATRON-69

    Currently blocked. Asking Khalilah to add the link to the JIRA that's blocking this one.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODINVOICE-292

   Unclear why this is only an issue via the API, and not the UI. Is it due to not following the required order of operations?

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODINV-492

    In progress, will be included in Bugfest.

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key MODINV-475

   Assigned to Prokopovych dev team. We originally thought it should be solved at a more general level (Cross SIG?). There isn't a clear set of requirements that would be consistent for all use cases. 

• Jira
  server FOLIO Issue Tracker serverId 6ccf3fe4-3301-368a-983e-20c466b11a49 key CIRC-1112

   Revised the Affected Institution list. Could have been put into an Iris Hotfix but it didn't make it. And it's not Juniper. Added comment asking Holly to escalate it as a P1, since it's having a major impact on many libraries.
• Discussion of how to deal with bugs that have aged a year or more.