Bug 13752 - Item level holds crossed if item moved to another bib
Summary: Item level holds crossed if item moved to another bib
Status: RESOLVED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-23 23:14 UTC by Christopher Brannon
Modified: 2023-07-28 21:50 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2015-02-23 23:14:49 UTC
I haven't tested this yet by moving an item from one bib to another, but we did see an instance where an item level hold was placed on an item that was ordered in acquisitions in one basket, and then the item was transferred to another basket.  We think this somehow attached the item to another bib in the process, and then the hold was showing up on the item itself, but not that bibs holds, and showing in the holds on a different bib (the one the item was originally attached to.

Need some help testing this.  If this is the case when moving an item with item level holds from one basket to another in acq, or in cataloging alone, there needs to be either a mechanism to stop the transfer of the item from bib to bib, or it needs to update the holds properly.

Christopher
Comment 1 Joy Nelson 2015-02-24 00:10:31 UTC
I have verified this in Christopher's data.  An order was placed, item created and attached to biblionumber 232243.  A hold was placed on that on order item and a line in the reserves table created. 

The order was moved to another basket and the biblionumber on that basket was 246109.  The item moved (i.e. biblionumber in items table changed), however, the reserves table retained the old biblionumber (232243) and not the new one.  

-joy nelson

(In reply to Christopher Brannon from comment #0)
> I haven't tested this yet by moving an item from one bib to another, but we
> did see an instance where an item level hold was placed on an item that was
> ordered in acquisitions in one basket, and then the item was transferred to
> another basket.  We think this somehow attached the item to another bib in
> the process, and then the hold was showing up on the item itself, but not
> that bibs holds, and showing in the holds on a different bib (the one the
> item was originally attached to.
> 
> Need some help testing this.  If this is the case when moving an item with
> item level holds from one basket to another in acq, or in cataloging alone,
> there needs to be either a mechanism to stop the transfer of the item from
> bib to bib, or it needs to update the holds properly.
> 
> Christopher
Comment 2 Katrin Fischer 2019-02-04 23:37:38 UTC
Marking this acquisitions as Joy's comment reads like this happens when using the 'transfer order' option.
Comment 3 Katrin Fischer 2020-01-06 15:06:46 UTC
Wondering: if you move the order using the transfer option, the biblionumber would not change. There must be another step we are missing?
Comment 4 Christopher Brannon 2020-02-25 17:42:58 UTC
I don't think this is limited to acquisitions.  This is primarily a cataloging/holds issue.  I think the same might occur if two bibs are merged.
Comment 5 Christopher Brannon 2020-02-25 17:44:27 UTC
(In reply to Christopher Brannon from comment #4)
> I don't think this is limited to acquisitions.  This is primarily a
> cataloging/holds issue.  I think the same might occur if two bibs are merged.

Ignore this comment.  I think I am thinking of something else.
Comment 6 Christopher Brannon 2020-06-26 20:58:13 UTC
(In reply to Katrin Fischer from comment #3)
> Wondering: if you move the order using the transfer option, the biblionumber
> would not change. There must be another step we are missing?

If there is a step that is missing, I'm not sure what it is.  But, this does point out how this can get messed up.
Comment 7 Katrin Fischer 2020-09-13 09:56:01 UTC
Christopher, could you clear up how the order/items were moved so we can try and replicate this? Was it transfer order or was the item attached to another record from cataloguing? I think a step by step test plan could be really helpful here.
Comment 8 Katrin Fischer 2020-09-13 09:59:44 UTC
I've tried something:

- Find record A
- Place an item level hold on one of the items
- Move the item to another record B
- The item hold was moved with the item

I believe this is the only way the biblionumber would change and it looks like the issue might have been fixed.
Comment 9 Christopher Brannon 2020-10-30 15:20:09 UTC
(In reply to Katrin Fischer from comment #8)
> I've tried something:
> 
> - Find record A
> - Place an item level hold on one of the items
> - Move the item to another record B
> - The item hold was moved with the item
> 
> I believe this is the only way the biblionumber would change and it looks
> like the issue might have been fixed.

Are you saying the scenario that Joy outlined in Comment 1 is no longer an issue?  Your test you do here doesn't talk about orders and baskets, so I am not sure that you addressed this issue.
Comment 10 Katrin Fischer 2020-10-30 19:04:14 UTC
I've tried to make sense of the descriptions here - can you provide a step by step?
Comment 11 Christopher Brannon 2020-10-30 19:35:09 UTC
Joy, I defer to you, since you actually tested this.  Are you able to provide a step by step?  I can only go off what I've heard and have seen after the fact.  I don't touch acquisitions enough to do anything with it.
Comment 12 Joy Nelson 2020-10-30 19:40:18 UTC
Christopher-
It may be best if you can verify the steps from someone on your technical services staff.  Given the age of this ticket a fresh replication in your system is probably a good idea.

joy

(In reply to Christopher Brannon from comment #11)
> Joy, I defer to you, since you actually tested this.  Are you able to
> provide a step by step?  I can only go off what I've heard and have seen
> after the fact.  I don't touch acquisitions enough to do anything with it.
Comment 13 Christopher Brannon 2020-10-30 19:41:02 UTC
I will see what I can do.
Comment 14 Katrin Fischer 2023-07-28 21:50:45 UTC
Since we haven't been able to replicate the issue I am closing this INVALID for now. Please reopen if this issue is still visible to you and provide steps for testing.