Peer Review History

Original SubmissionJune 11, 2025
Decision Letter - Matteo Bodini, Editor

PONE-D-25-31659

ANCHOLIK-NER: A Benchmark Dataset for Bangla Regional Named Entity Recognition

PLOS ONE

Dear Dr. Muhammad,

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.

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.

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

Matteo Bodini, 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. 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.

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

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

Additional Editor Comments:

The manuscript presents a valuable and technically sound contribution to Bangla regional NER. For acceptance, the authors should include entity-wise F1 scores, per-dialect confusion matrices, and comparisons with existing Bangla NER datasets or LLM-based baselines. An error analysis and confirmation of full data availability are also required. Minor improvements to the abstract, figures, and language are recommended.

[Note: HTML markup is below. Please do not edit.]

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

Reviewer #3: Yes

**********

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

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: 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: No

Reviewer #2: Yes

Reviewer #3: 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

Reviewer #3: 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: The authors present a real and underexplored challenge NER in Bangla regional dialects—which is often ignored in NLP due to data scarcity and linguistic diversity.

Creation of ANCHOLIK-NER is a useful resource contribution for the Bangla NLP community.: The annotation process, pre-processing, and evaluation are well explained with detailed steps and illustrative figures. They use standard BIO tagging and Cohen’s Kappa for inter-annotator agreement, enhancing transparency.

The evaluation with three transformer-based models (Bangla BERT, Bangla BERT Base, and Multilingual BERT) provides a sound baseline for future benchmarking.

While the dataset is new, methodologically, the work is largely a synthesis of established practices: standard BIO annotation, off-the-shelf BERT models, and conventional metrics.

The paper overstates novelty in model usage, even though the models are not fine-tuned innovatively or modified for dialectal handling (e.g., no dialect-aware pretraining or adapters). Authors should also try some LLMs, so they can show performance with discriminative models like BERT and generative models like llama, mistral as in https://link.springer.com/article/10.1007/s10115-024-02321-1, which is a comparative stuy.

No error analysis or detailed per-entity-type performance is included. For instance, which entity types (e.g., FOOD, ROLE, REL) are harder for the models across dialects? This is essential given the known imbalance.

Performance variance across regions is acknowledged (e.g., Chittagong underperforms), but no linguistic or statistical explanation is provided. Lack of baseline comparison against prior Bangla NER datasets like B-NER, BNLP, or IndicNER makes it difficult to quantify improvements.

The class distribution is highly skewed but no strategies (e.g., re-weighting, data augmentation, few-shot adaptation) are explored to address this.

There is no discussion on token overlap across dialects. Are some dialects lexically closer to Standard Bangla, making the task easier?

No attempt is made to adapt or augment models for dialect-specific tokens, even though dialect lexical gaps (e.g., merged/missing tokens) are acknowledged.

Use of multilingual BERT for dialect variation is questionable, as it is not tuned for intra-language dialectal variance, which limits its effectiveness.

The manuscript suffers from verbose repetition, and in places, casual phrasing like "going strong" or "real world variability" weakens the scientific tone.

Figures and Tables are numerous and informative but not always referenced or discussed sufficiently in the text.

Typographic errors (e.g., “Bangla Bert” instead of “Bangla BERT”) and inconsistent punctuation should be cleaned up.

Identify common failure modes per dialect or entity class. Is there confusion between FOOD vs. OBJ? LOC vs. ORG? Compare model performance with existing Bangla NER datasets if exists or use LLM based baselines to contextualize results.

Explore re-weighting or data augmentation to address class imbalance.

report entity-wise F1 scores and per-dialect confusion matrices.

overall, the dataset is a meaningful contribution to Bangla NLP, but the methodological novelty is limited, and the evaluation lacks analytical depth.

Reviewer #2: This is a great contribution to the researchers that are using language models in their research. Moreover, with LLMs and GenAI continuous developing, this NER dataset will help the models develop more accordingly, resulting in more accessibility for those in regions that use dialets. The authors could have emhasized these implications more in their conclusion. Thank you for the great work!

Reviewer #3: Dialectal variation is a core weakness of LLMs. Modern LLMs (even multilingual ones) still perform poorly on regional dialects. Fine-tuning or building benchmarks like ANCHOLIK-NER helps identify and quantify those weaknesses systematically.

This study makes a valuable contribution to the field for an important set of dialects. The authors identify the key problem, namely that existing Bangla NER models are trained on small or synthetic datasets, resulting in poor performance in many real-world contexts. The paper also serves as a model to follow for other sets of dialects.

The abstract should present a summary of other results, something along the lines of what is found on page 22 (“The results show that Bangla BERT performed best in the Mymensingh region, achieving the highest F1-score of 82.268% at epoch 20. In Barishal, it also performed well, reaching an F1-score of 81.481% at epoch 20. Sylhet and Noakhali showed moderate performance, with Sylhet achieving a peak F1-score of 78.754% at epoch 20, and Noakhali reaching 78.497% at epoch 20. The Chittagong region, however, showed relatively lower performance compared to the other regions, with the highest F1-score of 75.307% at epoch 20. Overall, Bangla BERT demonstrated strong performance, with its highest F1-scores observed in Mymensingh and Barishal.”)

Minor language errors exist (“it’s” instead of “its”, for example) but overall the paper is well written, carefully organized and systematically presented. Statistical analyses are appropriate. Conclusions are supported by the data.

Figures 6 and 8 are too small to read properly.

**********

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

Reviewer #3: 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

Additional Editor Comments: The manuscript presents a valuable and technically sound contribution to Bangla regional NER. For acceptance, the authors should include entity-wise F1 scores, per-dialect confusion matrices, and comparisons with existing Bangla NER datasets or LLM-based baselines. An error analysis and confirmation of full data availability are also required. Minor improvements to the abstract, figures, and language are recommended.

Response: We appreciate the editor’s feedback. In the revised manuscript we have addressed all the issues.

Reviewer #1

Comment-1: While the dataset is new, methodologically, the work is largely a synthesis of established practices: standard BIO annotation, off-the-shelf BERT models, and conventional metrics. The paper overstates novelty in model usage, even though the models are not fine-tuned innovatively or modified for dialectal handling (e.g., no dialect-aware pretraining or adapters).

Response: We appreciate the reviewer’s observation. Our study does not aim to introduce new model architectures but rather to benchmark existing pretrained transformer models on Bangla regional dialects. This approach ensures reproducibility and isolates the dataset’s contribution to performance. Accordingly, we have revised the Introduction and Methodology section to clarify that pretrained models were used for fine-tuning and evaluation, emphasizing benchmarking over model innovation.

Comment-2: Authors should also try some LLMs, so they can show performance with discriminative models like BERT and generative models like llama, mistral as in https://link.springer.com/article/10.1007/s10115-024-02321-1, which is a comparative study.

Response: We thank the reviewer for this valuable suggestion. We agree that evaluating large generative LLMs (e.g., LLaMA, Mistral) would provide an interesting complementary perspective. However, conducting such experiments requires substantial computational resources and inference tokens, which were beyond the feasible scope of the present study. To maintain reproducibility, uniform training conditions, and consistent baseline comparison, we focused on fine-tuning openly available discriminative transformer models commonly used in Bangla NLP research.

We have now clarified this in the Limitations and Future Work section and added a note that benchmarking large generative LLMs on ANCHOLIK-NER is a promising direction for future expansion of the dataset’s benchmark suite.

Comment-3: No error analysis or detailed per-entity-type performance is included. For instance, which entity types (e.g., FOOD, ROLE, REL) are harder for the models across dialects? This is essential given the known imbalance.

Response: We thank the reviewer for this observation. We have now added a dedicated error analysis section that includes detailed per-entity F1-scores across all five dialects. This analysis clearly identifies which entity types are harder (e.g., ANI, ROLE, ORG) and which are easier (e.g., FOOD, LOC, REL), directly addressing imbalance-related performance differences.

Comment-4: Performance variance across regions is acknowledged (e.g., Chittagong underperforms), but no linguistic or statistical explanation is provided. Lack of baseline comparison against prior Bangla NER datasets like B-NER, BNLP, or IndicNER makes it difficult to quantify improvements.

Response: We appreciate the reviewer’s suggestion regarding baseline comparison. However, the cited datasets (B-NER, BNLP, and IndicNER) are designed for Standard Bangla and do not account for regional or dialectal variation. As our dataset focuses exclusively on Bangla regional dialects, direct comparison with Standard Bangla benchmarks would not be methodologically appropriate due to differences in domain, linguistic distribution, and annotation schema.

Comment-5: The class distribution is highly skewed but no strategies (e.g., re-weighting, data augmentation, few-shot adaptation) are explored to address this.

Response: We appreciate this suggestion. In response, we conducted an additional experiment using class-weighted loss on Bangla BERT to directly address the skewed class distribution. We have added a new subsection describing this approach along with updated entity-wise results and confusion matrices. This provides insight into how re-weighting affects minority entity types.

Comment-6: There is no discussion on token overlap across dialects. Are some dialects lexically closer to Standard Bangla, making the task easier?

Response: We thank the reviewer for this feedback. We have now added a discussion that examines lexical similarity across dialects and its impact on model performance. Dialects closer to Standard Bangla (e.g., Barishal, Mymensingh) show higher scores, while those with greater lexical divergence (e.g., Chittagong, Noakhali) exhibit more errors. This explanation has been incorporated into the revised manuscript.

Comment-7: No attempt is made to adapt or augment models for dialect-specific tokens, even though dialect lexical gaps (e.g., merged/missing tokens) are acknowledged.

Response: We thank the reviewer for pointing this out. The current study intentionally did not modify pretrained transformer models to handle dialect-specific lexical variations such as merged, missing, or regionally altered tokens. Our goal was to benchmark existing models on the ANCHOLIK-NER dataset in a controlled and reproducible manner, isolating the contribution of the dataset itself to model performance. We have clarified this choice in the Methodology section by noting that all models were fine-tuned using their default tokenizers and vocabularies. Additionally, we have added a discussion in the Conclusion and Future Work section acknowledging this limitation and highlighting future directions, including dialect-aware tokenization, vocabulary extension, and adapter- or LoRA-based fine-tuning to better capture region-specific lexical patterns.

Comment-8: Use of multilingual BERT for dialect variation is questionable, as it is not tuned for intra-language dialectal variance, which limits its effectiveness.

Response: We thank the reviewer for this insightful observation. To address this point and clarify our methodological rationale, we have added a new Discussion section. This section explains the inclusion of multilingual BERT as a cross-lingual baseline, interprets the performance differences across dialects, and discusses broader implications for dialect-aware LLMs and future research.

Comment-9: The manuscript suffers from verbose repetition, and in places, casual phrasing like "going strong" or "real world variability" weakens the scientific tone.

Response: We thank the reviewer for this valuable observation. We have thoroughly reviewed the manuscript to remove redundant expressions and improve academic tone throughout the text. Informal phrases such as “going strong” and “real world variability” have been replaced with formal equivalents.

Comment-10: Figures and Tables are numerous and informative but not always referenced or discussed sufficiently in the text. Typographic errors (e.g., “Bangla Bert” instead of “Bangla BERT”) and inconsistent punctuation should be cleaned up.

Response: We thank the reviewer for this valuable feedback. We have revised the manuscript to ensure that all Figures and Tables are now clearly referenced and discussed in the corresponding sections. In addition, all typographic inconsistencies, including capitalization errors such as “Bangla Bert,” and punctuation issues have been carefully corrected throughout the manuscript to improve readability and presentation quality.

Comment-11: Identify common failure modes per dialect or entity class. Is there confusion between FOOD vs. OBJ? LOC vs. ORG?

Response: We thank the reviewer for this encouraging feedback We have now analyzed all dialect-specific confusion matrices and identified recurrent failure modes. The revised manuscript includes a clear description of common misclassification patterns.

Reviewer #2

Comment-1: This is a great contribution to the researchers that are using language models in their research. Moreover, with LLMs and GenAI continuous development, this NER dataset will help the models develop more accordingly, resulting in more accessibility for those in regions that use dialects. The authors could have emphasized these implications more in their conclusion. Thank you for the great work!

Response: We thank the reviewer for their encouraging feedback and insightful suggestion. In the revised manuscript, we have expanded the conclusion to emphasize the broader implications of ANCHOLIK-NER for large language models (LLMs), generative AI, and linguistic inclusivity.

Reviewer #3

Comment-1: The abstract should present a summary of other results, something along the lines of what is found on page 22 (“The results show that Bangla BERT performed best in the Mymensingh region, achieving the highest F1-score of 82.268% at epoch 20. In Barishal, it also performed well, reaching an F1-score of 81.481% at epoch 20. Sylhet and Noakhali showed moderate performance, with Sylhet achieving a peak F1-score of 78.754% at epoch 20, and Noakhali reaching 78.497% at epoch 20. The Chittagong region, however, showed relatively lower performance compared to the other regions, with the highest F1-score of 75.307% at epoch 20. Overall, Bangla BERT demonstrated strong performance, with its highest F1-scores observed in Mymensingh and Barishal.”)

Response: We thank the reviewer for this helpful suggestion. In the revised manuscript, we have updated the Abstract to include a concise summary of region-wise F1-scores and comparative model performance, ensuring that key quantitative results are clearly presented upfront.

Comment-2: Minor language errors exist (“it’s” instead of “its”, for example) but overall the paper is well written, carefully organized and systematically presented. Statistical analyses are appropriate. Conclusions are supported by the data.

Response: We thank the reviewer for the positive feedback and kind remarks regarding the overall organization and presentation of our manuscript. All identified language errors, including instances such as the incorrect use of “it’s” instead of “its,” have been carefully corrected throughout the revised version.

Comment-3: Figures 6 and 8 are too small to read properly.

Response: We appreciate the reviewer’s observation. In the revised manuscript, Figures 6 and 8 have been resized and reformatted to ensure improved readability and visual clarity.

Attachments
Attachment
Submitted filename: Response to Reviewers.pdf
Decision Letter - Joanna Tindall, Editor

ANCHOLIK-NER: A Benchmark Dataset for Bangla Regional Named Entity Recognition

PONE-D-25-31659R1

Dear Dr. Muhammad,

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,

Joanna Tindall, PhD

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

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

Reviewer #3: Yes

**********

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

Reviewer #2: Yes

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

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

Reviewer #3: 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 #2: The research team made efforts to address the feedbacks from the initial review. Through this process the paper is in a much better place and I fully recommend this paper to be accepted.

Reviewer #3: All my comments have been adequately addressed. The paper is ready for publication, in my view. The authors have been very responsive.

**********

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 #2: No

Reviewer #3: No

**********

Formally Accepted
Acceptance Letter - Joanna Tindall, Editor

PONE-D-25-31659R1

PLOS One

Dear Dr. Muhammad,

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 Joanna Tindall

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