<div dir="ltr">Although the holdings data is all present in 952, some important data is not dedicated to a single subfield. For example, rather than Koha's $v for the price, the cost is instead held in a subfield and delimited within that subfield along with a lot of other important data. Even MarcEdit is not sophisticated enough to parse this and copy the data to alternate subfields. Does anyone know of a utility that can?<br>
<br>I've been rethinking Jesse's idea of importing the MARC BIBs (without holdings) in Koha, then importing the holdings directly into the sql items table and running the sync script (after first exporting the biblionumbers and matching them into my exported holdings CSV, assuming that the biblionumber or the biblioitemnumber are the key field for syncing).<br>
<br>Does anyone have any better ideas?<br><br>Thank you.<br><br><br><div class="gmail_quote">On Wed, Aug 13, 2008 at 6:04 PM, Galen Charlton <span dir="ltr"><<a href="mailto:galen.charlton@liblime.com">galen.charlton@liblime.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<div class="Ih2E3d"><br>
On Wed, Aug 13, 2008 at 5:39 PM, Library Guy <<a href="mailto:library.guy.zero@gmail.com">library.guy.zero@gmail.com</a>> wrote:<br>
> Good news. I will be able to export BIBs with embedded items data, but in<br>
> field 852 rather than 952. Would the correct preparation for import into<br>
> Koha be to convert all 852 fields to 952, to adjust the default MARC<br>
> framework for my BIBs or both?<br>
<br>
</div>To avoid having to edit both the framework and the Zebra indexing<br>
rules, I suggest converting the 852s to 952s.<br>
<br>
Regards,<br>
<br>
Galen<br>
<font color="#888888">--<br>
Galen Charlton<br>
VP, Research & Development, LibLime<br>
<a href="mailto:galen.charlton@liblime.com">galen.charlton@liblime.com</a><br>
p: 1-888-564-2457 x709<br>
skype: gmcharlt<br>
</font></blockquote></div><br></div>