Difference between revisions of "Research Documentation"

Jump to: navigation, search
(Created page with "This page is a stub.")
 
Line 1: Line 1:
This page is a stub.
+
When [[Dissemination|publishing research]], it is important to make '''documentation''' available so that readers can understand the details of the [[Research design|research design]] that the work reports. This includes all of the technical details and decisions that could influence how the findings are read or understood. Usually, this will involve producing a document along the lines of a methodological note or appendix. That document will describe how a given study was designed and how the design was carried out. The level of detail is in such a document should be relatively high. This page will describe some common approaches to compiling this kind of material and retaining the needed information in an organized fashion throughout the life of a research project.
 +
 
 +
== Read First ==
 +
* '''Research documentation''' provides the context to understanding the results of a given research output.
 +
* There is no standard form for this documentation, and its location and format will depend on the type of research output produced.
 +
* For academic materials, this documentation often takes the form of a structured methodological appendix.
 +
* For policy outputs or online products, it may be appropriate to include an informative <code>README</code> webpage or document.
 +
* The most important process for preparing this documentation will be retaining and organizing the needed information throughout the life of the project, so that the team will not have to search through communications or data archives for small details at publication time.

Revision as of 22:13, 26 January 2021

When publishing research, it is important to make documentation available so that readers can understand the details of the research design that the work reports. This includes all of the technical details and decisions that could influence how the findings are read or understood. Usually, this will involve producing a document along the lines of a methodological note or appendix. That document will describe how a given study was designed and how the design was carried out. The level of detail is in such a document should be relatively high. This page will describe some common approaches to compiling this kind of material and retaining the needed information in an organized fashion throughout the life of a research project.

Read First

  • Research documentation provides the context to understanding the results of a given research output.
  • There is no standard form for this documentation, and its location and format will depend on the type of research output produced.
  • For academic materials, this documentation often takes the form of a structured methodological appendix.
  • For policy outputs or online products, it may be appropriate to include an informative README webpage or document.
  • The most important process for preparing this documentation will be retaining and organizing the needed information throughout the life of the project, so that the team will not have to search through communications or data archives for small details at publication time.