PublicnEUro's policies describe what the repository, data controllers, depositors and users commit to doing. Its standards describe how datasets and their governance information are represented, validated, exchanged and preserved.

The summaries below are provided for orientation. The complete policy pages, signed service agreements and dataset-specific licences or Data User Agreements remain authoritative.

Preservation and dataset lifecycle

Explains retention, storage, and the five published lifecycle states:

  • active: normally available from PublicnEUro;
  • archived: retained in cold storage and subject to retrieval delay;
  • retired: files are no longer held by PublicnEUro, but metadata and a controller contact remain;
  • withdrawn: data access has ceased;
  • superseded: a newer version or replacement should normally be used.

Dataset metadata and DOI landing pages are maintained independently of the availability of the files. Withdrawn records retain an appropriate public record where legally possible. This follows Crossref's guidelines that landing pages guidance remain public even when content is restricted or removed -- see the y the Communication of Retractions, Removals, and Expressions of Concern (CORREC) paper.

FAQ: lifecycle states · metadata availability

Read the preservation and lifecycle policy →

Sustainability and continuity

Explains the repository's institutional basis, cost-recovery model, service review, succession arrangements and what happens to metadata, identifiers and preserved data if the service changes or closes.

Read the sustainability and continuity policy →

Metadata and technical standards

PublicnEUro currently uses or produces:

  • BIDS for neuroimaging organisation and metadata;
  • BIDS Validator for technical validation;
  • DataLad for versioned data management;
  • CrossRef DOIs for persistent identification;
  • NeuroBagel annotations for federated participant-level discovery;
  • Digital Use Conditions for structured summaries of licences and DUAs;
  • JSON Schema for dataset-level governance records;
  • OpenAIRE CERIF XML for repository-wide exchange;
  • re3data XML for repository description.

Each dataset record separates:

  • repository lifecycle status;
  • retrieval mode;
  • authoritative licence or Data User Agreement;
  • machine-readable Digital Use Conditions.

FAQ: licence, DUA and DUC · dataset citation

Read the metadata and technical standards →