[Koha-bugs] [Bug 3796] Place a hold on a specific copy allows impossible items

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3796

--- Comment #5 from Christopher Brannon <cbrannon at cdalibrary.org> ---
We don't have specifics yet. All we have is the evidence left the table.

I think that there should be a check somewhere...a cron job, or something, that
checks the validity of the reserves table.  Particularly between the item
number and bib number.  And perhaps against the patron account.  There are two
problems evident:

1) Mismatched item and bib numbers in the reserves table.
2) Reserves showing in the reserves table, and not showing in the patron
account.  Most likely because of issue 1.

Is it necessary to have a bib number in the reserves table when the item number
is recorded for an item level hold?  Seems redundant if the bib number is in
the items table.  That would be the simplest remedy for this issue.  So, rather
than using the bib number in the reserves table for any holds functions, it
could be referenced from the items table.

Otherwise, we might need a checkpoint to verify accuracy.

As I said, we don't have an answer as to how this is happening.  I can think of
a few ways it might happen, but I don't think one of them is the case, since it
happened to a couple of items with the same patron.

One way it could happen is that a patron is reconstructing the URL manually and
blending mismatched info.

The second way is that a hold is placed on an item.  The item record is then
turned into a different item and attached to a different bib.  OR better yet,
an item is created and accidently attached to the wrong bib, and after the hold
is placed, the item is moved to the correct bib.

It seems that maybe when items are moved from one bib to another, a check
should take place to verify any possible holds in the reserves table.

I don't know if this helps, but that's my two cents.

Christopher

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are watching all bug changes.