Collection model

Table of contents

  1. Introduction
  2. Fields
  3. Permissions
  4. API access

Introduction

Collections allow for creating subgroups of sessions within a project. They can be used to define a set of sessions for a specific analysis or figure. All sessions in a collection must belong to the same project. The membership is ordered: sessions keep the order you give them.

This model with its direct connections only: drag to pan, Ctrl + scroll to zoom, click a model to select it, use the chevron to see its fields.

Fields

FieldDescription
Collection nameName of the collection (required; string; maximum length: 100 characters; must be unique within the project). Example: “Place Cell Analysis”, “Learning Sessions Day 1-5”
ProjectThe project the collection belongs to (required). A collection belongs to a single project. Example: “Spatial Memory Project”
SessionsSessions in the collection (required). All sessions must belong to the same project. Add sessions and reorder them using drag-and-drop; the order is stored. Example: “Recording1”, “Recording2”, “Recording3”
DescriptionA text description of the collection. Pictures can be uploaded and inserted through rich text formatting.
TagsTags for organization and filtering. Tags are shared across all users. Example: “place-cells”, “figure-1-data”

Permissions

Collections inherit permissions from their associated project. You can only add sessions to the collection that are part of the same project. Deleting the project deletes its collections.

Visit the permissions page to learn more.

API access

The API allows for programmable access to collections. Learn more about the collections’ fields and data structure on the Collection API page.