Catalogue

Purpose

Making Wellcome Collection's catalogue open, accessible and discoverable.

The catalogue consists of multiple sources including:

• Library holdings
• Archives and manuscripts
• Born digital content
• Images from what was previously wellcomeimages.org

As and when these sources are made available digitally, we will consume them via our pipeline, unify them into a single model and make them discoverable via our API.

Interested in how we make these services?

Take a look at our documentation on the design and decision making processes of the services within the catalogue repo.

Interested in making use of our data to build your own products or use in your research?

Take look at our developer documentation or go straight to our API.

Interested in other parts of the Wellome Collection digital platform works?

Take a look at our Platform repo

Interested in how all of this works Keep reading about the architecture of the services in this repo.

Architecture

The catalogue consists of three main parts with supporting services. These are:

• Sierra adapter: Allowing us to store data from Sierra that is retrievable performantly and at scale.
• Pipeline: Taking adapter data and putting it into our query index, Elasticsearch
• API: Serving the data from Elastic search to clients via HTTP

Dependencies

• Java 1.8
• Scala 2.12
• SBT
• Terraform 0.11
• Docker
• Make

Problems you might have

• Stack overflow from scalac (in IntelliJ) when building projects:

  Go to Settings > Build, Execution, Deployment > Compiler and change Build process heap size (Mbytes) to something large, eg 2048.

Things you might want to do

Generally small things you might want to do irregularly involving the API & data are stored within [./scripts].

---

Part of the Wellcome Digital Platform.