Documentation
  • Overview
  • Key Concepts
  • Getting Started
  • Release Notes
  • Installation & Configuration
    • Production Deployment
    • Configuration Properties Reference
    • Single Sign-On
    • Events
    • Power Search
    • Email
  • Integrations
    • Benchling
    • Egnyte
    • GitLab
    • Amazon Web Services
    • Microsoft Azure
  • Managing Your Tenant
    • Getting Started
    • Managing Users
    • Storage Folders
    • Programs
    • Assay Types
  • Using Study Tracker
    • Studies
      • Creating Studies
      • Working with studies
    • Assays
    • Study Collections
    • File Manager
    • Frequently Asked Questions
Powered by GitBook
On this page
  1. Using Study Tracker

Studies

Creating and working with studies

PreviousAssay TypesNextCreating Studies

Last updated 1 year ago

are the primary unit of work in Study Tracker and make up the bulk of record keeping, but how you choose to define and utilize them is entirely up to you (). When you are ready to perform some wet- or dry-lab work on a new study, Study Tracker should be the first place you go before getting started. The reason for this is that Study Tracker will take care of some of the tedious first steps in preparing the systems you are required to work within by creating a few things for you:

  • A unique that can be used to identify your study in the lab or in other systems.

  • A folder and summary notebook entry in your electronic laboratory notebook system (eg. Benchling).

  • A folder in your organization's cloud storage service (eg. SharePoint or Egnyte) for capturing documents & results.

  • An optional source code repository in a connected Git server (eg. GitLab) for managing data science notebooks.

You can reference the below diagram for an example workflow for when and how to use Study Tracker:

Studies
Study Code
The basic study tracker workflow
we do provide some guidance