RESEDA API Search

Prerequisites

• git >= 2.7.0
• Node.js >= 16
• npm >= 7.20.0
• Docker
• docker-compose

Installation

$ git clone https://gitbucket.inist.fr/git/METADoRe/reseda-search.git
$ cd ./reseda-search

Production

$ docker-compose up -d api

Usage

API Key

A master API key is created at the first launch of the application, API keys are stored in ./api-keys.json file.

An API key gives access to more fields returned by the API, for examples:

{
  "a7e666ed93d877d9a4f9": {
    "name": "my-api-key",
    "fields": {
      "employees": ["*"],
      "structures": ["field", "field.subfield", "field.*"],
    }
  },
  "939500eae15165ab4b8a": {
    "name": "my-api-key",
    "fields": {
      "employees": ["field"],
    }
  },
  "e24d1167135d65bfcaad": {
    "name": "my-api-key",
    "fields": {
      "structures": ["field.*"],
    }
  }
}

employees (type: Array) and structures (type: Array) are optional, the fields returned by the API will be the default ones (cf: Environment variables - FIELDS_NAME).

The values of its tables can be:

• * gives access to all the fields.
• field gives access to a field
• field.subfield gives access to a subfield
• field.* gives access to all subfields

There are two ways to use an api key, by the header x-api-key (in lowercase) or the url parameter apiKey.

Examples:

$ curl -H "x-api-key: 6596ae25fdfdc83b85a7" http://localhost:3000/employees

$ curl http://localhost:3000/employees?apiKey=6596ae25fdfdc83b85a7

Development

$ npm install # Install Node.JS dependencies
$ docker-compose -f docker-compose.debug.yml run --rm elastic chown -R elasticsearch /usr/share/elasticsearch/ # Chown ElasticSearch volume
$ docker-compose -f docker-compose.debug.yml up -d elastic # Run ElasticSearch
$ docker-compose -f docker-compose.debug.yml up -d api # Run API in development mode

Tests

$ npm run test

Environment variables