Page Comparison

• Request policy still be designed (re-designed) and some elements may be moving to the Loan policy. Cate, Sean and Tania working to get this nailed down for the developers asap
• While some aspects of circulation are independent enough to be worked by a team other teams (e.g. loan and request policy CRUD, extending the loan rules editor) making these new policies effective will really need to be done by the Core team.
• Making policies effective needs to be done in exactly the same code being modified for other ongoing circulation features such as in transit to home location and fulfilling pickup requests. Not a lot of work can be done concurrently here.
• Title requests - still not clear what the plan is here.
• Library opening hours calendar - Sean is finding bugs and issues with this Qulto-developed app. Which team is responsible for maintaining it? Sean would be the best fit from a PO perspective given his other features are primary consumers of calendar data.
• Here is a list of circ related features likely needed by Chalmers to go live which will need to carry over in some form to Q1. The list is long and there are dependencies.

Mid sprint 51

CIRC-154: check-in by barcode API (IN PROGRESS by William, to be handed off to Marc). William will issue a PR today and Marc will handle the review and any remaining work, once completed it will allow to unblock CIRC-146

CIRC-146: Change status to "in transit" upon check-in (IN PROGRESS handed over from Jeremy to Marc). Emma, Marc and I had a good meeting about specific uses cases and requirements not flashed out earlier (e.g repeated check-in/scan). We have also discussed extensions to handle pickup requests (a backend prerequisite for  UXPROD-118), they seem quite manageable and contained but we decided that they will not be in scope for CIRC-146 to avoid putting UPROD-601 under threat.

CIRC-150: validation of check-in/check-out SP during loan CRUD (IN PROGRESS re-assigned to Kurt from Jeremy) required to complete UIU-485

CIRC-151: Make mod-circulation Service Point enabled (DONE, Kurt)

OKAPI/RMB, performance NFRs

MODINVSTOR-215: During the meeting with EPAM Postgres experts on Tuesday it has been decided that Julian will continue with a solution similar to what has been proposed and he will implement the solution in RMB. The Core Team will not need more support from EPAM. (see RMB-301)

Devops:

• FOLIO-1577: Created automated builds for 'next-release' (IN PROGRESS, John) – there were missing releases blocking completion of this issue and it has become the focus of the last devops call. We have decided that it is not devops responsibility to request specific backend or front-end module releases, on the contrary – new "next-release" builds should be triggered by availability of new module releases. The specific dependency issues that prevent the current build are being investigated by Marc and John. We have decided to put additional guards in place to ensure that future releases are free from those dependency issues (OKAPI

• FOLIO-1548: Create a lighter-weight folio/testing-backend VM – the SPIKE has concluded and the approach is to slim down the Vagrant VM and provide ability to load additional modules dynamicall (STCLI-15, STCLI-114)