Commit 99f87448 authored by Ewa Smula's avatar Ewa Smula
Browse files

Merge branch 'manual-update1' into 'manual-update1'

Manual update1

See merge request elixir/daisy-doc!7
parents a5835a9c 37c53ef8
......@@ -22,7 +22,7 @@ In the *Other comments* section you may describe the nature of the document or i
<span style="display:block;text-align:center">![Alt]({{ "img/contract_add_form.png" | relative_url }}){:width="800px"}</span>
4. Click SUBMIT. Once you successfully save the form, you will be taken to the newly created
1. Click SUBMIT. Once you successfully save the form, you will be taken to the newly created
contract's details page, as seen below.<br />
<span style="display:block;text-align:center">![Alt]({{ "img/contract_created.png" | relative_url }}){:width="800px"}</span>
......
......@@ -58,7 +58,7 @@ This field captures important information, but, for the first-time users of DAIS
<!-- <span>&#9675;</span><mark><strong></strong></mark> -->
- **Newly incoming data/samples**
When you select this option, it means you are obtaining data from a collaborator institute or from a repository and this data is being recorded for the first time in DAISY. With this option DAISY will first ask you to select a partner (institutes and repositories are both in the partner list). Once you select a partner DAISY will then list all those contracts that are in the system involving this partner and that have local custodians overlapping with the custodians of the dataset you're detailing. If there are no such contracts or if none of the existing contracts foresee the receipt of this data, then you have to option to create an empty contract. You can later on provide the details and documentation for this empty contract. It is possible that in some DAISY deployments the *Contract Management* module, in that case the empty contract acts as a link to the source partner for the data.
When you select this option, it means you are obtaining data from a collaborator institute or from a repository and this data is being recorded for the first time in DAISY. With this option DAISY will first ask you to select a partner (institutes and repositories are both in the partner list). Once you select a partner DAISY will then list all those contracts that are in the system involving this partner and that have local custodians overlapping with the custodians of the dataset you're detailing. If there are no such contracts or if none of the existing contracts foresee the receipt of this data, then you have to option to create an empty contract. You can later on provide the details and documentation for this empty contract. In that case the empty contract acts as a link to the source partner for the data.
<span style="display:block;text-align:center">![Alt]({{ "img/datadec_newly_incoming.png" | relative_url }}){:width="800px"}</span>
<br>
<br>
......@@ -89,7 +89,8 @@ Once created you are advised to edit the declaration to provide further informat
<div style="text-align: right"> <strong><a href="#top">Back to top</a></strong></div>
<br />
## 4.2.2 Manage Dataset Legal bases
## 4.2.2 Manage Dataset Legal basis
GDPR outlines six legal basis under which data processing is legally permitted ([find out more about the Legal basis](https://gdpr-info.eu/art-6-gdpr/)).
<mark> To add new data legal bases: </mark>
......
......@@ -40,7 +40,7 @@ The information kept on cohorts can be seen in the associated *Editor Page* seen
### 6.2 Partners Management
A *Partner* is a research collaborator that is the source and/or recipient of human data. Partners are also legal entities with whom contracts are signed. Clinical entities that run longitudinal cohorts, research institutes, or data hubs are all examples of Partners.
In accordance, when maintaining *Dataset* source info, *Dataset* transfer info or when creating *Contract* records, you will be asked to select Partners.
In accordance, when maintaining *Data Declaration's* data source, *Dataset* transfer or when creating *Contract* records, you will be asked to select Partners.
The information kept on partners can be seen in the associated *Editor Page* seen below.
......
......@@ -15,7 +15,7 @@ In order to create a new project:
2. Click the add button in the right bottom corner.<br />
![Alt](../img/add_button.png)
3. You will see an empty Project Form. *Acronym*, *Title* and *Local Custodians* are mandatory fields, whereas the others are optional. Provide the values for the fields. Note that at least one of the Local Custodians **must be VIP user**. E.g. in the demo deployment *alice.white* is a research principle investigator and VIP user.<br />
3. You will see an empty Project Form. *Acronym*, *Title* and *Local Custodians* are mandatory fields, whereas the others are optional. Provide the values for the fields. Note that at least one of the Local Custodians **must be VIP user**.<br />
<!-- ![Alt](../img/project_custodians.png) -->
<span style="display:block; text-align:center">![Alt](../img/project_custodians.png "Project custodians"){:width="800px"}<br/></span>
......@@ -27,14 +27,12 @@ In order to create a new project:
<!-- <a name="PM2"></a> -->
## 3.2 Manage Project Details
[**See full section here.**]({{ "/manual/project_management_details/" | relative_url }})
When you first create a *Project* in DAISY, it will be isolated, with no links to other entities. The project page provides shortcuts to create (and edit) following entities: dataset, contract, personnel, contacts, documentation and publications. If you use these shortcuts the newly created entities will automatically be linked to the project.
To add some details, click plus button in the particular entity box.
<span style="display:block;text-align:left">![Alt]({{ "img/add_details_button.png" | relative_url }}){:width="400px"}</span>
[**See full section here.**]({{ "/manual/project_management_details/" | relative_url }})
[**See full section Project Management**]({{ "/manual/project_management_details/" | relative_url }})
---
......
......@@ -91,7 +91,7 @@ Personnel can be unlinked from a Project by clicking on the trash icon that will
<!-- <a name="PM24"></a> -->
### 3.2.4 Manage Project Contacts
A project's *Contacts* refer to those persons that are associated with the project, but these **are not users** of the DAISY system. Under the *Definitions Management* module, it is possible to manage *Contacts* and search for them. The *Contacts* detail box on the *Project* page also allows on contact management.
A project's *Contacts* refer to those persons that are associated with the project, but these **are not users** of the DAISY system. Under the [*Definitions Management*]({{ "/manual/definitions_management_details" | relative_url }}) module, it is possible to manage *Contacts* and search for them. Management of contacts can be also done directly on *Project's* page via The *Contacts* detail box.
<mark>To add project's contact details:</mark>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment