Wednesday, 1 December 2010

Disruptive technologies in digitisation

Much of my fellowship has been taken up with examining three tech initiatives, all of which could be used in an on-demand process and could also be classed as disruptive. One is software, two are hardware.

Here is a bit more information ...

1) The Copyright calculator

Public Domain Calculators from Open Knowledge Foundation on Vimeo.



What is it?
A software development that assesses the copyright status of a creative work by looking at associated metadata. I've made an initial attempt to tie the Open Knowledge Foundation calculator into LibrarySearch, or new catalogue interface.

Why is it disruptive?
It can give the reader a useful indication of the copyright status of a book, allowing them to decide how they can re-use it. Its potentially useful as the first stage in a digitisation selection workflow, but also useful on its own. Its also an example of the commoditisation of a basic legal service.

What problems are there?
The be effective, the calculator needs author death-date information. Libraries only record this information when they wish to differentiate a name. Linked data tying a record into other sources of information could help overcome this


2) Kirtas book-scanner



What is it?
An automatic book-scanner. Turns pages using a vacuum equipped robot-arm and images pages with dual high-spec cameras

Why is it disruptive?
Books can be scanned and turned into PDF or other documents in a matter of hours, with minimal human interaction required.

What problems are there?
Its not cheap and still not 100% accurate. Its also a robot, so should not entirely be trusted.


3) Espresso book machine



What is it?
A photocopy sized book creation machine that does not require a printing-works to run it. Can print and bind a book in minutes.

Why is it disruptive?
Provides a library or a bookstore with a massive research collection/ back catalogue with none of the storage problems or overheads . Could have implications on acquisition, collection development and every part of library activity.

What problems are there?
As with the Kirtas, its not cheap, and limited in formats and outputs. And its a robot.

I'll have more to say on my project as I slog through write-up ...

No comments: