OPTIMADE support

[ml-evs]

Hi @janosh, great work on this (as always!) -- now you've grown this to include structure viz, I'm wondering if you'd be interested in a PR adding differing degrees of OPTIMADE support? I'm imagining:

• Simply support for visualising a single OPTIMADE structure saved to disk as a JSON file (some minor content negotiation needed to check if pymatgen JSON or OPTIMADE)
• As above, but multiple structures saved as JSONLines
• As above, but also parse and display additional metadata fields present in the files and any definitions (e.g., energies and other properties)
• Loading single structures via a URL, e.g., https://optimade.materialsproject.org/v1/structures/mp-1226325

I wouldn't want to go much further than this myself (e.g., multi-provider queries, paginatoin, filters and so on) (though it would be cool to build a full OPTIMADE client on top of this as a separate package in the future!)

[janosh]

yes! all of the above sound like great ideas, esp. 3 and 4! 😄

Loading single structures via a URL, e.g., https://optimade.materialsproject.org/v1/structures/mp-1226325

this would be useful. i had MP detail pages working at some point but they broke when the file structure in AWS open data changed such that you can't fetch gzipped assets by material ID anymore. some of that code can maybe be repurposed

(though it would be cool to build a full OPTIMADE client on top of this as a separate package in the future!)

yes! i was thinking about exactly that a few days ago. would be great to get that working 🚀

[ml-evs]

No promises as to timing (and feel free to work on some yourself) but I'll have a go!

[janosh]

@ml-evs just started working on 4 (i.e. loading single structures via a URL) and wondering if you have thoughts on what a good UI might look like. should there be a grid of providers that a user clicks on followed by typing in a material ID? this is what i'm working on atm which is still very barebones and easy to tweak