<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@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='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hmmmm, Verónica, I hadn’t considered this before, but reading
the specs, I believe that a 77x field could work.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In our case, we’d want to use 770 (Supplement/Special Issue),
but the real key is the subfield ‘w’. Now, if I’m not mistaken, this would be
the biblio number of the analytic record. It would then be easy enough to add
something to our template to pull the items associated with those bibs, and
display them either intermingled with our other items, or better, to add them
to a different tab or display box.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>This would be an improvement over our existing system, since it
would allow for arbitrarily complex hierarchy to be built (should we ever need
it), and new items would not need to be attached to two different records,
making the growth and maintenance half the work.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Does anyone else have an opinion on this? I’m going to bring it
to my catalogers, and see if it will indeed meet our needs, then we’ll probably
work on a way to make it display in our template.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Ian Walls<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Systems Integration Librarian<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>NYU Health Sciences Libraries<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>550 First Ave., New York, NY 10016<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>(212) 263-8687<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<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>Veronica Lencinas<br>
<b>Sent:</b> Friday, June 19, 2009 8:55 AM<br>
<b>To:</b> koha@lists.katipo.co.nz<br>
<b>Subject:</b> Re: [Koha] Linking an item to multiple bibliographic records<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0>
<tr>
<td valign=top style='padding:0in 0in 0in 0in'>
<p class=MsoNormal>Hi,<br>
<br>
shouldn't this be done with the "w" Subfield of the 773 field (Host
Item Entry) of Marc21? I have right now this problem in a Library with a lot
of analytical records.<br>
<br>
Regards<br>
<br>
Verónica Lencinas<br>
Córdoba, Argentina<br>
<br>
<br>
<br>
<br>
--- El <b>vie 19-jun-09, Nicole Engard <i><nicole.engard@liblime.com></i></b>
escribió:<o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
De: Nicole Engard <nicole.engard@liblime.com><br>
Asunto: Re: [Koha] Linking an item to multiple bibliographic records<br>
Para: "Walls, Ian" <Ian.Walls@med.nyu.edu><br>
Cc: koha@lists.katipo.co.nz<br>
Fecha: viernes, 19 de junio de 2009, 8:09 am<o:p></o:p></p>
<div>
<p class=MsoNormal>Ian,<br>
<br>
I too used to do something similar when cataloging for an academic<br>
library. Once in a while we would catalog the articles in a journal<br>
(professors often requested it) and we would then attach the item for<br>
the full journal to the article record.<br>
<br>
I'd add one more suggestion. Add another table to the database that<br>
takes care of linking the items to the bibs - this table can just have<br>
the ID of the item and ID of the bib - that way you can link the same<br>
item to multiple bibs without duplicating all of the information about<br>
the item and worrying about syncing.<br>
<br>
---<br>
<br>
Nicole C. Engard<br>
Open Source Evangelist, LibLime<br>
(888) Koha ILS (564-2457) ext. 714<br>
<a href="/mc/compose?to=nce@liblime.com">nce@liblime.com</a><br>
AIM/Y!/Skype: nengard<br>
<br>
<a href="http://liblime.com" target="_blank">http://liblime.com</a><br>
<a href="http://blogs.liblime.com/open-sesame/" target="_blank">http://blogs.liblime.com/open-sesame/</a><br>
<br>
<br>
<br>
2009/6/18 Walls, Ian <<a href="/mc/compose?to=Ian.Walls@med.nyu.edu">Ian.Walls@med.nyu.edu</a>>:<br>
> Koha folks,<br>
><br>
><br>
><br>
><br>
><br>
> In the migration process for my library, I’ve come across an odd subset
of<br>
> records in our existing ILS. This system allows you to link an
item record<br>
> to multiple bib records. We use this for providing additional
access to<br>
> certain issues of certain medical journals; these issues are at once a<br>
> volume/issue of a series AND a monographic publication with ISBN.
Patrons<br>
> may look for the resource under either paradigm, either trying to find
an<br>
> article within (using a journal citation), or obtain a book on a
specific<br>
> topic (these certain issues are grouped by subject).<br>
><br>
><br>
><br>
> Example:<br>
><br>
><br>
><br>
> Seminars in Neurology, volume 12 (1992) has the monographic title<br>
> “Neurodermatology”. The series record just has the subject heading<br>
> “Neurology-Periodicals”, while monographic record has subject heading<br>
> “Neurodermatitis” and an authority link to the editor.<br>
><br>
><br>
><br>
> Koha’s data structure doesn’t allow a record in the Items table to point
to<br>
> multiple records in the Biblio and Biblioitems table. Let’s ignore
that<br>
> Biblio and Biblioitems are split, since there has been discussion of
merger<br>
> in the future, and best not to hack a solution on something that’ll<br>
> disappear. What other ways could we come up with share the item
information<br>
> between two different bibs? Here are a few of my ideas; I’d love
to hear<br>
> more!<br>
><br>
><br>
><br>
> · Attach the item to the
monographic record, and fill in the series<br>
> information to match the series record. Add some kind of code to
the series<br>
> record’s display to show items attached to other bibs with the same ISSN<br>
> and/or series title.<br>
><br>
> · Attach the item to
either record, and then do some kind of field<br>
> repurposing in the Item record to include the biblio/biblioitem number
of<br>
> the other, and have the OPAC display this somehow.<br>
><br>
> · Just include a link
the monographic record to the series, and tell<br>
> people to look there for the item’s location/availability<br>
><br>
> · Duplicate the item
record, and come up with some kind of way to<br>
> sync it… must show both items checked out if one is.<br>
><br>
> · Keep the item data in
both MARCXML records, but only import the<br>
> info into MySQL for one<br>
><br>
> · Use the Summary level
in Koha 3.2… somehow….<br>
><br>
><br>
><br>
> Have any of you encountered this kind of problem before? What were
your<br>
> solutions? Does the above make sense? Could something else
be done?<br>
><br>
><br>
><br>
> Thanks so much,<br>
><br>
><br>
><br>
><br>
><br>
> Ian Walls<br>
><br>
> Systems Integration Librarian<br>
><br>
> NYU Health Sciences Libraries<br>
><br>
> (212) 263-8687<br>
><br>
><br>
><br>
><br>
><br>
> ------------------------------------------------------------<br>
> This email message, including any attachments, is for the sole use of
the<br>
> intended recipient(s) and may contain information that is proprietary,<br>
> confidential, and exempt from disclosure under applicable law. Any<br>
> unauthorized review, use, disclosure, or distribution is prohibited. If
you<br>
> have received this email in error please notify the sender by return
email<br>
> and delete the original message. Please note, the recipient should check<br>
> this email and any attachments for the presence of viruses. The
organization<br>
> accepts no liability for any damage caused by any virus transmitted by
this<br>
> email.<br>
> =================================<br>
><br>
> _______________________________________________<br>
> Koha mailing list<br>
> <a href="/mc/compose?to=Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
> <a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
><br>
><br>
_______________________________________________<br>
Koha mailing list<br>
<a href="/mc/compose?to=Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><o:p></o:p></p>
</div>
</td>
</tr>
</table>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>
<hr size=1 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style='font-size:7.5pt;font-family:"Verdana","sans-serif"'>¡Viví
la mejor experiencia en la web!<br>
Descargá gratis el nuevo Internet Explorer 8<br>
http://downloads.yahoo.com/ieak8/?l=ar</span><span style='font-size:10.0pt;
font-family:"Calibri","sans-serif"'><o:p></o:p></span></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>