Reporting: LDP-based Reports (UXPROD-1319)

[UXPROD-2024] RA-Holds Cluster Created: 28/Aug/19  Updated: 07/Dec/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Reporting: LDP-based Reports

Type: New Feature Priority: TBD
Reporter: Angela Zoss Assignee: Angela Zoss
Resolution: Unresolved Votes: 0
Labels: report-cluster, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to REP-109 Reservations / priority notices Open
Epic Link: Reporting: LDP-based Reports
Back End Estimate: XXL < 30 days
Development Team: Reporting
Report Functional Area(s):
Resource Access
Rank: Chalmers (Impl Aut 2019): R3
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R2

 Description   

Current situation or problem:

In scope

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Erin Nettifee [ 13/Jan/20 ]

Angela Zoss - I think this might need more depth in terms of hold reporting if we're trying to make one SQL query. I'm thinking about things like total holds, holds by pickup location, holds by patron group type, holds that expired, all filterable by timeframe.

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