Peer Review History
| Original SubmissionJuly 28, 2025 |
|---|
|
Dear Dr. Tesfaye, Please submit your revised manuscript by %DATE_REVISION_DUE. 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, Mourad Mahmoud 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 the online submission form, you indicated that [The data that support the findings of this study are available from the corresponding author upon reasonable request.]. All PLOS journals now require all data underlying the findings described in their manuscript to be freely available to other researchers, either 1. In a public repository, 2. Within the manuscript itself, or 3. Uploaded as supplementary information. This policy applies to all data except where public deposition would breach compliance with the protocol approved by your research ethics board. If your data cannot be made publicly available for ethical or legal reasons (e.g., public availability would compromise patient privacy), please explain your reasons on resubmission and your exemption request will be escalated for approval. 3. When completing the data availability statement of the submission form, you indicated that you will make your data available on acceptance. We strongly recommend all authors decide on a data sharing plan before acceptance, as the process can be lengthy and hold up publication timelines. Please note that, though access restrictions are acceptable now, your entire data will need to be made freely accessible if your manuscript is accepted for publication. This policy applies to all data except where public deposition would breach compliance with the protocol approved by your research ethics board. If you are unable to adhere to our open data policy, please kindly revise your statement to explain your reasoning and we will seek the editor's input on an exemption. Please be assured that, once you have provided your new statement, the assessment of your exemption will not hold up the peer review process. 4. Your ethics statement should only appear in the Methods section of your manuscript. If your ethics statement is written in any section besides the Methods, please move it to the Methods section and delete it from any other section. Please ensure that your ethics statement is included in your manuscript, as the ethics statement entered into the online submission form will not be published alongside your manuscript. 5. We note that Figure 1 in your submission contain [map/satellite] images which may be copyrighted. All PLOS content is published under the Creative Commons Attribution License (CC BY 4.0), which means that the manuscript, images, and Supporting Information files will be freely available online, and any third party is permitted to access, download, copy, distribute, and use these materials in any way, even commercially, with proper attribution. For these reasons, we cannot publish previously copyrighted maps or satellite images created using proprietary data, such as Google software (Google Maps, Street View, and Earth). For more information, see our copyright guidelines: http://journals.plos.org/plosone/s/licenses-and-copyright. We require you to either (1) present written permission from the copyright holder to publish these figures specifically under the CC BY 4.0 license, or (2) remove the figures from your submission: 1. You may seek permission from the original copyright holder of Figure(s) [#] to publish the content specifically under the CC BY 4.0 license. We recommend that you contact the original copyright holder with the Content Permission Form (http://journals.plos.org/plosone/s/file?id=7c09/content-permission-form.pdf) and the following text: “I request permission for the open-access journal PLOS ONE to publish XXX under the Creative Commons Attribution License (CCAL) CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). Please be aware that this license allows unrestricted use and distribution, even commercially, by third parties. Please reply and provide explicit written permission to publish XXX under a CC BY license and complete the attached form.” Please upload the completed Content Permission Form or other proof of granted permissions as an "Other" file with your submission. In the figure caption of the copyrighted figure, please include the following text: “Reprinted from [ref] under a CC BY license, with permission from [name of publisher], original copyright [original copyright year].” 2. If you are unable to obtain permission from the original copyright holder to publish these figures under the CC BY 4.0 license or if the copyright holder’s requirements are incompatible with the CC BY 4.0 license, please either i) remove the figure or ii) supply a replacement figure that complies with the CC BY 4.0 license. Please check copyright information on all replacement figures and update the figure caption with source information. If applicable, please specify in the figure caption text when a figure is similar but not identical to the original image and is therefore for illustrative purposes only. The following resources for replacing copyrighted map figures may be helpful: USGS National Map Viewer (public domain): http://viewer.nationalmap.gov/viewer/ The Gateway to Astronaut Photography of Earth (public domain): http://eol.jsc.nasa.gov/sseop/clickmap/ Maps at the CIA (public domain): https://www.cia.gov/library/publications/the-world-factbook/index.html and https://www.cia.gov/library/publications/cia-maps-publications/index.html NASA Earth Observatory (public domain): http://earthobservatory.nasa.gov/ Landsat: http://landsat.visibleearth.nasa.gov/ USGS EROS (Earth Resources Observatory and Science (EROS) Center) (public domain): http://eros.usgs.gov/# Natural Earth (public domain): http://www.naturalearthdata.com/ 6. 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. 7. 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. Additional Editor Comments (if provided): [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: Yes ********** 2. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #1: Yes Reviewer #2: Yes ********** 3. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #1: Yes Reviewer #2: Yes ********** 4. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #1: Yes Reviewer #2: Yes ********** Reviewer #1: Hemoglobin polymorphism in different blood levels of Ethiopian Zebu × Holstein Friesian crossbred dairy cattle: The article is well articulated but lacks a clearly defined conclusion and recommendations based on the results. Recommendations Breeding Programs: Incorporate hemoglobin polymorphism as one of the genetic markers in selection strategies for crossbred dairy cattle to balance productivity with adaptability. Health Monitoring: Further studies should examine associations between Hb genotypes and disease resistance, metabolic efficiency, and milk yield to guide herd management. Environmental Adaptation: Since Hb variants may contribute to tolerance against hypoxia and heat stress, future crossbreeding strategies should consider hemoglobin types in relation to regional agro-ecologies. Expanded Research: Larger sample sizes and molecular characterization of Hb genes are recommended to validate the observed polymorphism and its practical implications for genetic improvement of dairy cattle in Ethiopia. Farmer Awareness: Extension programs should raise awareness among farmers about the potential role of genetic markers, including hemoglobin polymorphism, in improving crossbred cattle performance. Reviewer #2: PONE-D-25-40346 Haemoglobin polymorphism 1 in different blood levels of Ethiopian Zebu x Holstein Friesian crossbred dairy cattle Abstract 1. Line 24–25: Misinterpretation of FIS values. FIS= 0.38 and 0.41 are described as “inbreeding coefficient value of the HF crosses relative to the subpopulations grouped into…”, but FISis not a single value per grouping type—it should be one estimate per subpopulation or an average, not two separate values for “blood levels” and “locations” without clarifying they are separate analyses. 2. Line 26–27: States FST = 0.01 for location and 0.06 for blood level, implying higher genetic differentiation among blood levels—but FST = 0.06 is still very low (near panmixia), yet the phrasing may mislead readers into overinterpreting biological significance. 3. Line 29–30: Concludes a “relatively higher level of similitude” based on low heterozygosity and high homozygosity—this is contradictory: high homozygosity suggests low genetic variation, not necessarily “similitude” across groups. The term is vague and scientifically imprecise. Introduction 4. Line 57: Calls hemoglobin an “evergreen red protein”— non-scientific, metaphorical language inappropriate for a research manuscript. 5. Line 68–69: States only “a few research works” on Hb polymorphism in Ethiopia, citing Gezahegn (1996) and Pal & Mummed (2014)—but Pal & Mummed (2014) studied Ogaden cattle, not general Ethiopian breeds. This misrepresents scope. 6. Line 77–78: Asserts protein polymorphism studies are “easier to implement” than DNA-based methods—but this is context-dependent and outdated (e.g., PCR-based genotyping is now cheaper and more accessible than electrophoresis in many settings). 7. Line 85–86: Hypothesis states Hb frequencies “are under Hardy-Weinberg equilibrium”—but HWE is a null model, not a hypothesis to be confirmed; appropriate phrasing would be testing deviation from HWE. Materials and Methods 8. Line 120–122: Claims 13 cows per blood level per location → 3 blood levels × 3 locations × 13 = 117, which is correct—but later tables report genotype counts that don’t sum correctly (e.g., Table 1: HF87.5% shows 38+1+0 = 39, but 13 per location would be 39 total—OK), yet Table 2 totals per location (e.g., SHA: 35+3+1=39) seem consistent, so this is not an error, but potential confusion arises. 9. Line 140–143: Uses carbon tetrachloride (CCl4) for hemolysate prep—CCl4 is highly toxic, carcinogenic, and largely obsolete in modern labs. No safety or ethical justification provided despite known hazards. 10. Line 147–148: Uses agarose gel electrophoresis at pH 8.6 for Hb typing—standard practice uses starch or cellulose acetate gels, not agarose, for Hb isoform separation. Agarose has poor resolution for small charge differences in globins—methodologically questionable. 11. Line 155–157: Assigns fast band = HbBB, slow = HbAA—but in cattle, HbB is typically the slow-migrating variant (contrary to human HbS). Literature (e.g., Bachmann et al. 1978) shows HbB (Zebu) migrates slower than HbA (taurine). Likely misassignment of allele identity. Results 12. Table 1, HF87.5% row: Expected HbBB = 0, observed = 0—but Chi-square value listed as “1.0ns”—this is mathematically impossible if expected = observed = 0. Likely a software or transcription error. 13. Table 1, Entire population: Observed HbAB = 13, expected = 22.4 → large deviation, Chi-square = 0.00 (p < 0.001)—but 0.00 is not a valid Chi-square value; probably means p = 0.00, but mislabeled. 12. Table 3: Expected heterozygosity (He) for HF50% = 0.32, Observed (Ho) = 0.18 → deficit of heterozygotes, consistent with inbreeding—but no statistical test (e.g., FIS per group) is provided in table, only pooled. 13. Table 5: Genetic identity >1.0 (e.g., HF50% vs HF50% = 1.0, OK—but HF75% vs HF75% = -0.99? Negative identity? Impossible—values must be 0–1. Typo: likely 0.99, not -0.99. 14. Table 6: SHA vs SHA = -1.0—again, identity cannot be negative. Should be 1.0. Formatting error (hyphen misread as minus). 15. Line 263–265: Reports FST= 0.01 (locations) as “significant” and FST= 0.06 (blood levels) as “non-significant”—but no p-values or confidence intervals provided to support “significance” claims. Discussion 16. Line 294–295: Claims “highest frequency HbB was observed in HF50%”—but Table 1 shows HbB freq = 0.19 in HF50%, 0.12 in HF75%, 0.01 in HF87.5%—so correct, but then implies HbB is Zebu-associated, which aligns with literature. However, if allele labeling is inverted (see point 12), this conclusion collapses. 17. Line 306–307: Links HbA frequency to altitude—but Shashemene (1900–1950 m), Hawassa (1750 m), Dilla (1300–2500 m)—yet Dilla has lowest HbA (0.85) vs SHA (0.94). Contradicts the claim. 18. Line 316–317: States “average heterozygosity of 0.1”—but Table 3 shows pooled Ho = 0.11, close—but then compares to “recommended range 0.3–0.8”— no citation for this arbitrary “recommended” range. Genetic diversity expectations depend on species and marker type; for single-locus protein markers, Ho < 0.2 is common. References 19. Reference formatting inconsistencies: - Braend (1972): DOI `10.5555/19730102670` is invalid. - Gebrehiwet (2020): DOI `10.5555/20203476252` similarly invalid. - Takezaki and Nei (1996): Journal name shortened incorrectly; should be Genetics, not Genet. → Suggests inadequate reference validation. ********** 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: Habtamu Abera Goshu(PhD) Reviewer #2: Yes: Prof. Dr. Ali Hussein Aldujaily ********** [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 |
|
Haemoglobin polymorphism in different blood levels of Ethiopian Zebu x Holstein Friesian crossbred dairy cattle PONE-D-25-40346R1 Dear Dr. Tesfaye, 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, Mourad Mahmoud Academic Editor PLOS One Additional Editor Comments (optional): Reviewers' comments: |
| Formally Accepted |
|
PONE-D-25-40346R1 PLOS One Dear Dr. Tesfaye, 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. Mourad Mahmoud 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 .