System and architecture
Helps users find datasets by the type of model system without forcing one label.
Examples: Organoid, spheroid, tissue chip, organ-on-chip, body-on-chip, barrier model, perfused system, hybrid/custom system.
Back to Home
Contributor metadata
Metadata that makes submissions searchable and reusable
PhysioVerse uses flexible component and process descriptors so contributors can describe complex model systems without forcing one label. The same metadata helps reviewers evaluate submissions and helps users find relevant datasets later.
Contributor access note
Sign up or sign in before contributing raw data and metadata
Anyone can use the public MPS Engine to search and compare study metadata without signing in. Contributors who want to add raw or processed data directly to PhysioVerse must sign up or sign in before uploading omics, imaging, functional data, ZIP packages, metadata files, repository links, or supporting documents. After signing in, contributors can complete the submission workflow and keep metadata connected to each contributed dataset record.
Why this matters
Good search starts with clear submission metadata
Terms such as organoid, organ-on-chip, body-on-chip, and tissue chip are useful, but they do not always describe what a system contains or how it was generated. Many datasets include multiple cell sources, materials, devices, culture processes, perturbations, assays, and data modalities.
PhysioVerse therefore asks contributors to describe the dataset through searchable descriptors. Contributors can select multiple options and add an explanation when they choose Other or when a system does not fit existing choices.
View Submission GuideMetadata should help answer
- What system was studied?
- What biological components were included?
- How was the system generated or treated?
- What was measured?
- Which files or links belong to the dataset?
- What information is needed for review and reuse?
Descriptor groups
What contributors are asked to describe
These descriptor groups are used in the submission form and in the Find Data filters. They are meant to be flexible: contributors can select more than one option and use Other when a term is missing.
Cell source and biological context
Describes where the biological material comes from and what it represents.
Examples: Primary, tumor-derived, iPSC-derived, immortalized, co-culture, species, tissue or organ, disease context.
Components, materials, and devices
Captures the physical and biological parts that influence system behavior.
Examples: Epithelial, endothelial, immune, stromal, neuronal, or cardiac components; scaffold, matrix, hydrogel, device material, flow or mechanical context.
Processes and perturbations
Explains how the system was generated, maintained, matured, treated, or challenged.
Examples: Directed differentiation, self-assembly, perfusion, maturation, drug exposure, toxicant exposure, infection, hypoxia, or genetic perturbation.
Assays and data modalities
Connects what was measured to the files or repository links provided by the contributor.
Examples: Imaging, histology, transcriptomics, single-cell data, proteomics, metabolomics, functional assays, TEER, permeability, viability, secretion, longitudinal measurements.
Files, packages, and provenance
Keeps uploaded data, metadata files, ZIP packages, external links, and processing history connected to the dataset record.
Examples: Raw files, processed files, dataset package ZIP, sample metadata, experimental design file, data dictionary, protocol, README, DOI, accession, repository link.
Required and optional metadata
Only core searchable information is required
PhysioVerse should not make contributors enter fields that do not apply. Core fields are required so a dataset can be identified, attributed, reviewed, and discovered. More detailed sample, treatment, dose, time point, and replicate information should be added when available or relevant.
Required for a searchable submission
- Dataset title and short description
- Contributor identity and institution
- At least one system or architecture descriptor
- At least one data modality
- Data location: uploaded files, metadata files, ZIP package, external repository link, or a combination
- Access and reuse expectations
- Basic provenance or processing notes
Optional when applicable
Detailed experimental context improves reuse
Optional fields are still valuable. They help reviewers and future users understand sample groups, comparisons, treatments, time points, and file-to-sample relationships. When these details are not relevant, contributors can leave them blank.
Helpful when available
- Sample IDs or group labels
- Control, treated, or comparison group
- Treatment or exposure
- Dose or concentration
- Time point or collection time
- Replicate number
- Detailed reagent information
- Assay endpoint details
- Additional notes for unusual or custom systems
Using Other
Other is allowed, but it should be explained
If a contributor chooses Other or describes a custom system, they should add a short explanation. That explanation helps reviewers understand the submission and may help improve future descriptor choices.
This keeps the metadata model flexible without losing the structure needed for search, review, and reuse.
When to use Other
- The system does not fit an existing category.
- A material, device, or process is not listed.
- A modality or assay type is missing from the choices.
- The dataset uses a novel or hybrid workflow.
- The contributor needs to preserve terminology used by the source data.
Prepare metadata
Use metadata that makes the dataset understandable before upload
Review the submission guide, prepare core descriptors, and sign in when you are ready to create a dataset record, upload files, link repositories, or submit for review.
