Downloading metadata via the Website is not consistent

[jh-RLI]

Description of the issue

Currently we offer two download buttons:

1. Via the table-detail pages in the meta information tab:

2. As part of the oemetaBuilder tool for creating/edeting oemetadata:

The resulting json file is not consistent:

• Empty fields are either empty strings or null
• The metadata contains different fields, for example in the context field of the oemeta data

The problem occurs because:

• The oemetaBuilder only uses the json schema provided for an oemetadata release.
• The "Download json" button on the table´s "meta information" tab retrieves the metadata from the database in which the metadata was compiled using omi before it was saved.

Steps to Reproduce

tbd

Ideas of solution

In general, make sure that the metadata is always the same and complies with the oemetada specification for the version to which the metadata refers.

This could include an omi update or the inclusion of omi in the download function of the metaBuilder tool.

First, determine if omi is returning correct results.

Context and Environment

• Version used:
• Operating system:
• Environment setup and (python) version:

Workflow checklist

• [x] I am aware of the workflow in CONTRIBUTING.md

[jh-RLI]

There was a thing (I would call it a bug) in omi that intentionally removes these fields from context if they are null:

"fundingAgency": null,
"fundingAgencyLogo": null,