Loans (UXPROD-788)

[UXPROD-1621] Loans in-app report: Weekly overdue report (thin thread for Q2) Created: 22/Mar/19  Updated: 16/Sep/20  Resolved: 25/Jun/19

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

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Emma Boettcher
Resolution: Done Votes: 0
Labels: appreport, chalmers_visit_nov, loans, q1-2019-spillover, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-940 Loans in-app report: Weekly overdue r... Closed
Defines
is defined by UIU-983 Overdue loans report (fields already ... Closed
is defined by UIU-984 Overdue loans report (borrower fields) Closed
is defined by UIU-985 Overdue loans report (additional loan... Closed
is defined by UIU-986 Overdue loans report (additional item... Closed
Epic Link: Loans
Front End Estimate: Medium < 5 days
Front End Estimator: Emma Boettcher
Front-End Confidence factor: Low
Back End Estimate: XL < 15 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: Assumes a similar approach to the requests CSV export.

Needs integration between circulation and fees and fines and notices.

Will likely slow down the fetching of loans, and so may require some performance work.
Development Team: Concorde
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R5
Rank: 5Colleges (Full Jul 2021): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Purpose: See all overdues to determine if additional outreach to patron (or other actions) are needed. Would include items, notices (out of scope until UXPROD-1627 Closed implemented), renewals.

As a thin thread, this requires:

  • Interaction in UI for staff user to generate report
  • report generated of all loans with due date before the current date and time (i.e., overdue)
  • export of loans and loan information, including name of patron, loan policy, total fines/fees associated with item


 Comments   
Comment by Marc Johnson [ 25/Mar/19 ]

Emma Boettcher

Would include items, notices, renewals

Does this mean the report needs to include:

  • Which notices have been sent relating to a particular loan?
  • Whether a loan has been renewed? Would this be a count, or the renewal actions?

total fines/fees associated with item

Does this mean we would need the fees and fines information (at the moment circulation does not know about these)

Jakub Skoczen Given that notices are sent from within mod-circulation. If we use a similar approach to the requests CSV export, this could present challenges with circular dependencies (might be mitigated by mod-notify acting as an intermediary).

Comment by Emma Boettcher [ 25/Mar/19 ]

Renewals would be a count, not the history of the actions.
Notices might be out of scope for this, actually, because I'm not sure notices sent is documented in any way on the loan for now.

What do you mean when you say circulation doesn't know about fines/fees? If I add a fee/fine to the loan, I can see that amount on a user's open loans, so is it possible to use whatever that link is?

Comment by Marc Johnson [ 25/Mar/19 ]

Renewals would be a count, not the history of the actions.

Ok, that is on the loan already

Notices might be out of scope for this, actually, because I'm not sure notices sent is documented in any way on the loan for now.

I don't think we have a relationship between loans and the sent notices.

Please can you update the scope description to reflect this?

What do you mean when you say circulation doesn't know about fines/fees? If I add a fee/fine to the loan, I can see that amount on a user's open loans, so is it possible to use whatever that link is?

I mean the back end, at the moment, all of the fees / fines (and blocks) integration is in the UI only.

If there is a specific relationship we can likely use that, introducing that into mod-circulation will take more time and likely affect performance.

Comment by Anya [ 05/Apr/19 ]

FC: having data available would be good, not needed in-app - but need the data

Comment by Emma Boettcher [ 25/Jun/19 ]

Splitting and moving fines/fees work to UXPROD-1804 Closed

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