Welcome to the list Marc!


I don't know whether an Evergreen site has yet done this, but FWIW, another approach is to sign up for OCLC's WorldCat Local (to be rebranded WorldCat Discovery) service. Among the (apparently less-known) features included is web-scale discovery. OCLC makes its records discoverable via Google and other search services. These in turn -- via WCL -- are linked in real-time to availability information in subscribers' ILSes.

That might be true, but I'm perplexed as to why a library would pay for this discoverability through WorldCat Local when they already get it out of the box with Evergreen?

Of course, there might be other reasons for signing up for WorldCat Local, but I think the work Dan has done has put Evergreen, Koha, and VuFind ahead of the pack in this area.

Kathy

On 04/09/2015 09:15 AM, Marc Truitt wrote:
On 2015-04-09 1005, Ben Shum wrote:
That all said, I suppose one potential "danger" of having bots freely
scan over your site is that if they get too busy with indexing your
site's contents, they can overwhelm and cause interruptions in your
ability to use Evergreen.  This happened to us at least once before,
where some indexer in China scanned our whole catalog and tried to
index every page causing us to run out of system resources trying to
serve up all the content it was requesting.

Disclaimer: I'm a lurker who is very interested in and hopeful for Evergreen's success. Our site currently uses a proprietary ILS.

I don't know whether an Evergreen site has yet done this, but FWIW, another approach is to sign up for OCLC's WorldCat Local (to be rebranded WorldCat Discovery) service. Among the (apparently less-known) features included is web-scale discovery. OCLC makes its records discoverable via Google and other search services. These in turn -- via WCL -- are linked in real-time to availability information in subscribers' ILSes.

cheers,

- mt


--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
kluss...@masslnc.org
Twitter: http://www.twitter.com/kmlussier

Reply via email to