... | @@ -2,9 +2,9 @@ |
... | @@ -2,9 +2,9 @@ |
|
|
|
|
|
Projects are used to group samples. All samples in LiST have to be associated with a project. That is, whenever a sample is created in LiST, a project has to be chosen. A sample can be transferred to another project later.
|
|
Projects are used to group samples. All samples in LiST have to be associated with a project. That is, whenever a sample is created in LiST, a project has to be chosen. A sample can be transferred to another project later.
|
|
|
|
|
|
The project also determines who can see and modify samples. When a project is created, researchers and faculty are assigned to the project. Only those people can add or modify samples. All projects are visible (in readonly mode) to all 2DCC personnel, though.
|
|
The project also determines who can see and modify samples. When a project is created, researchers and faculty are assigned to the project. Only those assigned people can add or modify samples. All projects are visible (in read-only mode) to all 2DCC personnel, though.
|
|
|
|
|
|
User projects (which can be Sample Projects or Research Projects) are added to LiST by Kevin Dressler when they are approved.
|
|
User projects (which can be Sample Projects or Research Projects) are added to LiST by Kevin Dressler once they are approved.
|
|
Kevin also assigns faculty and researchers to a project. Once created, User Projects can be updated by the assigned faculty.
|
|
Kevin also assigns faculty and researchers to a project. Once created, User Projects can be updated by the assigned faculty.
|
|
|
|
|
|
In-House projects can be created by Faculty and Instrument managers.
|
|
In-House projects can be created by Faculty and Instrument managers.
|
... | | ... | |