Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a point of contact for each provider on dashboard? #27

Open
mkhorton opened this issue Feb 17, 2021 · 2 comments
Open

Add a point of contact for each provider on dashboard? #27

mkhorton opened this issue Feb 17, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@mkhorton
Copy link

In case there is an issue with a specific provider, it would be good to be able to direct users to a contact email for the specific individual(s) who have primary responsibility over that provider's OPTIMADE endpoint.

This may be difficult to add since this information is not contained in the /info endpoint, but I thought I'd create the issue for discussion.

@ml-evs
Copy link
Member

ml-evs commented Feb 18, 2021

This may be difficult to add since this information is not contained in the /info endpoint, but I thought I'd create the issue for discussion.

The spec allows for people to provide maintainer emails for within the meta response to all queries, see e.g. meta->implementation->maintainer->email at https://optimade.odbx.science/v1/info, so it shouldn't be difficult to add this on the dashboard where it is present. Unfortunately no-one is "in charge" of this dashboard, and it could really do with some work...

@ml-evs ml-evs added the enhancement New feature or request label Feb 18, 2021
@mkhorton
Copy link
Author

Thanks @ml-evs, I'd missed that key in the meta. That sounds ideal then (in principle), perhaps showing it on the dashboard could encourage a provider to specify a maintainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants