FAIR EVA's API expects the API endpoint to request the (meta)data, which puts the burden on the user as (s)he needs to know this value for triggering the evaluation. This situation could be easily avoided since this value is already known by the FAIR EVA's API through within each plugin's config.ini.
A solution is to create a new API path /endopoints that provide all the plugin's endpoints. A sample response could be:
FAIR EVA's API expects the API endpoint to request the (meta)data, which puts the burden on the user as (s)he needs to know this value for triggering the evaluation. This situation could be easily avoided since this value is already known by the FAIR EVA's API through within each plugin's
config.ini
.A solution is to create a new API path
/endopoints
that provide all the plugin's endpoints. A sample response could be:This allows to use query parameters, such as
/endpoints?plugin=epos
that would return: