public_repositories

Name publicRepositories.txt
JSON File Name publicRepositories.json
Typesingle
Schema Version 3.37
Description The public repository template allows one or more public repository accession(s) and name(s) to be assigned to an experiment sample.
Download ⬇️ publicRepositories.xlsx

⬇️ publicRepositories.txt

⬇️ publicRepositories.json

This top-level schema references companion files (e.g. publicRepositories.Datum.json) in the same json-templates folder — download the all_templates.zip to get them all together.

Reading this table: see How to read the template documentation for what Required / Conditionally required / Optional mean and how to read the Type & Constraints column.

Template ColumnRequirementType & ConstraintsDescription
Expsample IDRequiredText, max 15 characters
Reference — must already exist (in this package or the workspace) as a expsample
JSON: expsampleId (string)
The experiment sample user defined ID is an identifier chosen by the data provider to refer to this sample. This ID may be referenced by other data records (e.g. assay results). The user defined ID is not shared.
The identifier should be unique to the ImmPort workspace to which the data will be uploaded.
Repository NameRequiredText, max 50 characters
Controlled vocabulary — value must be one of lk_public_repository
JSON: repositoryName (enum)
ImmPort expects array gene expression results to be deposited in NCBI GEO since this is a prerequisite for publication. Please choose this repository name from the list.
Array gene expression results are expected to be deposited in NCBI GEO Please choose this repository name from the list.
Repository AccessionRequiredText, max 20 characters
JSON: repositoryAccession (string)
The public repository accession should be the most granular or highest resolution provided (e.g. sample level accession, not sample group accession).
Enter the accession that links to the assay result file(s).