<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">I have requested a few times PDB files when reviewing a paper but never got the request granted.
<div><br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF903536" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> 3dem [3dem-bounces@ncmir.ucsd.edu] on behalf of James Whisstock [james.whisstock@monash.edu]<br>
<b>Sent:</b> Thursday, April 30, 2015 7:58 PM<br>
<b>To:</b> 3dem@ncmir.ucsd.edu<br>
<b>Subject:</b> Re: [3dem] sharing em maps during peer-review process<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Hiya
<div><br>
</div>
<div>In crystallography this happens a lot, particularly in the case of lower resolution structures or where the interpretation of a critical point really needs the reviewer to actually review the quality of the structure and look at it - and, in support of
what Eva wrote, anecdotally I have heard (from authors of papers who have been the subject of such requests) that some important points have been picked up as a consequence - for example structures in wrong Space Groups, twinning and so on. There is also
often a spike of debate around this issue on ccp4bb. For what its worth I've often shared coords with no issue and I guess that one has to trust that most people are decent individuals who will do the right thing.</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
<div>J</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 1 May 2015 at 07:16, Eva Nogales <span dir="ltr"><<a href="mailto:enogales@lbl.gov" target="_blank">enogales@lbl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div bgcolor="#FFFFFF"><font face="Helvetica Neue">Hi Friedrich,<br>
<br>
We got the same request and we provided the map and model as a Chimera session to the editor and reviewer. I understand your point, but we have to trust the system and understand where the reviewers may be coming from. We do know of more than one example where
having had such access may have precluded publication of</font><font face="Helvetica Neue"><font face="Helvetica Neue"> some really terrible structures</font>. It will be interesting to hear what others think (and I have no doubt the reviewer(s) that asked
for your and our maps is/are within the list reading this email...)<br>
<br>
Eva<br>
</font>
<div>
<div class="h5"><br>
<div>On 4/30/15 1:49 PM, Friedrich Foerster wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>dear colleagues,<br>
<br>
</div>
i would be interested in experiences / suggestions / views of others in the field on the following issue that may be of interest to many of us:<br>
</div>
the editor of our manuscript forwarded the request of a peer-reviewer to access the cryo-em map of our beloved complex. this has never happened to us, but to our surprise the editor did not consider the request to be unusual.<br>
of course, we share the point that the map would be of great help in judging the interpretation of the data. however, we also feel very uncomfortable sending the condensed result of lengthy research to an anonymous colleague, who could theoretically make considerable
misuse of it. nevertheless, the policy of the journal seems to let us little choice: "<font size="2">Supporting data must be made available to editors and peer</font><font size="2">-</font><font size="2">reviewers at the time of</font><font size="2"> submission
for the purposes of evaluating the manuscript.</font><font size="2"> Peer</font><font size="2">-</font><font size="2">reviewers</font><font size="2"> may be asked</font><font size="2"> to comment on the terms of access to materials, methods and/or data sets</font><font size="2">"</font>.<br>
</div>
in any case we would be curious whether others indeed got similar requests and how they dealt with it. a good solution for (paranoid?) people like us could be a good web-based viewer that lets others view our map, but i would not know of such a tool.<br>
<br>
</div>
Thanks <br>
<br>
</div>
Friedrich<br clear="all">
<div><br>
-- <br>
<div>Dr. Friedrich Foerster<br>
Max-Planck Institut fuer Biochemie<br>
Am Klopferspitz 18<br>
D-82152 Martinsried<br>
<br>
Tel: <a href="tel:%2B49%2089%208578%202632" value="+498985782632" target="_blank">
+49 89 8578 2632</a><br>
Fax: <a href="tel:%2B49%2089%208578%202641" value="+498985782641" target="_blank">
+49 89 8578 2641</a><br>
<br>
<a href="http://www.biochem.mpg.de/foerster" target="_blank">www.biochem.mpg.de/foerster</a><br>
</div>
<br>
</div>
</div>
<br>
<fieldset target="_blank"></fieldset> <br>
</div>
</div>
<pre>_______________________________________________
3dem mailing list
<a href="mailto:3dem@ncmir.ucsd.edu" target="_blank">3dem@ncmir.ucsd.edu</a>
<a href="https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem" target="_blank">https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
__________________________________________________________________
Eva Nogales
Howard Hughes Medical Institute
Molecular and Cell Biology Department
QB3, Stanley Hall 708C
University of California, Berkeley
Berkeley, CA 94720-3220
Phone: <a href="tel:%28510%29%20642-0557" value="+15106420557" target="_blank">(510) 642-0557</a> Fax: <a href="tel:%28510%29%20666-3336" value="+15106663336" target="_blank">(510) 666-3336</a>
URL: <a href="http://cryoem.berkeley.edu" target="_blank">cryoem.berkeley.edu</a>
<a href="tel:%28510%29%20666-3334" value="+15106663334" target="_blank">(510) 666-3334</a> Teresa Tucker, Assistant to Eva Nogales
Professor, UC Berkeley and Lawrence Berkeley Natl. Lab
__________________________________________________________________
</pre>
</div>
<br>
_______________________________________________<br>
3dem mailing list<br>
<a href="mailto:3dem@ncmir.ucsd.edu" target="_blank">3dem@ncmir.ucsd.edu</a><br>
<a href="https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem" target="_blank">https://mail.ncmir.ucsd.edu/mailman/listinfo/3dem</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>Professor James Whisstock</div>
<div>Director of the ARC Centre of Excellence for Advanced Molecular Imaging</div>
<div>NHMRC Senior Principal Research Fellow</div>
<div>Department of Biochemistry and Molecular Biology</div>
<div>Monash University</div>
<div>Clayton Campus</div>
<div>Melbourne</div>
<div>VIC 3800</div>
<div>Australia</div>
<div>Phone: +61 418 170 585</div>
<div>Website: <font color="#0000ff" style="color:rgb(0,0,255)"><a href="http://www.imagingcoe.org/" target="_blank">www.imagingcoe.org</a></font></div>
<div><font color="#000000">Twitter: <a href="https://twitter.com/ImagingCoE" target="_blank">@imagingCoe</a></font></div>
<div><font face="arial, helvetica, sans-serif" size="1"><b><br>
</b></font></div>
<div dir="ltr"><b style="font-family:arial,helvetica,sans-serif"><span style="">Join us at the 3rd Prato conference on Pore Forming Proteins, Prato, Italy - </span><span style="text-align:center"><a>12th to 15th May, 2015</a>: </span><a href="http://www.pores2015.org/" style="color:rgb(17,85,204)" target="_blank">www.pores2015.org</a><span style=""> </span></b></div>
<div dir="ltr"><b style="font-family:arial,helvetica,sans-serif"><span style=""><br>
</span></b></div>
<div dir="ltr"><img src="https://mail.google.com/mail/u/1/?ui=2&ik=0626e17f9a&view=fimg&th=14b2071d2ba48b49&attid=0.1&disp=emb&realattid=ii_14b2071aec53cd5b&attbid=ANGjdJ-xN4VgDCh2Z_-unt55zxr_wks4-QdU1nTXprFT4nCyJcj6vb-eOf1lQrf-1xrRO-R-42dct9_xJsbZIobvVvhL3y-guwBsO-WNXuBljSxAcvBDOzqn-Ga0zbk&sz=w994-h398&ats=1422178545392&rm=14b2071d2ba48b49&zw&atsh=1">
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>