change section titles on apge 4 and respective cross refs

Author: MalikaIhle

training/research-cycle-handbook/01-plan-and-design.qmd

@@ -612,7 +612,7 @@ A **Data Management Plan (DMP)** documents how you will handle research data thr
 
 ::: {.ms-1} 
 - **Decide _before_ data collection whether you will eventually share your data publicly (and where)**, in order to (i) get ethics approval on the right plan, (ii) design consent form for participants, (iii) collect appropriate metadata for the target repository, ect.
-- **Start with what you know, and refine the details as your project develops.** Your DMP is a living document that you will refine to match the reality of your project while ensuring data protection and streamline collaborations (see [2.2. Data Management](02-collect-and-manage.qmd#sec-data-management){.mark}, [3.1. Data Processing & Analysis](03-analyze-and-collaborate.qmd#sec-data-processing-analysis){.mark}, and [4.1. Data Sharing](04-preserve-and-share.qmd#sec-data-sharing){.mark}).
+- **Start with what you know, and refine the details as your project develops.** Your DMP is a living document that you will refine to match the reality of your project while ensuring data protection and streamline collaborations (see [2.2. Data Management](02-collect-and-manage.qmd#sec-data-management){.mark}, [3.1. Data Processing & Analysis](03-analyze-and-collaborate.qmd#sec-data-processing-analysis){.mark}, and [4.1. FAIR Data Sharing](04-preserve-and-share.qmd#sec-fair-data-sharing){.mark}).
 :::
 
 ##### <i class="bi bi-list-check"></i> Your DMP will ask:
@@ -622,7 +622,7 @@ A **Data Management Plan (DMP)** documents how you will handle research data thr
 - **How will you organize files** (naming conventions, folder structure, versioning)?
 - **Where will you store it** (locations, backups, access controls)?
 - **How will you ensure quality** (validation checks, error-handling)?
-- **How will you share outputs** (repositories, licenses, embargo periods)? See our lecture "[Why share data openly?](https://lmu-osc.github.io/training/data-management/open-data.html)" and [4.1. Data Sharing](04-preserve-and-share.qmd#sec-data-sharing){.mark}
+- **How will you share outputs** (repositories, licenses, embargo periods)? See our lecture "[Why share data openly?](https://lmu-osc.github.io/training/data-management/open-data.html)" and [4.1. FAIR Data Sharing](04-preserve-and-share.qmd#sec-fair-data-sharing){.mark}
 - **What constraints apply** (consent, anonymization, GDPR, data use agreements)? See our lecture "[Maintaining privacy with open data](https://lmu-osc.github.io/training/data-management/maintaining-privacy-with-open-data.html)", [1.2.3. Ethics](#sec-legal-requirements){.mark} and [2.3. Ethics & Privacy](02-collect-and-manage.qmd#sec-ethics-and-privacy){.mark}.
 
 <br>

training/research-cycle-handbook/03-analyze-and-collaborate.qmd

@@ -439,7 +439,7 @@ Before publishing your project (see [4. Preserve & share](04-preserve-and-share.
 
 #### 3.1.4. Documentation
 
-As with all documentation, your project repository’s documentation should be written early - initially for your near-future self to support efficient re-engagement after interruptions, then revised for internal team review, and ultimately expanded and refined for public sharing (see [4.2. Code Publishing](04-preserve-and-share.qmd#sec-code-publishing){.mark}).  
+As with all documentation, your project repository’s documentation should be written early - initially for your near-future self to support efficient re-engagement after interruptions, then revised for internal team review, and ultimately expanded and refined for public sharing (see [4.2. Open Source Code](04-preserve-and-share.qmd#sec-open-source-code){.mark}).  
 
 <br>
 
@@ -559,7 +559,7 @@ For users of R, Python, and Julia, **Quarto** has become the standard tool for c
 
 - **Create an analyses report with Quarto.** To make your results reproducible, you should provide the analysis code that creates the results of the manuscript with explanations for each of the steps. Quarto is an ideal tool for such purpose (see [Quarto tutorial](https://lmu-osc.github.io/introduction-to-Quarto/)). Your analysis report should contain your research question, data loading instructions, preprocessing steps, statistical procedures, tables and figures, session info and software versions (in the report itself or in your README).
 
-This will facilitate your own revisions, code-review by your team, **reproducibility checks** that some journals conduct as part of peer-review, and verification of results reproducibility by other researchers. The code repository can be published with simulated, synthetic, or real data, depending on the project, together with the respective article (see [4.2. Code Publishing](04-preserve-and-share.qmd#sec-code-publishing){.mark}).
+This will facilitate your own revisions, code-review by your team, **reproducibility checks** that some journals conduct as part of peer-review, and verification of results reproducibility by other researchers. The code repository can be published with simulated, synthetic, or real data, depending on the project, together with the respective article (see [4.2. Open Source Code](04-preserve-and-share.qmd#sec-open-source-code){.mark}).
 
 <br>
 

training/research-cycle-handbook/04-preserve-and-share.qmd

@@ -34,7 +34,7 @@ include-in-header:
 <details class="orc-details-panel">
 <summary markdown="1"><i class="bi bi-database-up"></i> 
 
-### Data Sharing {#sec-data-sharing}
+### FAIR Data Sharing {#sec-fair-data-sharing}
 
 </summary>
 
@@ -438,7 +438,7 @@ _in construction_<!-- Reema? -->
 <details class="orc-details-panel">
 <summary><i class="bi bi-file-code"></i> 
 
-### Code Publishing {#sec-code-publishing}
+### Open Source Code {#sec-open-source-code}
 
 </summary>
 
@@ -646,7 +646,7 @@ Learn more about open licenses for data and code in our [code publishing tutoria
 
 #### 4.2.4. Archiving & DOIs
 
-To publish you code on Zenodo, we recommend to<!-- these instructions contradict https://lmu-osc.github.io/code-publishing/archive.html -->
+To publish you code on Zenodo, we recommend to<!-- these instructions contradict https://lmu-osc.github.io/code-publishing/archive.html but see https://github.com/lmu-osc/code-publishing/issues/86 -->
 
 - **Push your clean repository to GitHub** (see GitHub tutorial).
 - **Create an account on [Zenodo](https://zenodo.org/).**
@@ -716,7 +716,7 @@ To publish you code on Zenodo, we recommend to<!-- these instructions contradict
 <details class="orc-details-panel">
 <summary><i class="bi bi-journal-arrow-up"></i> 
 
-### Materials Sharing {#sec-materials-sharing}
+### Open Materials {#sec-open-materials}
 
 </summary>
 
@@ -1276,3 +1276,19 @@ Remove personal or participant data
 Review entire git history
 Add simulated data if needed
 Document dependencies clearly -->
+
+
+
+::: {.orc-gradient-box}
+
+## <i class="bi bi-card-checklist"></i> Preserve & Share Checklist {.unnumbered}
+
+**Before sharing resources**
+
+- [ ] Complete metadata, README (with instructions), and documentation (e.g. data dictionary)
+- [ ] No sensitive information in any files to be shared
+- [ ] Data quality validated, code peer-reviewed, materials checked and cleaned
+- [ ] Results reproducible, following reporting guidelines, separated in preregistered vs exploratory
+- [ ] All authors have ORCID
+
+:::