A repository is a container for multi-modal research data, projects, roles, sites, forms and tools.
The repository encapsulates all these objects and controls who has access to them. Repositories are completely separated entities on the platform, and are only accessible to specified users. In this article, you are presented with the contents of a repository, and how to manage this content from the repository view. Note that for a project member that is not assigned a role with repository scope, only member-relevant Projects and Tasklist will be visible in the repository view. The full content of a repository is only accessible to users assigned to roles with repository scope.
Projects
A project is a specific container to achieve one particular research objective (e.g. a clinical trial phase) and is typically the core of a research repository. The project has members performing roles, a pipeline to collect and analyze data, subjects which are processed through the pipeline and a result measuring the objective. A repository may contain multiple projects, sharing access to roles, sites and forms defined in the repository. You can read more about projects here. An A-Z instruction on how to create a new project can be found on this page.
View of existing projects within a repository
Tasklist
Members that are assigned tasks in a pipeline of a repository project can see their tasks in the repository tasklist. The repository tasklist can contain tasks from different projects in the repository, if the member is assigned to one or multiple roles assigned to tasks in different repository projects.
A repository tasklist, with tasks from "Emblas Test Workshop Project"
Members
The members section displays all current repository members along with their roles and site affiliations. The permissions assigned to each role dictate the level of access that each member has within the repository. You can read more about repository members and how to add a new repository member here.
Roles
A role defines permissions and data scope for a user within a repository, project and/or site. A user of Collective Minds is given a role for a specific project and is therefore a member of that project. Roles are defined in the repository, and can then be used within projects of the repository, to regulate e.g. data access and pipeline assignments in a granular manner. You can read more about roles here.
Viewing roles within a repository
Sites
A site represents a physical or virtual site from where subject data originates (e.g. a hospital). Members with data scope “site” are able to interact with the data originating from the sites to which they belong. Sites are defined in the repository and can then be used to govern data permissions for members in projects by assignment. You can read more about sites and how to use them to govern data permission access granularly here.
Viewing repository sites
Forms
A form, which is part of a repository-wide library, can be loaded into events in project pipelines. Forms are intended to handle manual structured data input, such as a data transfer form (DTF, scanlog), eCRFs or a quality assurance form. Forms can also be used side-by-side with the integrated medical image viewer, to e.g. determine quality of images or segmentations. Forms are created in the repository and loaded to projects You can read more about forms and how to create them here.
Forms in a repository
Tools
A tool, which is part of a repository-wide library, is a function built into a container for automated execution on the pipeline. Tools can be uploaded to the system, checked in and integrated into an event on the pipeline. You can read more about tools here.
Audit log
The audit log records “who has seen or done what, when?” in the repository. It records both when data is inserted through a pipeline event or when the project structure itself is built out or modified, and can be utilized as part of the audit trail. You can read more about audit logs here.