On Thu, Dec 26, 2013 at 1:25 PM, Lazar, Alexey Vladimirovich < [email protected]> wrote:
> On 2013-12-20, at 13:32 , Erica Rohlfs <[email protected]> wrote: > > > Happy Holidays! > > > > I would like to begin updating the Roster of Evergreen Libraries on the > Evergreen Wiki. It’s been on my to-do list for a few months now. My hope is > to have it updated in time to, hopefully, help whoever volunteers to work > on the Evergreen map. > > Happy holidays to you too, Erica. > > Thanks for taking up the work on this page. I just went in an updated our > entries with newer Evergreen versions. > > Looking at the list, it seems like an awful lot of Evergreen libraries out > there run on version 1.6, or 2.0 and various old OS and PostgreSQL > versions. I think these are just outdated entries (I hope). > > Question: how important is it to have all the extra info, like Evergreen > versions, OS, databases, etc, on this particular page? It is interesting > information, but if it is not kept current, it is not very useful — just > noise. > > If we opt to keep Evergreen version information, we could keep that relatively current by running the scripted equivalent of "curl -d service=open-ils.search -d locale=en-US -d method=opensrf.open-ils.system.ils_version http://laurentian.concat.ca/osrf-gateway-v1"; against each public Evergreen catalogue. Anything that we can't automate will, I fear, fall out of date. But given the public catalogue URL for each library, we can at the very least automatically gather a) whether the public catalogue is still responding at the listed URL and b) the Evergreen version. Maybe c) the server OS (based on the Apache headers). And that much, I think, would be a win.
