Writing Microbiology Resource Announcements (MRA)
Author(s): Arturo Diaz1, Julia Lee-Soety2, Shima Chaudhary3, Denise L Monti4, Viknesh Sivanathan5, Richard Pollenz6
1. La Sierra University 2. Saint Joseph’s University 3. South Texas College 4. University of Alabama at Birmingham 5. Howard Hughes Medical Institute 6. University of South Florida
1503 total view(s), 979 download(s)
Summary:
This resources provides a framework for students to write a Microbiology Resource Announcement, collaboratively.
Contents:
- 0 - MRA Facilitator Guide.docx(DOCX | 21 KB)
- 1 - MRA Data Collection Template.xlsx(XLSX | 22 KB)
- 2 - MRA Template.docx(DOCX | 39 KB)
- 3 - MRA Faculty Checklist.docx(DOCX | 17 KB)
- 4 - MRA Rubric.docx(DOCX | 22 KB)
- Microbiology Resource Announcements
- License terms
0 Like
Christa Bancroft @ on (Edited: @ on )
The QUBES MRA resources was hugely helpful for our past two MRA submission. I received this comment from our last submission: "Each accession number reported in the manuscript must be hyperlinked to the publicly available data record." Might also be good to have as reference the MRA checklist before submission to make sure authors include all of the details they are looking for: https://journals.asm.org/pb-assets/pdf-text-excel-files/MRA-Author-Checklist-1659729670130.pdf
Copy link Report abuse
0 Like
Imade Nsa @ on
The MRA Resource, combined with the quick turn around of feedback from the Internal Review was great.
We annotated two genomes from the Genome Exchange.
MRA 1 : The reviewer commented that the paper was in a pretty good shape and asked for the following:
MRA 2 : Some comments from a different Reviewer:
Copy link Report abuse
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
Comment removed by original commenter @ on (Edited: @ on )
0 Like
Steven M Caruso @ on
We had two MRAs, both written by students, one edited by me and one edited by Ivan. The editors were different, and from their styles the reviewers were likely different as well.
Both asked for the SRA snd GBK links to be moved from a separate paragraph back into a table. I don't know if they all prefer that since it was suggested that we do the oposit, but that's what ours prefered. It may be luck of the draw. Both also had us cut down the additional reasearch we added as a figure a bit. Here are pretty much all of the details.
MRA 1 (Cluster BI phages) -
MRA 2 (Cluster BF phages) -
Overall, not too many changes.
Steve
Copy link Report abuse
0 Like
Julia Lee-Soety @ on
The reviewer for our submission requested additional information:
1. Include databased used to mine HHPred and BLASTp.
2. Indicate how gene similarities were determined (same as Ellen Wisner's comment).
Copy link Report abuse
0 Like
Ellen Wisner @ on (Edited: @ on )
This resource was great, without it we would not have been able to publish our MRA.
We have a unique situation as the phage we annotated was from the Genome Exchange, as a result we had to reach out to the institution that did the isolation for a lot of information about the isolation of the phage. This was fine as they had great notes and responded quickly, but got me thinking that perhaps all of that information (the info required for an MRA) could be included somewhere on phagesdb. Below I have listed all of the extra information (that wasn't already on PhagesDB) that we had to get from the discovery/isolation team:
We felt like the review process went pretty well. This is what the reviewer had us change/suggestions:
Copy link Report abuse
Comment removed by original commenter @ on (Edited: @ on )
0 Like
Victoria Jane Frost @ on
I just wanted to share a couple of tips about the MRA submission process:
Copy link Report abuse
0 Like
Sergei A Markov @ on
Reviewers may ask to add to manuscript the date at which the phage sample was taken and GPS
For software cited, reviewers/editors may ask to specify settings or indicate that default settings were used. The authors can include a blanket statement, e.g. "Default parameters were used for all software unless otherwise specified."
Sergei Markov
Copy link Report abuse
0 Like
Sara Sybesma Tolsma @ on (Edited: @ on )
Having others in the SEA read and comment on our manuscript was enormously helpful! And having the workflow got us over the "activation energy" we needed to submit our first manuscript. We have a second one that has been accepted since so apparently the activation energy was truly lowered :).
Some comments we got from reviewers and other advice:
1. We needed GPS coordinates to be more precise. I truncated them because I thought it looked better. Don't do that.
2. We needed to clarify the use of Newbler and Consed and to let them know how the genome ends were determined.
3. We needed to include "putative" or "predicted" with all our functional calls.
4. Include staining method for TEMs.
5. Reviewers said due to ICTV revision, Siphoviridae is no longer being used. Suggested using "siphovirus morphology".
6. Include whether soil samples were from surface and volume of soil used in isolation.
7. One reviewer wanted the total reads for each phage so I included that in our table.
8. I had some trouble at first getting our plaque pictures to have the correct resolution. I used this online converter and it worked well: https://image.online-convert.com/convert-to-tiff
9. Give yourself some nice, uninterrupted time to do the submission. It took me longer than I thought it would.
Thanks to the team (especially Vik!) for your help!
Copy link Report abuse
0 Like
Viknesh Sivanathan @ on
This is helpful, Sara. Can you share how you clarified for the reviewers the use of Newbler/Consed for genome end determination?
Copy link Report abuse
0 Like
Sara Sybesma Tolsma @ on
Sure. This is how we have the sentence in the version that was accepted:
Untrimmed reads were assembled using Newbler (v2.9) and checked for completeness using Consed (v29.0) with default parameters (4, 5). The genome ends were determined using Consed (v29.0) with default settings (5).
Copy link Report abuse
1 Like
Shallee Page @ on (Edited: @ on )
Hi, on the checklist, it would be good to include that the accession numbers and software URLs need to be hyperlinked. MRA has that on their checklist and I missed it the first time.
Copy link Report abuse
0 Like
Ellen Wisner @ on
Agreed, we also missed this as well.
Copy link Report abuse