Managing Projects

Projects provide a top-level organizational structure in the Gallery. Each project represents a distinct unit of work and contains one or more datasets. Project-level information applies globally to all datasets contained within it.

Projects are used to organize datasets into coherent units of study. A project may represent an experiment, a field campaign, a musical performance, or any other grouping that benefits from structured organization.

Each project maintains its own metadata that applies to all subordinate datasets. Examples include:

  • Babbeleaf software version used to collect the recordings
  • Researcher or operator details
  • General project notes and methodology statements

This information remains consistent across all datasets within the project, ensuring that context is preserved and does not need to be repeated for each recording session.

Projects are self-contained and independent of one another. Information from one project cannot be directly copied into another, ensuring clarity and preventing cross-contamination of metadata.

Users may assign any name when creating a project. If a duplicate name is entered, the system automatically generates a unique identifier to distinguish between projects. This guarantees unambiguous project tracking without requiring users to manually maintain unique names.

Projects serve as the highest level of organization within the Gallery and form the basis for all subsequent dataset management.