<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Don,</p>
<p>There is a global flag that allows the records to appear in
consortium-wide searches. More information on that global flag is
available at
<a class="moz-txt-link-freetext" href="http://docs.evergreen-ils.org/2.12/_cataloging_electronic_resources_8201_8212_8201_finding_them_in_catalog_searches.html">http://docs.evergreen-ils.org/2.12/_cataloging_electronic_resources_8201_8212_8201_finding_them_in_catalog_searches.html</a></p>
<p><br>
</p>
<p>Kathy<br>
</p>
<br>
<div class="moz-cite-prefix">On 06/14/2017 09:28 AM, Donald
Butterworth wrote:<br>
</div>
<blockquote
cite="mid:CACXGyX9gK5V5KgZPk21z4NFu13JJnOv2zX+=t=rkySK=DFDYbA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Catalogers,<br>
<br>
</div>
You'd think after using Evergreen for 3 years we would
have our act together when it comes to ebook records.
Not. <br>
<br>
</div>
We have not been using the $9 option in our 856 tags, and
it has become painfully obvious that we need to, now that
two of the smaller libraries in our consortium are ready
to come online. All of our restricted ebooks are showing
up in their catalogs, and overwhelming their search
results. This must change before they go public.<br>
<br>
</div>
I have been resisting this because whenever a $9 is used,
the only way to find the bib record is to be logged into a
library that already includes the $9. We cannot even find
the record when logged in at the consortium level. <br>
<br>
</div>
An example:<br>
</div>
AU already has an ebook which they purchased years ago as part
of a Netlibrary package, that ATS now wants to purchase. Their
bib record has an 856 tag with the $9AU. I log in at the
consortium level, search for the title, and find nothing. I log
in at my local branch level and find nothing. So I import a
duplicate bib record. Not good. I should just be adding a second
856 tag, and I sure don't want to accidentally wipe out their
856 tag with an overlay. <br>
<div>
<div><br>
How are the rest of you handling this scenario? Is there a
setting that I am missing? Is this a bug? Surely it isn't a
feature. Making the title searchable at the consortium level
would solve our problem.<br>
<br>
</div>
<div>Thanks for your insights!<br>
<br>
</div>
<div>Don <br clear="all">
</div>
<div>
<div>
<div>
<div>
<div>
<div><br>
-- <br>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>Don Butterworth<br>
Collection Management Librarian /<br>
Faculty Associate<br>
B.L. Fisher Library<br>
Asbury Theological Seminary<br>
<a moz-do-not-send="true"
href="mailto:don.butterworth@asburyseminary.edu"
target="_blank">don.butterworth@asburyseminary.edu</a><br>
(859) 858-2227<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Evergreen-catalogers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
<a class="moz-txt-link-abbreviated" href="mailto:klussier@masslnc.org">klussier@masslnc.org</a>
Twitter: <a class="moz-txt-link-freetext" href="http://www.twitter.com/kmlussier">http://www.twitter.com/kmlussier</a></pre>
</body>
</html>