The document discusses open source software (OSS) solutions used by libraries, including Koha, Evergreen, and Drupal. It summarizes Bibliotheque's involvement with Koha in France, including their growth as a vendor providing Koha support and services. It also briefly introduces Evergreen integrated library system and Drupal projects like SOPAC that integrate a library catalog with Drupal. The document advocates an approach using Drupal and Lucene/Solr to build a flexible catalog system.

1. The stuff we do with OSS in libraries Nicolas Morin [email_address]

3. Koha: why was it a success in France so far?

4. Evergreen: short intro

6. drupal/lucene/solr

7. BibLibre

9. Nicolas Morin as translator in 2003

11. Henri R. Maintainer version 3.0.x

16. x2 from 2008 to 2009

17. We're growing as slowly as possible

19. Evergreen

20. Drupal

21. On-demand development / Consulting

22. Why was Koha a success in France?

24. 2003 : 1 st (small) libraries in France

25. 2006 : 1 st (bigger) public library in France (170.000 records) -> Mover&Shaker

26. 2008 : 1 st (bigger) university library in France (800.000 records)

29. vendor acquired by competitor

30. Feeling among libraries that products didn't really take on the web before it was too late

31. maintenance fees universally percieved as excessive and not providing value-for-money

33. Management issue : buy maintenance, cover your ass

35. Libraries tend to do OSS themselves when a commercial solution doesn't exist

37. users of Koha

38. people merely interested in Koha => not a one-to-one relationship between library and vendor

40. On the web, tools age very quickly -> requires a lot of Human ressources that libraries don't necessarily have -> OSS adapts well to this new situation : we don't sell a tool, we sell services

42. A lot of lightweight companies (little overhead costs)

43. We don't have bad habits nor VCs behind us and are often militants of OSS

44. vendors lower their prices in reaction

46. BibLibre runs mailing lists

47. BibLibre runs koha-fr.org (french community site)

48. BibLibre sponsors Nicole's work on documentation => Or : if you want to harness the power of the community, you have to give back

50. open source IT projects : +75% from 2007

51. « les temps demeurent cependant difficiles pour les petites et moyennes sociétés du secteur et pour quelques rares grandes entreprises qui n’arrivent pas à faire face au développement des logiciels libres. » Marc Maisonneuve, Tosca, March 2009 (in LH 767)

52. Evergreen

53. Evergreen Oct. 2009 : agreement to provide support for Evergreen and help Evergreen grow in Europe

56. 14+ million circs

57. statewide resource-sharing network => Designed to be robust and scalable => http://open-ils.org/

59. Marc21 Holdings records (serials)

60. Clustering options (load balancing, failover, etc.)

62. Serials

63. More language sets

64. Evergreen Evergreen Academic or PL consortia August 1, 2009 December 31, 2009 Conifer 4 4 Evergreen Indiana 38 52 Michigan Evergreen 9 11 NTLC 13 PINES 51 51 SC LENDS 3 10 SITKA 18 30 Spruce 1 1 Tsuga 1 1 (Independent) 4 5 Totals 129 178

65. Evergreen opac

66. Evergreen staff search

67. Evergreen staff circ

68. Drupal related stuff

70. MySQL/PHP

71. Highly Modular & flexible / slightly complex

72. Good separation data / workflows / presentation -> it's a CMS and a development framework

73. Drupal

74. Drupal

75. Drupal

77. #1 perfect graphical integration between the catalog UI and the library's Drupal web site

79. reviews

80. ratings

82. Sopac

83. Sopac

86. Web pages and biblio cannot share tags/comments/stars, etc.

87. 2 search forms (sopac + drupal)

88. Display hardcoded in sopac (doesn't take advantage of drupal code – views anyone?)

89. Doesn't interact with cool drupal modules like RDF, RSS, etc.

93. Each record a web page (CCK fields)

94. Uses drupal modules (stars, comments, etc)

96. Drupal dependant ( eh, we like this, actually; is that a negative? )

98. Suggestions (did you mean...?)

99. Facets

100. Work on « Drupac »

102. Suggestions (did you mean...?)

103. Facets

104. Field weighting

105. Work on « Drupac »

107. Suggestions (did you mean...?)

108. Facets

109. Field weighting

110. Index definition

111. Work on « Drupac »

113. Suggestions (did you mean...?)

114. Facets

115. Field weighting

117. Work on « Drupac »

118. « Drupac »

120. Can scale

121. Code quality and maintainability + : reuse of Lucene / solr /drupal code

123. Use as is -> custom stuff

124. Fairly usual (ILS) -> advanced stuff (lucene/solr)

125. Thanks for listening. Questions? Objections? Remarks? Contributions? [email_address]