[Koha] Koha migration & subfield problem
Ian.Walls at med.nyu.edu
Wed Oct 28 03:34:59 NZDT 2009
Koha is MARC agnostic on its own; you can adjust your MARC Frameworks to accept repeated subfields as you like. So, as far as MARC record validity goes, you should be just fine with multiple 952$o.
In my experience, if you supply multiple subfields within a 952, they all get loaded into mapped database field (952$o -> itemcallnumber in the default framework), separated by " | ", up to the character limit of the field (30 in the case of itemcallnumber). This would let you cram multiple bits of information into the same field; if you don't like the " | " (and you didn't lose too much info), you could export back to MarcEdit, change the " | " to a more pleasant separator, and re-import.
Another option, depending on your comfort with XSLT, would be to convert your old MARC into MARCXML, run it through a stylesheet that merges the subfields into 952$o, then convert back to MARC. You can get a little more fine grained control with the logic in MARCXML (not a lot, but enough).
Hope this helps.
Systems Integration Librarian
NYU Health Sciences Libraries
550 First Ave., New York, NY 10016
From: koha-bounces at lists.katipo.co.nz [mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of Amy Schuler
Sent: Tuesday, October 27, 2009 10:25 AM
To: koha at lists.katipo.co.nz
Subject: [Koha] Koha migration & subfield problem
Does anyone have any ideas regarding my problem with 852/952 $m. The problem is that, in editing all of my holdings data to migrate nicely into Koha, I cannot figure out how to migrate my old 852 $m data (call number suffix, a standard MARC subfield, I have publication years and volume #s stored in this field). When I use MarcEdit to swap fields & edit data, I can write a regular expression that will find all 852 $h, i, and m and move them to 952 $o. However, this only finds & replaces those 852s that have all 3 of those subfields. Most of my records do not have all 3, they only have $h and i. So, when I run a second find & replace to pick up the 852s that only have those two subfields, then a second 952 $o is created.
In short, it seems that my choices in regard to $m data are: (1) move $m to some completely different subfield ($z public note, $t copy number? Little misleading), or (2) have 2 instances of $o in some of my 952 fields, although I am not sure how this will render, or even whether Koha will accept this (is $o repeatable??)
I hope I have been clear. Please let me know if you have ideas. I am running Koha v. 3.0001005 and I attach a sample record (with most edits made) below. Note that this record contains two 952s because it is a 2 volume set, as well as the $m's.
=LDR 01105cam 2200301 i 4500
=010 \\$a 74075531 //r952
=100 10$aEgler, Frank Edwin,$d1911-
=245 14$aThe plight of the rightofway domain :$bvictim of vandalism /$cby Frank E. Egler, consultant, and Stan R. Foote.
=260 0\$aMt. Kisco, N.Y. :$bFutura Media Services,$c
=300 \\$a2 v. :$bill. ;$c23 cm.
=500 \\$aVol. 2 has also special title: Personalized documentation.
=504 \\$aIncludes bibliographical references.
=650 \0$aLandscape protection$zUnited States.
=650 \0$aRight of way$zUnited States.
=650 \0$aBrush$xcontrol$xEnvironmental aspects$zUnited States.
=650 \0$aPlant ecology$zUnited States.
=700 10$aFoote, Stan R.,$ejoint author.
=952 \\$p10020$oHC 110 .E5 E35$mv.1$d20030108
=952 \\$p10021$oHC 110 .E5 E35$mv.2$d20030108
Amy C. Schuler
Manager of Information Services
Cary Institute of Ecosystem Studies
PO Box AB
Millbrook, NY 12545
(845) 677-7600 x164
schulera at caryinstitute.org<mailto:schulera at ecostudies.org>
This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is proprietary, confidential, and exempt from disclosure under applicable law. Any unauthorized review, use, disclosure, or distribution is prohibited. If you have received this email in error please notify the sender by return email and delete the original message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email.<br />
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Koha