1. Developing a crush on Evergreen Dan Scott, Laurentian University October 9, 2009

2. My relationship to Evergreen

3. About Conifer...

4. Evergreen and Conifer ca. 2007

5. Cautionary tales (#1) If you want to get things done, you need to commit resources to the tasks

6. Cautionary tales (#2) Giving your primary developer the additional role of project manager, on top of full-time librarianship responsibilities, might not give you the results you desire

7. Evergreen and Conifer ca. 2008

8. How academics learn

9. Evergreen and Conifer ca. 2009 In production as of May 2009! 2 million bib records, 2.5 million copies 40,000 users

10. Conifer hardware Polaris DB (Master ) Galaxy DB (Slave) Starburst (syslog / onsite backup) dwarf (off-site backup) comet (web / apps) Test & development darkmatt er (DB) Protostar (*) “Brick” (Web, apps, ejabber) Carbon (*) neutron (memcac hed) If we add a second brick, neutron becomes a standalone memcached server Replica for reports and disaster recovery SL B Web

11. Cautionary tales (#3) Nobody likes a prenuptial agreement... until things get messy

12. Cautionary tales (#4) Free software is never gratis, and not necessarily cheap.

13. Cautionary tales (#5) Budgets change – and they don't often grow. Your plans may have to change accordingly.

14. Reservations about reserves

15. Cautionary tales (#6) Loosely coupled means loosely coupled, and that's not always good OLE, OCLC, take note!

16. What hath Conifer wrought Internationalization support Migration scripts, customized skins, discussions Localized URIs* Basic serials display and editing Reserves module** Lots of input on how acquisitions works in Canadian academic institutions Z39.50 server maturity*** Early testing (and fixing) of the 1.6 release

17. Serials in Evergreen 1.6

18. Serials, in full MFHD glory

19. Challenges at the academic level Circulation rules Set date/time instead of just interval Override time as well as date Interlibrary loan Integration of incoming ILL items Z39.50 server needs finer-grained indices Z39.50 server has some i18n holes

20. Challenges at the academic level OPAC - refined metadata display in templates Reporting – no default set of report templates Adjustment in general to user-friendly search Controlled process to roll out updates

21. Downtime

22. Problems, features, and docs

23. Canada: a nation of Evergreen early adopters David Fiander, UWO (SIP & MFHD developer) BC Sitka (second live system) UPEI (first academic library) Innisfil Township, Ontario (first known self-hosted public library) Conifer (first academic library consortium) Natural Resources Canada Manitoba SPRUCE (public library consortium) Mohawk College, Hamilton, Ontario

24. Measuring project health Number of committers & affiliation Number of submitted patches DocumentationTesting Community and commercial support Current releases & release history

25. Good things to come A maturing community

26. Measuring community: email Statistics courtesy

27. Measuring community: commits Statistics courtesy

28. WANTED: skilled developers!

29. Building an on-ramp for developers

30. Communicate, communicate, communicate

31. Rethinking the release process

32. Better living through automation

33. I look forward to tests

34. Shorter release cycles

35. Documentation

36. A solid foundation

37. Please bear with us...

38. http://www.flickr.com/photos/davidw/2132684141 /

39. http://www.flickr.com/photos/tronics/380379732 /

40. http://www.flickr.com/photos/julien_harneis/3027936866/

41. http://www.flickr.com/photos/33619843@N08/3125532414 /

42. http://commons.wikimedia.org/wiki/File:Hydropwer_Pipeline_McKenzie_Country.jp g

43. More information Evergreen home: http://evergreen-ils.org http://evergreen-ils.org Blog aggregator: http://planet.evergreen-ils.org http://planet.evergreen-ils.org Mailing lists: http://evergreen-ils.org/listserv.php http://evergreen-ils.org/listserv.php IRC: #evergreen on chat.freenode.net