[Koha] same barcode number

[Steven F. Baljkas]

From: Chris Cormack <chris at katipo.co.nz>
Date: 2004/12/22 Wed PM 02:49:09 CST
To: Martin Longo <jmlongo at uncu.edu.ar>
CC: jjenning at fastmail.fm,  koha at lists.katipo.co.nz
Subject: Re: [Koha] same barcode number
 
> On Wed, Dec 22, 2004 at 05:20:09PM +0100, Martin Longo said:
> > I have a similar problem, but regarding different items with the same 
> > barcode number but from different branches
> > 
> > Say I have branches A and B
> > 
> > there's an item with barcode 1234 at branch A
> > and a completely different item at branch B with barcode 1234
> > 
> > both items were "bulmarkimported" into Koha
> > 
> > If I search the catalogue for barcode '1234' I find both items, with 
> > their correspondig 'holdingbranch'
> > 
> > *BUT*
> > 
> > when I try to issue item 1234 ... Koha always issues item 1234 from 
> > branch A...  and I never get to choose item 1234 from branch B..
> > 
> Hmm, unfortunately no easy fix. Koha is built on the assumption every item
> you will want to circulate (issue/return) will have a unique barcode.
> 
> So its going to always get the first one. This is so you can return an item
> at another branch and it will get its holdingrbanch set to there.
> IE it allows people to borrow from one branch and return at another.
> 
> Barcode to Koha should be unique .. if you are going to do any issuing.
> As Jared said, the restriction on unique was removed earlier to allow for
> people who didnt have barcodes. Which was perhaps a mistake. 

> Think of barcode as being id .. it needs to be unique, its the only way koha
> can tell items apart.
> 
> 
> Chris


Hi, Chris. I don't think it was a mistake to give folks the option to NOT use barcodes.

However, if people opt to use barcodes, you are absolutely right that the barcodes should be unique. I don't know how that would complicate the coding for you as programmers, but I would think you could just have it On or Off, but if On, then the field would have to be a unique key.

Now, I hate to be throwing a Ludite solution at this problem when you've already engaged your programmer brain, but wouldn't it be easier for Jared just to have the B branch assign a new barcode label?

That should take like 30 seconds to correct in cataloguing, if that, and the problem will vanish.

In the future, Jared, your branches should subscribe to a standardised number sequence. There are at least two easy ways to do this:

1) As in the present state of my home city's public library system, the different branches of the system all forward all items received to central cataloguing. This has several advantages, not the least of which is concentrating human and material resources necessary to cataloguing in one office. Barcodes are assigned centrally and the items are returned to their home branches once processed and catalogued.

2) As had apparently been done in the past here, both in the public, government and university library systems, different branches can be sent sets/ranges of barcodes from a central order. Locally different branches' cataloguers catalogued to  their local practices and standards (the cataloguer in me shivers remembering the lovely mess this caused) but duplicates were avoided.

That's my 2 cents worth anyway.

Cheers,
Steven F. Baljkas
library tech at large
Koha neophyte
Winnipeg, MB, Canada