Patron Expiration on current date is not handled the same between the Patron Indicators and the Circulation functions

Bug #1342989 reported by Carrie Curie on 2014-07-16
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Low
Unassigned

Bug Description

If a patron has an expiration date that is the same as the current date, the patron indicator does not indicate the patron is expired. Circulation (check out) is blocked because it does consider the patron as expired. This means that staff do not know a patron is expired, until a checkout is attempted.

In some situations, staff may want to check an item out to the patron for a couple of hours or the day but not extend the expiration date of the account. For example, the patron may be checking out headphones to use with a library computer. This would be useful for schools where the account expires on the last day of the school year/term.

So, ideally, it would be nice if circulations to patrons were permitted on the day their account expires following whatever conditions the library had chosen with the YAOUS proposed in bug 1046420 (Wishlist: Cut off due dates so they don't extend past card expiration date).

tags: added: wishlist
tags: added: date due expiration patron
tags: added: checkout
removed: circulation date due expiration patron wishlist
Sam Link (sam-link) wrote :

Still present in 2.9.1

To test:

* Set patron account expiration date to current date.
* Attempt to circulate or renew items; it will be blocked.
* Observe that patron information screen does not indicate that the account is expired.

Kathy Lussier (klussier) wrote :

Thanks for confirming Sam!

I also just wanted to add a note that anyone with a Launchpad account who can replicate a bug in Evergreen also has the ability to set a bug status to confirmed. I think there are probably many people who think this power is only given to people with special privileges, so I just want to get the word out that anyone can confirm a bug (provided that you have verified it exists) and that it really helps us with managing Evergreen bugs.

I'm also noting that I can't verify whether this problem continues to exist in the web client due to bug 1522599. At this time, the only visual indicator in the web client telling staff that an account is expired is on the alert screen.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Low
tji@sitka.bclibraries.ca (tji) wrote :

EG 3.0.1 with web client

Setting the expiry date to current date on the staff client, the account is marked expired immediately.
Names and expiry date in the summary area appear in red.

I noticed another issue that could affect the behaviour. When creating a new patron account, the time portion of the expiration date is set to the time of the creation time, while editing the expiration date sets the time to 00:00. The dates appear to be the same as you do not see the time. But time matters when assessing an account is expired or not.

Tina Ji
BC Libraries Coop

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers