Requests (UXPROD-790)

[UXPROD-931] Requests in-app report: Recall list Created: 13/Jun/18  Updated: 04/May/22  Resolved: 04/May/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Requests

Type: New Feature Priority: P5
Reporter: Darcy Branchini Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: appreport, printslips, requests, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-867 Reporting: In-App Reports Open
relates to REP-138 Recall requests for items loaned to c... Closed
Epic Link: Requests
Analysis Estimate: Medium < 5 days
Analysis Estimator: Darcy Branchini
Front End Estimate: Medium < 5 days
Front End Estimator: Marc Johnson
Front-End Confidence factor: Low
Back End Estimate: XL < 15 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: Given the limited knowledge we currently have about how in-app reporting is going to work...
Development Team: Vega
Report ID (pre-May 2019): ID447
Report Contact(s):
Mike Paxton
Report Functional Area(s):
Resource Access
PO Rank: 19
PO Ranking Note: 2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R4
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

Recalled and currently loaned out through ILL and/or another consortial partnership.



 Comments   
Comment by Cate Boerema (Inactive) [ 28/Jun/18 ]

Hi Darcy Branchini, this feature doesn't have an epic. Does it belong with Requests (meaning Tania Fersenheim would own it)?

Comment by Tania Fersenheim [ 28/Jun/18 ]

Good question - while it sounds like straight up requesting, it might fall under "resource sharing" - not sure how closely that is tied to requests.

Comment by Cate Boerema (Inactive) [ 24/Aug/18 ]

Tania Fersenheim, these features need epic links. Can you please link them up?

Comment by Holly Mistlebauer [ 07/Mar/22 ]

This feature is marked DRAFT until Brooks Travis has a chance to review it for validity.

Comment by Erin Nettifee [ 15/Apr/22 ]

I think this is a valid report request but just scoped very small b/c it came out of reporting and not general discussion. The problem with ILL and consortial stuff is that libraries will all do their associated workflows differently (for valid reasons.) Some might use dummy users, some might use loan type, some might use locations or a combination of all of these.....

The circulation log now has an event you can search on ("recall requested"). That could perhaps help in some cases for libraries that don't have access to a reporting tool.

I wonder if we might meet some of these reporting needs by adding filters to the circ log to search for additional things (item effective location, loan type, material type?) and then direct people there...

Comment by Erin Nettifee [ 04/May/22 ]

Closing as "Won't do". Individual libraries will manage consortial and ILL loans in different ways, and creating an in-app report is not feasible to meet all library use cases. This is better suited to a reporting tool like the LDP.

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