ElasticSearch returns search results as JSON
files which have three top level entries
for us to parse:
"project", "file", and "metadata".
Change the class structure to match this
hierarchy. This means, that the mapping
from JSON to Java objects just works
and we can pass the data on to the
front-end in the same structure as
the back-end received it.

This allows the separation of the
"standardized" metadata which is provided
by the platform's users
and our implementation-detail metadata,
such as GitLab related data.
This way, no conflicts arise when a new
key is introduced to the metadata standard.

Metadaten geladen und an der Oberfläche die Suche ausgelöst, sobald
Eingaben da sind (nicht nur Volltext)

Give more space to search results.

added additional metadata fields -> difficulty, education level, status, type, version, format, keywords, requirements

jetzt

Create object for metadata search query.
This object is part of the SearchInputDTO object,
which gets parsed from the JSON file sent by the
front-end.