Help & Documentation

CRCNS Hippocampus: hc-11

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

Recordings from hippocampal area CA1, PRE, during and POST novel spatial learning. [about] This data set is composed of eight bilateral silicon-probe multi-cellular electrophysiological recordings performed on four male Long-Evans rats. These recordings were performed to assess the effect of novel spatial learning on hippocampal CA1 neural firing and LFP patterns in naïve animals. Each session consisted of a long (~4 hour) PRE rest/sleep epoch home-cage recordings performed in a familiar room, followed by a Novel MAZE running epoch (~45 minutes) in which the animals were transferred to a novel room, and water-rewarded to run on a novel maze. These mazes were either A) a wooden 1.6m linear platform, B) a wooden 1m diameter circular platform or C) a 2m metal linear platform. Animals were rewarded either at both ends of the linear platform, or at a predetermined location on the circular platform. The animal was gently encouraged to run unidirectionally on the circular platform. After the MAZE epochs the animals were transferred back to their home-cage in the familiar room where a long (~4 hour) POST rest/sleep was recorded. All eight sessions were concatenated from the PRE, MAZE, and POST recording epochs. In addition to hippocampal electrophysiological recordings, neck EMG and head-mounted accelerometer signals were recorded, and the animal’s position during MAZE running epochs was tracked via head-mounted LEDs. Some publications based on all or parts of these data are: Grosmark, A.D., and Buzsáki, G. (2016). Diversity in neural firing dynamics supports both rigid and learned hippocampal sequences. Science 351, 1440–1443. Chen, Z., Grosmark, A.D., Penagos, H., and Wilson, M.A. (2016). Uncovering representations of sleep-associated hippocampal ensemble spike activity. Sci. Rep. 6, 32193.

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.