Built site for gh-pages

.nojekyll

@@ -1 +1 @@
-f3d48f64
+9899293d

data-organisation.html

@@ -371,7 +371,7 @@ <h1 class="title">1) Organization</h1>
 <section id="general-notes" class="level2">
 <h2 class="anchored" data-anchor-id="general-notes">General notes</h2>
 <p>Research data is valuable for researchers and forms the basis for their research. Therefore, it is advisable to structure the data well to save time and effort in the daily handling of research data. In this part of the workshop, we will look closer at organizational aspects of data management, mainly the folder structure, file and folder naming, and file formats.</p>
-<p>A clear and consistent folder structure and folder and file naming convention are important for making your data <a href="https://www.go-fair.org/fair-principles/"><strong>f</strong>indable and <strong>i</strong>nteroperable</a>. You should think about it beforehand in order to avoid inconsistencies or the need to rename large amounts of data.</p>
+<p>A clear and consistent folder structure and folder and file naming convention are important for making your data <a href="https://www.go-fair.org/fair-principles/"><strong>f</strong>indable</a> and <a href="https://www.go-fair.org/fair-principles/"><strong>i</strong>nteroperable</a>. You should think about it beforehand in order to avoid inconsistencies or the need to rename large amounts of data.</p>
 <p>Your structure and your naming conventions should be intuitive. However, we recommend to explicitly describe them (typically in a <a href="./documentation.html#readme-file">README file</a>) because they may not be that intuitive for others or your future self (“why did I do it like this?”).</p>
 <p>In the following sections, you’ll find some input on the organizational aspects you should consider. Note that not all of them may apply to each dataset. Besides the tasks, we’ll provide some general hints and rules. Some rules only apply to some use cases, and sometimes, there are good arguments for not sticking to every rule. However, in such cases you should know (and potentially document) why you decide differently.</p>
 </section>

documentation.html

@@ -371,7 +371,7 @@ <h1 class="title">2) Documentation</h1>
 
 <section id="overview" class="level2">
 <h2 class="anchored" data-anchor-id="overview">Overview</h2>
-<p>Effective documentation is a crucial aspect of <a href="https://www.go-fair.org/fair-principles/">FAIR</a> data management, ensuring that research data are not only well-organized but also easily <strong>F</strong>indable, <strong>A</strong>ccessible, and <strong>R</strong>eusable by others. In this section, we’ll delve into the importance of documentation by exploring how to create best practice documentation that supports the entire research lifecycle. We’ll cover the essential components like including metadata that provide context and description of the dataset, as well as README files that offer a concise introduction to the dataset. Additionally, we’ll discuss the role of codebooks for making all components of the dataset self-explanatory.</p>
+<p>Effective documentation is a crucial aspect of <a href="https://www.go-fair.org/fair-principles/">FAIR</a> data management, ensuring that research data are not only well-organized but also easily <strong>f</strong>indable, <strong>a</strong>ccessible, and <strong>r</strong>eusable by others. In this section, we’ll delve into the importance of documentation by exploring how to create best practice documentation that supports the entire research data life cycle. We’ll cover the essential components like including metadata that provide context and description of the dataset, as well as README files that offer a concise introduction to the dataset. Additionally, we’ll discuss the role of codebooks for making all components of the dataset self-explanatory.</p>
 </section>
 <section id="metadata" class="level2">
 <h2 class="anchored" data-anchor-id="metadata">Metadata</h2>

publication.html

@@ -375,7 +375,7 @@ <h1 class="title">3) Publication</h1>
 
 <section id="overview" class="level2">
 <h2 class="anchored" data-anchor-id="overview">Overview</h2>
-<p>Data publication is the final step of <a href="https://www.go-fair.org/fair-principles/">FAIR data management</a>, ensuring data <strong>F</strong>indability and <strong>A</strong>ccessibility (when done well). If you have taken care of the previous sections <a href="./data-organisation.html">Data organization</a> and <a href="./documentation.html">Documentation</a> and thereby made your data <strong>I</strong>nteroperable and <strong>R</strong>eusable, publishing those data will take minimal effort.<br>
+<p>Data publication is the final step of <a href="https://www.go-fair.org/fair-principles/">FAIR data management</a>, ensuring data <strong>f</strong>indability and <strong>a</strong>ccessibility (when done well). If you have taken care of the previous sections <a href="./data-organisation.html">Data organization</a> and <a href="./documentation.html">Documentation</a> and thereby made your data <strong>i</strong>nteroperable and <strong>r</strong>eusable, publishing those data will take minimal effort.<br>
 Most commonly, data are published as supplements to journal articles and an increasing number of journals actually require that. Datasets can also be published in specialized data journals (e.g., Scientific data, Data in Brief), which means that the article itself is a rich and detailed description of the dataset. As you may have guessed, this option is mainly chosen for rather large, sampling-intensive datasets. Last but not least, it is also possible to publish an independent (without connected publication) dataset in a repository and this is often required by funders like the DFG or EU. Irrespective of the publication option, there are common good practices when publishing data, namely</p>
 <ul>
 <li>indicating in the article that data and/or code are available,</li>