Link Search Menu Expand Document

Data storage model

Table of contents

  1. Introduction
  2. Session fields
  3. Permissions
  4. Session API access

Introduction

Data storages describe the storage solution for sessions. A data storage can be accessible with multiple protocols. You must also defined how data is organized in the Data storage.

Session fields

FieldDescription
NameName of the data storage (required; string; maximum length: 100 characters). Example: “Lab Server 01”
Authenticated groupsGroups that have change permissions for this data storage (required). Example: “Lab B Data Team”
DescriptionRich text description of the data storage. Can include uploaded images. Example: “Primary data storage server for electrophysiology recordings…”
Data organizationHow data is organized in the data storage. Example: “Projects/Subjects/Sessions/Data”
Data storage protocolsProtocols used (local, network, cloud, web, peer-to-peer). Include path and public status for each. Example: “Network: smb://labserver/data, Private access”

Permissions

You manage permissions through the management tab, where you can assign individual users and groups access levels to a data storage. Data storage have four permission levels: membership (read access), contributors, managers, and owners.

Visit the permissions page to learn more.

Session API access

The API allows for programmable access to Data storage, enabling you to read, edit, and delete data storage through the API. Learn more about the sessions’ fields and data structure on the Session API page.