We are currently in the process of digitising a vast collection of books produced by the business. This process is finicky, tedious, requiring a great attention to detail and persistent oversight.

The information and digital assets produced by this process are being stored and archived in a manner that will yield benefits to the business for years to come.

The book depository can be viewed as a data layer, 'oil in the ground' ready to be extracted by developers whenever they need to display book pages within features of online educational products.

With the book depository we have answered the question 'where do we get our digital book content' and replaced it with 'how do I make use of this content'.

For the technically minded, the book depository is a HTTP API responding in both JSON and JSONP formats.

The book reading experience exhibited in this library is a piece of reusable technology built on-top of the aforementioned book depository data layer .

It gives developers a very fast albeit standardised way of displaying a modal book reading experience within any web based product.

The book reader can be currently customised to the extent of the navigation arrows and logo displayed top centre. We have many more features and customisations touted for development, please read our development plan to better understand the course we are charting.

There will be occasions whereby editorial will require a book content related feature within an online product that cannot be fulfilled by the book reader.

This is entirely acceptable. Given this scenario a developer can skip down to using the lower level book depository layer in-order to construct a more customised one-off experience to fulfil editorial requirements.

For the technically minded the book reader is a JavaScript library. Using it requires the inclusion of one remote JavaScript file and one remote CSS file.

It calls out to the book depository internally using Ajax and processes a JSONP response.