Policies

Technologies

API CODEX


» Codex Home
» API Basics
» Requests
» Responses
 »  Object Structure
 »  Field Reference
» Glossary
» Policies
» Philosophy
Technologies
» Troubleshooting & FAQ
 »   Issue Tracker
» Contact

We have no problem using the open-source creations of others.  In fact, we embrace it.  So we’ve got a fully open technology stack.  And here it is:

DPLA

Our delightful little platform pulls lots of data from lots of places, ties our whole stack together, and lives comfortably at our GitHub.

JSON-LD

Everyone likes JSON, but it’s not great for every purpose.  Pointing from one JSON object to another is a good example (because we do that a lot).  So we use JSON-LD.

No worries – it’s still JSON.  It’s just got a couple of standardized fields.

Lucene

Search is hard.  Good thing smart people are working on it.  Smart people like those at Lucene.  They do search so we don’t have to.

Search is so complicated, in fact, that we don’t actually touch Lucene all that much.  For that we turn to…

elasticsearch

How does one do distributed search with a handsome, coherent API?

You certainly don’t write your own.  We use elasticsearch.

Redmine

Holy cow! Even our issue tracker is open.  And open source.

Standards

Tech stuff may be hard, but the cat-wrangling, hair-pulling thunderdome of standards creation is a whole ‘nother thing.

We do a bit of this ourselves, but we let do other organizations do a lot of the heavy lifting.  For that reason, you’ll see a whole bunch of namespaces scattered throughout.  Here’s a de-acronymed list:

Namespaces