|
|
What
Jangle (Just another generic library environment) is an experiment with middleware for library applications. If you build, use, manage or just want simple access to a library system, Jangle could be for you.
Why
The aim of the Jangle project is to provide a free, easy to use framework for building web services for LMSs/ILSs.
There are a few approaches to this floating around at the moment (see RelatedWork). Jangle is an attempt to take on board this work, and apply it to create tools for building generic RESTful APIs for library systems.
We also keep in mind the points in the Library Software Manifesto and look for intuitive, simple, standards-based approaches.
Who
Several Jangle developers work for Talis, a major provider of library systems. More information about Talis' involvement.
However, Jangle is open source software, released under the GPL v2: see Licensing for more information. It is free for anyone to use, modify and redistribute under the terms of that licence.
The project hopes to engage with:
- Developers of open source ILS software who want to develop consistent, standardised APIs for their software
- Developers who would like to add REST services to an ILS they have been provided by a vendor
- Companies interested in adding REST services to their products
Documentation
Installation
Design
- JangleAndConnectors
- Why we chose Rails as the platform for Jangle
- Discussion around the right back-end for Jangle
- Terminology used in Jangle
Connector API
The format for requests to connectors and responses from connectors.
- General principles for Jangle connector APIs
- Generic services provided by every Jangle connector
Jangle API
The format for requests to Jangle and responses back.
Prototypes/experiments
- BorrowerSchemaDiscussion ( discussing the database schema for borrower info.)
- NCIPXMLSchemaForBorrowers (experiments with translating the NCIP requests to REST requests, and mapping borrower model onto NCIP responses)
Developers
Sign in to add a comment
