Help & Documentation

CRCNS Hippocampus: hc-3

Home › Stem › Projects › CRCNS Hippocampus: hc-3
CRCNS Hippocampus: hc-3

Multiple single unit recordings from different rat hippocampal and entorhinal regions while the animals were performing multiple behavioral tasks. [about] The data set contains recordings made from multiple hippocampal areas in Long-Evans rats, including: Cornu Ammonis: CA1 and CA3; dentate gyrus (DG), and entorhinal cortex: EC2, EC3, EC4, EC5.  The data was obtained during 442 recording sessions and includes responses of 7,737 neurons in eleven animals while they performed one of fourteen behaviors.  Total time for all experiments is 204.5 hours.   The raw (broadband) data was recorded at 20KHz, simultaneously from 31 to 127 channels.  The raw data was processed to extract the LFPs (Local Field Potentials) and detect spikes. Included in the data set are the following items:

  • Times and waveforms of detected potential spikes.
  • Results of spike sorting.
  • LFPs.
  • For many sessions, the coordinate and direction of the rats head and video files from which the positions were extracted.
  • Metadata tables giving properties of the neurons and characteristics of the recording sessions.

A fuller description of the data set is in crcns-hc3-data-description.pdf Several publication based on some of the data are: Theta oscillations provide temporal windows for local circuit computation in the entorhinal-hippocampal loop. Mizuseki K, Sirota A, Pastalkova E, Buzsáki G., Neuron. 2009 Oct 29;64(2):267-80. Hippocampal network dynamics constrain the time lag between pyramidal cells across modified environments. Diba K, Buzsáki G., J Neurosci. 2008 Dec 10;28(50):13448-56. The following publication describes this data set: Neurosharing: large-scale data sets (spike, LFP) recorded from the hippocampal-entorhinal system in behaving rats [version 2] Kenji Mizuseki, Kamran Diba, Eva Pastalkova, Jeff Teeters, Anton Sirota, György Buzsáki. F1000Research 2014, 3:98. doi: 10.12688/f1000research.3895.2

None
None
None

None
None
       
back
Help
Projects

Projects serve as an overall way to group subjects, datasets, and collections together. A project can be used to relate experiments for publications, as well as to describe day-to-day experiments or sharing experimental data with collaborators. Projects define the overall permissions level of most other content. See section below on Permissions for further details.

Two-Part Form

The project submission form consists of two parts. In the first part, you fill in the required fields. Once you click "Create and continue," the project entry is created, and you can continue editing it on the second part of the form, which contains all the fields.

Project fields:

  • Name: The project name must be unique across BrainSTEM (required).
  • Authenticated groups: Please assign one or more groups to the project. Assigned groups will have change permissions to the project. You can continue to assign permissions on the "Manage permissions" page of the created project (required).
  • Description: A rich text description of the project.
  • Publications: List of related publication IDs formatted as strings.
  • Extra Fields: Allows you to add additional fields to the project. The values can be strings or numeric values.
  • Public Project: Determines if the project is publicly available or accessible only through the private portal.
  • Name Used in Repository: Use this field if you have another name for your project (maximum length: 200 characters).
  • Tags: Tags for the project. Tags are useful for organizational purposes, allowing you to quickly label a project and use them as filters.

Permissions

Projects define the overall permissions level for subjects, datasets, collections, and module data. You manage permissions through the management tab, where you can assign individual users and groups access levels to a project. Projects have four permission levels: membership (read access), change permissions, managers, and owners. For more information on permissions, please visit the permissions page.

Project API Access

The API allows for programmable access to projects, enabling you to read, edit, and delete projects through the API. For details about the project's fields and data structure, refer to the API Documentation on the Project API endpoint.