Sorry for the delay. Pulled in a few different directions at the moment.
Thanks for the clarification Pablo. I haven’t looked at that record yet (just about to leave for the day), but I imagine the number was from OCLC or some other system. I think Katrin has responded more recently mentioning that cataloguing plugins might be helpful. I suspect that she’s correct. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Pablo Bianchi [mailto:[email protected]] Sent: Tuesday, 15 September 2015 11:45 PM To: David Cook <[email protected]> Cc: Koha-org - List <[email protected]> Subject: Re: [Koha] System generated field 001 control number Hi David, On Mon, Sep 14, 2015 at 10:37 PM, David Cook <[email protected] <mailto:[email protected]> > wrote: While I agree that the 001 should be populated with a unique bibliographic control number, it's not the way that Koha is typically set up. Yet for example on Koha demo of Catalyst IT Ltd. (New Zealand) we can find this record <http://demo-intra.mykoha.co.nz/cgi-bin/koha/catalogue/MARCdetail.pl?biblionumber=20895> with biblionumber=999$c=999$d==20895 but control number 001==30908. Maybe they take 30908 from OCLC, but that is not what we are looking for, we want just an incremental system generated number like barcode.pl <http://barcode.pl> plugin builder does for items, but for biblios, with no relation with Koha biblionumber. In theory, it's configurable, but there are parts of Koha that expect the biblionumber to be in the 999$c field (e.g. MARC21slim2OPACResult.xsl). I know 999 is used internally by Koha, so I don't wish to touch nothing about biblionumber/999$c/999$d. Cheers, Pablo _______________________________________________ Koha mailing list http://koha-community.org [email protected] https://lists.katipo.co.nz/mailman/listinfo/koha
