Peer Review History
| Original SubmissionAugust 30, 2025 |
|---|
|
Dear Dr. Alzate, 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. ============================== Both reviewers judged the study fairly conceived and scientifically relevant but the metagenomics approach to identify yeast species insufficiently robust and accurate. Sample set is also suggested to be broadened using cultivated taxa for comparison. Other issues are mostly related to the methodological clarifications or disagreements between the methodology and the obtained results. Hence, there are several major obstacles for this manuscript to be further considered for publication in this stage. I advise the authors to meticulously analyze both reviewers' reports and to thoroughly revise the manuscript, after additional experiments and analyses have been done. ============================== Please submit your revised manuscript by Dec 04 2025 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.
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: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols . We look forward to receiving your revised manuscript. Kind regards, Branislav T. Šiler, 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. In your Methods section, please provide additional information regarding the permits you obtained for the work. Please ensure you have included the full name of the authority that approved the field site access and, if no permits were required, a brief statement explaining why. 3. Please note that PLOS One has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, we expect all author-generated code to be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse. 4. We note that the grant information you provided in the ‘Funding Information’ and ‘Financial Disclosure’ sections do not match. When you resubmit, please ensure that you provide the correct grant numbers for the awards you received for your study in the ‘Funding Information’ section. 5. Thank you for stating the following financial disclosure: “AEPM This research was developed under the project: Experimental Development for the Competitiveness of the Coffee Sector of the Department of Quindío, code 2017000100099, financed by the General System of Royalties, Gobernación de Quindío in agreements signed with the National Colombian Coffee Growers Federation (Cenicafé—Crossref Funder ID 100019597). No. 002-of-2020.” Please state what role the funders took in the study. If the funders had no role, please state: "The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript." If this statement is not correct you must amend it as needed. Please include this amended Role of Funder statement in your cover letter; we will change the online submission form on your behalf. 6. Thank you for uploading your study's underlying data set. Unfortunately, the repository you have noted in your Data Availability statement does not qualify as an acceptable data repository according to PLOS's standards. At this time, please upload the minimal data set necessary to replicate your study's findings to a stable, public repository (such as figshare or Dryad) and provide us with the relevant URLs, DOIs, or accession numbers that may be used to access these data. For a list of recommended repositories and additional information on PLOS standards for data deposition, please see https://journals.plos.org/plosone/s/recommended-repositories . 7. 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. 8 If the reviewer comments include a recommendation to cite specific previously published works, please review and evaluate these publications to determine whether they are relevant and should be cited. There is no requirement to cite these works unless the editor has indicated otherwise. [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? Reviewer #1: Yes Reviewer #2: Partly ********** 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 Reviewer #1: Yes Reviewer #2: No ********** 4. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #1: Yes Reviewer #2: Yes ********** Reviewer #1: The paper entitled “Uncovering the Hidden Yeast Diversity in Fermented Coffee: Insights from a Shotgun Metagenomic Approach” by Katherine Bedoya-Urrego, Aida Esther Peñuela-Martínez, and Juan Fernando Alzate is an original descriptive study of fungal diversity in coffee fermentations. The paper is well-written, thoroughly analyzed, and clearly presented. Although there is a long tradition of studies focusing on the culturable fraction of fungi and metabarcoding of molecular marker DNA (ITS, ribosomal RNA genes) associated with various coffee bean fermentations, the metagenomic approach—understood as the sequencing of all genes and species present in a sample or habitat—represents a novel perspective in this field. The article is original and interesting; however, in its current version, the identification of yeasts based solely on metagenomic information is insufficient for publication in PLOS ONE (IF 2.6, Q1–Q2). The arguments supporting this opinion are presented below. If the authors are able to enlarge the genomic and metagenomic analyses, the paper could be reconsidered. In my opinion, the study would have been strengthened by including genomes from the cultivable fungal fraction. This information could help confirm the relative abundance of each species, improve species-level identifications, and enable the investigation of important genes related to relevant phenotypic traits during mixed coffee fermentation, among other opportunities. I understand that there may be limitations in achieving species-level identification; however, in some cases, species belonging to certain clades are not mentioned. In addition to phylogenomic analyses, species-level identification should be further supported by ANI and AAI estimates, in silico DNA–DNA hybridization, and other complementary analyses. If the authors consider it appropriate and the results suggest the discovery of a potential new species, they could mention this possibility without committing to a formal description. Beyond taxonomic analyses, the study does not fully exploit the large amount of data generated to perform comparative genomic analyses among the identified yeast species. Such analyses could provide insights into the role of widely distributed yeast species in coffee bean fermentation. Furthermore, no genes or metabolic pathways relevant to fermentation—such as extracellular enzymes, carbohydrate assimilation, secondary metabolites, fermentation metabolism, and other functional aspects—are highlighted. If the metagenomic work is intended to remain descriptive, it should also include bacterial and archaeal communities or microbiomes. It would also be valuable to compare the presence or absence of fungal genera detected by similar or different approaches in previous coffee fermentation studies with those identified in this work. In Figure 4, sequences corresponding to several animals such as Dendroctonus, Caenorhabditis, Callosobruchus, and probably Drosophila are reported. This likely reflects an issue with inadequate data filtering. Please provide an explanation. For instance, Dendroctonus is a conifer bark beetle. I consider that Figures 1, 2, 3, and 9 should be moved to the supplementary material section, as they only present quality analyses of massive sequencing. Regarding taxonomic assignments (Fig. 4): Taxonomic assignment using MEGA alone is quite limited, as it relies on outdated databases. It is therefore recommended to use more updated and robust tools such as QIIME2 (https://library.qiime2.org/quickstart/moshpit). Minor details: Line 114: Change −20 °C to −20°C (no space between the number and unit). Lines 722–723: Debaryomycetaceae sp. — the term “sp.” is unnecessary. Finally, regarding omics approaches to explore the coffee fermentation microecosystem and its effects on cup quality, I believe that some important works that could strengthen the research’s international context are missing from the introduction or discussion. Reviewer #2: Summary Bedoya-Urrego et al. apply shotgun metagenomics, binning, and a phylogenomic framework based on a large set of single-copy proteins to profile Saccharomycotina yeasts in spontaneous Colombian coffee fermentations. The abstract reports 24 yeast MAGs (later 22 after filtering), dominated by Pichia kluyveri, with additional Hanseniaspora, Torulaspora, and Kurtzmaniella lineages and putative novel taxa. The study is timely and relevant; however, key reporting gaps (eukaryotic MAG quality control), internal inconsistencies (counts; assembly strategy), and methodological ambiguities prevent full evaluation. Major revisions 1. Eukaryotic MAG quality control not reported The manuscript does not present per-MAG completeness/duplication (e.g., BUSCO) or contamination estimates (e.g., EukCC), nor a MAG-level QC table. This is core to genome-resolved metagenomics. Please report for each MAG: BUSCO lineage/version with C/F/M/D %, an explicit contamination estimate (e.g., EukCC), size, N50, scaffold count, GC%, median depth, and breadth. 2. Workflow clarity: per-sample assemblies vs. co-assembly Results describe one assembly per sample; Methods describe mapping to co-assembled scaffolds. These are presented as a single workflow though they are distinct. Please state unambiguously which assembly underlies binning, coverage, and figures (per-sample, co-assembly, or both) and align text/metrics accordingly. 3. Counts and tallies disagree Abstract: 24 MAGs; species-level tallies sum to 22; one sentence mentions removal of a single MAG (would total 23). Please reconcile counts across Abstract, Results, legends, and supplements. 4. Read handling for MEGAN is misdescribed Reads are said to be “merged into longer single-end reads using “seqtk”,” which does not generate longer consensus reads. The manuscript also alternates between MEGAN on reads vs. on scaffolds. Please correct the tool description and specify whether MEGAN used reads or scaffolds, which classifier/database (e.g., DIAMOND + NR; version/date), and LCA parameters. 5. Abundance is visualized but not quantified A length-vs-depth scatterplot is presented as “relative abundance,” but no explicit metric or presence threshold is provided. Please provide a per-sample, per-MAG abundance table (e.g., reads mapped per kb; TPM/RPKM) and breadth thresholds for presence. 6. Host (Coffea) depletion undocumented Plant sequences are acknowledged; no reference genome, mapping criteria, or % removed are reported. Please specify the Coffea reference(s), filtering criteria, and per-sample host removal summary. 7. Phylogenomic model scope vs. claims Deep-rank statements (e.g., family non-monophyly) are paired with uniformly high UFB support under a single model description. Please either provide a brief robustness check (partitioning and/or site-heterogeneous model) or temper claims; indicate whether key placements are model-stable. Methodological clarifications BLASTN thresholds. “E-value = 0” and “bitscore > 10,000” are not biologically interpretable cutoffs. Define alignment length, % identity, and coverage criteria; indicate whether reciprocal hits or AAI/ortholog identity supported species calls. Rank terminology. The text refers to “class-level” structure while listing “-ales” groups (orders). Harmonize rank labels with current taxonomy. Software versions/commands. Resolve the Cutadapt version mismatch (“version 3” vs “v2.10” in parameters). Provide exact versions and key command lines (trimming, assembly, binning, mapping, phylogeny) in Supplementary Methods. Other Flavor/functional claims. Several passages imply causal impacts on sensory outcomes; no metabolomics/sensory data are presented. Either add minimal genomic context (e.g., presence/absence of ester/pectinase loci per MAG) or consistently frame these as literature-based hypotheses. “Megan sequencing depth” → mean sequencing depth. “CF15 showed two distinct species of Hanseniaspora.” Consistent capitalization (MEGAN), consistent “phylogenomics” wording, report “UFBoot support = 100%”. Avoid mixing CFxx and Fxx for the same batches; provide a simple crosswalk table. ********** 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: Yes: César Hernández-Rodríguez 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 ensure your figures meet our technical requirements, please review our figure guidelines: https://journals.plos.org/plosone/s/figures You may also use PLOS’s free figure tool, NAAS, to help you prepare publication quality figures: https://journals.plos.org/plosone/s/figures#loc-tools-for-figure-preparation. NAAS will assess whether your figures meet our technical requirements by comparing each figure against our figure specifications. |
| Revision 1 |
|
Dear Dr. Alzate, 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. Several minor, mostly technical omissions still remained in the revised manuscript. Please address them as suggested by Reviewer #2. Please submit your revised manuscript by Feb 25 2026 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.
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: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols . We look forward to receiving your revised manuscript. Kind regards, Branislav T. Šiler, Ph.D. Academic Editor PLOS One Journal Requirements: If the reviewer comments include a recommendation to cite specific previously published works, please review and evaluate these publications to determine whether they are relevant and should be cited. There is no requirement to cite these works unless the editor has indicated otherwise. Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice. [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #2: (No Response) ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #2: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #2: Yes ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #2: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #2: Yes ********** Reviewer #2: Thank you for the thorough revision. The manuscript is substantially improved and most major concerns have been addressed (workflow clarity, MAG counts, MEGAN read handling, and inclusion of per-MAG BUSCO and TPM outputs in the Supplementary material). The study is timely and the phylogenomic framework is a strength. A small number of points still need tightening before acceptance: (i) please add an explicit MAG contamination estimate (e.g., EukCC or comparable) and consider reporting read-mapping breadth to each MAG (breadth can be calculated against the MAG scaffolds themselves, not only against external references); (ii) resolve remaining reproducibility inconsistencies (notably the Cutadapt version mismatch) and ensure database/version/date details are complete; (iii) revise the BLAST screening description to include interpretable criteria (alignment length, % identity, and coverage), even if phylogenomics is the primary basis for species assignment; and (iv) harmonize taxonomic rank terminology and ensure any residual “non-monophyly” language is tempered unless supported by robustness checks. With these minor clarifications, I would support publication. ********** 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 #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 ensure your figures meet our technical requirements, please review our figure guidelines: https://journals.plos.org/plosone/s/figures You may also use PLOS’s free figure tool, NAAS, to help you prepare publication quality figures: https://journals.plos.org/plosone/s/figures#loc-tools-for-figure-preparation. NAAS will assess whether your figures meet our technical requirements by comparing each figure against our figure specifications. |
| Revision 2 |
|
Uncovering the Hidden Yeast Diversity in Fermented Coffee: Insights from a Shotgun Metagenomic Approach PONE-D-25-47268R2 Dear Dr. Alzate, 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 will be generated when your article is formally accepted. Please note, if your institution has a publishing partnership with PLOS and your article meets the relevant criteria, all or part of your publication costs will be covered. Please make sure your user information is up-to-date by logging into Editorial Manager at Editorial Manager® and clicking the ‘Update My Information' link at the top of the page. For questions related to billing, please contact billing support . 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, Branislav T. Šiler, Ph.D. Academic Editor PLOS One Additional Editor Comments (optional): Reviewers' comments: |
| Formally Accepted |
|
PONE-D-25-47268R2 PLOS One Dear Dr. Alzate, I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS One. Congratulations! Your manuscript is now being handed over to our production team. At this stage, our production department will prepare your paper for publication. This includes ensuring the following: * All references, tables, and figures are properly cited * All relevant supporting information is included in the manuscript submission, * There are no issues that prevent the paper from being properly typeset You will receive further instructions from the production team, including instructions on how to review your proof when it is ready. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few days to review your paper and let you know the next and final steps. Lastly, 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. You will receive an invoice from PLOS for your publication fee after your manuscript has reached the completed accept phase. If you receive an email requesting payment before acceptance or for any other service, this may be a phishing scheme. Learn how to identify phishing emails and protect your accounts at https://explore.plos.org/phishing. If we can help with anything else, please email us at customercare@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. Branislav T. Šiler 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 .