<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;font-size:small">Might there not be system-specific reasons for wanting to use a designated field for links? They need to be managed in various ways, and there are free-text fields to describe the link, which could be just as well be copy-specific as related to the resource generally. The definition of the field certainly fits the bill:</div>
<div class="gmail_default" style="font-family:georgia,serif;font-size:small"><br></div><div class="gmail_default" style="font-family:georgia,serif;font-size:small">"<span style="text-align:justify;font-family:arial">Information
needed to locate and access an electronic resource. The field may be
used in a bibliographic record for a resource when that resource or a
subset of it is available electronically. In addition,<i> it may be used
to locate and access an electronic version of a non-electronic resource
described in the bibliographic record</i> [emphasis added] or a related electronic resource."</span></div><div class="gmail_default" style="font-family:georgia,serif;font-size:small"><span style="text-align:justify;font-family:arial"><br>
</span></div><div class="gmail_default" style="font-size:small"><span style="text-align:justify"><font face="georgia, serif">If any field that now lacks it really needs |5 that would seem to be the one. Or is that just one more deck chair on the good ship MARC?</font></span></div>
</div><div class="gmail_extra"><br clear="all"><div><font face="'courier new', monospace">RICHARD NOBLE :: RARE MATERIALS CATALOGUER :: JOHN HAY LIBRARY</font><div><font face="'courier new', monospace">BROWN UNIVERSITY :: PROVIDENCE, R.I. 02912 :: 401-863-1187</font></div>
<div><span style="font-family:'courier new',monospace"><</span><a href="mailto:RICHARD_NOBLE@BROWN.EDU" style="font-family:'courier new',monospace" target="_blank">Richard_Noble@Br</a><span style="font-family:'courier new',monospace"><a href="http://own.edu" target="_blank">own.edu</a></span><span style="font-family:'courier new',monospace">></span></div>
</div>
<br><br><div class="gmail_quote">On Thu, Apr 10, 2014 at 6:29 PM, Deborah J. Leslie <span dir="ltr"><<a href="mailto:DJLeslie@folger.edu" target="_blank">DJLeslie@folger.edu</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:11.0pt;font-family:"Georgia","serif";color:#1f497d">I don't know if it would be confusing because I haven't used the 856 for that. And don't want to, really; I want to make the 581 carry its weight. (-;<u></u><u></u></span></p>
<div class="">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#31849b">Deborah J. Leslie | Folger Shakespeare Library | djleslie@ <a href="http://folger.edu" target="_blank">folger.edu</a> | <a href="tel:202.675-0369" value="+12026750369" target="_blank">202.675-0369</a> | 201 East Capitol St., SE, Washington, DC 20001 | www. <a href="http://folger.edu" target="_blank">folger.edu</a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1f497d"><u></u> <u></u></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""> <a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a> [mailto:<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a>]
<b>On Behalf Of </b>Allison Jai O'Dell<br>
<b>Sent:</b> Thursday, 10 April 2014 15:11<br>
<b>To:</b> DCRM Users' Group</span></p><div class=""><br>
<b>Subject:</b> Re: [DCRM-L] Limitations of MARC 581<u></u><u></u></div><p></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I'd say that the 544 similarly suffers, and that the 501 would greatly benefit from some linking capability. (Nevermind that URIs would be beneficial in most MARC fields...)<u></u><u></u></p>
</div><div class="">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">In practice, I use the 856 (2nd indicator 2) to address the problem. Deborah, do you find that using a separate field makes things confusing for your users?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Allison Jai O'Dell<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><u></u> <u></u></p>
</div>
</div></div>
</div>
</div>
</blockquote></div><br></div>