Stuff we do with OSS in libraries (Bergen, 2009)
Download as ODP, PDF1 like1,574 views
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.
![The stuff we do with OSS in libraries Nicolas Morin [email_address]](https://image.slidesharecdn.com/2009bergen-091112060912-phpapp02/85/Stuff-we-do-with-OSS-in-libraries-Bergen-2009-1-320.jpg)
Stuff we do with OSS in libraries (Bergen, 2009)
- 1. The stuff we do with OSS in libraries Nicolas Morin [email_address]
- 3. Koha: why was it a success in France so far?
- 7. BibLibre
- 8. BibLibre history Early involvement in Koha Paul Poulain in 2002
- 9. Nicolas Morin as translator in 2003
- 10. Henri-Damien Laurent as developer in 2005 Paul Poulain R. Manager versions 2.x
- 11. Henri R. Maintainer version 3.0.x
- 12. BibLibre now Incorporated oct. 2007
- 13. Headcount now 10: 3 librarians
- 14. 7 developers Business in 6 countries in 2009
- 15. Turnover : x2 from 2007 to 2008
- 16. x2 from 2008 to 2009
- 17. We're growing as slowly as possible
- 18. What we do We're not a « koha vendor », we provide services for libraries with Open Source : Koha
- 19. Evergreen
- 20. Drupal
- 21. On-demand development / Consulting
- 22. Why was Koha a success in France?
- 23. Koha (in France) 2002 : Internationalisation and norms ( Uni marc)
- 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)
- 27. Why is Koha a success in France? Koha's a good product, and now mature
- 28. proprietary vendors « misbehaving »: ILS stops
- 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
- 32. Why is Koha a success in France? We created a vendor! Without a vendor, OSS in libraries stays on the outskirts
- 33. Management issue : buy maintenance, cover your ass
- 34. Tech issues : Level of IT to become an expert on any given ILS is too big
- 35. Libraries tend to do OSS themselves when a commercial solution doesn't exist
- 36. Why is Koha a success in France? a few militant libraries are pushing for an alternative relationship between libraries and vendors -> kohala: French not-for-profit includes: developpers of Koha
- 37. users of Koha
- 38. people merely interested in Koha => not a one-to-one relationship between library and vendor
- 39. Why is Koha a success in France? general evolution from IT as a set of tools to IT as a service A lot of the data is outside the library (Google, Elsevier, etc...)
- 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
- 41. Why is Koha a success in France? Koha tends to bring the price down : Cost of development shared
- 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
- 45. Why is Koha a success in France? We do a lot of Community Work H-D. Laurent (BibLibre): R. Maintainer 3.0
- 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
- 49. Why is Koha a success in France? Market for IT in Libraries in France in 2008 : Down -7% at 42 m€
- 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
- 54. Evergreen Dev. Started 2004
- 55. li ve Sept. 2006 (PINES): 40+ PL systems, 250+ outlets
- 57. statewide resource-sharing network => Designed to be robust and scalable => http://open-ils.org/
- 58. Evergreen notable features R ich, highly flexible policy control
- 59. Marc21 Holdings records (serials)
- 60. Clustering options (load balancing, failover, etc.)
- 61. Release 2.0 (2010) Acquisitions Second Release (including EDI support)
- 62. Serials
- 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
- 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
- 76. SOPAC - What does it try to achieve? http://thesocialopac.net
- 77. #1 perfect graphical integration between the catalog UI and the library's Drupal web site
- 78. #2 add « social » functionalities to the OPAC: tags
- 79. reviews
- 80. ratings
- 81. rss #3: pools social data together (remote server - Insurge) => SOPAC replaces and enhances your OPAC
- 82. Sopac
- 83. Sopac
- 84. Limits of Sopac Sopac perfect when used as is but...
- 85. Not fully integrated with Drupal Ratings / comments coded in 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.
- 90. Limits of Sopac (2) Search engine (sphinx) Facets are hardcoded
- 91. Some functionalities missing (« more like this ») Items and subjects managed within biblio => not integrated in Drupal vs Drupal dependent
- 92. Work on « Drupac » Positives Lucene / solr (see blacklight, VuFind, etc...)
- 93. Each record a web page (CCK fields)
- 94. Uses drupal modules (stars, comments, etc)
- 95. Uses drupal Views to create different views of records Negatives sharing of social aspects (Insurge) lost for the time being ( wasn't used yet in Sopac )
- 96. Drupal dependant ( eh, we like this, actually; is that a negative? )
- 97. Work on « Drupac » Lucene/solr Spellchecker
- 98. Suggestions (did you mean...?)
- 99. Facets
- 100. Work on « Drupac »
- 101. Work on « Drupac » Lucene/solr Spellchecker
- 102. Suggestions (did you mean...?)
- 103. Facets
- 104. Field weighting
- 105. Work on « Drupac »
- 106. Work on « Drupac » Lucene/solr Spellchecker
- 107. Suggestions (did you mean...?)
- 108. Facets
- 109. Field weighting
- 110. Index definition
- 111. Work on « Drupac »
- 112. Work on « Drupac » Lucene/solr Spellchecker
- 113. Suggestions (did you mean...?)
- 114. Facets
- 115. Field weighting
- 116. Index definition Drupal Views
- 117. Work on « Drupac »
- 118. « Drupac »
- 119. « Drupac » Very flexible
- 120. Can scale
- 121. Code quality and maintainability + : reuse of Lucene / solr /drupal code
- 122. Conclusion OS solutions for libraries : Small libraries -> big libraries
- 123. Use as is -> custom stuff
- 124. Fairly usual (ILS) -> advanced stuff (lucene/solr)
- 125. Thanks for listening. Questions? Objections? Remarks? Contributions? [email_address]