"Dynamic" enums from within the branch

[silvester-pari]

For some properties (example: osc:projects) it should be possible to have a selection of existing ids to reference:

Example flow

• user creates a new project my-new-project
• user then creates a new product (in the same branch), and under "projects" sees a list (autocomplete) of all projects (file paths), including my-new-project
• user selects the project and its id is stored

Evolution

• instead of showing all project ids (file paths) in the autocomplete, the user can see a property from inside the file (title) and store the value (id)
• When selecting one of the values, it also can do other things (like adding a related link to the links array)

In the OSC use case, this will apply to osc:themes, osc:missions, osc:project, osc:variables.

Ideally this would be a plugin that can be used in a specific git-clerk instance.

[silvester-pari]

A more detailed description (including evolution):

• a JSON schema is used with a custom format. Example: "format": "osc-project",
• this allows a custom plugin to look for all osc projects (living in /projects/<id>/collection.json)
• the user sees the projects (project title)
• the user selects one of the projects (project id)
• a related link is added to the links (example: https://github.com/ESA-EarthCODE/open-science-catalog-metadata/blob/58f8b4970ec910f425b3938e535f7a4fc3dcbe5f/products/absolute-sea-level-heights-baltics-sar-hsu/collection.json#L25)

If we can offer this as a plugin for eox-jsonform (json-editor), then this editor can create custom form controls for the formats:

• osc-prject
• osc-themes
• osc-missions
• osc-variables

Ideally, this json-editor plugin could live in the /public folder of git-clerk and could be passed via config.js to eox-jsonform.