Projects¶
Create/Update projects¶
A project is the key element to share data with thaliadb users.
Projects can be managed in the menu Admin > Team > Project.
It is defined by the fields described in the table below. Fields in bold are required while italic ones are optional when submitting the form. Projects can be edited from the table below the form.
Field name |
Description |
---|---|
Name |
The name of the project (for instance : Amaizing ) |
Authors |
A string describing authors of this project |
Start date |
Start date of the project |
End date |
End date of the project |
Description |
Description of the project |
Users |
The list of users who can access to data shared in this project |
Institutions |
List of institutions involved in the project |
Linked files |
List of documents available for the project |
Manage documents in projects¶
A document is a set of files that can be linked to a project. It can be, for instance, a set of data files, a scienfic article with source data and/or scripts, a document describing the scientific project etc. Documents are managed in the menu Admin > Team > Documents.
It is defined by the fields described in the table below. Fields in bold are required while italic ones are optional when submitting the form.
Field name |
Description |
---|---|
Name |
The name of the document (for instance : “Raw phenotyping data from 2019 to 2022”) |
Type |
A category describing these files : Project, Images, Phenotying data, Article, Referential |
Documents can be edited from the table below the form. This table is different of the classic one, you can add files to this Document by clicking on , you will access a form to add a new file to this document.
A file is defined by the fields described in the table below. Fields in bold are required while italic ones are optional when submitting the form.
Field name |
Description |
---|---|
Datafile |
The source file to upload in thaliadb |
Source |
The person that provides this data file |
Comments |
A description or a comment for this file |
Give access to projects¶
One of the aim of thaliadb is to share project data to a specific set of users. To do so, browse to Admin > Team > link data to projects.
From this interface you will be able to manage user access to projects. First, choose if you want to link or unlink users (1), select one or several projects (2) and one or several users (3).
If you choose to link users to projects, this action will add the selected users to the selected projects. Thus, these users will access to the data of these projects.
If you choose to unlink users from projects, this action will remove the selected users from the selected projects. Thus, these users won’t have access anymore to the data of these projects.
Instead of selecting a list of users in the form, you can upload a list of users (4) in a simple text file and select the projects to link/unlink users.
Another way to give access to project data is to edit the project itself. From the form, in edition mode, you can select/unselect the list of users who can access this project.
Specific sharing : Accession, Seedlot, Sample, GenotypingID¶
Linking genetic material (Accession, Seedlot, Sample, GenotypingID) to projects can be achieve the same way than other objects. Anyway, specific rules will be applied for this kind of objects.
Sharing objects in projects will follow an ascending linking according to the genetic material organisation (GenotypingID → Sample → Seedlot → Accession) For instance in the figure below, GenotypingID 1.1.1 is shared in the Amaizing project, the consequence is that Sample 1.1, SeedLot1 and Accession objects will be automatically shared in the Amaizing project. However, this sharing rules only apply in the ascending way. In the same figure, sharing SeedLot2 will result in the automatic sharing of Accession in the project, but all other objects at a lower hierarchical level (Sample2.1, Sample 2.2, GenotypingID 2.1.1, GenotypingID 2.2.1, GenotypingID 2.2.2) won’t be shared automatically in the project.
Unlink genetic material from a project will follow the reverse way of linking objects. For instance, if we consider the starting state of the DROPS project (figure below, 1/2) : Accession, SeedLot1 and all related Sample and GenotypingID are linked to the project.
Unlink Sample1.1 from the project will result in the automatic unlink event of GenotypingID1.1.1 and GenotypingID1.1.2, but all the objects with a higher hierarchical level remains shared with the project. The new state is described in the figure 2/2.