Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems
(UXPROD-2598)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Lotus (R1 2022) | Parent: | Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Brooks Travis | Assignee: | Brooks Travis |
| Resolution: | Done | Votes: | 0 |
| Labels: | consortia, d2ir-circulation-flow | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Epic Link: | Add Support for D2IR API Integration with INN-Reach Resource Sharing Systems | ||||||||||||||||||||||||||||||||
| Front End Estimate: | Out of scope | ||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||
| Development Team: | Volaris | ||||||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R5 | ||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R5 | ||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R2 | ||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R5 | ||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: When an item requested through INN-Reach from another local server and the item is received by the borrowing site, it is checked in and placed on the hold shelf for pickup by the requesting patron. If the patron picks up the item, it should be circulated to the patron using the standard FOLIO circulation flows (mod-circulation) and the loanId of the resulting loan should be stored in the INN-Reach transaction record in mod-innreach (
In scope
Out of scope
Use case(s) Proposed solution/stories Thin Thread: Create a screen in the INN-Reach UI app that duplicates the existing Check Out application. When an INN-Reach item is picked up, library staff will switch to this "mode" and process the loan as a typical loan transaction:
The UI/Backend will then:
If more than one INN-Reach item is being picked up, scan the next item barcode and repeat UI/Backend steps 1-3. If no INN-Reach transaction is found for the item (i.e. the item is an item owned by the borrowing site), process this item as a normal loan. The check out session should expire after the configured timeout period, or be ended manually by the operator to trigger relevant notices. Ideal solution: Using the standard check out app in FOLIO, when a staff member attempts to check out an INN-Reach item to the borrowing patron, mod-circulation would publish an event to message queue to which mod-innreach could subscribe and determine if the loan is of an item/patron combination for which it has an open transaction. If so, mod-innreach would store the loanId in the INN-Reach transaction record as described in the thin-thread story above for future reference. Links to additional info Questions |