Bug 13546 - Branch transfer records orphaned when an item is withdrawn
Summary: Branch transfer records orphaned when an item is withdrawn
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-09 17:02 UTC by Barton Chittenden
Modified: 2016-08-10 14:29 UTC (History)
2 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 Barton Chittenden 2015-01-09 17:02:39 UTC
It is possible to withdraw an item that has an outstanding branch transfer, leaving an uncompleted branch transfer record.

To reproduce:

1) Check in an item whose home branch is not the current branch
2) Confirm the transfer
3) Set the item to 'withdrawn'
4) Check the branch transfers table -- the branch transfer will still exist, even though the item is withdrawn (i.e. not in circulation).

See Also: 12362 Branch transfer records orphaned on cancelled holds
Comment 1 Owen Leonard 2016-08-10 14:29:12 UTC
I think this raises some of the same questions as Bug 12362 in terms of trying to understand what might be physically happening to items which have an open transfer.

I think it's also important to consider the fact that Koha has, as far as I know, no official definition of what 'withdrawn' should mean in functional terms.