Reporting: LDP-based Reports
(UXPROD-1319)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Reporting: LDP-based Reports |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Vandana Shah | Assignee: | Angela Zoss |
| Resolution: | Done | Votes: | 0 |
| Labels: | report-cluster, reporting | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Epic Link: | Reporting: LDP-based Reports | ||||||||||||
| Development Team: | Reporting | ||||||||||||
| Report Functional Area(s): |
Resource Access
|
||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||||||
| Rank: Chicago (MVP Sum 2020): | R3 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R3 | ||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||
| Description |
|
Current situation or problem: In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Sharon Beltaine [ 03/Nov/20 ] |
|
Note from Joanne Leary - Will item-related exceptions be an inapp report? |
| Comment by Joanne Leary [ 03/Nov/20 ] |
|
We're interested specifically in having a report for Lost items that have been returned or renewed in the date range and for the owning library (or service point) specified. We would use the report daily, to review and update patron fines or blocks. Will this be an in-app report? If not, it should be developed as an LDP report. |
| Comment by Erin Nettifee [ 16/Nov/20 ] |
|
The title would suggest that these reports are about which staff are overriding which FOLIO functions. This may not be a report that can be written yet, since overrides are still being developed. If that's correct, I think Joanne Leary maybe you're looking for a different kind of report than this. If we're (Duke) wrong in our understanding, then we need to have the override report added in as a report development request. Interested parties: Andrea Loigman Angela Zoss |
| Comment by Joanne Leary [ 16/Nov/20 ] |
|
Because this cluster is called "Overrides and Exceptions" I was thinking it encompassed transaction exceptions (that's Voyager-speak) that occurs when a Lost book is discharged. Voyager generates a daily "Transaction-related exceptions report" and "Item-related exceptions report." You're correct that it's not an override; if overrides are going to be considered in a separate cluster, then we need to speak to Sharon Beltaine about how to split these out. |
| Comment by Angela Zoss [ 11/May/21 ] |
|
https://github.com/folio-org/folio-analytics/tree/main/sql/report_queries/item_related_exceptions |