What is SciNote’s Structure?

SciNote's data structure is broken down into: Organization, Teams, Projects, Experiments, and Tasks.

The basic SciNote components are organized into a hierarchical structure:

1. Projects - the first structural level of data organization (each table row represents a project).
   1. Each Project has a unique identifier (Project ID) that is auto-numbered by SciNote and will never change over time. E.g., PR1608
      1. 
   2. Team Owners can also create Project Folders and subfolders to further group and organize Projects within the same SciNote Team.
2. Experiments - can be thought of as project subfolders. These represent different workflows within the larger project.
   1. Individual SciNote Experiments can be things like: batches, process development "versions", set time periods, a unique lab process, etc.
   2. Each Experiment has a unique identifier (Experiment ID) that is auto-numbered by SciNote and will never change over time. E.g., EX4608
      1. 

3. Tasks – can form experimental workflow when connected to each other, or they can be stand-alone units. All of your data will be entered into the tasks.

   1. Tasks have due dates, protocol steps and results attached, assigned users (task assigned to), and linked inventory items. The point of data entry in SciNote is the Task!

   2. Every Task has a unique identifier (Task ID) that is auto-numbered by SciNote and will never change over time. E.g., TA21171

   3. Every task also includes an overview of the protocol, results, task activity, signatures history, assigned inventory items, and archived results.

      1. 

For a more detailed explanation of SciNote's structure, read this document.

To learn more about SciNote's structure watch our video. 

If you have any additional questions, please contact us at support@scinote.net. For more info about the Premium plans, please request a quote.