The DOME platform should store sufficient information about a data consumer (e.g. a provider of simulation services, or a data analysis service), such that it can pass on data entries resulting from a query that the data consumer can handle.
This includes:
A (short) human readable name of the data consumer
A list of the data formats understood by the consumer (e.g. OPTIMADE, or JSON, etc...)
A 'template string' of the base URL for the data consumers frontend e.g. https://data-analyser.com/analyse?data={URL} where DOME would replace {URL} with the URL of the catalogue entry that the user wants to analyse
A field with the name of a DOME KeyCloak group of users that are allowed to use the service. This can be blank if the service is public.
This data should be incorporated into the DOME 'providers' ontology such that we now have 'providers' and 'consumers', perhaps with a common parent class that groups attributes that they share.
The DOME platform should store sufficient information about a data consumer (e.g. a provider of simulation services, or a data analysis service), such that it can pass on data entries resulting from a query that the data consumer can handle. This includes:
This data should be incorporated into the DOME 'providers' ontology such that we now have 'providers' and 'consumers', perhaps with a common parent class that groups attributes that they share.