Nested Knowledge

Bringing Systematic Review to Life

User Tools

Site Tools


wiki:autolit:admin:protocol

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:autolit:admin:protocol [2022/01/18 21:38]
katcow
wiki:autolit:admin:protocol [2022/10/18 21:01] (current)
nicole_hardy_alumni.brown.edu [Organizational Protocol Templates]
Line 1: Line 1:
 ====== Nest Protocol ====== ====== Nest Protocol ======
  
-===== Purpose===== +===== Purpose =====
-The Nest Protocol outlines the goal, scope, and key tasks of your systematic literature review or meta-analysis. In it, the project leadership should provide critical background information, the context of the review, and primary and secondary endpoints. +
  
-===== Open the Protocol Editor =====+The Nest Protocol outlines the goal, scope, and key tasks of your systematic literature review or meta-analysis. In it, the project leadership should provide critical background information, the context of the review, and primary and secondary endpoints.
  
-==== 1. Navigate to the Admin Page ====+===== Accessing the Protocol Editor =====
  
-To create a nest protocol, you must have admin permissions on a nest. +The Protocol can be viewed and edited from the Nest Home.
->Need admin permissions? Email the nest owner and/or project lead+
  
-==== 2Select Protocol Editor ====+==== 1. Open Nest Home and select edit. ====
  
-{{:wiki:autolit:admin:nk-protocol-editor-2022-red.png?800|}}+{{  :wiki:autolit:admin:2.png?nolink&  }}
  
 ===== Write the Protocol ===== ===== Write the Protocol =====
  
 Add headers, bullet points, and bold font. There is no one-size-fits all formula for a protocol! The goal of a 'best practices' protocol should be: enable someone unfamiliar with the project to carry out any of the Search, Screening, Tagging, Extraction, or interpretive tasks in your project in the same way that you, as project lead, would do. Add headers, bullet points, and bold font. There is no one-size-fits all formula for a protocol! The goal of a 'best practices' protocol should be: enable someone unfamiliar with the project to carry out any of the Search, Screening, Tagging, Extraction, or interpretive tasks in your project in the same way that you, as project lead, would do.
-{{nk-protocol.png}} 
  
-==== Formatting and Organization ==== +{{  :wiki:autolit:admin:3.png?nolink&  }}
  
-Use bullet points and short sentences. Keep it brief. You may add images to the protocol when applicable. Optionally, you may add a table with common abbreviations and terminology. +==== Linking to External Resources ====
  
-**Suggested Sections:** Purpose/Research Question, Search Strategy, Scope, Population, Interventions, Outcomes +You can link to any external resource by highlighting relevant text and then selecting the "link" icon!
  
-=====Share the Protocol ===== 
  
-The protocol will appear at the nest home!  Ensure that all reviewers on your team know where to find the Protocol. Optionally, you can download the protocol as a Word document in one-click. +===== Organizational Protocol Templates =====
  
-The Protocol generally does not usually include specific reviewing instructions; it contains generalized nest methods. Be sure to communicate individual instructions and deadlines outside of the Protocol's contents.+If your Organization has created Protocol Templates, you can import them by clicking the three dots and then click "Templates" in the upper right hand corner.
  
 +To see instructions on how to create Organizational Templates, see [[:wiki:autolit:admin:settings:orgs:templates|here]].
  
 +
 +===== Protocol Best Practices =====
 +
 +To see general practice recommendations on protocol drafting (and a generic template), see [[:wiki:guide:plan:protocol|Protocol Best Practices]].
  
  
wiki/autolit/admin/protocol.1642541888.txt.gz · Last modified: 2022/01/18 21:38 by katcow