Current situation or problem: Continuing work to enable title and item level requests in enhanced consortia support environments

In scope:

1. To enable the release of ECS cross-tenant requests to the community:

   1. PC & TC approval - mod-tlr, mod-circulation-bff (one ticket per module for TC)

      • The team needs to do a self-review checklist

        • Modules need to be approved by PC before going through TC (Steph will manage PC work)

      • PC approval is more heavily PO work (Steph will manage)

      • Prep to TC approval

        • error handling

        • module renaming

   2. Get rid of temporary feature flags and release modules for the FOLIO community (more refined estimates will be available as Ramsons' work proceeds)

      • ~5 w.d. (BE estimate); scope will be clarified during preparation for R release

      • FE has a plan, but it should be reviewed and approved by the community; ~3 w.d.

2. Enable Routing service points for general ECS case (in its original sense - to show that an item is allowed for cross-tenant circulation) - This will be required for a classic consortium; it has already been implemented, but efforts for checking and verification are needed. ~3-5 w.d. (BE & FE)

   1. FE will need to merge the code for routing service point support to the master

3. Technical improvement: The ability to continue searching for fulfillment materials if a request created in one tenant fails (e.g., expires, is found to be missing, etc.)

   1. User statement: As a librarian, if a title-level request has been placed and cannot be filled by the item in the data tenant selected to fulfill it, I want FOLIO to automatically find an item in another tenant that can fulfill the request.

Out of scope:

• Enable functionality of the Hold shelf clearance report from the central tenant - (More information about requirements will become available after work in Ramsons is complete )
  ****Needs to be addressed in Trillium if still required after Ramsons clarifies requirements.

• More sophisticated management of TLR requests in several Data tenants - XXL (it depends on which of the scenarios are needed, needs prioritization)

  1. The ability for additional prioritization when selecting a lender (for example, to prefer Library A over Library B because A is in the same city, while B is in a different city or state)

• The ability to request an item across all tenants at once to 1) expedite the fulfillment process and 2) avoid missing an item in another tenant that was checked out at the time of the request creation but later became available

  • User statement: As a librarian, I want title level requests placed as quickly and efficiently as possible, ensuring the item selected to fulfill the request has the best chance to fulfill the request. If items that were unavailable to fulfill the request when it was placed becomes available before the request can be fulfilled, that item should have a chance to fulfill the request if appropriate.

Proposed solution/stories:

Links to additional info:

Questions:

1. 7 days (5 BE, 2 FE) for removing temporary flags seems like a lot of time to undo work - is there a way to protect the main branch without needing so much time to undo the work?

2. In classic EDS system when a data/member tenant is an individual library, what happens when they cannot fulfill a request that FOLIO mod-tlr has sent their way? How would canceling a request in this scenario work? Does this fit in with any of the scenarios for improving the sophistication of TLR requests?

Thoughts for discussion at the refining session:

• Renaming mod-tlr to something more meaningful (e.g. mod-ecs-circulation, mod-circulation-ecs, mod-requests-ecs, or something similar)

  • Will be far more difficult to change after it’s been approved by PC & TC

  • Algorithm

    • Follow the instructions from

      • Should we consider creating a new module and repository and moving all code over, rather than changing the name of the existing module

    • Create tickets for Indexdata DevOps to change the module name in the platform-complete configuration and add the new module to the reference environments

    • Don't forget to update permissions

    • Check database access (use this as an example - )

  • Estimate:

    • could take a week to a sprint to complete

    • RA: ~10 w.d. BE only (the estimate is based on Folijet’s experience in the Orchid when it took them ~1 sprint for everything)

• Adding support for Proxy Requester functionality for ECS setup