Bug 3529

Summary: Import of items with non-existent branch code fails w/o explaination
Product: Koha Reporter: Chris Nighswonger <cnighswonger>
Component: MARC Bibliographic record staging/importAssignee: Galen Charlton <gmcharlt>
Status: RESOLVED DUPLICATE QA Contact:
Severity: major    
Priority: P5 - low CC: sophie.meynieux
Version: Main   
Hardware: All   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:
Bug Depends on:    
Bug Blocks: 3530    

Description Chris Cormack 2010-05-21 01:11:47 UTC


---- Reported by cnighswonger@foundations.edu 2009-08-13 13:53:29 ----

Importing items which contain a branch code that is non-existent in the db being imported into results in the items failing to be imported properly and gives no indication to the user.

This also affects other aspects of item batch operations such as generating label batches based on the batch.

A possible fix would be to provide a warning on the import page if such a condition exists as well as a drop-down menu allowing the user to select a valid branch to assign the imported items to. The drop-down could be provided in any case as the user might want to re-assign the items in bulk to another branch.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:11 UTC  ---

This bug was previously known as _bug_ 3529 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3529
This bug blocked bug(s) 3530.

Actual time not defined. Setting to 0.0

Comment 1 Owen Leonard 2013-01-15 14:11:06 UTC
This bug still exists in master. I would hope that if it were fixed the scope would be expanded to cover other authorized values as well: ccode, itemtype, damaged, etc.
Comment 2 Owen Leonard 2013-01-15 14:12:42 UTC
(In reply to comment #1)
> This bug still exists in master.

Whoops, I'm not reading well. I found that an import of items with bad branch codes did *not* fail at all, which I don't think was the goal of this bug. The import should fail and provide feedback on the reason.
Comment 3 Sophie MEYNIEUX 2016-04-22 08:51:53 UTC

*** This bug has been marked as a duplicate of bug 6852 ***