Summary: | RESERVESLIP shows incorrect information in items.holdingbranch on first scan | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | major | ||
Priority: | P5 - low | CC: | george, gmcharlt, jonathan.druart, kyle, nick, veron |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 13482 | ||
Bug Blocks: |
Description
Christopher Brannon
2015-04-30 15:29:43 UTC
What I think is going on is the following: 1) The "print slip, confirm and transfer" button it clicked 2) The item is transferred, this act updates the holdingbranch to the destination branchcode for the item 3) The data is gathered and the slip is printed <-- This is why the branch is "wrong" 4) Rescanning the item triggers and update of the holdingbranch again and sets it to your branchcode 5) Reprinting the slip now makes it look "correct" but has possibly screwed up the transfer and the item needs transferred again ( or possibly the holdingbranch is updated a second time later on in step 4 after the data is gathered for the slip ) So, Kyle, are you saying that scanning the item a 2nd time messes up the transfer? I have seen no evidence of that, and it shouldn't. The process works as expected. It is just the holding branch that appears to be incorrect. But it sounds like you are saying it really isn't incorrect until it is scanned and printed again. Am I understanding that correctly? Would like to see further discussion or follow-up on this bug. Christopher |