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.
extras\/microscope_hardware\.json	✓	[QA/QC] A file generated by the micro-meta app that contains a description of the hardware components of the microscope. Email HuBMAP Consortium Help Desk help@hubmapconsortium.org if help is required in generating this document.
extras\/microscope_settings\.json		[QA/QC] A file generated by the micro-meta app that contains a description of the settings that were used to acquire the image data. Email HuBMAP Consortium Help Desk help@hubmapconsortium.org if help is required in generating this document.
raw\/.*	✓	All raw data files for the experiment.
raw\/[^\/]+_LabWorksheet.txt	✓	An Excel spreadsheet to refer to in setting up the library. This file documents all of the samples from a single collection plate. Generated by DSP run, prior to sequencing.
raw\/[^\/]+_config\.ini	✓	Needed to generate the DCC file from the fastq file. Contains pipeline processing parameters. Generated by DSP run, prior to sequencing.
raw\/[^\/]+_SeqCodeIndices\.csv	✓	A file with sample information needed by the Illumina software. Use the contents of the SeqCodeIndices.csv file to create a SampleSheet.csv for input to the Illumina sequencer. (NextSeq 1000/2000 users download a SampleSheet.csv and whitelist.txt instead of SeqCodeIndices.csv.) Generated by DSP run.
raw\/markers\.csv		A csv file describing any morphology markers used to guide ROI and/or AOI selection [this should be similar in structure to the antibodies file]
raw\/[^\/]*targets\.pkc	✓	The file listing probe barcode sequence and corresponding gene symbol or proteins targeted by that probe. This should be consistent for the same probe panel.
raw\/additional_panels_used\.csv		If multiple commercial probe panels were used, then the primary probe panel should be selected in the “oligo_probe_panel” metadata field. The additional panels must be included in this file. Each panel record should include:manufacturer, model/name, product code.
raw\/custom_probe_set\.csv	✓	This file should contain any custom probes used and must be included if the metadata field “is_custom_probes_used” is “Yes”. The file should minimally include:target gene id, probe seq, probe id. The contents of this file are modeled after the 10x Genomics probe set file (see https://support.10xgenomics.com/spatial-gene-expression-ffpe/probe-sets/probe-set-file-descriptions/probe-set-file-descriptions#probe_set_csv_file).
raw\/fastq\/.*	✓	Raw sequencing files for the experiment
raw\/fastq\/oligo\/.*	✓	Directory containing fastq files pertaining to oligo sequencing.
raw\/fastq\/oligo\/[^\/]+\.fastq\.gz	✓	This is a gzip version of the fastq file. This file contains the cell barcode and unique molecular identifier (technical).
raw\/images\/.*		Directory containing raw image files. This directory should include at least one raw file.
raw\/images\/overlay\.(?:jpeg|tiff)		State whether an overlay image was used to guide ROI selection. If an overlay is used, then the overlay details will be provided in the protocols.io protocol. If used, this needs to be uploaded. It is not included in the OME TIFF. This can be a JPEG or TIFF file
lab_processed\/.*	✓	Experiment files that were processed by the lab generating the data.
lab_processed\/Initial\s{1}Dataset\.xlsx	✓	[QA/QC] An excel spreadsheet that is downloaded from the GeoMx DSP Data Analysis Suite containing QA/QC metrics based on raw, unprocessed target counts. This file contains one row per AOI/segment and no analyses span AOI. The AOIs included in this file can come from different GeoMx runs and hence span Globus uploads. So care must be taken to make sure the appropriate AOIs are included in the file.
lab_processed\/annotations\.xlsx		AOI specific annotations. This might include cell type and anatomical information.
lab_processed\/dcc\/.*	✓	DCC files generated from fastq by the Nanostring GeoMx NGS Pipeline.
lab_processed\/dcc\/[^\/]+\.dcc	✓	DCC files containing target probe counts, generated from fastq by the Nanostring GeoMx NGS Pipeline.
lab_processed\/images\/.*	✓	Processed image files
lab_processed\/images\/[^\/]+\.ome\.tiff	✓	OME-TIFF files (multichannel, multi-layered) produced by the microscopy experiment. If compressed, must use loss-less compression algorithm. For Visium this stitched file should only include the single capture area relevant to the current dataset. For GeoMx there will be one OME TIFF file per slide, with each slide including multiple AOIs. See the following link for the set of fields that are required in the OME TIFF file XML header. https://docs.google.com/spreadsheets/d/1YnmdTAA0Z9MKN3OjR3Sca8pz-LNQll91wdQoRPSP6Q4/edit#gid=0
lab_processed\/images\/[^\/]*ome-tiff\.channels\.csv	✓	This file provides essential documentation pertaining to each channel of the accommpanying OME TIFF. The file should contain one row per OME TIFF channel. The required fields are detailed https://docs.google.com/spreadsheets/d/1xEJSb0xn5C5fB3k62pj1CyHNybpt4-YtvUs5SUMS44o/edit#gid=0