System generated field 001 control number
Hi! As MARC manual say about control number <http://www.loc.gov/marc/bibliographic/bd001.html> *"Field 001 may be system generated"* we wish Koha generate this number (lastUsed++), to avoid creating manually and periodically having to run a report to remove duplicates (from wiki <http://wiki.koha-community.org/wiki/Multipart_Bibliographics> *"There is currently no way to enforce uniqueness in the 001, or rather uniqueness in 001 + 003."*). We have *autoMemberNum* syspref for "next available card number", *autoBarcode* for 952$p, barcode. but nothing for 001, no marc21_field_001.pl vuilder plugin, only bug 9921 <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921> about *"Make it possible to force 001 = biblionumber"*, but that is not exactly what we are looking for. Being this something basic (but asked before <https://lists.katipo.co.nz/public/koha/2010-December/026618.html>) I wonder If I'm getting all wrong... Regards, Pablo BTW on current manual Cataloging Guides say that 001 is "accession number <http://manual.koha-community.org/current/en/catguides.html>", which is usually name to barcode.
Hi, Pablo-- I'm not really sure what you're asking--we use the 001 for a unique bibliographic control number, which for us is the OCLC record number. Are you saying that you wish Koha could automatically generate a unique control number in the 001? Would you use this differently from the Koha record number in the 999 $c field? (That, for us, is the unique Koha record number, as opposed to what we think of as the inter-system "control number" for that title--the OCLC record number.) By the way, I've read the document at http://manual.koha-community.org/current/en/catguides.html as a cheat sheet particular to the American Numismatic Society provided as an example, but not as a procedure applicable for every library, but maybe I've got that wrong! I hope this is helpful! Cheerio! --h2 ~~~~~~~~~~~~~~ Heather Hernandez Technical Services Librarian San Francisco Maritime National Historical Park Research Center 415-561-7032, heather_hernandez@nps.gov http://www.nps.gov/safr/learn/historyculture/museum-collections.htm "The sailor does not pray for wind, he learns to sail."--Gustaf Lindborg On Mon, Sep 14, 2015 at 11:37 AM, Pablo Bianchi <pablo.bianchi@gmail.com> wrote:
Hi!
As MARC manual say about control number <http://www.loc.gov/marc/bibliographic/bd001.html> *"Field 001 may be system generated"* we wish Koha generate this number (lastUsed++), to avoid creating manually and periodically having to run a report to remove duplicates (from wiki <http://wiki.koha-community.org/wiki/Multipart_Bibliographics> *"There is currently no way to enforce uniqueness in the 001, or rather uniqueness in 001 + 003."*). We have *autoMemberNum* syspref for "next available card number", *autoBarcode* for 952$p, barcode. but nothing for 001, no marc21_field_001.pl vuilder plugin, only bug 9921 <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9921> about *"Make it possible to force 001 = biblionumber"*, but that is not exactly what we are looking for.
Being this something basic (but asked before <https://lists.katipo.co.nz/public/koha/2010-December/026618.html>) I wonder If I'm getting all wrong...
Regards, Pablo
BTW on current manual Cataloging Guides say that 001 is "accession number <http://manual.koha-community.org/current/en/catguides.html>", which is usually name to barcode. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hi Heather, On Mon, Sep 14, 2015 at 4:42 PM, Hernandez, Heather <heather_hernandez@nps.gov> wrote:
Hi, Pablo--
I'm not really sure what you're asking--we use the 001 for a unique bibliographic control number, which for us is the OCLC record number.
We wish to have 001 as unique bibliographic control number, but our library have nothing to do with OCLC. Are you saying that you wish Koha could automatically generate a unique
control number in the 001?
Yes.
Would you use this differently from the Koha record number in the 999 $c field?
Yes. In fact we already have a control number on old records because they come from a migration, and this numbers could overlap with biblionumber (999$c). That's why bug 9921 is not useful for us. We need on 001 a unique record number that is not equal neither with OCLC control number nor Koha's biblionumber. Cheers, Pablo
Hi David, On Mon, Sep 14, 2015 at 10:37 PM, David Cook <dcook@prosentient.com.au> 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 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
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:pablo.bianchi@gmail.com] Sent: Tuesday, 15 September 2015 11:45 PM To: David Cook <dcook@prosentient.com.au> Cc: Koha-org - List <koha@lists.katipo.co.nz> Subject: Re: [Koha] System generated field 001 control number Hi David, On Mon, Sep 14, 2015 at 10:37 PM, David Cook <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > 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
Hi Pablo, maybe using a catalouging plugin for 001 could be a solution. There are some plugins for the stocknumber/inventory number field in the item, that are made to autogenerate different kinds of sequential numbers, that could be a starting point for this. stocknumberAV.pl, for example, uses the authorised value "INVENTORY" for storing the last number used and avoids generation of duplicate numbers this way. Hope this helps, Katrin Am 15.09.2015 um 01:07 schrieb Pablo Bianchi:
Would you use this differently from the Koha record number in the 999 $c field?
​Yes. In fact we already have a control number on old records because they come from a migration, and this numbers could overlap with biblionumber (999$c). That's why ​​bug 9921 is not useful for us. We need on 001 a unique record number that is not equal neither with OCLC control number nor Koha's biblionumber.
Cheers, Pablo _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Does this mean we can use MARC 999$c or 999$d for record matching and merging purpose during import, as it didn't seem to work properly when we first start to use Koha a while back. At this moment, we manually enter Koha record number found in 999$c into 001, while OCLC number is swapped to 035 in MARCedit. Iming ----- Iming Chan Translib Information Service Melbourne, Australia http://opac.translib.com Phone: +61 3 9801 5097 Fax: +61 3 9801 4024 E-mail: iming@translib.com -- View this message in context: http://koha.1045719.n5.nabble.com/System-generated-field-001-control-number-... Sent from the Koha-general mailing list archive at Nabble.com.
We use 999$c to match our records (most of which don't have ISBN). This is especially important when we've had to edit a batch offline and re-upload them. On Mon, Sep 21, 2015 at 11:10 PM, Iming Chan <imingchan@yahoo.com.au> wrote:
Does this mean we can use MARC 999$c or 999$d for record matching and merging purpose during import, as it didn't seem to work properly when we first start to use Koha a while back.
At this moment, we manually enter Koha record number found in 999$c into 001, while OCLC number is swapped to 035 in MARCedit.
Iming
----- Iming Chan Translib Information Service Melbourne, Australia http://opac.translib.com
Phone: +61 3 9801 5097 Fax: +61 3 9801 4024 E-mail: iming@translib.com -- View this message in context: http://koha.1045719.n5.nabble.com/System-generated-field-001-control-number-... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://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 (This number is for the English Folk Dance and Song Society in London, England. If you wish to phone me personally, send an e-mail first. I work off site) -------------------------------------------------------------------------- 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)
participants (6)
-
David Cook -
Elaine Bradtke -
Hernandez, Heather -
Iming Chan -
Katrin Fischer -
Pablo Bianchi