Stuff we do with OSS in libraries (Bergen, 2009)

1,853 views
1,754 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,853
On SlideShare
0
From Embeds
0
Number of Embeds
131
Actions
Shares
0
Downloads
21
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Stuff we do with OSS in libraries (Bergen, 2009)

  1. 1. The stuff we do with OSS in libraries Nicolas Morin [email_address]
  2. 2. Program <ul><li>BibLibre
  3. 3. Koha: why was it a success in France so far?
  4. 4. Evergreen: short intro
  5. 5. Drupal: </li><ul><li>drupal/sopac
  6. 6. drupal/lucene/solr </li></ul></ul>
  7. 7. BibLibre
  8. 8. BibLibre history <ul><li>Early involvement in Koha </li><ul><li>Paul Poulain in 2002
  9. 9. Nicolas Morin as translator in 2003
  10. 10. Henri-Damien Laurent as developer in 2005 </li></ul><li>Paul Poulain R. Manager versions 2.x
  11. 11. Henri R. Maintainer version 3.0.x </li></ul>
  12. 12. BibLibre now <ul><li>Incorporated oct. 2007
  13. 13. Headcount now 10: </li><ul><li>3 librarians
  14. 14. 7 developers </li></ul><li>Business in 6 countries in 2009
  15. 15. Turnover : </li><ul><li>x2 from 2007 to 2008
  16. 16. x2 from 2008 to 2009
  17. 17. We're growing as slowly as possible </li></ul></ul>
  18. 18. What we do <ul>We're not a « koha vendor », we provide services for libraries with Open Source : <ul><li>Koha
  19. 19. Evergreen
  20. 20. Drupal
  21. 21. On-demand development / Consulting </li></ul></ul>
  22. 22. Why was Koha a success in France?
  23. 23. Koha (in France) <ul><li>2002 : Internationalisation and norms ( Uni marc)
  24. 24. 2003 : 1 st (small) libraries in France
  25. 25. 2006 : 1 st (bigger) public library in France (170.000 records) -> Mover&Shaker
  26. 26. 2008 : 1 st (bigger) university library in France (800.000 records) </li></ul>
  27. 27. Why is Koha a success in France? <ul><li>Koha's a good product, and now mature
  28. 28. proprietary vendors « misbehaving »: </li><ul><li>ILS stops
  29. 29. vendor acquired by competitor
  30. 30. Feeling among libraries that products didn't really take on the web before it was too late
  31. 31. maintenance fees universally percieved as excessive and not providing value-for-money </li></ul></ul>
  32. 32. Why is Koha a success in France? <ul><li>We created a vendor! </li><ul><li>Without a vendor, OSS in libraries stays on the outskirts
  33. 33. Management issue : buy maintenance, cover your ass
  34. 34. Tech issues : </li><ul><li>Level of IT to become an expert on any given ILS is too big
  35. 35. Libraries tend to do OSS themselves when a commercial solution doesn't exist </li></ul></ul></ul>
  36. 36. Why is Koha a success in France? <ul><li>a few militant libraries are pushing for an alternative relationship between libraries and vendors -> kohala: French not-for-profit includes: </li><ul><li>developpers of Koha
  37. 37. users of Koha
  38. 38. people merely interested in Koha </li></ul></ul>=> not a one-to-one relationship between library and vendor
  39. 39. Why is Koha a success in France? <ul><li>general evolution from IT as a set of tools to IT as a service </li><ul><li>A lot of the data is outside the library (Google, Elsevier, etc...)
  40. 40. On the web, tools age very quickly </li></ul></ul>-> 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. 41. Why is Koha a success in France? <ul><li>Koha tends to bring the price down : </li><ul><li>Cost of development shared
  42. 42. A lot of lightweight companies (little overhead costs)
  43. 43. We don't have bad habits nor VCs behind us and are often militants of OSS
  44. 44. vendors lower their prices in reaction </li></ul></ul>
  45. 45. Why is Koha a success in France? We do a lot of Community Work <ul><li>H-D. Laurent (BibLibre): R. Maintainer 3.0
  46. 46. BibLibre runs mailing lists
  47. 47. BibLibre runs koha-fr.org (french community site)
  48. 48. BibLibre sponsors Nicole's work on documentation </li></ul>=> Or : if you want to harness the power of the community, you have to give back
  49. 49. Why is Koha a success in France? <ul><li>Market for IT in Libraries in France in 2008 : </li><ul><li>Down -7% at 42 m€
  50. 50. open source IT projects : +75% from 2007
  51. 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) </li></ul></ul>
  52. 52. Evergreen
  53. 53. Evergreen Oct. 2009 : agreement to provide support for Evergreen and help Evergreen grow in Europe
  54. 54. Evergreen <ul><li>Dev. Started 2004
  55. 55. li ve Sept. 2006 (PINES): </li><ul><li>40+ PL systems, 250+ outlets
  56. 56. 14+ million circs
  57. 57. statewide resource-sharing network </li></ul></ul>=> Designed to be robust and scalable => http://open-ils.org/
  58. 58. Evergreen notable features <ul><li>R ich, highly flexible policy control
  59. 59. Marc21 Holdings records (serials)
  60. 60. Clustering options (load balancing, failover, etc.)
  61. 61. Release 2.0 (2010) </li><ul><li>Acquisitions Second Release (including EDI support)
  62. 62. Serials
  63. 63. More language sets </li></ul></ul>
  64. 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. 65. Evergreen opac
  66. 66. Evergreen staff search
  67. 67. Evergreen staff circ
  68. 68. Drupal related stuff
  69. 69. Drupal <ul><li>http://www.drupal.org
  70. 70. MySQL/PHP
  71. 71. Highly Modular & flexible / slightly complex
  72. 72. Good separation data / workflows / presentation </li></ul>-> it's a CMS and a development framework
  73. 73. Drupal
  74. 74. Drupal
  75. 75. Drupal
  76. 76. SOPAC - What does it try to achieve? <ul><li>http://thesocialopac.net
  77. 77. #1 perfect graphical integration between the catalog UI and the library's Drupal web site
  78. 78. #2 add « social » functionalities to the OPAC: </li><ul><li>tags
  79. 79. reviews
  80. 80. ratings
  81. 81. rss </li></ul><li>#3: pools social data together (remote server - Insurge) </li></ul>=> SOPAC replaces and enhances your OPAC
  82. 82. Sopac
  83. 83. Sopac
  84. 84. Limits of Sopac <ul><li>Sopac perfect when used as is but...
  85. 85. Not fully integrated with Drupal </li><ul><li>Ratings / comments coded in sopac
  86. 86. Web pages and biblio cannot share tags/comments/stars, etc.
  87. 87. 2 search forms (sopac + drupal)
  88. 88. Display hardcoded in sopac (doesn't take advantage of drupal code – views anyone?)
  89. 89. Doesn't interact with cool drupal modules like RDF, RSS, etc. </li></ul></ul>
  90. 90. Limits of Sopac (2) <ul><li>Search engine (sphinx) </li><ul><li>Facets are hardcoded
  91. 91. Some functionalities missing (« more like this ») </li></ul><li>Items and subjects managed within biblio </li></ul>=> not integrated in Drupal vs Drupal dependent
  92. 92. Work on « Drupac » <ul><li>Positives </li><ul><li>Lucene / solr (see blacklight, VuFind, etc...)
  93. 93. Each record a web page (CCK fields)
  94. 94. Uses drupal modules (stars, comments, etc)
  95. 95. Uses drupal Views to create different views of records </li></ul><li>Negatives </li><ul><ul><li>sharing of social aspects (Insurge) lost for the time being ( wasn't used yet in Sopac )
  96. 96. Drupal dependant ( eh, we like this, actually; is that a negative? ) </li></ul></ul></ul>
  97. 97. Work on « Drupac » <ul><li>Lucene/solr </li><ul><li>Spellchecker
  98. 98. Suggestions (did you mean...?)
  99. 99. Facets </li></ul></ul>
  100. 100. Work on « Drupac »
  101. 101. Work on « Drupac » <ul><li>Lucene/solr </li><ul><li>Spellchecker
  102. 102. Suggestions (did you mean...?)
  103. 103. Facets
  104. 104. Field weighting </li></ul></ul>
  105. 105. Work on « Drupac »
  106. 106. Work on « Drupac » <ul><li>Lucene/solr </li><ul><li>Spellchecker
  107. 107. Suggestions (did you mean...?)
  108. 108. Facets
  109. 109. Field weighting
  110. 110. Index definition </li></ul></ul>
  111. 111. Work on « Drupac »
  112. 112. Work on « Drupac » <ul><li>Lucene/solr </li><ul><li>Spellchecker
  113. 113. Suggestions (did you mean...?)
  114. 114. Facets
  115. 115. Field weighting
  116. 116. Index definition </li></ul><li>Drupal Views </li></ul>
  117. 117. Work on « Drupac »
  118. 118. « Drupac »
  119. 119. « Drupac » <ul><li>Very flexible
  120. 120. Can scale
  121. 121. Code quality and maintainability + : reuse of Lucene / solr /drupal code </li></ul>
  122. 122. Conclusion <ul><li>OS solutions for libraries : </li><ul><li>Small libraries -> big libraries
  123. 123. Use as is -> custom stuff
  124. 124. Fairly usual (ILS) -> advanced stuff (lucene/solr) </li></ul></ul>
  125. 125. Thanks for listening. Questions? Objections? Remarks? Contributions? [email_address]

×