<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Why do you need separate records for this? I would have one record with call numbers for the organizational scheme. Also implementing the monographic parts functionality would create volume blocks that would make holds easier (if you allow holds on magazines.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Having duplicate records in a consortial database is not a good idea since it can create too many records for patrons to navigate. It also can have a negative impact on holds and other functionality. </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I would merge those records and have the classification scheme direct the patrons to the pile for the correct year. You could have either all issues for one year have the same call number an essentially look like multiple copies or you could assign a call number like Midwest Living 2016a, or Midwest Living 2015-1 and have distinct call numbers per issue.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">The only time I would have multiple records for a serial is if it needed it for title changes.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I particularly would not have multiple records with the same OCLC control number. Any batch processing with OCLC (like setting holdings for your consortia members or having the update service where they update records when changes are made to them) you do or might do might have negative consequences. </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Also, if you should add consortia members, migrations would be more difficult. </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Elaine</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div><div><div><div><font face="tahoma,sans-serif"><br></font></div><div><font face="tahoma,sans-serif"><br></font></div><div><font face="tahoma,sans-serif">J. Elaine Hardy<br></font></div><font face="tahoma,sans-serif">PINES & Collaborative Projects Manager<br></font></div><font face="tahoma,sans-serif">Georgia Public Library Service/PINES<br></font></div><font face="tahoma,sans-serif">1800 Century Place, Ste. 150<br></font></div><font face="tahoma,sans-serif">Atlanta, GA 30045<br><br></font></div><font face="tahoma,sans-serif">404.235.7128 Office<br></font></div><div><font face="tahoma,sans-serif">404.548.4241 Cell<br></font></div><div><font face="tahoma,sans-serif">404.235.7201 FAX<br></font></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Jun 21, 2016 at 3:54 PM, Sharon Douglas <span dir="ltr"><<a href="mailto:douglass@exchange.larl.org" target="_blank">douglass@exchange.larl.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:14.0pt">Hello Everyone,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">We are exploring the idea of allowing duplicate OCLC control numbers and I’d like to hear your thoughts on this idea.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">As a small consortium of small public libraries, we keep magazine issues broken into yearly piles to help customers quickly find the yearly issues they are most concerned about.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Example: Midwest Living 2011-2014, Midwest Living 2015, Midwest Living 2016<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">The oldest title record has the OCLC control number in it, and the newer titles do not.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">Our previous ILS required unique OCLC control numbers, but I’m not finding a compelling reason to continue this practice in the Evergreen ILS.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt">What are your thoughts on allowing duplicate OCLC control numbers?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">Sharon Douglas - Automation Coordinator for Lake Agassiz Regional Library<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">118 5th St S • Moorhead, MN 56560 • <a href="tel:218-233-3757%20ext%20138" value="+12182333757" target="_blank">218-233-3757 ext 138</a> - <a href="mailto:douglass@exchange.larl.org" target="_blank">douglass@exchange.larl.org</a><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>_______________________________________________<br>
Evergreen-catalogers mailing list<br>
<a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers</a><br>
<br></blockquote></div><br></div>