An API of APIs: a content silo mashup for library websites

At Johns Hopkins University, silos are at the base of their battle with web content. Our philosophy about library content has been to put our content where our users already are. Minor content updates became a full-day workload of managing multiple content management systems and custom applications....

Full description

Saved in:
Bibliographic Details
Published in:Online Searcher Vol. 39; no. 3; pp. 54 - 59
Main Author: Hannan, Sean
Format: Magazine Article Trade Publication Article
Language:English
Published: Medford Information Today, Inc 01.05.2015
Subjects:
ISSN:2324-9684
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:At Johns Hopkins University, silos are at the base of their battle with web content. Our philosophy about library content has been to put our content where our users already are. Minor content updates became a full-day workload of managing multiple content management systems and custom applications. This approach was unsustainable. Once they identified this issue, their goal became to decouple Web site content from the platforms on which it was displayed. What we actually needed was our own API that could bundle all these external services together under one umbrella. Rapier is what we call our API of APIs. It provides con- tact information, service and building hours, lists of subject guides, lists of licensed databases, tweets, and blog content across our platforms. Rapier is around 300 lines of Ruby code. Just 300 little lines allow us to pull the bulk of our content from six different content silos.
ISSN:2324-9684