Prepare your metadata based on the latest metadata schema using one of the template files below. See the instructions in the Metadata Validation Workflow document for more information on preparing and validating your metadata.tsv file prior to submission.

Related files:

• 📝 Excel template: For metadata entry.
• 📝 TSV template: Alternative for metadata entry.

Metadata schema

Version 2 (use this one)

Directory schemas

Version 2.0 (use this one)

pattern	required?	description
extras\/.*	✓	Folder for general lab-specific files related to the dataset.
derived\/.*	✓	The EPIC data is placed in TOP/derived/, so it doesn’t conflict with any files, if it’s uploaded with a primary dataset.
derived\/extras\/.*	✓	Folder for general lab-specific files related to the derived dataset.
derived\/obj_by_analyte\/.*	✓	Directory containing object by analyte table(s).
derived\/obj_by_analyte\/[^\/]+\.h5mu$	✓	This is a MuData object conforming to the HuBMAP object x analyte file specifications and not a more general hdf5 hierarchical data file. There should be one file containing all relevant AnnData objects.
derived\/obj_by_analyte\/README\.md$		A file containing clear explanations of all data included within thsi dataset submission that will allow anyone who is interested in reusing your data to easily understand it. In the interest of standardization and comprehensiveness, we recommend consulting the Dryad guidelines and resources and Dryad example README file.
derived\/obj_by_analyte\/pipeline_extras\/.*		Additional parameter, QA/QC, log or analyses files generated by the analysis pipeline. This might, for example, include the “_cmdline”, “metrics_summary.csv”, and “web_summary.html” files from a 10X Genomics pipeline.