Fees/Fines in-app report: Lost items requiring actual cost
Description
Priority
Fix versions
None
Development Team
UNAM
Assignee
Solution Architect
None
NoneParent
Parent Field Value
None
Parent Status
None
duplicates
has to be finished together with
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Holly Mistlebauer July 20, 2020 at 10:28 PM
Duplicated by .
Holly Mistlebauer March 23, 2020 at 12:28 PM
Use Emma's as an example...

Anya March 29, 2019 at 11:03 PM
Comment from the March meeting : the ability to pull a CSV or get to the data is a must .
Duplicate
Details
Details
Reporter
Potential Workaround
Holly: The workaround would be for a library to run a query against the database (or data warehouse?) to produce this report. An alternative to including this in-app report in the MVP would be to plan it for Q1 2020, given it won't require as much testing by the implementing institutions. If we end up not doing this report as an in-app report, the Reporting SIG needs to be notified ASAP so they can make other arrangements.
PO Rank
15
Estimation Notes and Assumptions
We haven't done any canned reports yet so I have no idea what will be involved.
Front End Estimate
Large < 10 days
Front End Estimator
Front-End Confidence factor
Low
Back End Estimate
Medium < 5 days
Back End Estimator
Rank: FLO (MVP Sum 2020)
R4
Rank: 5Colleges (Full Jul 2021)
R4
Rank: Cornell (Full Sum 2021)
R4
Rank: Chalmers (Impl Aut 2019)
R5
Rank: GBV (MVP Sum 2020)
R4
Rank: hbz (TBD)
R4
Rank: Hungary (MVP End 2020)
R1
Rank: TAMU (MVP Jan 2021)
R5
Rank: Chicago (MVP Sum 2020)
R5
Rank: Leipzig (ERM Aut 2019)
R5
Rank: MO State (MVP June 2020)
R4
Rank: U of AL (MVP Oct 2020)
R2
Rank: Lehigh (MVP Summer 2020)
R5
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 6, 2018 at 4:11 PM
Updated July 7, 2022 at 12:20 PM
Resolved July 20, 2020 at 10:28 PM
TestRail: Cases
TestRail: Runs
Update on November 22, 2019: This report needs to be part of the MVP in support of the Aged to Lost and Declared Lost workflow.
Purpose: Some libraries want to charge the actual cost for certain types of items. When the item ages to lost or is reported as lost by the patron, the actual cost may not be know. The item will be reported to the selectors as needing to be costed and then a manual lost item fee/fine can be entered. If a workflow engine is available, this could be done on-line using that.