Merge pull request #79 from biosustain/dmp-updates2

docs: update the DMP sections based on the current UI

Author: VasileiaVagena

docs/Project/DMP.md

@@ -4,85 +4,51 @@ The **Data Management Plan (DMP)** helps you describe how your project’s data
 
 You can access the DMP from your project's home page under the **DMP tab**.
 
-```{tip}
-Most fields here are automatically filled and extracted from the information you provided during project or dataset creation. You only need to review and add any missing details.
-```
 
 ## How to complete the DMP
 
-The DMP is divided into several section(s). Each group contains fields that either:
-
-* **Require your input**: Information such as funding details and storage location
-
-    or
-
-* **Auto-filled by the system**: Based on the information provided during project and dataset creation (e.g., project name, description, ID)
+The DMP is divided into several section(s). Each group contains fields that **require your input**
 
 Let's look at each group in detail:
 
 
-### 1. Project Details
-
-This section provides general information about the project:
+### 1. Project Metadata
 
-   * **Project Identifier**: A unique ID for your project generated by the system
+In this section you select the expected project end date. You can edit it later if needed.
 
-   * **Project Title & Description**
+### 2. Funding 
 
-   * **Contact Persons**: Project Creator, PI, Collaborator
+Here you can enter the funding details:
 
-   * **Project creation & end date**
+   * **Funding Identifier** (e.g.,https://ror.org/027754r66)
+   * **Funder Name** (e.g., Novo Nordisk Foundation)
+   * **Funding Status** which can be:
 
-   * **Funding information**: Funding source and grant details
+     * Planned
+     * Applied
+     * Granted
+     * Rejected
 
-   * <span style="color:#999999">**LIMS (Benchling) project**: Indicate if there is a Benchling project to link (coming soon)</span>
 
 ### 2. Data Collection
 
-This section covers what data you collect and how it is generated:
-
-   * **Existing Data**: State if you use pre-existing datasets
-
-   * **Dataset Identifier**: A unique ID for your dataset generated by the system
-
-   * **Dataset Title & Description**
-
-   * **Dataset Creator**
-
-   * **Dataset Created Date**
-
-   * **Access Rights**: Define who can access the dataset → *(For more details see [Note](this_is_the_reference_point).)*
-
-        * Restricted
-        * BRIGHT-visible 
+This section focuses on whether this project uses external data.
 
-   * **Dataset Type**: Specify the type of the data:
+If **yes**, you can add information about each external data source by providing a **Title** and a short **Content** description. 
+You can add as many entries as needed.
 
-        * Raw
-        * Processed
-        * Results
-
-   * **Resource Type**: The type of experiment or analytical approach that produced the data, such as:
-
-        * DNA sequencing
-        * RNA sequencing
-        * Proteomics (DIA)
-
-   * **Instrument**: List the instrument or equipment used to generate the data such as:
-
-        * MiSeq (illumina)
-        * NextSeq (illumina)
-        * GridION (Nanopore)
 
 ### 3. Data Storage & Backup
 
-*(All fields in this section require your input!)*
-
 This section covers questions about how and where your data will be stored and backed up during and after the project is finished:
 
-   * **Main & Other Data storage**: Specify the main storage and any secondary location.
+```{important}
+All project and dataset metadata **during the project** will be stored in the BRIGHT Data Catalog and backed up daily. All raw and processed files will be stored in a cloud storage (currently a Microsoft Storage account; Region: West Europe)
+```
 
-   * **Physical data location**: Indicate where physical copies (if any) are stored.
+   * **Additional data storage**: Select any secondary storage location from the dropdown.
+
+   * **Physical data location**: Provide details about where physical copies (if any) are stored.
 
    * **Backup solutions**: Describe any other backup solution (e.g., *Additional backups on my personal laptop are stored on an external hard drive*).
 
@@ -94,34 +60,34 @@ Be aware that if you store data in **DTU M-drive** or **DTU personal OneDrive**,
 
 ### 4. Documentation 
 
-*(The field in this section require your input!)*
-
 Provide details about project documentation:
 
 * **Documentation**: List documentation formats
 
  **Example**: All electronic lab notebooks (ELNs) will be stored in Benchling project folder 'Microbial_soil_community'. Whenever applicable, a README file will be created for each dataset, detailing the data collection methods, processing steps, and any relevant metadata.
 
+
 ### 5. Data Sharing, Access & Compliance
 
-*(All fields in this section require your input, except for the last one!)*
+This section includes a series of questions about compliance and data sharing. Most questions are answered by choosing **Yes**, **No**, **Uncertain**, or **Not applicable** (dependig on the field):
 
-This section includes questions about compliance and data sharing:
+* **Biological Material**: State whether the project uses biological material such as microorganisms or material of animal, plant, or human origin.
 
-* **Biological Material / Hazardous Substances:**: State if your project involves these
+* **Medicines, Drugs, Radioactive Isotopes**: State if any of these substances are part of the project.
 
-* **Personal Data (GDPR)**: State if personal or sensitive data is involved
+* **Toxic Substances**: Answer whether toxic chemicals or naturally produced toxins are used.
 
-* **Access Controlled in Data Catalog**: Choose who can view your data:
+* **Nanoscale Practicles**: Specify how nanoscale materials are handled.
 
-    * Restricted
-    * BRIGHT-visible 
+* **Personal Data (GDPR)**: State if any personal or sensitive data is involved in the project, such as age, DNA, RNA, biometrics, etc.
 
-* **Sharing After Project Ends**: Specify if data will be made public after completion
+* **Access Controlled Inside and Outside the Data Catalog**: Describe how access to the data is controlled both inside and outside BRIGHT Data Catalog.
+
+* **Sharing After Project Ends**: Explain what will happen to the data once the project is complete. For example, whether it will be deposited in DTU Data, shared on GitHub, or restricted due to NDA/GDPR.
 
 
 ```{note}
-(this_is_the_reference_point)=
+
 → **Restricted**: Access for all project, dataset metadata and files in Microsoft Azure Storage account is restricted to project members and collaborators.
 
 → **BRIGHT-visible**: READ-ONLY access for project and dataset metadata is granted to all BRIGHT employees. Access to files in Microsoft Azure Storage account remains restricted to project members and collaborators.