JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CCP4BB Archives


CCP4BB Archives

CCP4BB Archives


CCP4BB@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CCP4BB Home

CCP4BB Home

CCP4BB  October 2011

CCP4BB October 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: raw data deposition

From:

Michel Fodje <[log in to unmask]>

Reply-To:

Michel Fodje <[log in to unmask]>

Date:

Thu, 27 Oct 2011 15:55:07 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

We store raw data for two main reasons:

a)  We currently use only a fraction of the information actually contained in raw images and extraction of that fraction can be improved. Destroying the data means 

- we lose the extra information, and make future research in some areas either impossible or more costly

- we make it more difficult to improve current data reduction methods

b)  Raw data is the best way to independently validate a published structure and prevent fraud.



The majority of crystallographers already recognize these truths. That is why almost all of them do keep backups of their data even after structures have been published.   



To those still against making data public I would ask a simple question:  Would you object to providing the raw data from a published structure if such data were available and you did not have to bear an unreasonable inconvenience in the process? My guess is that most crystallographers are reasonable scientists and such a "Poll" will probably result in ~100% "Yes" and ~0% "No". I'm I wrong?



The real issue then is how do we make the data available in such a way that the inconvenience (if any) to all the stake-holders is reasonable.  Some great ideas have already been advanced. 



In the short-term,  we could start by using the fact that synchrotron facilities already store raw data for a period. However, a lot of data is collected which is not published. Given the limited disk space, it may be useful to know exactly which datasets result in a publication and should be kept for an extended period. If a unique ID (such as the DOI suggestion) is provided to every dataset and required during deposition/publication, then synchrotron facilities can preserve only those datasets which have been published after a given "grace" period. Combined with a central Meta-data server similar to TARDIS, such a system could be developed in a relatively short period of time, while longer term central storage ideas are worked out.



Again the best solution is going to be one which requires the least amount of effort from crystallographers. In fact, I can see a system in which the experiment metadata for a PDB entry/dataset comes directly from the synchrotron facility during deposition so that users simply provide a unique dataset ID and the experimental details are pre-filled for them.



Of course the above completely ignores home sources.





/Michel

> -----Original Message-----

> From: CCP4 bulletin board [mailto:[log in to unmask]] On Behalf Of D

> Bonsor

> Sent: October-27-11 3:10 PM

> To: [log in to unmask]

> Subject: Re: [ccp4bb] raw data deposition

> 

> Why should we store images?

> 

> From most of the posts it seems to aid in software development. If that is

> the case, there should be a Failed Protein Databank (FPDB) where people

> could upload datasets which they cannot solve. This would aid software

> development and allow someone else to have ago at solving the structure.

> 

> If it is for historical reasons, how can someone decide whether their

> structure is historical? I would propose that images should be uploaded for a

> protein or protein-complex that has never be solved before. That way the

> images are there if that structure does become historical.

> 

> The question is not whether or not images should be uploaded but who

> would use the images that were uploaded.

> 

> For example, people who use crystallography as a tool to aid in

> characterization of their protein, would probably not look at images for 99.5%

> of other protein datasets, and they probably would not look at images for a

> protein that is related to their own protein. They are more interested in the

> final structure. I too would probably not be interested in reprocessing and

> solving a structure again when I can easily access the final product already.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager