<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Bright";
panose-1:2 4 6 2 5 5 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Times New Roman","serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Amy,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>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.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>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.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>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).<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Hope this helps. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Ian Walls<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Systems Integration Librarian<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>NYU Health Sciences Libraries<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>550 First Ave., New York, NY
10016<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>(212) 263-8687<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] <b>On
Behalf Of </b>Amy Schuler<br>
<b>Sent:</b> Tuesday, October 27, 2009 10:25 AM<br>
<b>To:</b> koha@lists.katipo.co.nz<br>
<b>Subject:</b> [Koha] Koha migration & subfield problem<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>Hello, <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>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.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>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??) <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>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.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=LDR
01105cam 2200301 i 4500<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=001
\\\74075531\//r952<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=003
DLC<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=005
19950918112125.9<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=008
750501s1975\\\\nyua\\\\\b\\\\00010\eng\\<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=010
\\$a 74075531 //r952<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=020
\\$a091384800X<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=040
\\$aDLC$cDLC$dDLC<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=043
\\$an-us---<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=050
\\$aQH76$b.E36<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=082
00$a333.7/2<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=100
10$aEgler, Frank Edwin,$d1911-<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=245
14$aThe plight of the rightofway domain :$bvictim of vandalism /$cby Frank E.
Egler, consultant, and Stan R. Foote.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=260
0\$aMt. Kisco, N.Y. :$bFutura Media Services,$c[1975]<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=300
\\$a2 v. :$bill. ;$c23 cm.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=500
\\$aVol. 2 has also special title: Personalized documentation.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=504
\\$aIncludes bibliographical references.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=650
\0$aLandscape protection$zUnited States.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=650
\0$aRight of way$zUnited States.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=650
\0$aBrush$xcontrol$xEnvironmental aspects$zUnited States.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=650
\0$aPlant ecology$zUnited States.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=700
10$aFoote, Stan R.,$ejoint author.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=952
\\$p10020$oHC 110 .E5 E35$mv.1$d20030108<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>=952
\\$p10021$oHC 110 .E5 E35$mv.2$d20030108<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'>Amy
C. Schuler<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'>Manager
of Information Services<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'>Cary
Institute of Ecosystem Studies<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'>PO
Box AB <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'>Millbrook,
NY 12545<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'>(845)
677-7600 x164<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'><a
href="mailto:schulera@ecostudies.org">schulera@caryinstitute.org</a><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Bright","serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<pre></PRE>
<html>
<body>
------------------------------------------------------------<br />
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 />
=================================
</body>
</html>
<PRE>
</pre></body>
</html>