<div dir="ltr"><div>Hi Dan,</div><div><br></div><div>Last year, we needed to disable OTS for all libraries using it temporarily because it was causing major issues with availability. However, at the beginning of the year, we were able to do some testing with EBSCO and they rolled out some changes to our implementation that seemed to resolve the issue. I had assumed this meant they would be able to make those changes for other Evergreen sites. I can check in with the individual we worked with there and see if those changes are widely available, and if the documentation can be updated if so.</div><div><br></div><div>Thanks,</div><div>Jessica<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 7, 2023 at 10:06 AM Kathy Lussier via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi!</div><div><br></div><div>I don't have answers to Dan's questions, but to add on to what Lindsay was saying, from the perspective of making Evergreen appealing to new libraries considering a system switch, I think it would be a worthwhile investment for the community to do whatever work is needed to remove notes like these from vendor web sites. There are so many benefits to using Evergreen, but this note could stop a library from even investigating Evergreen as an ILS.</div><div><br></div><div>Cheers!</div><div>Kathy</div><div><span class="gmail_signature_prefix">--</span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Kathy Lussier</div><div><a href="https://kmlussier.com/" target="_blank">https://kmlussier.com</a></div><div>26 days away from having an official reason to weigh in on Evergreen issues</div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 7, 2023 at 8:51 AM Lindsay Stratton via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I think we should be looking very seriously at Evergreen's APIs and improving the documentation, functionality, performance, etc. More vendors and services are moving to APIs, not just for holdings, but user and transaction data as well. Speaking personally, I run holdings uploads for Novelist and Syndetics (which also now offers API uploads but not for Evergreen) and would love to shift them over to an API method. We also use a discovery layer where user data conections needs some improvement. And we have libraries interested in analytics platforms that would also benefit hugely from API connections.<div><br></div><div>Lindsay</div><div><br clear="all"><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><b>Lindsay Stratton</b><div><b>Systems Librarian</b></div><div>Westchester Library System</div><div>570 Taxter Rd., 4th Floor</div><div>Elmsford, NY 10523</div><div><a href="mailto:lstratton@wlsmail.org" target="_blank">lstratton@wlsmail.org</a></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 6, 2023 at 6:15 PM Dan Moore via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<div lang="EN-US">
<div>
<p class="MsoNormal">Heyo all,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Our collections group is looking to tweak our Novelist implementation to make use of On The Shelf functionality, info here:
<a href="https://connect.ebsco.com/s/article/Setting-up-On-The-Shelf?language=en_US" target="_blank">
https://connect.ebsco.com/s/article/Setting-up-On-The-Shelf?language=en_US</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">There’s a curious (if not perhaps a little rude) note at the bottom of the page that states: “There is an Evergreen API that supports automatic harvesting of your collection. However, we were unable to obtain a complete harvest for any
customers during the testing of this functionality, as Evergreen’s Web Services API was not built for such a wide-scale application. We discourage Evergreen customers from utilizing this feature for collection harvesting.”
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Additionally, on their KB page for the feature (<a href="https://eis1.my.site.com/ebsco/s/article/ILS-Export-for-NoveList-Products-and-Features?language=en_US" target="_blank">https://eis1.my.site.com/ebsco/s/article/ILS-Export-for-NoveList-Products-and-Features?language=en_US</a>),
we can see some handy older screenshots of what I presume to be the old non-browser client. Combining that with the statement above about “during the testing of this functionality,” I’m presuming this was tested with EBSCO/Novelist at some point but that there
hasn’t been an update to it since the browser client rolled out. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">There’s a slew of questions about this in my mind… the first being if what’s written here is accurate about the Evergreen API method of harvesting collection information not being robust enough (which generates an immediate follow up –
what would make it robust enough?). But I’m also curious about the collective wisdom of the community about these strategies. We’re moving toward a Lean-based purchasing model wherein selectors will have a daily cap of titles to order so as not to create a
wave for shipping/receiving folks to drudge through later. Real-time availability of holdings information would be a huge boon in supporting both Lean purchasing strategies AND maximizing Novelists’ effectiveness for reader’s advisory. However, if uploading
holdings records is just the best way of doing it due to the performance of the API as-is or the time/money needed to extend it, then we’ll go that route instead – whatever delivers the best, most accurate information to patrons.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thoughts? <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">All the best, <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="background:white none repeat scroll 0% 0%"><span style="color:black">Dan Moore<u></u><u></u></span></p>
<p class="MsoNormal" style="background:white none repeat scroll 0% 0%"><span style="color:black">Integrated Library System Administrator<u></u><u></u></span></p>
<p class="MsoNormal" style="background:white none repeat scroll 0% 0%"><span style="color:black">King County Library System<u></u><u></u></span></p>
<p class="MsoNormal" style="background:white none repeat scroll 0% 0%"><span style="color:black">Service Center, Issaquah<u></u><u></u></span></p>
<p class="MsoNormal" style="background:white none repeat scroll 0% 0%"><span style="color:black">(425) 369-3413<u></u><u></u></span></p>
<p class="MsoNormal" style="background:white none repeat scroll 0% 0%"><span style="color:black"><a href="mailto:dtmoore@kcls.org" target="_blank"><span style="color:blue;border:1pt none windowtext;padding:0in">dtmoore@kcls.org</span></a><u></u><u></u></span></p>
<p class="MsoNormal" style="background:white none repeat scroll 0% 0%"><span style="color:black"><a href="https://kcls.org/" target="_blank"><span style="color:black;text-decoration:none"><img style="width: 0.5104in; height: 1.0104in;" id="m_-5818541141936426428m_-7080629593643489925m_7537916347498961808Picture_x0020_1" src="cid:18895df35634ce8e91" width="49" height="97" border="0"></span></a></span><span style="color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p></p>
<hr>
<span style="padding:0px;margin:0px;font-family:Calibri,sans-serif;font-size:13px;color:rgb(90,90,90)">King County Library System is subject to the Washington State Public Records Act (RCW 42.56). Senders and receivers of KCLS email should presume
that this email and any attachments are subject to public release upon request and to state record retention requirements, unless otherwise exempted.</span>
<hr>
<p></p>
</div>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</div></blockquote></div>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</blockquote></div>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Jessica Woolford<div>Evergreen Systems Manager<br></div><div>Bibliomation, Inc.</div><div>24 Wooster Ave.</div><div>Waterbury, CT 06708</div><div>203-577-4070 ext. 105</div></div></div></div></div></div></div></div></div>