meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| general:dokuwiki:how2document [2022/12/20 09:30] – [References] ingo | general:dokuwiki:how2document [2025/10/13 11:19] (current) – [References] ingo | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Scientific writing ====== | ||
| + | Each scientific project culminates in writing scientific text. Reason is, that the data, information, | ||
| + | - comprehend what you did and why | ||
| + | - understand what you found out | ||
| + | - reproduce your work | ||
| + | - embed it into state of the art in the research field | ||
| + | The only reasonable way to achieve this is, to cast the corresponding information into text, figures, and tables, just to mention the main three components of a text. | ||
| + | Now, many people are not what one would call a __gifted writer__. Until recently, this resulted in text that leaves some room for improvement both with respect to content and style, and this after spending days and weeks on the text. Meanwhile, AI based solutions abound whose service can range from a mere polishing of your close to finished text to writing the entire text for you. <wrap important> | ||
| + | Goethe University has compiled a [[https:// | ||
| + | <table AI-use> | ||
| + | ^Phase in the writing process ^Support through AI ^Own contribution| | ||
| + | |Topic selection and literature research| Brainstorming Rough overview of topics | Focus on finding scientific sources| | ||
| + | |Reading and excerpting |Summary/ | ||
| + | |Rough draft |Formulating bullet points; Cooperative freewriting |Jot down key points; Write to clarify your thoughts; Revise AI-generated texts| | ||
| + | |Revise |Generate different text versions; Adjust style/ | ||
| + | |Linguistic correction|Specialized tools such as DeepL, Write, and Duden Mentor|Check if meaning has changed| | ||
| + | < | ||
| + | </ | ||
| ====== Lab protocols ====== | ====== Lab protocols ====== | ||
| Most practical modules in your curriculum require that you write a lab protocol at the end of your project. This lab protocol is your proof of achievement, | Most practical modules in your curriculum require that you write a lab protocol at the end of your project. This lab protocol is your proof of achievement, | ||
| - | <WRAP important><fs 1.5em>There is a difference between a lab protocol, and the daily documentation of your work in the WIKI. You can write, in principle, a lab protocol as a set of WIKI pages, but then we expect that it adheres to the guidelines listed below</fs></ | + | <WRAP important> |
| ===== Objective ===== | ===== Objective ===== | ||
| Before writing a lab protocol, you should ask yourself not only //why// your are writing a lab protocol, but much more //what you want to achieve// with the lab protocol. The answer is considerably simple: You write the lab protocol for | Before writing a lab protocol, you should ask yourself not only //why// your are writing a lab protocol, but much more //what you want to achieve// with the lab protocol. The answer is considerably simple: You write the lab protocol for | ||
| Line 15: | Line 33: | ||
| ===== How to write a lab protocol ===== | ===== How to write a lab protocol ===== | ||
| It happens often that people have no clear idea of how to write a protocol. We have, therefore, compiled a short guideline of what to take into account when writing a protocol. | It happens often that people have no clear idea of how to write a protocol. We have, therefore, compiled a short guideline of what to take into account when writing a protocol. | ||
| - | - A protocol is a scientific text, and thus the [[howto:scientific_essay|same rules]] apply | + | - A protocol is a scientific text, and thus the same {{ :general: |
| - A protocol is typically written for a short term project. Its focus is more on the technical part and the results, and less on answering a particular scientific question((It is, thus ok to keep introduction and discussion concise)) | - A protocol is typically written for a short term project. Its focus is more on the technical part and the results, and less on answering a particular scientific question((It is, thus ok to keep introduction and discussion concise)) | ||
| - A protocol is meant to provide< | - A protocol is meant to provide< | ||
| Line 24: | Line 42: | ||
| Follow this [[https:// | Follow this [[https:// | ||
| - | <fs 1.5em><wrap tip>It is a good idea to carefully read the guidelines {{ : | + | <wrap tip>It is a good idea to carefully read the guidelines {{ : |
| ===== Some additional points to consider ===== | ===== Some additional points to consider ===== | ||
| Below, we have compiled a collection of points that you should check before writing a protocol, and afterwards as well | Below, we have compiled a collection of points that you should check before writing a protocol, and afterwards as well | ||
| ==== Structure of the protocol ===== | ==== Structure of the protocol ===== | ||
| - | Try sticking to the standard structure< | + | Try sticking to the standard structure, which is also referred to as the [[wp> |
| * Introduction | * Introduction | ||
| * Material & Methods | * Material & Methods | ||
| Line 41: | Line 59: | ||
| Each figure... | Each figure... | ||
| - | * has a figure number. | + | * **has a figure number**. Figures |
| - | * has to be mentioned in the text | + | * **has to be mentioned in the text** |
| - | * has a short, informative title | + | * **has a short and informative title** |
| - | * has a description that reflects the message of the figure. Make sure that the figure description does not end up in the main text | + | * **has a description that reflects the message of the figure**. Make sure that the figure description does not end up in the main text |
| - | * should be interpretable on its own. It is generally not optimal to refer to other figures (other than supplementary figures) in the figure caption | + | * **should be interpretable on its own**. It is generally not optimal to refer to other figures (other than supplementary figures) in the figure caption. Likewise, you do not want to have figure descriptions in the main text. |
| <wrap important></ | <wrap important></ | ||
| * Screenshots as figures can be ok, but only when the image quality is sufficiently high. | * Screenshots as figures can be ok, but only when the image quality is sufficiently high. | ||
| * make sure that the font and the font size is uniform across the figures. Text must be <fs 0.1 em> | * make sure that the font and the font size is uniform across the figures. Text must be <fs 0.1 em> | ||
| - | * avoid figures landscape format | + | * avoid figures |
| ==== Tables ==== | ==== Tables ==== | ||
| Like with figures, think about the information that should be provided with a table | Like with figures, think about the information that should be provided with a table | ||
| - | * tables have to be successively numbered according to the order they are referred to in the text | + | |
| - | * each table has to be mentioned in the text | + | |
| - | * each table has an informative title. Table columns can be explained in the table footnotes | + | |
| - | * avoid landscape tables | + | |
| - | * avoid tables that extend over more than one page. Consider placing large tables into the supplement | + | |
| - | * don't use vertical lines to delimit table columns. Horizontal lines to delimit rows are ok, though | + | |
| ==== Methods ==== | ==== Methods ==== | ||
| Line 65: | Line 83: | ||
| ==== References ==== | ==== References ==== | ||
| - | <wrap important></ | + | <wrap important></ |
| * Make sure that references in the text, and your bibliography is correctly and consistently formatted. We prefer the //author, year// format for in-text citations over numbers. | * Make sure that references in the text, and your bibliography is correctly and consistently formatted. We prefer the //author, year// format for in-text citations over numbers. | ||
| You can read more about how to cite in this document provided by the University of Cologne (in German only): [[http:// | You can read more about how to cite in this document provided by the University of Cologne (in German only): [[http:// | ||