Done
Details
Reporter
Brooks TravisBrooks TravisPO Ranking Note
May need to split this off into a ticket to cover owning library checkout separately and create a new ticket with slightly lower priority for viewing transaction state.Front End Estimate
TBDRank: 5Colleges (Full Jul 2021)
R5Rank: Cornell (Full Sum 2021)
R5Rank: GBV (MVP Sum 2020)
R5Rank: TAMU (MVP Jan 2021)
R5Rank: Chicago (MVP Sum 2020)
R5Rank: MO State (MVP June 2020)
R2Rank: U of AL (MVP Oct 2020)
R5TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter
Brooks Travis
Brooks TravisPO Ranking Note
May need to split this off into a ticket to cover owning library checkout separately and create a new ticket with slightly lower priority for viewing transaction state.
Front End Estimate
TBD
Rank: 5Colleges (Full Jul 2021)
R5
Rank: Cornell (Full Sum 2021)
R5
Rank: GBV (MVP Sum 2020)
R5
Rank: TAMU (MVP Jan 2021)
R5
Rank: Chicago (MVP Sum 2020)
R5
Rank: MO State (MVP June 2020)
R2
Rank: U of AL (MVP Oct 2020)
R5
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 22, 2021 at 7:23 AM
Updated June 16, 2022 at 3:00 PM
Resolved June 16, 2022 at 3:00 PM
Split from UXPROD-2793
Splitting out stories for transaction detail action menu items that aren't needed for MVP if we can get the Kafka event-driven functionality in place.
Current situation or problem:
There are aspects of INN-Reach transactions that are not easily mapped/not mappable onto the current FOLIO circulation, inventory, and users system. An interface is needed to view these transaction details and perform INN-Reach specific UI functionality (such as owning library checkout).
In scope
Building a UI app that interacts with the INN-Reach integration module(s)
UI App permissions
UI App settings
Out of scope
Storage of INN-Reach transaction data
Use case(s)
Proposed solution/stories
A UI App that provides the ability to view the unified transaction state of an INN-Reach request throughout its lifecycle, including data that is not stored in existing FOLIO modules (eg. INN-Reach Item Status, PType, IType, etc.), as well as perform actions such as those described in UXPROD-2766, as well as in-app reports for INN-Reach.
Links to additional info
Questions
One unified app, or separate apps (eg. INN-Reach Checkout, INN-Reach Requests, etc.)?