Imaging

AF

Related files:

🔬 Background doc: More details about this type.
📝 Excel template: For metadata entry.
📝 TSV template: Alternative for metadata entry.

This schema is for autofluorescence (AF). For an example of an AF dataset & directory, see this example autofluorescence dataset and click the Globus link.

Metadata schema

Version 1 (use this one)

Shared by all types

version
description
donor_id
tissue_id
execution_datetime
protocols_io_doi
operator
operator_email
pi
pi_email
assay_category
assay_type
analyte_class
is_targeted
acquisition_instrument_vendor
acquisition_instrument_model

Unique to this type

resolution_x_value
resolution_x_unit
resolution_y_value
resolution_y_unit
resolution_z_value
resolution_z_unit
number_of_channels
overall_protocols_io_doi
contributors_path
data_path

Shared by all types

`version`

Version of the schema to use when validating this metadata.

constraint	value
enum	`1`
required	`True`

`description`

Free-text description of this assay.

constraint	value
required	`True`

`donor_id`

HuBMAP Display ID of the donor of the assayed tissue. Example: ABC123.

constraint	value
pattern (regular expression)	`[A-Z]+[0-9]+`
required	`True`

`tissue_id`

HuBMAP Display ID of the assayed tissue. Example: ABC123-BL-1-2-3_456.

constraint	value
pattern (regular expression)	`(([A-Z]+[0-9]+)-[A-Z]{2}\d(-\d+)+(_\d+)?)(,([A-Z]+[0-9]+)-[A-Z]{2}\d(-\d+)+(_\d+)?)*`
required	`True`

Start date and time of assay, typically a date-time stamped folder generated by the acquisition instrument. YYYY-MM-DD hh:mm, where YYYY is the year, MM is the month with leading 0s, and DD is the day with leading 0s, hh is the hour with leading zeros, mm are the minutes with leading zeros.

constraint	value
type	`datetime`
format	`%Y-%m-%d %H:%M`
required	`True`

`protocols_io_doi`

DOI for protocols.io referring to the protocol for this assay.

constraint	value
required	`True`
pattern (regular expression)	`10\.17504/.*`
url	prefix: `https://dx.doi.org/`

`operator`

Name of the person responsible for executing the assay.

constraint	value
required	`True`

`operator_email`

Email address for the operator.

constraint	value
format	`email`
required	`True`

`pi`

Name of the principal investigator responsible for the data.

constraint	value
required	`True`

`pi_email`

Email address for the principal investigator.

constraint	value
format	`email`
required	`True`

`assay_category`

Each assay is placed into one of the following 4 general categories: generation of images of microscopic entities, identification & quantitation of molecules by mass spectrometry, imaging mass spectrometry, and determination of nucleotide sequence.

constraint	value
enum	`imaging`
required	`True`

`assay_type`

The specific type of assay being executed.

constraint	value
enum	`AF`
required	`True`

`analyte_class`

Analytes are the target molecules being measured with the assay. Leave blank if not applicable.

constraint	value
required	`False`

`is_targeted`

Specifies whether or not a specific molecule(s) is/are targeted for detection/measurement by the assay.

constraint	value
type	`boolean`
required	`True`

`acquisition_instrument_vendor`

An acquisition instrument is the device that contains the signal detection hardware and signal processing software. Assays generate signals such as light of various intensities or color or signals representing the molecular mass.

constraint	value
required	`True`

`acquisition_instrument_model`

Manufacturers of an acquisition instrument may offer various versions (models) of that instrument with different features or sensitivities. Differences in features or sensitivities may be relevant to processing or interpretation of the data.

constraint	value
required	`True`

Unique to this type

`resolution_x_value`

The width of a pixel.

constraint	value
type	`number`
required	`True`

`resolution_x_unit`

The unit of measurement of the width of a pixel. Leave blank if not applicable.

constraint	value
enum	`nm` or `um`
required	`False`
required if	`resolution_x_value` present

`resolution_y_value`

The height of a pixel.

constraint	value
type	`number`
required	`True`

`resolution_y_unit`

The unit of measurement of the height of a pixel. Leave blank if not applicable.

constraint	value
enum	`nm` or `um`
required	`False`
required if	`resolution_y_value` present

`resolution_z_value`

Optional if assay does not have multiple z-levels. Note that this is resolution within a given sample: z-pitch (resolution_z_value) is the increment distance between image slices, ie. the microscope stage is moved up or down in increments to capture images of several focal planes.

constraint	value
type	`number`
required	`True`

`resolution_z_unit`

The unit of incremental distance between image slices. Leave blank if not applicable.

constraint	value
enum	`mm`, `um`, or `nm`
required	`False`
required if	`resolution_z_value` present

`number_of_channels`

Number of channels capturing the emission spectrum from natural fluorophores in the sample.

constraint	value
type	`integer`
required	`True`

`overall_protocols_io_doi`

DOI for protocols.io referring to the overall protocol for the assay.

constraint	value
required	`True`
pattern (regular expression)	`10\.17504/.*`
url	prefix: `https://dx.doi.org/`

`contributors_path`

Relative path to file with ORCID IDs for contributors for this dataset.

constraint	value
required	`True`

`data_path`

Relative path to file or directory with instrument data. Downstream processing will depend on filename extension conventions.

constraint	value
required	`True`

Version 0