Project
Projects are organisation entities in which runs, substrates and chemical containers are organised. This allows reporting of substrate and chemical consumption and also details overviews of all activities in the specific project.
Projects can be found via Organisation > Project which shows a list of all projects with a filter option
In this section an overview of all features related to projects is given
Project options
Per project different options can be chosen, where here an overview is given of all options
| Option | Explanation |
|---|---|
| Project name | Public name of the project |
| Abbreviation | Short abbreviation of the project, can be used as prefix in runs when the Run prefix settings are set to project |
| Start date | Start date of the project |
| End date | End date of the project |
| Approval required | Toggle to determine if runs in this project require approval before start |
| Private | Toggle to determine if runs in this project are only visible for management and members of the projects. This is useful for confidential projects |
| Substrate required | Option to determine if substrates are required in runs in this project (see Substrate requirement for more details) |
| Multiple substrates per part | Option to determine if the experimental split in runs can be more than 1 substrate (see Substrate requirement for more details) |
| Team | Team(s) to which this project belongs |
| Status | Toggle status of the project (active / inactive). Projects with runs, substrates or chemical containers cannot be deleted but can be set to inactive |
Project users
In each project responsible users and regular users (members) are active. Responsible users have full access to the project and runs, substrates and chemical containers in the project and can manage users in the project.
New responsible users can be added via Project > Responsible users by pressing the
button Add responsible user to project and complete the form. Note that the end-date is optional and will remove the
user as responsible if the end-date has passed. Each responsible user in the project has his/her own Organisational
role (
Leader, Financial, etc.) and the list of available organisation roles can be managed
via Admin > Organisation > Organisation Roles
A user has to be member or responsible user in a project to be able to select the project when creating a new run. New
members of the project can be added via Project > Users and the button Add user to project
Substrate requirement
It is possible to set the substrate requirement per project. There are 2 settings on project level which have impact on the substrate requirements in runs executed in this project. These 2 settings are:
- Substrate required
- No substrate required
- Substrate required
- Multiple substrates per part
- Part can represent a batch of multiple substrates
- Only 1 substrate per part
A parts corresponds to Experimental split in runs.
When runs can be created without a substrate, then the project settings of the selected project has to be No substrate required, then SoloDB allows the creation of runs without any substrate. When the setting is set to Substrate required runs in this project can only be started when a substrate, parent run or consumable is selected.
For runs in projects where many substrates are processed in batch (for example in Solar Cell Processing) it is possible to put the value of Multiple substrates per part to Part can represent a batch of multiple substrates, this allows the configuration of 200 substrates split in 4 parts (Experimental split) of 50 where each part corresponds to 50 substrates.
When the Multiple substrates per part is set to Only 1 substrate per part each Part corresponds to 1 substrate.