Peer Review History
| Original SubmissionApril 21, 2020 |
|---|
|
PONE-D-20-11526 The yeast mitophagy receptor Atg32 is ubiquitinated and degraded by the proteasome PLOS ONE Dear Dr. Camougrand, Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Two expert reviewers have carefully examined your manuscript, and I have read the manuscript as well. Certainly, the manuscript requires very considerable revision. Of note, the construct used has not been demonstrated to fully recapitulate the behavior of endogenous Atg32p, due to the presence of a carboxyl-terminal tag and potential over-expression from a plasmid. Mitochondrial localization of your construct has not been adequately demonstrated. It would be important to show that endogenous Atg32p, or a chromosome-integrated, internally tagged Atg32p previously demonstrated to perform as endogenous Atg32p, localizes to mitochondria and behaves similarly in key assays. Both reviewers raise additional, substantial issues regarding whether the manuscript is technically sound, and these points should be addressed in a revised manuscript. Finally, the results reported are in conflict with previous findings. In a revised manuscript, the authors should directly address and rationalize differences with earlier publications. We would appreciate receiving your revised manuscript by Jun 28 2020 11:59PM. When you are ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. To enhance the reproducibility of your results, we recommend that if applicable you deposit your laboratory protocols in protocols.io, where a protocol can be assigned its own identifier (DOI) such that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols Please include the following items when submitting your revised manuscript:
Please note while forming your response, if your article is accepted, you may have the opportunity to make the peer review history publicly available. The record will include editor decision letters (with reviews) and your responses to reviewer comments. If eligible, we will contact you to opt in or out. We look forward to receiving your revised manuscript. Kind regards, Cory Dunn, Ph.D. Academic Editor PLOS ONE Journal requirements: When submitting your revision, we need you to address these additional requirements. 1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and 2. Please include captions for your Supporting Information files at the end of your manuscript, and update any in-text citations to match accordingly. Please see our Supporting Information guidelines for more information: http://journals.plos.org/plosone/s/supporting-information. 3. Please include your tables as part of your main manuscript and remove the individual files. Please note that supplementary tables (should remain/ be uploaded) as separate "supporting information" files [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author 1. Is the manuscript technically sound, and do the data support the conclusions? The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented. Reviewer #1: No Reviewer #2: No ********** 2. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes Reviewer #2: No ********** 3. Have the authors made all data underlying the findings in their manuscript fully available? The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified. Reviewer #1: Yes Reviewer #2: No ********** 4. Is the manuscript presented in an intelligible fashion and written in standard English? PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here. Reviewer #1: Yes Reviewer #2: Yes ********** 5. Review Comments to the Author Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters) Reviewer #1: In this manuscript, Camougrand et al examine the regulation of the yeast selective autophagy receptor, Atg32. The authors observe that while Atg32 is specifically expressed during growth in non-fermentable carbon sources, the protein gets degraded in stationary phase, during nitrogen starvation, or rapamycin treatment. The latter two are accordance with previous observations (Levchenko et al, Plos one, 2016). Surprisingly, and in contrast to this published work, the authors determine that protein destabilization is mediated by the proteasome and not by vacuolar degradation. Using a purification/mass spec approach, they identify a potential ubiquitination site on Atg32. Finally, the authors mutagenize the site, finding a subtle stabilization of the protein and, correlatively, a subtle (but statistically insignificant) enhancement in mitophagy. This study is of potential interest because it suggests a balance between Atg32 function and its degradation by the proteasome may fine-regulate mitophagy, which indeed warrants further exploration. However, the results are in direct conflict with published observations, which is not discussed and should be addressed. Additionally, the effects with proteasomal inhibition are only convincingly observed after extended periods of time, raising the concern that the stabilization of Atg32 seen is indirectly due to a stress response rather than acute inactivation of Atg32 degradation. Further, the data suggesting that Atg32 is ubiquitinated in a regulated manner at the K282 site are based on an unconvincing purification approach. Specific points: 1. Stabilization of Atg32 upon proteasome inhibition is only observed after 24h of treatment in stationary phase growth. The data shown in Fig. 4B after shorter periods of treatment are not quantified or convincing. This raises the concern that the authors are not observing a prevention of the typical Atg32 degradation, but rather a potential cell stress response or adaptation. Under nitrogen starvation conditions, the stabilization the authors claim exist at 3h is unconvincing, and there is no effect during longer term treatment. The authors also examine Atg32 stability during MG132/rapamycin treatment (Fig. S3), and this time find a compelling effect. However, this is several hours after treatment and also in conflict with data from Levchenko et al (who treated with MG132 for 2h and saw no stabilization of Atg32). This needs to be discussed/addressed by the authors. 2. The data identifying a ubiquitinated form of Atg32 are lacking key controls. The authors purify Atg32, and perform a western blot with ubiquitin. However, there is no western blot indicating that the Coomassie stained band is indeed the purified protein. No input is shown from the purification. This is all particularly concerning given that the protein is supposedly SDS resistant after purification, and no protein is observed at the native size. The authors do identify one single peptide of ubiquitinated protein, which they map to K282, however, it is impossible to assess if this is biologically relevant as the mutagenized protein has a negligible effect. 3. It is not clear whether quantification of all western blots is normalized to Pgk1, however this is required. The authors state in the legends, “Atg32-V5 expression was quantified as the percentage of Atg32-V5 level of T0”. 4. The clarity of the manuscript needs to be improved. The authors should explicitly state growth conditions of their assays. It is not obviously stated that “growth” means allowing cultures to reach saturation after dilution to exponential phase. Specific growth media are not always mentioned. Another example of confusion is the Idp1 degradation assay – while this may be standard for the field, the relationship between its cleavage as an indicator of mitophagy is not explicitly stated. Reviewer #2: In this manuscript, the authors found that the mitophagy receptor Atg32 is degraded upon mitophagy induction or under nitrogen starvation conditions. They further showed that the degradation of Atg32 is mediated by the 26S proteasome but not by autophagy. Using mass spectrometry analysis, they identified Lys 282 is an ubiquitination site on Atg32. Intriguingly, the replacement of Lys 282 with Ala did not slow down the degradation rate of Atg32 in their experimental conditions. Overall, the authors concluded that the yeast mitophgy receptor Atg32 can be ubiquitinated and degraded by the proteasome. Based on the presented data, this reviewer think this manuscript is not technically sound and many critical controls are missing (see below for details). The quantification data are confused, as some blots contain 5 repeats whereas some blots in the same experiments contain 6 repeats (for example, 8 hrs vs. 24 hrs in Fig. 2B and Fig. 3B). Most quantification assays lack statistical analyses. The writing basically sounds good, but typos and errors avoid the reviewer to fully understand the context. Major problems: 1. The Atg32 degradation assay were performed by using an epitopic-tagged Atg32 construct instead of integrated tagged Atg32, which makes the full story less convincing. This reviewer suggest the authors at least re-examine the stability and ubiquitination of Atg32 using integrated form. 2. In Figure 1A, the authors should examine the localization of Atg32-V5 protein by immunoflorescent staining instead of gradient assay alone. Co-fraction of two protein does not necessarily mean that they spatially localized together. Moreover, in previous results, Dr. Koji Okamoto showed that the C-terminal tagging in Atg32 would disrupt mitochondrial targeting and out-membrane insertion. Therefore, they generated an internally 3xHA-tagged Atg32 variant (Atg32-3HAn) to replace the endogenous protein. This is the major problem in this manuscript. 3. CHX assay is critical to confirm the decrease of Atg32 over the time (upon to 48 hrs) under mitophagy induction is due to protein degradation but not the synthesis of mRNA transcripts. Unfortunately, the whole Figure 4 are somehow disrupted and this reviewer can not see it. 4. In Figure 3, the ubiquitination levels of Atg32 should be examined by immunoprecipitation of Atg32. The ubiquitination levels of total proteins does not mean Atg32 is also ubiquitinated. In addition, PMSF is unstable in aqueous solutions, and its half-life is about 30 min. How the authors exclude the possibility that less protein levels of Atg32 is due to no effect of PMSF after 24 or 48 hours incubation. 5. In Figure 5A, the strain source of pre2-2 should be referred. The authors should clearly describe how they inactivate 20S proteasome using this mutant strain. The positive control is missing in 5A and 5C. 6. In Figure 6D, ATG32 deletion strain should be included as a negative control. 7. From Figure 7 to 10, these data may remove to the supplemental data since they are negative results and the model figure is not closely related to the main conclusion. 8. The discussion part should be more concise. Minor issues: 1. Page 8, line 170, the font of “107” is weird. 2. Page 11, line 221, remove “we” 3. Page 14, line 291, the blue label should be removed. 4. Page 31, line 709, where shows “against histidine”? 5. Figure 7B, “imput” should be “input”. ********** 6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy. Reviewer #1: No Reviewer #2: No [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files to be viewed.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email us at figures@plos.org. Please note that Supporting Information files do not need this step.
|
| Revision 1 |
|
PONE-D-20-11526R1 The yeast mitophagy receptor Atg32 is ubiquitinated and degraded by the proteasome PLOS ONE Dear Dr. Camougrand, Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process. One expert reviewer has returned comments on your resubmission. This reviewer still has concerns about the manuscript that should be addressed by further revision. Specifically, you must address concerns regarding the different K282A clones and their differential behavior. Furthermore, you should also address the reviewer's query about MG-132 treatment and, if additional experiments are not forthcoming, you should provide all necessary caveats within the text of your manuscript. Please submit your revised manuscript by Nov 01 2020 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:
If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter. If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols We look forward to receiving your revised manuscript. Kind regards, Cory D. Dunn, Ph.D. Academic Editor PLOS ONE [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author 1. If the authors have adequately addressed your comments raised in a previous round of review and you feel that this manuscript is now acceptable for publication, you may indicate that here to bypass the “Comments to the Author” section, enter your conflict of interest statement in the “Confidential to Editor” section, and submit your "Accept" recommendation. Reviewer #1: (No Response) ********** 2. Is the manuscript technically sound, and do the data support the conclusions? The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented. Reviewer #1: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: I Don't Know ********** 4. Have the authors made all data underlying the findings in their manuscript fully available? The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified. Reviewer #1: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English? PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here. Reviewer #1: No ********** 6. Review Comments to the Author Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters) Reviewer #1: In the revised manuscript by Camougrand et al, the authors made modest changes to address concerns raised in their original submission. While I have my doubts that their purification strategy is effectively working (ie, a concern is that the oligomerized band is non-specifically cross-reacting with the anti-his antibody), the authors have now provided the requested data. However, it is somewhat glaring that the authors have now removed data from Figure 8 related to the ubiquitinated band they identified via proteomic analysis. They had previously generated two clonal lines of a K282A mutant, one of which showed no change in Atg32 turnover and the other which mildly stabilized Atg32 at the 8h timepoint. In the revised manuscript, the “negative” data is removed while “significantly (P<0.05) impaired” is added to the text. The authors should return “clone 1” to the manuscript for transparency purposes and graphically display the values that led to this conclusion. My other primary concern regarding lengthy treatment with MG-132 was not addressed. In their response, the authors write that “we did not present results from shorter than 24 hours in the presence of inhibitors, so we are not sure what led the reviewer to raise a concern that stabilization of Atg32 occurs only after long incubation times and may be an indirect effect.” This is exactly the point – because the authors do not examine other time points (for example, 1h, 2h, 4h) after MG-132 addition at 8h, they can only state that 16h of treatment leads to stabilization of Atg32 during stationary growth. While the authors now demonstrate that such treatment does not inhibit cell growth, they also cannot state whether the protein is acutely stabilized or stabilized as part of an adaptive cellular response to prolonged proteasomal inhibition. In exponentially growing cells, where there is no appreciable mitophagy, the authors use short-term MG132 treatment in combination with cycloheximide and observe a very modest inhibition of proteasomal turnover. So while the authors can conclude that Atg32 can be targeted to the proteasome during exponential growth, it is not clear that this is an acute cellular response to regulate mitophagy when cells reach stationary phase. If the authors are unwilling to perform new experiments, they must substantially improve the clarity of the manuscript and acknowledge the potential caveats and alternative explanations of their results. ********** 7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy. Reviewer #1: No [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step. |
| Revision 2 |
|
PONE-D-20-11526R2 The yeast mitophagy receptor Atg32 is ubiquitinated and degraded by the proteasome PLOS ONE Dear Dr. Camougrand: Thank you for your manuscript resubmission. I believe that the reviewer comments were addressed appropriately in your latest version, and I do not currently plan on sending the paper again to the reviewers. However, I have received the following guidance from the PLOS ONE staff: "PLOS ONE now requires that submissions reporting blots or gels include original, uncropped and unadjusted blot/gel image data in addition to complying with our image preparation guidelines described at https://journals.plos.org/plosone/s/figures#loc-blot-and-gel-reporting-requirements. The revised submission should include the raw blot/gel image data for your review, either in Supporting Information or via a public data repository; the Data Availability Statement should indicate where these data can be found. The original blot/gel image data should (1) represent unadjusted, uncropped images, (2) be provided for all blot/gel data reported in the main figures and Supporting Information, and (3) match the images in the manuscript figure(s). If you have any questions or concerns about the blot/gel data, or about the author’s compliance with the journal’s blot/gel reporting requirements, you can raise these in your next decision letter or email us at plosone@plos.org". Could you please follow up with a new version of the manuscript which complies with these guidelines? Also, I have the following minor comments on the manuscript: Page 24: MG-123 instead of MG-132. Page 25: 'Youle's lab' 'Levine's lab' - please seek a more formal way to address the work of these laboratories. Please submit your revised manuscript by Nov 26 2020 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:
If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter. If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols We look forward to receiving your revised manuscript. Kind regards, Cory D. Dunn, Ph.D. Academic Editor PLOS ONE [Note: HTML markup is below. Please do not edit.] [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step. |
| Revision 3 |
|
The yeast mitophagy receptor Atg32 is ubiquitinated and degraded by the proteasome PONE-D-20-11526R3 Dear Dr. Camougrand, We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements. Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication. An invoice for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org. If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org. Kind regards, Cory D. Dunn, Ph.D. Academic Editor PLOS ONE Additional Editor Comments (optional): Reviewers' comments: |
| Formally Accepted |
|
PONE-D-20-11526R3 The yeast mitophagy receptor Atg32 is ubiquitinated and degraded by the proteasome Dear Dr. Camougrand: I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department. If your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information please contact onepress@plos.org. If we can help with anything else, please email us at plosone@plos.org. Thank you for submitting your work to PLOS ONE and supporting open access. Kind regards, PLOS ONE Editorial Office Staff on behalf of Dr. Cory D. Dunn Academic Editor PLOS ONE |
Open letter on the publication of peer review reports
PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.
We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.
Learn more at ASAPbio .