Matthew Evans
Matthew Evans
### First Check - [X] I added a very descriptive title to this issue. - [X] I used the GitHub search to find a similar issue and didn't find it....
**Describe the bug** The responses from the JARVIS-DFT OPTIMADE API have several outstanding issues, as reported by the [dashboard](https://www.optimade.org/providers-dashboard/providers/jarvis.html) and pasted into this gist (https://gist.github.com/ml-evs/89f7bacac1c8a266074b82c89b78a11a). I can't find a repo...
Closes #422. This PR adds the optional `database` field to all `meta` responses. It can be used to provide the same data on an individual database as that found at...
In the September 2022 web meeting we discussed adding an introductory paragraph to the specification that describes the design choices made for OPTIMADE as an API that can be implemented...
Currently the only place where a *database* can be given a human-readable description is at the links endpoint of the relevant index meta-database. It might be an idea to add...
Below is the text of an issue I wrote but never posted (one of a few...), this has come up again in the discussion on #386. Alternative discussion in the...
I think a potentially useful piece of syntax that we are missing is the ability to specify `response_fields` relative to the default response for that implementation. Typically you run into...
This point was raised on the forums (by @oarcelus) here: https://matsci.org/t/cod-response-does-not-include-response-fields-in-next-link/39530. Currently the pymatgen `OptimadeRester` (and presumably other clients) rely on the fact that they can just use the `links->next`...
I'll throw a wrench into the discussion. `nelements` should equal `len(elements)`, this is fine. In an experiment with known impurities, a DB might want to list those impurities but not...
At the 2021 workshop, we discussed including an OPTIONAL `archives` entry type and corresponding endpoint in the specification. Below is an incomplete summary of the ideas that were discussed (please...