OSCI - LIS

1. OSCI - LIS NEXT LIBRARY Workshop Ting – Open Source based Library Information System

2. Questions to be adressed • Why absolutely a new strategy for Integrated Library Systems ? • Can a SOA-based platform published in web perform satisfactory and support excellent userinterfaces • Can we designate the most important valuedrivers when it comes to establishing open platforms? • What will openness exactly means in library technology development?

3. Answers to be given • Alternating between short introductions and discussion

4. Why a new strategy? • Future needs for more flexible LIS solutions – with much higher grade of user-and library based selections among the total amount of services and content • Demands for better integration between ILS and digital world of content and service, as well as services from other platforms: SOA! • We ILS-vendors need to be kicked in …

5. SOA - web-based – only? • An integrated library platform 100% service based – all enduser functions and facilities available in a standard browser on their pc, a dedicated browser on their mobile, or a specialized interface on a big screen • All functions will be published through webservices, which gives the opportunity for libraries or partners to integrate THINGcomponents in their own solutions • We use the web-service architecture our selves, as the only internal service layer – taking our own medicine, so to speak

6. Select and Reject • Service Orientered Architecture – A true SOA • Every function and low level facility can be single- accessed or multi-accessed when it comes to families or functions, fx the NCIP-standard • Many so-called OPEN systems publish a selection of functions in an API environment with no attention from the vendor…or customers..or …

7. præsentations.TING PRESENTATION THING drupal php kilde.TING SOURCE THING METADATA SUPPL. METADATA CONTENT brønd.TING DATA WELL THING REPOSITORY SEARCH ENGINE PRESENTATION MANAGER mellem.TING MIDDLE LAYER THING WEBSERVICES ”alien websites and UI” transaktions.TING TRANSACTION THING LOCAL ILS integration

8. Library site Dissemination platform ÅKB KKB = Drupal thing workflow Data in – creating relations - Search - presentation Sources PHP libraries SOAP/XML-WSDL REST/JSON-EXPLAIN Harvesting Data import XML PDF MARC DataDock Fedora-Commons PTI Processing Transformation Indexing Search engine Objekt repository SolR Bibliotek Add on DC RDF taxonomies Indexering XSLT → TING.XML Postgres database Lucene indexer

9. THING Integration to other webservices library Middlelayer.THING og Transactions.THING SOAP/XML-WSDL REST/ JSON-EXPLAIN User behaviour DB Others who have.... User created data ILS Transactiondata Services Link resolving Search Engine SolR DDE-LIBRA INTEGRA ..... Import of DATA From other sites Async Sync Import of DATA ILS knowledge Database Lucene index frontpages Content

10. THING Integration to other webservices library Mellem.TING og Transaktions.TING SOAP/XML-WSDL REST/ JSON-EXPLAIN AAA Library services Library administration NCIP Open -Cirkulation Open-ACQ Open-Agency Open Directory Open-Proxy Search Engine SolR VIP ACQUISITION DB Cirkulation-DB Directory Lucene index

11. Web 1.0 2.0 and 3.0 • For library customers and endusers an Open OPAC/homepage is the mainroad to the ILS traditional facilities or ”library insite” • There is a main focus on web 2.0 social software – which gives libraries better opportunity to build public relations and partner relations • ”Web 3.0” – especially ”The semantic Web” and deep integration to mobile technologies and experiments with 3D userinterfaces are as well in focus

12. Valuedrivers? • Act open – be open – demand openness • From red underscores to taking responsibility and offering help • Partnership´s in stead of traditional vendor-customer relation in devoping phase • Don´t accept mediocrity – set high demands • Develop agile – find an appropriate and simpel project model • Choose components with international backing • Change from proprietary/closed vendor solutions to 100% open solutions

13. Openness OSCI • OPEN Source is an overall value driver in the solution • Open Content model for user trace, user created data and transactions established inside THING – focus on open content in DATA WELL • Open interfaces and protocols • Every single service can be selected or rejected • Integration with other providers solutions is not only a possibility but a main goal in the concept behind the THING

14. OPEN SOURCE • Every component is or will be implemented on a OPEN SOURCE platform • Linux; Apache; TomCat; Postgress, Lucene, SolR, Fedora Commons, Drupal, … • Free to choose a range of Database Managment systems • We use only GPL-licenced development toolkits • We publish code for backendplatform and middleware in GPL-3 • We publish code for webservices in A-GPL • This gives vendors as well as libraries a possibility to interact a broad range of business models on top of the technical solutions

15. Open interfaces • Every functionel service – relevant to access alone – is documented in a SOAP-XML.WSDL environment and REST-JSON.XPLAINdok • Defined standards and important market standards will be followed: • NCIP: The whole standard as well as implementation of functions in the same function family in a ”NCIP-like” way • Z3950 and SR/W-SW, …. • Z-ILL • etc • The standards mentioned here will definitely not cover any aspects of the vision for THING, but the rest of the facilities not possible to ”read” in the standards will be implemented in accordance with the standards ”way to do”