As I was writing my contact, it occurred to me that I think the changes
that were made were for the real time status update feature of OTS. I think
we still send an extract as well.
On Wed, Jun 7, 2023 at 1:34 PM Jessica Woolford
wrote:
> Hi Dan,
>
> Last year, we needed to disable OTS for all
Hi Dan,
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
Hi!
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
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
Heyo all,
Our collections group is looking to tweak our Novelist implementation to make
use of On The Shelf functionality, info here:
https://connect.ebsco.com/s/article/Setting-up-On-The-Shelf?language=en_US
There's a curious (if not perhaps a little rude) note at the bottom of the page
that
