Backdate a Checkout to Expired Patron

Bug #1222242 reported by Jason Stephenson on 2013-09-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

EG Version: Master
OpenSRF Version: N/A
PostgreSQL Version: N/A

When writing custom programs to load transactions for migrating libraries, it would be nice if one could "backdate" the chekcout time to an expired patron.

The notion is that if the checkout time is prior to the patron's expiration date, then the checkout continues rather than getting a PATRON_ACCOUNT_EXPIRED message.

I have a single commit on a branch that works for this. I'll split it off into its own branch and throw it up a bit later.

description: updated
Jason Stephenson (jstephenson) wrote :
tags: added: patron pullrequest
Ben Shum (bshum) wrote :

Jason, I'm going to keep targeting these missed pullrequest tagged bugs. Feel free to move them around or modify as needed before the next round of review work commences. Not sure what are bug fixes or others are feature changes and thus not eligible for this round of work.

Thanks.

Changed in evergreen:
status: New → Triaged
milestone: none → 2.6.0-rc1
Changed in evergreen:
milestone: 2.6.0-rc1 → 2.next
Erica Rohlfs (erohlfs) on 2016-02-26
Changed in evergreen:
assignee: nobody → Erica Rohlfs (erohlfs)
Erica Rohlfs (erohlfs) wrote :

Unable to test, cannot checkout to expired patron as an end-user within the staff client.

Changed in evergreen:
assignee: Erica Rohlfs (erohlfs) → nobody
Galen Charlton (gmc) wrote :

Reading the patch, one thing that strikes me is that it looks like it would provide a (rather motivated) patron who has expired privileges a way to bypass that check and successfully renew loans by passing in a checkout_time key.

Jason, given the age of this patch and the possibility of direct inserts into action.circulation during data migration, do you still need this?

Jason Stephenson (jstephenson) wrote :

No, I don't still need it.

Changed in evergreen:
status: Triaged → Won't Fix
milestone: 3.next → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers