{"id":67,"date":"2018-07-17T15:55:35","date_gmt":"2018-07-17T13:55:35","guid":{"rendered":"https:\/\/www.publiconsulting.com\/wordpress\/opentextbooksguidebyrebus\/chapter\/review-guide-template-google-docs\/"},"modified":"2019-09-13T19:25:50","modified_gmt":"2019-09-13T17:25:50","slug":"review-guide-template-google-docs","status":"publish","type":"chapter","link":"https:\/\/www.publiconsulting.com\/wordpress\/opentextbooksguidebyrebus\/chapter\/review-guide-template-google-docs\/","title":{"rendered":"Review Guide Template (Google Docs)"},"content":{"raw":"
This template may be used as you're conducing peer review on your project in Google Docs. Find an editable version here.<\/a>\u00a0This template was adapted from a similar work created by Billy Meinke-Lau<\/a> at the University of Hawaii, and includes a rubric developed by BCcampus Open Education<\/a>. Our thanks to Billy and the team at BCcampus Open Education.<\/div>\n

Rebus Community Review Guide<\/h1>\nWelcome to the guide for Rebus open textbook reviewers. This guide is meant to help you give great, useful feedback on the open textbooks we are helping to develop. You are welcome to print this Google doc, make a copy for yourself, or share with others.\n\nPlease read through sections below, and use this as a reference as you complete your review. If you have any questions, email the project lead.\n

Before We Begin<\/h2>\nAs we strive to work openly, all contributions made to this textbook will be licensed under a CC BY 4.0 International License<\/a>. Your name will be mentioned in the published version of the book as reviewer.\n\nNo OER textbook can serve all learners, so it is important to be aware of the context the book is meant to live in. Take a moment to read through the project summary to familiarise yourself with the book\u2019s purpose and audience before beginning your review.\n

About This Book<\/h2>\nInclude a quick summary and description of your project and book here. You should also link to project info page, so interested readers can learn more.<\/em>\n

Audience<\/h2>\nInsert a few sentences about the book\u2019s intended audience here. For example: \u201cThis book is meant for use in first-year introductory courses. The audience will primarily consist of undergraduates pursuing the major, however can also include some mixed-major undergraduates.\u201d You can include as much detail as you think is necessary, such as technical requirements, reading levels, etc.<\/em>\n

Core Components<\/h2>\nIf there were one single question your review should seek to answer, it should probably be:\n

\u201cTo what extent is the book successful in meeting the needs of its primary market?\u201d<\/p>\n

\u2014 tonybates.ca<\/a><\/p>\nWhen reviewing drafts, also consider:\n

    \n \t
  1. Comprehensiveness:<\/strong> The text covers all areas and ideas of the subject appropriately and provides an effective index and\/or glossary.<\/li>\n \t
  2. Content Accuracy:<\/strong> Content is accurate, error-free and unbiased.<\/li>\n \t
  3. Relevance Longevity:<\/strong> Content is up-to-date, but not in a way that will quickly make the text obsolete within a short period of time. The text is written and\/or arranged in such a way that necessary updates will be relatively easy and straightforward to implement.<\/li>\n \t
  4. Clarity:<\/strong> The text is written in lucid, accessible prose, and provides adequate context for any jargon\/technical terminology used.<\/li>\n \t
  5. Consistency:<\/strong> The text is internally consistent in terms of terminology and framework.<\/li>\n \t
  6. Organization Structure Flow:<\/strong> The topics in the text are presented in a logical, clear fashion.<\/li>\n \t
  7. Grammatical Errors:<\/strong> The text contains no grammatical errors.<\/li>\n \t
  8. Cultural Relevance:<\/strong> The text is not culturally insensitive or offensive in any way. It should make use of examples that are inclusive of a variety of races, ethnicities, and backgrounds.<\/li>\n<\/ol>\nThis rubric was developed by BCcampus Open Education<\/a>. This work is licensed under a Creative Commons Attribution 3.0 Unported<\/a> license.<\/em>\n

    Project Specific Questions<\/h2>\nThis is where you can add guiding questions for reviewers that are specific to your project. This helps to draw their attention to any areas you think need particular consideration, and helps ensure the feedback you receive is valuable.<\/em>\n

    Leaving Feedback<\/h2>\nPlease leave feedback in the Google doc using either the Comments tool or by providing feedback with the Suggestions tool.\n

    Commenting<\/h3>\nLeave a comment in the document by selecting \u00a0a portion of text, and clicking on the comment icon.\"\"<\/a>\n\nAlternatively, you can select the text, and choose Insert > Comment on the menu at the top of the page, or use the keyboard shortcut for your computer. You can select individual words or whole sentences, leaving feedback on specific parts of the document.\n\nOnce you enter your comment, be sure to click on \u201cComment\u201d to save it. Once it is saved, it will appear next to the selected text. You can edit or delete a comment by clicking on the ellipsis in the top right corner of the comment.\n\n\"\"<\/a>\n

    Suggesting<\/h3>\nYou can also leave proposed edits in the document by switching to Suggesting mode in the upper right-hand part of the document.\n\n\"\"<\/a>\n\nSimilar to track changes features of other word processing programs, the authors will see your proposed change and selectively roll or edit them in.\n\n\"\"<\/a>\n\nWhen in doubt, begin by leaving comments. Use the Suggesting mode as it is useful to you.\n

    Reviewer Etiquette<\/h3>\nHere you can add a few sentences about reviewer etiquette. The following is a short example, but could be expanded on, particularly if authors will see reviewer comments - you may want to mention this specifically.<\/em>\n\nWhen leaving feedback, please be conscious your language and tone and remember that the content you are critiquing is the product of many hours of concerted labour. Keep your criticism constructive, and avoid using derogatory phrases, or making personal remarks about the author. As a courtesy to the author or editor, avoid using abbreviations or short forms of words when providing feedback. Doing so ensures that your feedback remains clear and easy to understand for everyone.\n\nIf you run into any issues during this process, please contact the project lead.<\/strong>\n

    Deadline<\/h2>\nSpecify the deadline for completion of review here.<\/em>\n

    Compensation<\/h2>\nIf financial compensation is available for reviewers upon completion of the review, you can mention so here.<\/em>\n

    Recognition for Reviewers<\/h2>\nIf you plan to credit reviewers in a review statement, or elsewhere in the book, make a note of it here.<\/em>\n

    \fReferences<\/h2>\n