[Koha] Importing records preserving the system number

[Elaine Bradtke]

We have used the control number as our stable number. But as I
understand it the 77X link is done with a title search.  This works
well for some things with unique titles, and is nearly useless for
others.  A proper link based on the search for the control number
would bring about an exact match, in theory.

The other problem with control numbers:  They don't auto generate. Any
numbers for new items that we create must be unique.
So far the date, time and cataloguer's initials is the best option I
can come up with (eg 201101311346EB for me, now)
But it's easy to miss type something and it makes for a very long number. . .
Elaine

On Thu, Jan 27, 2011 at 2:21 PM, Linda Culberson
<lculber at mdah.state.ms.us> wrote:
>  We have found that using the Control-number:##### to be extremely slow
> and undependable. In our case, at least, this is definitely not a
> workable "solution" and is barely a solution at all.
>
> On 1:59 PM, Ian Bays wrote:
>> Hi Stefano,
>> We have thought about this for some of our customer requirements but
>> have (quickly) concluded that using the biblionumber (and
>> biblioitemnumber) in koha is not the way to achieve this linking.
>>
>> If you have a number that has significance to you and your data then
>> put that into the 001 control number field (Marc21).  You can link to
>> that from 77x just as easily as with biblionumber.
>>
>> If you try to use biblionumber for these links and you reload your
>> data then all the numbers will be wrong.
>>
>> The search for contents of the 001 field (say 12345) would be:
>>
>> Control-number:12345
>>
>> I hope this helps.
>>
>> Ian
>> On 26/01/2011 10:11, Stefano Bargioni wrote:
>>> This is an autoreply :-)
>>> I wonder why nobody have had this problem before. How can be
>>> preserved internal links -contained in fields like 77x- without
>>> preserving the system number?
>>> I'll try to solve it hacking the code (C4::Biblio), but in my opinion
>>> Koha needs a way to do this, an option in bulkmarcimport for instance.
>>> Bye. Stefano
>>>
>>> On Jan 20, 2011, at 11:27 , Stefano Bargioni wrote:
>>>
>>>> I'm trying to migrate about 140,000 records. Each of them has 001
>>>> with the original value. I copied it into 999c and 999d.
>>>> Importing in Koha, 999c and 999d are replaced by a new
>>>> (autoincremented) bibliotemnumber.
>>>> How can I force Koha to assign bibliotemnumbers using 001 or 999c/d?
>>>> Thank you. SB
>>>> _______________________________________________
>>>> Koha mailing list  http://koha-community.org
>>>> Koha at lists.katipo.co.nz
>>>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>>>
>>> _______________________________________________
>>> Koha mailing list  http://koha-community.org
>>> Koha at lists.katipo.co.nz
>>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>>
>>
>>
>
> --
> Linda Culberson                 lculber at mdah.state.ms.us
> Archives and Records Services Division
> Ms. Dept. of Archives&  History
> P. O. Box 571
> Jackson, MS 39205-0571
> Telephone:  601/576-6873
> Facsimile:  601/576-6824
>
>
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 
Elaine Bradtke
Data Wrangler
VWML
English Folk Dance and Song Society | http://www.efdss.org
Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY
Tel    +44 (0) 20 7485 2206 ext 36
--------------------------------------------------------------------------
Registered Company No. 297142
Charity Registered in England and Wales No. 305999
---------------------------------------------------------------------------
"Writing about music is like dancing about architecture"
--Elvis Costello (Musician magazine No. 60 (October 1983), p. 52)