1 / 25

Wageningen Library content Management System

Wageningen Library content Management System. Peter van Boheemen 32nd ELAG Library Systems Seminar 14 April 2008, Wageningen. Wageningen Library CMS. Wageningen Digital Library history Why build a Library Content Management System? Architecture Examples of applications

urielle-horton
Download Presentation

Wageningen Library content Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wageningen Library content Management System Peter van Boheemen 32nd ELAG Library Systems Seminar 14 April 2008, Wageningen

  2. Wageningen Library CMS • Wageningen Digital Library history • Why build a Library Content Management System? • Architecture • Examples of applications • What have we gained ? • Pro’s and Con’s?

  3. 1873 - 1980

  4. 1980 - 1994

  5. 1999

  6. 2003

  7. 2007

  8. Contents of the Digital Library • Catalogue • Institutional Repository • 6 in-house bibliographic databases • >200 external bibliographic databases • >10,000 electronic journals • >35,000 electronic books and reports • >600,000 hard copy books and journals

  9. Why build a Library Content Management System? • An ILS is insufficient, you need extra applications • The concept of an ILS is outdated. • We want a component based architecture • Buy existing components (SFX, MetaLib, Collexis) • Create missing components • Use Open Source tools (LibXML, Perl, PHP, MediaWiki, Subversion,…)

  10. Architecture XML DB Oracle Minisis xquery XML schema connector connector WebQuery xforms Search and Retrieval – SRU like post & get XSLT (server side) Update via structured HTML forms Applications

  11. Applications • WebOPAC on a variety of bibliographies • Cataloguing module • Order administration • Serials administration • Java circulation applet • NCIP interface • Z39.50 interface • OAI-PMH interface • Inter Library Loan / Online ordering system • Subject portals • General forms handling • News database • Comment database • Course libraries • ….

  12. It is all URL’s http://library.wur.nl/WebQuery/ • patron/xml/26310 • patron/renew/26310 • subscription/xml?supplier-isn=8000 • subscription/subscription.csv?supplier-isn=8000 • catalog/xml?classification/@cd=2007-11-21T*,2007-11-20T*,2007-11-19T* • catalog/rss

  13. One collection of bibliographic descriptions • Books, articles, chapters, serials, web pages, all bibliographic descriptions in XML in one collection • Library catalogue is just a view on this collection • Not completely true. The Wageningen repository containing publications of Wageningse UR form a separate collection for historical reasons, but we are going to get rid of that separation soon.

  14. Catalogue, a ‘view’ on the collection

  15. Same record, different view

  16. Many bibliographic views

  17. Subject oriented portals

  18. Other features of the LCMS

  19. Integration internally: extending the SFX knowledgebase

  20. Integration with others: order administration

  21. Pro’s • Complete standardisation on XML: well suited for a Service Oriented Architecture • Generic tools. With a decent knowledge of XSLT you can build most of the applications. • Fast development and deployment • Avoiding vendor lock-in • Lot’s of control

  22. Con’s • You will have to employ software developers • You will always have to defend your decision • Keeping IT staff is important • Maybe these are all pro’s ?

  23. Thank you for your attention

More Related