Storage of diffraction data: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
As the PDB isn't developing data storage and retrieval solution, community efforts are needed. Here are a few examples: | As the PDB isn't developing data storage and retrieval solution, community efforts are needed. Here are a few examples: | ||
* | * zenodo.org (including https://zenodo.org/communities/mx/?page=1&size=20 but maybe other "communities"); this is managed by CERN | ||
* | * SBGrid https://data.sbgrid.org/ | ||
* proteindiffraction.org (this has e.g. almost? all the JCSG data!) | |||
* Australian synchrotron.store - see https://store.synchrotron.org.au and http://scripts.iucr.org/cgi-bin/paper?S1399004714016174 | |||
* the ESRF makes all collected data available after 3 years; see http://www.esrf.eu/datapolicy | |||
Revision as of 21:33, 17 January 2018
Synchrotrons are very good at archiving all collected data. In contrast, there's no requirement for including diffraction data when submitting a structure to the PDB. Consequently, the connection between structure and the underlying data is lost for all practical purposes. Some think this is a problem, but there aren't any good solutions yet.
Diffraction data storage solution
As the PDB isn't developing data storage and retrieval solution, community efforts are needed. Here are a few examples:
- zenodo.org (including https://zenodo.org/communities/mx/?page=1&size=20 but maybe other "communities"); this is managed by CERN
- SBGrid https://data.sbgrid.org/
- proteindiffraction.org (this has e.g. almost? all the JCSG data!)
- Australian synchrotron.store - see https://store.synchrotron.org.au and http://scripts.iucr.org/cgi-bin/paper?S1399004714016174
- the ESRF makes all collected data available after 3 years; see http://www.esrf.eu/datapolicy