Dear community!
As I read from p. 6 of the Optimade API documentation, one can include property filter in a query, but I’m wondering, is it possible not just to filter on a property value but to retrieve properties values? In addition, I have two questions regarding properties names:
There are some examples of properties names in the Optimade API documentation, e.g. band_gap, cell_length_a and cell_volume. But can I somehow see the full list of possible properties?
There are also Database-Provider-Specific Namespace Prefixes and it is said in the documentation that lists of these prefixes are available at https://providers.optimade.org. However, I couldn’t find them there - can you please give an example for some database, e.g. Aflow or Materials Project?
Hi @antonf86, anything that you can filter on can be retrieved. As you state, there are not really any properties standardized in the OPTIMADE API definition, but databases can describe and serve their own properties with a well-defined mechanism.
We have the annual workshop coming up this month where we will hopefully be refining this process to allow for richer descriptions (https://github.com/Materials-Consortia/OPTIMADE/pull/376).
Hi, @ml-evs,
Thank you very much for a fast and detailed answer! Still, I have some refining questions:
1)
Directly from AFLOW we can extract e.g. Gruneisen parameter via “agl_gruneisen” keyword in the query, but it seems there are no such things listed in the above mentioned page. Does it mean that currently one can not deduce Gruneisen parameter and similar propeties from AFLOW via Optimade?
2)
Yes, it is up to the specific provider to choose which properties to serve via OPTIMADE (as well as their existing APIs). It actually seems like there are some issues with the aflow info/structures at the moment, for me the JSON response is cut off before the end… so your desired field may be hidden somewhere in there. Unfortunately there seem to be quite a few issues with AFLOW’s OPTIMADE API at the moment (as shown by the provider dashboard AFLOW: OPTIMADE provider dashboard), but perhaps they are currently working on the API ahead of our next meeting.
It is just for illustration, yes. _exmpl is the prefix we use for “example” data.
I will try to raise some of these issues at the upcoming workshop, but depending on your interest you could perhaps also raise them with the providers directly.
Just in case you are interested @antonf86, we have a few remote spaces left at the upcoming OPTIMADE workshop (30th May-3rd June) where there will be tutorials and opportunities to ask/make requests to providers! CECAM - Open Databases Integration for Materials Design