Quoting Dan Weeks <Dan@bibliofiche.com>:
FYI:
Typicly 852a would hold a "homebranch" and 852b the "holdingbranch": this is not always consistant but never-the-less defined as part of he 852 holding structure. Once you place a barcode on a book you need no acsession number (which is what I assume you mean by "Item number"). The barcode IS the item number. Thanks Dan,
actually, the itemnumber I am referring to is the koha items.itemnumber It can't be NULL, nor can items.barcode. (I think) It seems like I could either make the items.itemnumber just a sequence of unique numbers, or I could make them the same as the barcode, but koha won't seem to let me map two koha fields to the same MARC subfield. I could manually stick the data into the "items" table in the database, but I'm hoping to figure out the "right" way to do this during import so it will be useful for others. Thanks, Derek
All 900 fields are "user defined" and not part of any marc definition. Many combinations have been used and accepted through the years but 852 is the defined area
a holding. (A "holding" is specific to the individual item, as opposed the the Biblio which defines the title and author and publishing data. i.e. One "biblio" of a popular title could have many "holdings" in the library. This is also why the barcode of the book becomes the only "item" number you need.)
Here is the LC definition of 852. http://www.loc.gov/marc/bibliographic/ecbdhold.html#mrcb852
Dan
----- Original Message ----- From: "Derek Dresser" <Derek.Dresser@gouldacademy.org> To: "paul POULAIN" <paul.poulain@free.fr> Sent: Thursday, July 10, 2003 11:31 AM Subject: Re: [Koha] import question
Paul ... any ideas?
Of course yes :-) If you want import to put items into items table, you have to tell Koha where are hidden your items in your MARC datas... Let me explain : Koha supports any MARC flavour. And each MARC flavour hides items in a different place (for example in UNIMARC, it's 995. For NPL, that uses MARC21, it's 952) * Go to parameter section of Koha, MARC parameters tables. * Search for the field where items are hidden (for example 947) * Open subfields of field 947. * "map" each 947 subfield to a items.something field. * Put each subfield you've mapped to tab "items". * go back to main parameter page * run "checkmarc". If it reports no errors, you've win. * import again, using delete flag to empty your database during the process.
Hope This Helps
Hi, I've got a few questions and some more info. First of all, my data is in MicroLIF format, which is apparently basically USMARC from what I understand. I am using the MARC21 parameters at install time. I looked at the MARC records in Winnebago, and it seems that the "hidden" data is in the 852 field. However, it appears that the only data in that field is the call number and bar code, while the MARC Check requires that I map itemnumber, barcode, homebranch and holdingbranch at a minimum I think (and all within the 852 field).
It seems like the import works fine for the biblios and biblioitems. Should I just extract the barcode and call number afterwards and populate the items table separately? If so, should I use the barcode number for the item number, or just start with 1 and go up sequentially? How can I solve
for this
problem so it will be the most useful for others in the long run? Does it make sense to have another import type "MicroLIF", or "Winnebago"? Thanks in advance for any ideas. I have included a small piece of my data again, in case it is useful.
Thanks, Derek
00623pam 2200181 a
450000100130000000800410001302000150005405000210006908200140009010000350010424500860013926
00066002253000026002915040065003176500030003828520023004129610006004\35^^
85023778 ^^851129s1986 nyu b 00010 eng ^^ ^_a0025003402^^0 ^_aAZ221^_b.A35 1986^^0 ^_a001.2^_219^^10^_aAdler, Mortimer Jerome,^_d1902-^^12^_aA guidebook to le\arning :^_bfor a lifelong pursuit of wisdom /^_cMortimer J. Adler.^^0 ^_aNew York :^_bMacmillan ;^_aLondon :^_bCollier Macmillan,^_cc1986.^^ ^_axii, 163 p. ;^_c22 cm.^^ ^_a"Som\e books that may be helpful to autodidacts": p. 161-163.^^ 0^_aLearning and scholarship.^^1 ^_h001.2 Ad59g^_p10001^^WL^_t6^^^]00600pam 2200205 a
45000010013000000080041000130200\022000540200022000760500024000980820017001221000020001392
450064001592500012002232600038002353000035002735040039003086500016003478520025003639610006
00388^^
84028794 ^^841231s198\5 nyua b 00110 eng ^^ ^_a0716717174 (pbk.)^^ ^_a071671695X (hard)^^0 ^_aQA276.12^_b.M66 1985^^0 ^_a001.4/22^_219^^10^_aMoore, David S.^^10^_aStatistics :^_bconcepts \and controversies /^_cDavid S. Moore.^^ ^_a2nd ed.^^0 ^_aNew York :^_bW.H. Freeman,^_cc1985.^^ ^_axvii, 350 p. :^_bill. ;^_c24 cm.^^ ^_aIncludes bibliographies and index.^^ 0^\_aStatistics.^^1 ^_h001.422 M782s^_p10002^^WL^_t6^^^]
Note : the main constraint is that all MARC subfields mapped to item field MUST be in the same field (you can't have a part of an item into 947 & 2nd part in 935). If you have, then the only solution is to "rewritte" your MARC data before importing. We have a problem with itemtypes, that is not in items in Koha but seems to have it's place in there, that's what we will speak during today IRC meeting.
-- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
-- Derek Dresser http://network.gouldacademy.org/ Gould Academy Bethel, ME 04217 (207)824-7700
"Nothing endures but change" --Heraclitus
------------------------------------------------- This mail sent through IMP: http://horde.org/imp/
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Derek Dresser http://network.gouldacademy.org/ Gould Academy Bethel, ME 04217 (207)824-7700 "Nothing endures but change" --Heraclitus ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/
On Thu, Jul 10, 2003 at 02:32:31PM -0400, Derek Dresser said:
Quoting Dan Weeks <Dan@bibliofiche.com>:
FYI:
Typicly 852a would hold a "homebranch" and 852b the "holdingbranch": this is not always consistant but never-the-less defined as part of he 852 holding structure. Once you place a barcode on a book you need no acsession number (which is what I assume you mean by "Item number"). The barcode IS the item number. Thanks Dan,
actually, the itemnumber I am referring to is the koha items.itemnumber It can't be NULL, nor can items.barcode. (I think) It seems like I could either make the items.itemnumber just a sequence of unique numbers, or I could make them the same as the barcode, but koha won't seem to let me map two koha fields to the same MARC subfield. I could manually stick the data into the "items" table in the database, but I'm hoping to figure out the "right" way to do this during import so it will be useful for others.
Yep, thats right Derek. itemnumber is the internal number koha uses. In case for some reason barcode changes (eg the sticker falls off and a new one is put on or something). But yes its just a unique number. Starting a 1, and incrementing upwards would work fine. The danger with manually sticking in the data, is it wouldnt get stored in the MARC subfields. Chris -- Chris Cormack Programmer 027 4500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
participants (2)
-
Chris Cormack -
Derek Dresser