Dtool-lookup-server

---------------------

Fixed
^^^^^

- Made /dataset/summary route able to cope with individual datasets in the
mongo database missing the tags key

---------------------

Added
^^^^^

- Added "tags" and "datasets_per_tag" keys to JSON response from
/dataset/summary route
- Added ability to filter/search based on tags


Changed
^^^^^^^

- Registering a dataset now requires a key for ``tags`` in the JSON
content

---------------------

Added
^^^^^

- Added /dataset/annotations route to which one can POST a URI and get back the
associated dataset annotations


Changed
^^^^^^^

- Registering a dataset now requires a key for ``annotations`` in the JSON
content
- The /dataset/search route no longer returns manifest and readme in the body
of the JSON response. These will now have to be retrieved using the
/dataset/manifest and /dataset/readme routes respectively. This change was
implemented to overcome the slow response time when accessing many (>1000)
datasets using the /dataset/search route.

Fixed
^^^^^

- Made registration of datasets more tolerant to type of frozen_at in
admin_metadata, now accepts value as a string

---------------------

Added
^^^^^

- Added /dataset/manifest route to which one can POST a URI and get back the
associated dataset manifest
- Added /dataset/readme route to which one can POST a URI and get back the
associated dataset readme

---------------------

Added
^^^^^

- Ability to log request headers in debug mode

---------------------

Changed
^^^^^^^

- Added logic to config.Config that ignores ``JWT_PRIVATE_KEY_FILE`` and
``JWT_PUBLIC_KEY_FILE`` if ``JWT_PUBLIC_KEY`` is set in the environment.
This makes it easier to configure the ``dtool-lookup-server`` to make use
of tokens generated from another server. In other words where the private
key file is maintained in a different service.