Labels for the Deposit/Rental-fee fields are misleading.

Bug #1776939 reported by Nathan Eady
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

Steps to reproduce:
1. Catalog a new item.
2. Leave Deposit? set to No, because your library doesn't use deposits.
3. Accidentally fill the item's price into the Deposit Amount field,
   instead of the Price field.
4. Finish cataloging the item as normal.
5. Later, attempt to check the item out to a patron.

Actual Results:
Deposit is required.

Expected Results:
I am not entirely sure what the ideal behavior would be at checkout time.
However, there should be a warning of some kind when saving the record with this inconsistency in the first place.

Revision history for this message
Jeff Godin (jgodin) wrote :

Adding context:

There is support in Evergreen for the concept of copies that require a "rental fee" to check out.

The way you specify a rental fee as being required for an item is to place a non-zero value in the Deposit field and specify Deposit Required? of False.

There may be room for improving the documentation, display, or other aspects of this.

Nathan Eady (mrmcquack)
summary: - "No" value for the "Deposit?" field is ignored if Deposit Amount is
- nonzero
+ Labels for the Deposit/Rental-fee fields are misleading.
tags: added: cataloging
removed: webstaffclient
Revision history for this message
Terran McCanna (tmccanna) wrote :

Agree that the interface needs to clarify what is happening because the obvious assumption is that the "No" would override the amount.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
tags: added: circ-billing
tags: added: usability
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.