Page tree
Skip to end of metadata
Go to start of metadata

Date

Attendees

Discussion items

  • Discussion of the barcode index rebuild
  • MODINVSTOR-741 - Getting issue details... STATUS  Impacts probably most libraries.
  • MODINVSTOR-740 - Getting issue details... STATUS  Ditto. We marked them as P2 and assigned to the Core Platform team for now.
  • UICAL-159 - Getting issue details... STATUS  Calendar issue - UI - should be Vega team.
  • MODINVOICE-299 - Getting issue details... STATUS   Cornell will try again to reproduce; if it can't be reproduced then we'll close it.
  • MODDATAIMP-546 - Getting issue details... STATUS   Has a priority, assignee, and team, looks like it's in process.
  • UIU-2183 - Getting issue details... STATUS  Index Data is aware of it. Might be a data-related bug. Dev team is now Thor; no assignee yet.
  • UICIRC-430 - Getting issue details... STATUS  An old bug from early 2020. We are thinking it's browser-related.
  • UICHKOUT-726 - Getting issue details... STATUS  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. 
  • MODPATRON-69 - Getting issue details... STATUS   Currently blocked. Asking Khalilah to add the link to the JIRA that's blocking this one.
  • MODINVOICE-292 - Getting issue details... STATUS  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?
  • MODINV-492 - Getting issue details... STATUS   In progress, will be included in Bugfest.
  • MODINV-475 - Getting issue details... STATUS  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. 
  • CIRC-1112 - Getting issue details... STATUS  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.
  •