Commit 5203c7a1 authored by Ewa Smula's avatar Ewa Smula
Browse files

images url and hyperlinks corrected

parent d30ba367
......@@ -6,7 +6,7 @@ order: -1
---
<small>
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*4. Dataset Management*]({{ "/manual/#4-dataset-management" | relative_url }}) &raquo; [*4.2 Manage Dataset Details (**GO BACK to main page**)*]({{ "/manual/#42-manage-dataset-details" | relative_url }})
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*Datasets (**GO BACK to main page**)*]({{ "/manual/#22-datasets" | relative_url }})
</small>
---
......@@ -20,10 +20,8 @@ order: -1
---
<!-- <a name="DM"></a> -->
# 4 Dataset Management
<!-- <a name="DM1"></a> -->
## 4.1 Create New Dataset
<mark>In order to create a new Dataset:</mark>
......@@ -32,7 +30,7 @@ order: -1
<span style="display:block;text-align:center">![Alt]({{ "img/dataset_menubar.png" | relative_url }}){:width="800px"}</span>
2. Click the add button (in the right bottom corner) from the *Dataset Search Page*.<br />
![Alt](../img/add_button.png)
<span style="display:block;text-align:left">![Alt]({{ "img/add_button.png" | relative_url }}){:width="100px"}</span>
3. You will see the *Dataset Creation Quick Form*. Fill the fields and click SUBMIT. <br />
<span style="display:block;text-align:center">![Alt]({{ "img/dataset_quick_form.png" | relative_url }}){:width="800px"}</span><br />
......@@ -56,7 +54,6 @@ Dataset entity details box are displayed in dataset page, where you can add, edi
<br/>
After initial creation the dataset will be in a skeletal form. The dataset needs to be fleshed out with further information on the characteristics of the data it contains.
<!-- <a name="DM2"></a> -->
## 4.2.1 Declare Data within the Dataset
<mark> To add new data declaration: </mark>
......@@ -73,12 +70,10 @@ After initial creation the dataset will be in a skeletal form. The dataset needs
<br>
<!-- <a name="DDEC_OPTIONS"></a> -->
<big> **Obtained from** field</big>
This field captures important information, but, for the first-time users of DAISY it can be difficult to populate. Your choice among the three options will determine if and how your dataset will be linked to other entities in DAISY. If you are a first-time user and you are creating records for learning purposes, we suggest that you choose the option *Other* for simplicity.
<!-- <span> &#9675; </span> -->
- **From existing data/samples**
- **From existing data/samples**
When you state that the data is obtained from existing data/samples in your institution, DAISY will prompt you (as below) to search for and choose the data record which is the origin for your current declaration.
<span style="display:block;text-align:center">![Alt]({{ "img/datadec_from_existing.png" | relative_url }}){:width="800px"}</span>
You will be provided a searchable selection box, through which you can find existing data records by their Project, by responsible PI or by their title. As you will be making a selection from existing records, with this option, it is necessary that origin data had been entered into DAISY earlier.
......@@ -88,7 +83,6 @@ This field captures important information, but, for the first-time users of DAIS
<br>
<!-- <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. 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>
......@@ -98,9 +92,6 @@ This field captures important information, but, for the first-time users of DAIS
<span style="display:block;text-align:center">![Alt]({{ "img/newly_incoming_topology.png" | relative_url }}){:width="800px"}</span>
<!-- <span>&#9675;</span><mark><strong>Other:</strong></mark> -->
- **Other**
When you select this option, it means you do not want to create any structured DAISY records to denote the origin of data being declared. DAISY will prompt you to provide a free-text description of the origin of data as seen below.
<span style="display:block;text-align:center">![Alt]({{ "img/datadec_other.png" | relative_url }}){:width="800px"}</span>
......@@ -213,9 +204,9 @@ As discussed above, when data of one project is being accessed in the context of
## **4.2.6 Appendix for VIP user**
By clicking *eye button* in the dataset overview box, VIP user can enter *Change permission* page.
The management of the dataset's access permissions is alike to project's permissions described in [** 3.2.7. appendix**]({{ "/manual/project_management_details/#327-appendix-for-vip-users**" | relative_url }}).
By clicking *eye button* in the dataset overview box, VIP user can enter *Change permission* page.
The management of the dataset's access permissions is alike to project's permissions described in
[**3.2.7 VIP appendix**]({{ "/manual/project_management_details/#327-appendix-for-vip-users" | relative_url }}).
<!-- This section describes management of the dataset's access permissions. If VIP user (check [users groups here]({{ "manual/#what-are-the-users-groups" | relative_url }})) owns a dataset or is its Local Custodian, he can grant other users with permissions for the dataset.
......
......@@ -6,7 +6,7 @@ order: -1
---
<small>
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*6 Definitions Management (**GO BACK to main page**)*]({{ "/manual/#6-definitions-management" | relative_url }})
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*Definitions (**GO BACK to main page**)*]({{ "/manual/#24-definitions" | relative_url }})
</small>
---
......@@ -23,10 +23,10 @@ order: -1
<br>
DAISY *Definitions* module allows for the management of *Contacts*, *Cohorts* and *Partners*.
DAISY *Definitions* module allows for the management of *Contacts*, *Cohorts* and *Partners*.
<!-- <a name="COH_M"></a> -->
## 6.1 Cohorts
## 6.1 Cohorts
Cohort is a study that collects data and/or bio-samples from a group of participants (e.g. longitudinal case-control or family studies). A cohort is linked to the creation of data and is considered its ultimate source.
In order to effectively handle data subjects' requests, as per GDPR, it is crucial that an institution keeps track of what data it keeps from which cohorts. Inline with this, DAISY allows maintaining a list of *Cohorts* and link *Datasets* to *Cohorts*.
......@@ -37,7 +37,7 @@ The information kept on cohorts can be seen in the associated *Editor Page* seen
<!-- <a name="PAR_M"></a> -->
## 6.2 Partners
## 6.2 Partners
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 *Data Declaration's* data source, *Dataset* transfer or when creating *Contract* records, you will be asked to select Partners.
......@@ -48,7 +48,7 @@ The information kept on partners can be seen in the associated *Editor Page* see
<span style="display:block;text-align:center">![Alt]({{ "img/partner_edit_form.png" | relative_url }}){:width="800px"}</span>
<!-- <a name="CONN_M"></a> -->
## 6.3 Contacts
## 6.3 Contacts
*Contacts* are people affiliated with the external partner institutions (e.g. collaborator principle investigators, project officers at the EU).
DAISY keeps the contact details (e.g email address, affiliations) of external collaborators related to the *Projects*, *Datasets*, *Cohorts* and *Contracts*.
......
......@@ -6,7 +6,7 @@ order: -1
---
<small>
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*3. Project Management*]({{ "/manual/#3-project-management" | relative_url }}) &raquo; [*3.2 Manage Project Details (**GO BACK to main page**)*]({{ "/manual/#32-manage-project-details" | relative_url }})
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*Projects (**GO BACK to main page**)*]({{ "/manual/#21-projects" | relative_url }})
</small>
---
......@@ -20,32 +20,28 @@ order: -1
---
<!-- <a name="PM"></a> -->
# 3 Project Management
This section describes how to add a new project. Adding a project is available for standard user and VIP user.
<!-- <a name="PM1"></a> -->
## 3.1 Create New Project
<!-- <mark>In order to create a new project</mark>: -->
In order to create a new project:
1. Click Projects from the Menu Bar to enter Project Search Page.<br />
<span style="display:block; text-align:center">![Alt](../img/project_menubar.png "project menubar"){:width="800px"}</span>
<span style="display:block; text-align:center">![Alt]({{ "img/project_menubar.png" | relative_url }}){:width="800px"}</span>
2. Click the add button in the right bottom corner.<br />
![Alt](../img/add_button.png)
<span style="display:block; text-align:left">![Alt]({{ "img/add_button.png" | relative_url }}){:width="100px"}</span>
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>
<span style="display:block; text-align:center">![Alt]({{"img/project_custodians.png" | relative_url }}){:width="800px"}<br/></span>
4. Click SUBMIT. Once you successfully save the form, you will be taken to the newly create project's details page, as see below.<br />
<!-- ![Alt](../img/project_created.png) -->
<span style="display:block; text-align:center">![Alt](../img/project_created.png "Project created "){:width="800px"}<br/></span>
<span style="display:block; text-align:center">![Alt]({{"img/project_created.png" | relative_url }}){:width="800px"}<br/></span>
<br>
<!-- <a name="PM2"></a> -->
## 3.2 Manage Project Details
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.
......@@ -78,14 +74,13 @@ When a project is created, it will have no associated datasets. On the project's
2. You will see the **Dataset Creation Quick Form** as below. The *Project* field will be auto-selected, in addition you need to provide *Local Custodians* and a *Title* for your dataset. Typically the local custodians would be the same as the project, but you are free to choose any user as the custodian. Remember that one of the custodians needs to be a VIP user. Provide the field values and press submit.
<span style="display:block;text-align:center">![Alt]({{ "img/project_add_dataset_form.png" | relative_url }}){:width="800px"}</span>
3. Once the dataset is created, you will be taken to the **Dataset's Details Page**, seen below. You can continue working on the data set as described in [section Dataset Management]({{ "/manual/#4-dataset-management" | relative_url }}).
3. Once the dataset is created, you will be taken to the **Dataset's Details Page**, seen below. You can continue working on the data set as described in [section Dataset Management]({{ "/manual/dataset_management_details/" | relative_url }}).
If you want to go back to the Project that owns this dataset, then you can click the project link in the dataset's overview box, highlighted below.<br />
![Alt]({{ "img/project_add_dataset_result.png" | relative_url }})
<br>
<!-- <a name="PM22"></a> -->
### 3.2.2 Add Project Contract
Contract allows for recording legal documents signed in the context of research activities. It provides the necessary traceability for the GDPR compliant provision and transfer of data.
......@@ -99,11 +94,10 @@ Contract allows for recording legal documents signed in the context of research
Remember that one of the custodians needs to be a VIP user. Provide the field values and press submit.
<span style="display:block;text-align:center">![Alt]({{ "img/project_add_contract_form.png" | relative_url }}){:width="800px"}</span>
1. The contract can be viewed by clicking its name in the detail box. (See section [Contract Management]({{ "/manual/#5-contract-management" | relative_url }}).) The contract can be removed from a project by clicking on the trash icon that will appear when hovering over the items in the *Contracts* detail box.
1. The contract can be viewed by clicking its name in the detail box. (See section [Contract Management]({{ "/manual/contract_management_details" | relative_url }}).) The contract can be removed from a project by clicking on the trash icon that will appear when hovering over the items in the *Contracts* detail box.
<span style="display:block;text-align:center">![Alt]({{ "img/project_remove_contract.png" | relative_url }}){:width="800px"}</span>
<!-- <a name="PM23"></a> -->
### 3.2.3 Add Project Personnel
A project's *Personnel* refer to those persons that work on the project, we assume that these persons will all have a user account for the DAISY system. The *Personnel* detail box on the *Project* page also allows linking DAISY *Users* as personnel of a project.
......@@ -121,7 +115,6 @@ Personnel can be unlinked from a Project by clicking on the trash icon that will
<br>
<!-- <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*]({{ "/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.
......@@ -143,7 +136,6 @@ Contacts can be unlinked from a Project by clicking on the trash icon that will
<br>
<!-- <a name="PM25"></a> -->
### 3.2.5 Manage Project Documentation
Document management is done via the *Documents* detail box. You can attach documents to a project record in DAISY. Some examples of the documents are listed below:
......@@ -170,7 +162,6 @@ The format of the documents is not limited, these can be PDF, Word or images. If
<br>
### 3.2.6 Manage Project Publications
<!-- <a name="PM26"></a> -->
A project's *Publications* can be managed via the *Publications detail box*.
......@@ -194,7 +185,7 @@ Publications can be unlinked from a project by clicking on the trash icon that w
### **3.2.7 Appendix for VIP users**
This section describes management of the project's access permissions. If VIP user (check [users groups here]({{ "manual/#what-are-the-users-groups" | relative_url }})) owns a project or is its Local Custodian, he can grant users with the project's privileges.
This section describes management of the project's access permissions. If VIP user owns a project or is its Local Custodian, he can grant users with the project's privileges.
By clicking *eye button* in the project overview box, VIP user can enter *Change permission* page.
......
......@@ -25,13 +25,10 @@ After successful login, you see DAISY home page.
<br />
<!-- <a name="DIC"></a> -->
## 1.2 DAISY Interface Conventions
<!-- This section has three paragraphs. -->
The main view of each DAISY module is called [Search Page](#search-pages), where you choose entity you are interested in (or create a new module). You can inspect a particular entity details in [Entity Details Pages](#entity-details-pages) and edit them in [Entity Editor Pages](#entity-editor-pages).
<!-- <a name="SP"></a> -->
### Search Pages
DAISY provides search pages for all entities manageable via modules. Currently these modules are: *Datasets*, *Projects*, *Contracts* and under *Definitions*: *Cohorts*, *Partners*, *Contacts*. All search pages have similar layout and operational conventions. Search pages are also the only entry point for the functions in a module. When you select a module from the menu bar, you will be taken to the search page for the entity managed by that module.
......@@ -51,7 +48,7 @@ Each entity listed in the search results is displayed in a shaded box, containin
Depending on the permissions associated with your user type, you may see a **add button (denoted with a plus sign)** at the bottom right section of the search page. You can add a new entity by clicking the plus button, which will open up an empty editor form for you to fill in.
<br/>
<!-- <a name="EDP"></a> -->
### Entity Details Pages
Clicking the *DETAILS* button in the search result box takes you to *Details Page*, which contains the information about the chosen entity. An example of details page for *Project* named 'SYSCID' is given below.
......@@ -67,7 +64,6 @@ Each Details Page is headed with an **entity overview box** listing some of the
* edit entity button (denoted with a pencil icon),
* remove entity button (denoted with a bin icon).
<!-- Each Details Page is headed with an overview box) listing some of the entity’s attributes. Depending on the permissions associated with your user type, you may see an **edit entity button (denoted with a pencil icon) and an permissions button (denoted with an eye icon). These will take you to the Entity Editor Page and the Permissions Management Page respectively. -->
Beneath the entity overview box there are several information boxes, which display the further details of the entity (e.g. personnel, ethics).
......@@ -76,7 +72,7 @@ If you have edit permissions for the entity, then at the top right corner of par
* create (inline) detail records to the current entity e.g. one or more publications to a project.
<br/>
<!-- <a name="EEP"></a> -->
### Entity Editor Pages
When you click the edit button on the Details Page of an entity, you will be taken to the Editor Page containing a form for entity update. An example of **editor form** is given below.
......@@ -87,9 +83,6 @@ Each field in the form is be listed with a **name**, a **value** and a **help te
Editor forms can be saved by pressing **SUBMIT** button at the bottom of the page. The forms will be validated upon the submission. If the validation fails for one or more fields, these will be highlighted with inline validation error message, illustrated below.
<!-- ![Alt](../img/validation_error.png)
<center>Field validation error</center> -->
<span style="display:block; text-align:center">![Alt](../img/validation_error.png "Field validation error"){:width="800px"}<br/><small>Field validation error message</small></span>
<br/>
......@@ -97,8 +90,6 @@ Editor forms can be saved by pressing **SUBMIT** button at the bottom of the pag
Upon successful submission of a form, you will be returned to the Entity Details page.
DAISY may give success and/or warning messages upon the form submission; these will be displayed at the top of the page, as illustrated below.
<!-- ![Alt](../img/page_messages.png) -->
<!-- <center>Message display in DAISY</center> -->
<br/>
<span style="display:block; text-align:center">![Alt](../img/page_messages.png "Message display in DAISY"){:width="800px"}<br/><small>Status message displayed in DAISY</small></span>
<br/>
......
......@@ -6,7 +6,7 @@ order: -1
---
<small>
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*What are the users groups (**GO BACK to main page**)*]({{ "manual/#what-are-the-users-groups" | relative_url }})
[User guide]({{ "/manual/" | relative_url }}) &raquo; [*3 Different types of DAISY users (**GO BACK to main page**)*]({{ "manual/#3-different-types-of-daisy-users" | relative_url }})
</small>
---
......@@ -31,10 +31,13 @@ DAISY is intended to be used mostly by three categories of end users in a biomed
Above categories are assigned to particular DAISY **user groups**, which support the control of records access:
- **Standard**
This is the default group that users are mainly assigned to. All DAISY users can view all *Dataset*, *Project*, *Contract* and *Definitions* (*Cohorts*, *Partners*, *Contacts*). The document attachments of the records are excluded from this view permission.
<br>
- **VIP**
The research principle investigators are typically assigned to this group. VIP users have all privileges on the records they own, meaning the records where the user has been appointed as the `Local Custodian`. They also have the right to give permissions to others on these records.
<br>
- **Legal**
This group allows users to manage *Contract* records. Legal personnel will be able to create view and edit contract as well as view all other records in DAISY and manage their document attachments
<br>
- **Auditor**
This role would designed to an external person, who is given view-only temporary access to all DAISY records. This is typically happening during an audit scenario.
......@@ -43,33 +46,17 @@ Inside the group a user can be assigned with a specific **role**, which specifie
- Local Custodian
- Regular user
<br>
The *back end user* is called *superuser* and is granted with *all* DAISY privileges - to manage the application's content and administer DAISY settings.
<br>
DAISY supports fine-grained permission management with the following categories of permissible actions.
The right to *View*, *Edit* and *Delete* records; to *View Document attachments of records* and to *Administer Permissions*.
DAISY supports fine-grained permission management with the following categories of permissible actions.
The users permissions are summed up in the below table:
<span style="display:block;text-align:center">![Alt]({{ "img/permissions_table.png" | relative_url }}){:width="900px"}<br/><small>Users permissions</small></span>
<!-- Project permissions:
Permissions
- Admin
Grant the right to change permissions on this dataset and grant all other permissions.
- Delete
Grant the right to delete this dataset.
- Edit
Grant the right to edit this dataset.
- Protected
Grant the right to access protected information on this dataset.\
- View
Grant the right to view this dataset. -->
<!-- | User Category | Administer Permissions | Delete | Edit | View | View Document Attachments |
......@@ -80,8 +67,6 @@ Permissions
| auditor | | | |P<sub>all</sub>, D<sub>all</sub>, C<sub>all</sub>, Def<sub>all</sub>| P<sub>all</sub>, D<sub>all</sub>, C<sub>all</sub>, Def<sub>all</sub> |
| legal | C<sub>all</sub> | C<sub>all</sub> | P<sub>all</sub>, D<sub>all</sub>, C<sub>all</sub>, Def<sub>all</sub> | P<sub>all</sub>, D<sub>all</sub>, C<sub>all</sub>, Def<sub>all</sub> | P<sub>all</sub>, D<sub>all</sub>, C<sub>all</sub>, Def<sub>all</sub> | -->
<br />
---
......
# 2 What records can be kept with DAISY?
# 2 What records can be kept with DAISY?
This section contains a brief description of DAISY functions listed in the application's menu bar (image below) and some tips how to effectively familiarise with DAISY application.
......@@ -10,7 +10,7 @@ This section contains a brief description of DAISY functions listed in the appli
## 2.1 Projects
Projects Management module allows for the recording of research activities as projects. Documenting projects is critical for GDPR compliance as projects constitute the purpose and the context of use of the personal data.
Any document supporting the legal and ethical basis for data use can be stored in DAISY (e.g. ethics approvals, consent configurations or subject information sheets). [**Go to Project Management**]({{ "/manual/project_management_details/" | relative_url }})
Any document supporting the legal and ethical basis for data use can be stored in DAISY (e.g. ethics approvals, consent configurations or subject information sheets). [**Go to Project Management**]({{ "/manual/project_management_details/" | relative_url }})
## 2.2 Datasets
......@@ -37,8 +37,8 @@ Definitions Management module allows the maintenance of secondary entities, whic
# 3 Different types of DAISY users
Any user with an account can login to DAISY and start creating records. Users that create a record become the record's *owner* and will be able to change and delete the record at any time.
In DAISY, a records owner, however, is not the one with the utmost privileges. DAISY provides various types of users accounts, and associated priviliges.
Any user with an account can login to DAISY and start creating records. Users that create a record become the record's *owner* and will be able to change and delete the record at any time.
In DAISY, a records owner, however, is not the one with the utmost privileges. DAISY provides various types of users accounts, and associated privileges.
<br/>
......@@ -48,14 +48,13 @@ The default type of user is a standard user. Standard users can:
- view any *Dataset*, *Project*, *Contract* or *Definition* record in DAISY, including those created by others. The documents attachments on the records are, however, protected, and they are not visible to other standard users.
- create records of their own.
- edit and delete records of their own.
<br>
- **VIP user**
The research principle investigators are VIP type users. Whenever a *Dataset*, *Project*, *Contract* record gets created in DAISY, a VIP user **must be designated** as the record's **Local Custodian**. Records cannot be created without a local custodian.
In addition to the priviliges of the standard user, the VIP Users have the following rights:
- **VIP user**
The research principle investigators are VIP type users. Whenever a *Dataset*, *Project*, *Contract* record gets created in DAISY, a VIP user **must be designated** as the record's **Local Custodian**. Records cannot be created without a local custodian.
In addition to the privileges of the standard user, the VIP Users have the following rights:
- view, edit and delete records under his custodianship,
- view and manage the document attachments of records under their custodianship,
- grant other users permissions on the records under his custodianship.
- grant other users permissions on the records under his custodianship.
- **Legal user**
The users assigned to this group can are allowed to manage *Contract* records. Legal personnel can:
......
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