hard boundaries not respected on copy holds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Related bugs:
https:/
https:/
Evergreen: 2.2, Postgres 9.1
This is a bit convoluted, hopefully I can explain this properly.
When placing a hold, various methods check for possible copies and raise the no_ultimate_items error if there is no way that the hold will likely be fulfilled. These methods use something like this:
my %org_filter = create_
They then put the result in a big json_query call to get possible copies.
HOWEVER, copy-level holds don't do this. During a copy hold, only verify_
There are a few possible solutions, although a permanent solution would be a major rewrite of holds code, which Jason S. has discussed, and would probably be a good opportunity to integrate some relevant FulfILLment code. But, I am thinking a temporary fix will be to wrap verify_
description: | updated |
Changed in evergreen: | |
status: | New → Triaged |
tags: |
added: circ-holds removed: holds |