Evergreen ILS

Open Source Library Software

Downloads

Download files, Git repositories, installation instructions...

Downloads →

Documentation

Official documentation, community wiki, and other resources...

Documentation →

Get Involved

Events, mailing lists, IRC, and more. Join our community!

Community →

Evergreen 1.2.0

It’s amazing the emphasis folks put on public-facing software version numbers, and I used to think such things were mostly hype and marketing. However, we’ve been sitting on 1.2 (just released yesterday!) for longer than we would with a normal release, and we already have enough new things in the mainline trunk to cut a 1.2.2, and indeed there are a few tweaks and fixes that I feel compelled to check into the rel_1_2 branch for a future 1.2.x. So what is so special about 1.2? Well, there are some new features and architectural improvements, but more important is the list of contributors.

Evergreen 1.2 is the first Evergreen release that has received substantial contributions (patches, documentation, feedback, suggestions, testing, etc.) from folks affiliated with neither the Georgia Public Library Service nor Equinox Software.

So as a milestone, 1.2 is really significant because it is truly a community release. Thanks folks!

The next major milestone is 1.4, with which we can expect full internationalization, again, courtesy of the community.

— Jason

Acquiring Acquisitions, from You

Hi folks, this is a solicitation. We need your help. 🙂

We started acquisitions and serials development with a series of focus groups throughout the state of Georgia, and received a lot of useful input, insight, and suggestions from public librarians, academic librarians, and book vendors for what is needed in such a system.

We have what we believe is a useful framework for this, and some notions on how to further build on it, but what we’d like now is more end-to-end descriptions of your current (or ideal) acquisitions process, as well as your patterns for serials prediction, to rub off any rough edges we might have in our minds. And of course, we’d like this information in vendor-neutral language, so as to not to step on the toes, trademarks, or trade secrets of other library automation vendors. 😀

Here are two examples from the public OPEN-ILS-DEV mailing list, courtesy of Dan Scott: here and here.

And here are two examples of serials patterns on the development wiki.

Even if you don’t have the time to write up entries like these, if you could even comment on the ones we have (and the ones we get), it would really help us out.

Thanks!

Subscription and archive information for OPEN-ILS-DEV is here.

Write-access to the wiki is available on request (either to OPEN-ILS-DEV or to feedback@open-ils.org).

Or feel free to leave comments on this blog entry (and let us know through feedback@open-ils.org if you have any trouble with its anti-spam measures).

Thanks again!

— Jason

Meet the new Dan, same as the old Dan

Originally posted to the open-ils-dev and open-ils-general mailing lists.

Part of growing (as a software project, individually as developers, and generally in life) is to open up to others, to let others in, to be willing to allow others to explore and criticize and help. Even in the open source world that’s harder than it would seem, and only made more difficult when your “baby” is a 200k lines-of-code 3 year old (counting, and I do, the 2 year gestation period).
All that said, I’m overjoyed to announce that Dan Scott, a long time contributor of both patches and ideas, has accepted the offer of the core team to become a committer on the Evergreen project. It’s a milestone for the project, and Dan’s enthusiasm is, to me, a welcome sign that we’re on the right track.

I first met Dan in person at the Windsor University Future of the ILS Symposium where he needled me about non-English collation support and interface translation. Since then he’s been leading the charge for proper I18N, including providing a French-Canadian DTD for the OPAC and Staff Client. He’s also been producing VMWare images of running Evergreen development installations for quite some time, and providing installation support, patches and feedback.

Now I get to step out of his way (being the patch wrangler) and let him work his magic directly. It’s a nice feeling.

I’d like to note, too, that thanks is due to Laurentian University. Laurentian has been supportive of Dan’s efforts with Evergreen, funding his travel for the AcqFest, and enabling him to spend some of his office hours on Evergreen development.

Thanks, Dan, and welcome to the team … again!