Posted on July 30th, 2011 by Nick Jackson
Jerome is a system which is modular by design. It comprises of a variety of distinct modules which handle data collection, formatting, output, search, indexing, recommendation and more. It’s also fairly unique (as far as I can tell) in that different types of resource also occupy a modular ‘slot’ rather than being interwoven with Jerome itself – it has no differentiation at the code level between books, ebooks, dissertations, papers, journals, journal entries, websites or any other ‘resource’ which people may want to feed it.
As a result of this approach we can use Jerome as a true multi-channel resource discovery tool. All that’s required for anybody to add resources to Jerome and immediately make them searchable and recommendable is for a ‘collection’ to be created and for them to write a bit of code which can make the following API calls as necessary:
- Create a new resource as part of the collection, telling us as much about it as they can.
- Update an existing resource when it changes.
- Delete a resource which is no longer available.
- Optionally record a use of a resource against a user’s account to help build our recommendations dataset.
That’s it. Got a collection of awesome lecture slides you want to feed into Jerome and instantly make known as a resource? You can do that.
We’ll have your API documentation up soon.
Posted on July 21st, 2010 by Paul Stainthorp
Today’s Talis Linked Data and Libraries open day has motivated me to make a list of some of the external data tools, web services and APIs that could well end up being sucked into Jerome’s vortex of general awesomeness.
I was inspired (possibly through drinking too much SPARQL-themed coffee) by the thought that 2010 is effectively ‘year 1′ for library-themed Linked Data. (But I promise I’ll try and keep the ‘Lincoln’/'linking’ puns to a minimum after this post…)
“With the emergence of large, centralized sources entry to the Linked Data cloud might be easier than you think” (Ross Singer, The Linked Library Data Cloud: Stop talking and start doing, Code4Lib 2010)
So, which of these will make their way into the Jerome toolkit? (I’ll say now, before I get in trouble, that they’re not all purely Linked Data!) …compiled in part from these other lists, and by discussions/examples at the Talis event:
- Amazon Product Advertising API and affiliate scheme
- Bibliographic Ontology (BIBO)
- British Library Free Data Services - edit: added 25 August 2010, 13:40 BST
- Cambridge University Library APIs
- Classify (OCLC)
- Copac APIs inc. search
- data.lincoln.gov.uk - edit: added 6 September 2010, 09:47 BST
- Dewey Decimal Classification: Summaries
- EPrints (drives the Lincoln Repository)
- Free Decimal Correspondence - edit: added 20 August 2010, 12:06 BST
- Google Book Search
- Hathi Trust
- ISSN-L - edit: added 4 August 2010, 12:23 BST
- JISC Open Bibliography British National Bibliography dataset - edit: added 18 October 2010, 11:50 GMT
- Juice Project - edit: added 30 July 2010, 13:57 BST
- Library of Congress Authorities and Vocabularies
- LibraryThing book cover images
- Melvil Decimal System (LibraryThing) - edit: added 22 August 2010, 22:11 BST
- Mendeley - edit: added 22 July 2010, 16:51 BST
- MARC codes as Linked Data
- Open Library
- Open Metadata Registry
- OUseful ISBN Playground - edit: added 12 January 2011, 14:06 GMT
- RefWorks APIs as per the TELSTAR project
- SHERPA/RoMEO - edit: added 28 July 2010, 14:02 BST
- Silkworm Directory (Talis) - edit: added 21 July 2010, 22:57 BST
- Talis Keystone
- Talis Platform – e.g. the UK bib store
- ThingISBN (LibraryThing)
- VIAF: The Virtual International Authority File
- Web of Science web services (Thomson Reuters)
- WorldCat Search API (OCLC)
- WorldCat Registry (OCLC)
- xISBN (OCLC)
- xISSN (OCLC)
What have I missed? Which of these are not worth bothering with; which should we get stuck into without delay? You know where the comment form is…