Peer Review History

Original SubmissionAugust 25, 2020
Decision Letter - Eric Charles Dykeman, Editor

PONE-D-20-26741

BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage cluster FE

PLOS ONE

Dear Dr. Moberg Parker,

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.

==============================

Apologies for the long review process. I would be grateful if you could address the comments from both reviewers in the resubmission. Again, sorry for the delay.

==============================

Please submit your revised manuscript by Jan 24 2021 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:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.
  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.
  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled '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,

Eric Charles Dykeman, 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

https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2)  Thank you for stating the following in the Acknowledgments Section of your manuscript:

[This research was funded in part by the Microbiology, Immunology and Molecular Genetics Department, and the Dean of Life Sciences Division at UCLA.]

We note that you have provided funding information that is not currently declared in your Funding Statement. However, funding information should not appear in the Acknowledgments section or other areas of your manuscript. We will only publish funding information present in the Funding Statement section of the online submission form.

Please remove any funding-related text from the manuscript and let us know how you would like to update your Funding Statement. Currently, your Funding Statement reads as follows:

 [The author(s) received no specific funding for this work.]

Please include your amended statements within your cover letter; we will change the online submission form on your behalf.

[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: Yes

Reviewer #2: Yes

**********

2. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: N/A

Reviewer #2: Yes

**********

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: Yes

**********

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: Dear Editor,

The manuscript entitled “BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage cluster FE” is a very well written paper utilizing current methodologies to characterize the genome of phage BlueFeather and assign it to a cluster. The data are all very solid in support of the authors’ conclusions with regards to the classification of the phage. The in silico analyses seemed to be performed appropriately for what was being investigated. Again, the conclusions are in accordance with the data generated and presented.

In my opinion, however, the conclusion(s) of the paper is not scientifically novel nor important enough to warrant publication in PLOS One. The classification of a single phage to an already existing cluster does not provide sufficient scientific discovery for publication in this journal. A much deeper inquiry into how gene content similarities or dissimilarities would establish new clusters or reorganization of multiple phages would be helpful. Similar papers have classified many phage simultaneously to establish new phage clustering.

Thank you for the opportunity to comment.

Reviewer #2: Review of ‘BlueFeather, the singleton that wasn’t: Shared gene content analysis supports

expansion of Arthrobacter phage cluster FE’

Summary:

Clustering is used to categorize bacteriophages based upon genomic similarity. Previous analyses using nucleotide identity measures designated the novel Arthrobacter phage, BlueFeather, as a singleton indicating that it was not able to be clustered with other phages. This study investigated the use of gene content and amino acid conservation to cluster phage BlueFeather, as its small genome and extensive synteny with clustered phages warranted reevaluation of its designation. Characterization of BlueFeather in terms of plaque and phage morphology is also presented. The authors determined that shared gene content and amino acid conservation between BlueFeather and members of Cluster FI and Cluster FE and phylogenetic analysis using Splitstree warrant reclustering of BlueFeather and the current Cluster FI and Cluster FE phages into one cluster designated Cluster FE.

Due to the mosaic nature of bacteriophage genomes, clustering phages of a particular host can be challenging, especially if there are a limited number of sequenced phage genomes to work with. As the database of phage genomes has grown, the accuracy for clustering has improved, and for Arthrobacter phages, the number of sequenced phages available to evaluate in the initial publication 3 years ago was 46 while today there are 312 Arthrobacter phage genomes sequenced on phagesdb.com. In addition new tools and methods for evaluating genomic relationships have become available besides simply looking at nucleotide identity. Reevaluating cluster assignments is necessary, and in this case merging a singleton, BlueFeather, and Cluster FI phages with the Cluster FE phages is sound.

The authors presentation of their bioinformatic analyses used in this study is clear, and overall the article is well written. This data has not been published elsewhere, and conclusions presented are clear. The conclusions are supported by several different types of bioinformatic analyses making for a strong case for creation of a new Cluster FE and re-clustering of several phages. There are a few minor issues to address such as wording choices and clarification of plaque purifications, but these do not affect the overall conclusions. I recommend this article for publication.

Major issues: There are no major issues to address.

Minor issues: (listed in order of importance)

• Figure 1A: The plaques are difficult to see and are described as being 5mm in diameter though there is a mixture in plaques sizes on this plate. On pg 7, line 153-155, the figure is described as a plate produced from an infection using a picked plaque, so is this from purification steps before the high titer lysate was produced? Perhaps a clearer image of plaques from the lysate would be better and the plaques would be consistent in size. If plaques are variable in size for this phage, that is not uncommon and should be stated.

• Pg 9, line 219: In the text, Idaho has 34.18% shared gene content with BlueFeather while in Figure 4A itself it says that Idaho has 38.5% shared gene content with BlueFeather (though the text in the figure is hard to read in the pdf). These numbers should be consistent. 38.5% GCS would provide an even stronger argument for clustering BlueFeather with Idaho.

• Pg 5, line 96: A reference should be provided for phage purifications or details about the procedure should be included.

• Pg 6, line 126: may I suggest changing ‘whole amino acid sequences’ to ‘whole proteome amino acid sequences’ to clarify that the entire proteome was examined

• Pg 3, line 62: comma needed after phylogeny

• Pg 5, line 103: comma after (Philips, Amsterdam, Netherlands)

• Pg 10, line 228: comma between phages and which

• Pg 10, line 229: comma between 1 and were

• Pg 10, line 235: comma between phages and which

• Pg 10, line 236: comma between 1 and were

• Pg 16, line 373: may I suggest changing this sentence so that it flows better to ‘BlueFeather serves as yet another example of the highly intricate mosaic relationships which exist among phages and are a feature of the genetic landscape, making phage taxonomy an increasingly difficult task.’

**********

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.]

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 1

Response to Reviewer 1:

Thank you for the positive feedback regarding the writing, data, and analyses. We respectfully disagree with the reviewer’s suggestion that the conclusion is not scientifically novel or important enough for publication in PLOS ONE. In addition to reclassifying the novel phage BlueFeather from singleton to Cluster FE, this work did also result in the re-organization of the previously distinct Cluster FI into an expanded Cluster FE. Prior to this work, Arthrobacter phages were clustered using nucleotide identity as described by Klyczek et al. (2017), but now the Hatfull lab (which runs phagedb.org) has adopted the parameters we describe for clustering new Arthrobacter phages. We believe our paper has the strong scientific validity, methodology, and ethical standards necessary for publication in PLOS ONE, which doesn’t select articles based on perceived significance.

Response to Reviewer 2 (Minor Issues to Address):

• Figure 1A: The plaques are difficult to see and are described as being 5mm in diameter though there is a mixture in plaques sizes on this plate. On pg 7, line 153-155, the figure is described as a plate produced from an infection using a picked plaque, so is this from purification steps before the high titer lysate was produced? Perhaps a clearer image of plaques from the lysate would be better and the plaques would be consistent in size. If plaques are variable in size for this phage, that is not uncommon and should be stated.

Thank you for the suggestion, we went back and used ImageJ to calculate average plaque diameter (sentence added to methods at lines 99-100). A revised figure 1A has been submitted with an inset showing a magnification of the plaques, and a revised figure legend. The results section has been revised to reflect a more detailed description of plaque size and morphology variations (lines 150-153).

• Pg 9, line 219: In the text, Idaho has 34.18% shared gene content with BlueFeather while in Figure 4A itself it says that Idaho has 38.5% shared gene content with BlueFeather (though the text in the figure is hard to read in the pdf). These numbers should be consistent. 38.5% GCS would provide an even stronger argument for clustering BlueFeather with Idaho.

The GCS calculation was repeated confirming the 38.5% GCS for Phage Idaho (text updated in lines 221-223). The repeated analysis also indicated that the MaxGCDGap was between BlueFeather and Yavru (41.60%), rather than Whytu. The text (line 230), Figure 4b and legend have been revised.

• Pg 5, line 96: A reference should be provided for phage purifications or details about the procedure should be included.

Reference added at line 99.

• Pg 16, line 373: may I suggest changing this sentence so that it flows better to ‘BlueFeather serves as yet another example of the highly intricate mosaic relationships which exist among phages and are a feature of the genetic landscape, making phage taxonomy an increasingly difficult task.’

Thank you for the suggestion, the sentence has been edited.

The following suggested edits have been incorporated:

• Pg 3, line 62: comma needed after phylogeny

• Pg 5, line 103: comma after (Philips, Amsterdam, Netherlands)

• Pg 6, line 126: may I suggest changing ‘whole amino acid sequences’ to ‘whole proteome amino acid sequences’ to clarify that the entire proteome was examined

The suggested edits below change the meaning of the text, so the sentences were changed from “which exhibited” to “exhibiting” to improve clarity (lines 232 and 240).

• Pg 10, line 228: comma between phages and which

• Pg 10, line 229: comma between 1 and were

• Pg 10, line 235: comma between phages and which

• Pg 10, line 236: comma between 1 and were

We would like to thank Reviewer 2 for the detailed feedback, which helped improve the quality of our manuscript.

Attachments
Attachment
Submitted filename: Bluefeather Manuscript Response to Reviewers.docx
Decision Letter - Eric Charles Dykeman, Editor

BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage Cluster FE

PONE-D-20-26741R1

Dear Dr. Moberg Parker,

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,

Eric Charles Dykeman, Ph.D.

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

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: All comments have been addressed

Reviewer #2: All comments have been addressed

**********

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

Reviewer #2: Yes

**********

3. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

Reviewer #2: Yes

**********

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

Reviewer #2: 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: Yes

Reviewer #2: Yes

**********

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: Well written paper describing the reclassification of phage based on shared gene content analysis. The data fully support the authors' conclusions and the previous review improved some formatting and descriptive content in the paper.

Minor:

Line 26 delete 'shifting target' for 'challenge' or 'challenging task'.

Line 27 substitute Mycobacterium for Mycobacteria

Line 386 delete 'thus'

Reviewer #2: (No Response)

**********

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

Reviewer #2: No

Formally Accepted
Acceptance Letter - Eric Charles Dykeman, Editor

PONE-D-20-26741R1

BlueFeather, the singleton that wasn’t: Shared gene content analysis supports expansion of Arthrobacter phage Cluster FE

Dear Dr. Moberg Parker:

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. Eric Charles Dykeman

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 .