Loans (UXPROD-788)

[UXPROD-944] Loans in-app report: Items that are in transit Created: 13/Jun/18  Updated: 16/Sep/20  Resolved: 05/Dec/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q4 2019
Parent: Loans

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Emma Boettcher
Resolution: Done Votes: 0
Labels: appreport, cap-mvp, loans, po-mvp, q4-2019-at-risk, q4-2019-spillover, resourceaccess, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft Word ItemsInTransitReport2.xlsx    
Issue links:
Cloners
clones UXPROD-942 Loans in-app report: Volume of action... Closed
is cloned by UXPROD-946 Loans in-app report: Items that are c... In Progress
is cloned by UXPROD-2182 Loans in-app report: Items that are i... Closed
is cloned by UXPROD-947 Loans in-app report: Consortial loans Closed
is cloned by UXPROD-948 Inventory: Retrieve a list of items t... Draft
Defines
is defined by CIRC-518 BE: In transit report: basic fields Closed
is defined by CIRC-519 BE: In transit report: request fields Closed
is defined by CIRC-520 BE: In transit report: call number fi... Closed
is defined by UIIN-840 FE: In transit report: basic fields Closed
is defined by UIIN-841 FE - In transit report: request fields Closed
is defined by UIIN-842 FE: In transit report: call number fi... Closed
Duplicate
is duplicated by UXPROD-928 Requests in-app report: Requests over... Closed
Relates
relates to UXPROD-867 Reporting: In-App Reports Open
relates to UXPROD-2182 Loans in-app report: Items that are i... Closed
relates to REP-172 Items in transit for "too long" Closed
Potential Workaround: Query LDP, but data will be old - will lead to false alarms of items that used to be in transit but have since been checked in.
Epic Link: Loans
Front End Estimate: Medium < 5 days
Front End Estimator: Emma Boettcher
Back End Estimate: XL < 15 days
Back End Estimator: Emma Boettcher
Development Team: Vega
PO Rank: 100.9
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Purpose: Determine whether any items that are in transit seem to be "stuck". Would include the origin & destination as well as how long the item has been in transit.

Completed during Q4:

  • report that includes basic fields, information about the open request (if applicable) and where the item is in transit to and from


 Comments   
Comment by Anya [ 10/Jun/19 ]

HI Emma Boettcher in the capacity plan this ticket is marked for "Fix Version/s: Q1 2020" Could I change this status on this ticket to reflect that?

Comment by Cate Boerema (Inactive) [ 09/Aug/19 ]

Hi Emma Boettcher, I had an MVP feature in my backlog for requests in transit report ( UXPROD-928 Closed ). In talking to the SIG yesterday (2019-08-07), they actually wanted a report with all items in transit. I ended up gathering requirements for this report.

Current thinking is that thin thread could be a csv export of all items with Item status = In transit. You need some basic information about the request if it's in transit for a request. Attached is the spreadsheet we worked on with the columns ppl wanted and how they should populate.

Comment by Emma Boettcher [ 12/Aug/19 ]

Cate Boerema that's great news, and thanks for gathering requirements and passing them along. I put them into a Google sheet in case we both need to edit: https://docs.google.com/spreadsheets/d/1AO5lw213Dtiow2rRrsr7VLxu6JnjP6BhmMdwsjvc3gk/edit?usp=sharing

Comment by Emma Boettcher [ 05/Dec/19 ]

Closed, split remaining work into UXPROD-2182 Closed .

Generated at Fri Feb 09 00:11:40 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.