Your SlideShare is downloading. ×
0
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Session 5 - SOPAC: Further Separateing Front Office and Back Office Application
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Session 5 - SOPAC: Further Separateing Front Office and Back Office Application

783

Published on

This session will focus on how a tool developed in a few weeks for a single library in New Zealand has become an award winning ILS, developed worldwide, used by more than 1000 libraries, and supported …

This session will focus on how a tool developed in a few weeks for a single library in New Zealand has become an award winning ILS, developed worldwide, used by more than 1000 libraries, and supported by many OSS companies. Paul Poulain has been involved in free software since 1998 and the Koha project since early 2002. He has been Release Manager for Koha 2.0 and 2.2, and remains a major contributor. Paul co-founded BibLibre in 2007 to provide high level support, training, migration on Open Source software for libraries (Koha and Drupal)

Published in: Technology, Education
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
783
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SOPAC : connecting Drupal and Koha Breaking the barriers, April 2009 Paul Poulain [email_address]
  • 2. BibLibre <ul><li>we provide support for OSS in libraries </li></ul><ul><li>we develop & provide support for the OSS ILS KOHA (since 2002) </li></ul><ul><li>we provide support for the OSS CMS DRUPAL (just started) </li></ul><ul><li>=> SOPAC is a set of tools that connects your ILS (Millenium initially) with a Drupal site </li></ul>
  • 3. Small project : objectives <ul><li>providing the SOPAC connector for Koha </li></ul><ul><li>on Koha : creating the set of WS required to make SOPAC work </li></ul>
  • 4. SOPAC is the work of the ubiquitous John Blyberg. What is the Social OPAC (SOPAC)? <ul><li>http://aadl.org </li></ul><ul><li>http://www.darienlibrary.org </li></ul><ul><li>http://thesocialopac.net </li></ul><ul><li>http://www.blyberg.net/ </li></ul>http://www.flickr.com/photos/trucolorsfly/
  • 5. What does SOPAC try to achieve? <ul><li>#1 perfect graphical integration between the catalog UI and the library's Drupal web site </li></ul><ul><li>#2 add « social » functionalities to the OPAC: </li></ul><ul><ul><li>tags </li></ul></ul><ul><ul><li>reviews </li></ul></ul><ul><ul><li>ratings </li></ul></ul><ul><ul><li>rss </li></ul></ul><ul><li>=> SOPAC replaces and enhances your OPAC </li></ul>
  • 6. What it looks like at Darien
  • 7. What it looks like at Darien
  • 8. Patron creates account
  • 9. What it looks like at Darien
  • 10. How does it work? <ul><li>SOPAC harvests the records from the ILS through a connector </li></ul><ul><li>reindexes them in a separate engine </li></ul><ul><li>provides a new UI in Drupal for searching & actions (tags, holds...) </li></ul><ul><li>requires real time connectors for : </li></ul><ul><ul><li>Some informations such as item availability </li></ul></ul><ul><ul><li>Some actions such as placing a hold </li></ul></ul>
  • 11. SOPAC Architecture ILS ws ILS connector MySQL LOCUM sphinx SOPAC (php + add. Tables to Drupal's MySQL) Independent Social Repository Drupal UI INSURGE
  • 12. The Koha Connector <ul><li>we used the ILS Discovery Interfaces recommandation as a set of guidelines to develop KOHA WS </li></ul><ul><li>-> http://diglib.org/architectures/ilsdi/ </li></ul><ul><li>It provides for : </li></ul><ul><ul><li>harvesting of records : done through OAI-PMH server </li></ul></ul>
  • 13. The Koha Connector <ul><li>we used the ILS Discovery Interfaces recommandation as a set of guidelines to develop KOHA WS </li></ul><ul><li>-> http://diglib.org/architectures/ilsdi/ </li></ul><ul><li>It provides for : </li></ul><ul><ul><li>real-time search : not used by Sopac </li></ul></ul>
  • 14. The Koha Connector <ul><li>we used the ILS Discovery Interfaces recommandation as a set of guidelines to develop KOHA WS </li></ul><ul><li>-> http://diglib.org/architectures/ilsdi/ </li></ul><ul><li>It provides for : </li></ul><ul><ul><li>delivery (holds, availibility, etc) : done through new API in Koha </li></ul></ul>
  • 15. The Koha Connector <ul><li>we used the ILS Discovery Interfaces recommandation as a set of guidelines to develop KOHA WS </li></ul><ul><li>-> http://diglib.org/architectures/ilsdi/ </li></ul><ul><li>It provides for : </li></ul><ul><ul><li>patron information : done through new API </li></ul></ul>
  • 16. Issues with the connector <ul><li>Locum expects certain things, ILS-DI recommends something else </li></ul><ul><ul><li>locum uses patron barcode </li></ul></ul><ul><ul><li>ils-di expects not a barcode, but a user_id </li></ul></ul><ul><li>-> way around : translate barcode into user_id on the fly : performance issues. </li></ul><ul><li>-> way forward : sopac uses user_id </li></ul>
  • 17. Issues with ils-di <ul><li>ILS-DI often recommends SIP or NCIP as a way to provide WS. It doesn't work: </li></ul><ul><ul><li>many of the stuff we want doesn't exist in SIP </li></ul></ul><ul><ul><li>SIP is not really extendable </li></ul></ul><ul><ul><li>if you're going to have to do new WS, why bother with SIP at all : you'd rather have a homogenous set of APIs. </li></ul></ul>
  • 18. Issues with ils-di <ul><li>ILS-DI doesn't say much about the expected quality of the response. </li></ul><ul><li>-> adoption of ILS-DI will probably take time </li></ul><ul><li>-> compliance will mean different things </li></ul>
  • 19. Issues with SOPAC <ul><li>a lot of stuff is hardcoded : MARC21 in harvesting function (scrape_bib); item types, question to link accounts, locum configuration... </li></ul><ul><li>patron has 2 accounts : sopac / ils -> cries out for some sort of ldap solution... </li></ul>
  • 20. Issues with SOPAC <ul><li>if you replace your OPAC, you have to have at least the functionalities that your opac provides. For Koha, issues with : </li></ul><ul><ul><li>patron's account editing (phone, etc.) </li></ul></ul><ul><ul><li>record level holds </li></ul></ul><ul><ul><li>zotero (COinS) integration </li></ul></ul><ul><ul><li>... </li></ul></ul><ul><li>-> SOPAC needs time to mature </li></ul>
  • 21. general questions raised Sopac hints at erasing the limit between local data and outside data (Insurge): Independent Social Repository INSURGE <ul><ul><li>we need volumes of data for social functionalities </li></ul></ul><ul><ul><li>maybe we need volumes of data for searching too, even in small libraries (OCLC Grid Services; GBS...) </li></ul></ul>
  • 22. general questions raised <ul><li>Sopac knows very little about the user : </li></ul><ul><li>can one do social stuff without informations about who the persons are? </li></ul><ul><li>Shouldn't a result be relevant to someone? </li></ul><ul><li>-> we have to know what the students want </li></ul><ul><li>-> we also have to know who they are : </li></ul><ul><li>- major in computer science </li></ul><ul><li>- minor in philosophy </li></ul><ul><li>- has courses in building A, next to library B on thursdays </li></ul>
  • 23. general questions raised <ul><li>Sopac separates backoffice from UI, but we could go one step further and better separate searching tools and visualization -> every single result is displayed the same, but should not : </li></ul><ul><ul><li>display #1 when result set <10, display#2 when result > 1.000, etc... </li></ul></ul><ul><ul><li>display #1 when search limited to DVD, display #2 when search limited to ebooks, etc... </li></ul></ul><ul><li>=> we need proper visualization strategies </li></ul>
  • 24. what we learned <ul><li>we made the sopac connector for Koha : for some libraries, the integration in Drupal will make a lot of sense with SOPAC as is </li></ul><ul><li>we developed a 1st, tentative implementation of ILS-DI in Koha : ++ </li></ul><ul><li>NextGen Catalog tools need more work : </li></ul><ul><ul><li>User data </li></ul></ul><ul><ul><li>Visualization </li></ul></ul><ul><li>We have a feeling that they're transition tools... </li></ul>
  • 25. Thank you for you attention Questions? Comments? Paul Poulain [email_address]

×