local copy block and local copy alert settings not working at 2.0 or 2.1

Bug #954107 reported by Shae on 2012-03-13
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

This was first reported to me by a customer at version 2.0.10 but I tested internally on a 2.1.0 system. I expected that if local copy block was set to TRUE that when I tried to place a hold on a title where there are copies available, it would not allow the hold through. This was not the case. Here are the steps I took:

1. On the system, I made sure the library setting of local copy block was set to TRUE.
2. In the staff client, 2.1.0, I found a title in my local branch that had one copy available.
3. I clicked place hold and selected a local patron with no fines/overdues on their account and entered their info.
4. When I clicked Place Hold, it said hold was successfully placed.
5. I also went to the OPAC and found a title with several copies attached, all available.
6. I placed a hold for a Resident patron and it allowed the hold.
7. I had also selected local copy alert and set that to TRUE but I never saw an alert about copies being available.
8. I also tried this with just the local copy alert set to TRUE and local copy block set to FALSE to see if the Local Copy Alert feature worked on it's own. It never showed an alert.

Perhaps this setting isn't fully implemented? Or it has a bug. Let me know if you need more info about which in house system I tried this on. Thank you for checking into this.

Jason Stephenson (jstephenson) wrote :

At this point, needs confirmation in 2.2+.

Changed in evergreen:
status: New → Incomplete
Changed in evergreen:
status: Incomplete → Triaged
Ben Shum (bshum) wrote :

Marking incomplete pending further testing / confirmation of issue in more recent versions of Evergreen.

Changed in evergreen:
status: Triaged → Incomplete
Erica Rohlfs (erohlfs) wrote :

I tested this in Evergreen version 2.4.2 on both the staff client and patron OPAC.

When setting Has Local Copy Block and Has Local Copy Alert both to True (and when setting Has Local Copy Block to True with Has Local Copy Alert set to False), both the staff client and patron OPAC block the placing of a hold. The message reads: Hold was not successfully placed. There is already a copy available at your local library.

When setting Has Local Copy Alert to True and Has Local Copy Block to False, I received the alert when placing a hold in both the staff client and OPAC, and it required an override. The message reads: Hold was not successfully placed. Problem: There is already a copy available at your local library. Then it gave the “You have permission to override some of the failed holds” option.

I could not recreate an instance of these library settings not functioning as expected.

Shae (shae-esilibrary) wrote :

I was just working with these settings today on a 2.4.2 system. I agree that they are working as expected now. I think the only outstanding question is whether they work the way libraries want them to. In the JSPAC when the settings were initially implemented, they didn't make it look like your hold wouldn't go through. Now, in the TPAC, even if you just have the alert enabled, it looks like the hold is not allowed because it says "hold was not successfully placed" at first. Then they have to confirm whether they want to go through with the hold. So, overall, just an issue of possible confusion for patrons but not really a software bug.

Andrea Neiman (aneiman) wrote :

Marking invalid on the basis of comments #3 and #4

Changed in evergreen:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers