Circulation log/report (UXPROD-1704)

[UXPROD-3579] Add Backdate Return to events captured in Circulation Log Created: 23/Feb/22  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Circulation log/report

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Stephanie Buck
Resolution: Unresolved Votes: 0
Labels: enettifee-reviewed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File image-2022-02-23-16-14-39-258.png    
Epic Link: Circulation log/report
Development Team: Firebird
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem:

Occasionally, libraries may need to backdate an item return - make it look like it was returned at an earlier date/time than it actually was.

When this occurs, it needs to be captured as an event in the circulation log, as at most libraries this happens rarely, and would be viewed as an exception to a policy like a checkout override.

In scope

Out of scope

Use case(s)

  • A common use case for backdating returns is weather; suppose a library is unexpected closed on a Saturday and Sunday due to snow, when they arrive on Monday and start processing items left in their book drop over the weekend, they want to make them look like they were returned Friday night so that patrons aren't inadvertently charged fines.
  • Backdating returns can cause a fine to not be charged; libraries that are concerned about how this often backdating occurs will want to be able to monitor when it occurs using the circulation log.

Proposed solution/stories

Links to additional info

Questions

  • What determines if something is backdated? I don't think there is a field on the loan that indicates it was. So this may require some further discussion as to how to identify when a backdate occurs.

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