Recommended Labels
The following table provides a list of optional labels that TetraSciences recommends using when you first onboard data to the Tetra Data Platform (TDP). The list includes the most common scientific contexts that you can use to find and access your primary data.
For more information about how TetraScience labels work, see Attributes and Manage and Apply Attributes.
NOTE
To programmatically add the recommended labels on this list to your TDP deployment, contact your customer success manager (CSM). You can add any subset of the recommended labels to your TDP deployment as well.
Recommended TetraScience Labels
| Label Name | Description | Static or Dynamic | Common Configuration Points | Example Label Values |
|---|---|---|---|---|
vendor | Indicates the vendor of the instrument that's generating data Can be used to search for files associated with a specific vendor. Note: The list of vendor labels is pre-populated with specific vendors to promote spelling and label value consistency | Static | Agent data-source or path-level label Data-source label if the File-Log Agent (FLA) monitors from a single vendor or instrument Path-level label if the FLA monitors multiple instrument types or vendors | Sartorius |
instrument_owner | Indicates the person responsible for an instrument's status. Can be used to search for an instrument with a known serial number to discover that instrument's owner. | Static | Agent path-level label | Lindsey Weed |
department | Indicates the business department that's accountable for an instrument Can be used to search for data generated within a certain department Can be combined with Project ID and/or Compound ID for cross-functional collaboration | Static | Agent data-level label | Preclinical Manufacturing and Process Development |
instrument_type | Indicates the type of instrument that's generating data Can be used to search data from a specific instrument type or to quickly assess how many instrument types are generating data Note: The list of instrument types is pre-populated with specific instruments to promote spelling and label value consistency | Static | Agent data-source or path-level label Data-source label if the File-Log Agent (FLA) monitors from a single vendor or instrument Path-level label if the FLA monitors multiple instrument types or vendors | High Performance Liquid Chromatography (HPLC) |
instrument_model | Indicates a specific model of instrument type from a vendor Can be used to search for data generated on a specific instrument model Can be combined with other attributes as part of a search (for example, pc_name or instrument_serial_number)Can be used to search for how many models of a certain instrument type there are integrated into the TDP Note: The list of instrument models is pre-populated with specific instruments to promote spelling and label value consistency | Static | Agent data-source or path-level label Data-source label if the File-Log Agent (FLA) monitors from a single vendor or instrument Path-level label if the FLA monitors multiple instrument types or vendors | Waters Empower |
software | Indicates the software application that most recently handled the data (file) or the application the data (file) is intended for. For example, applications can include electronic lab notebooks (ELN), instrument control software (ICS), chromatography data systems (CDS), or instrument-specific analysis software. Note: Make sure that you include the software vendor in the label value. The list of software labels will be pre-populated with specific options to promote consistency of spelling and values. | Static | Agent data-source or path-level label Data-source label if the File-Log Agent (FLA) monitors from a single vendor or instrument Path-level label if the FLA monitors multiple instrument types or vendors | Cytiva UNICORN |
pc_name | Indicates the computer that's controlling the instrument and/or software Can be used to search for data generated from a specific computer, which may control one or more instruments Can be used for lightweight analytics on instrument inventory | Static | Agent path-level label | TTLSWDVR1234 |
instrument_serial_number | Indicates a unique instrument identifier within the same model line from a specific vendor Can be used to search for data generated by a specific instrument module or collection of modules Can be combined with other attributes as part of a search (for example, instrument_type or pc_name) | Static | Agent path-level label | DAB123 |
file_creation_date | Indicates an exact match or “close-enough-to” the date the data is created | Static | Collected automatically by agents | 12-14-2022 |
project_id | Indicates a unique name or identifier of a scientific/business initiative that's associated with the data within a set of experiments Can be used to search for all scientific data generated for a specific project, which is most often cross-departmental | Dynamic | In-folder/file-path label that's extracted by a pipeline | DRUG-123 |
experiment_id | Indicates a unique identifier associated with an experimental entry in which the primary and derived scientific data is used to test hypothesis, or to provide insight into a particular process An entry may or may not contain results from multiple assays in a workflow Most often generated within an ELN Can be used to search data with a particular experiment ID, or for files in the TDP as a link back to the original ELN entry Note: An experimental entry should contain additional context, such as purpose, materials, method, and conclusions. | Dynamic | In-folder/file-path label that's extracted by a pipeline | EXP-15-AC9100 |
compound_id | Indicates a unique identifier for a specific chemical or biochemical structure, or substance that is being investigated. Can apply to any drug substance, drug product intermediate, or drug product across small molecules, biologics (protein-based drugs), and cell and gene therapies (CGT). | Dynamic | In-folder/file-path label that's extracted by a pipeline | 7647-14-5 Note: Can indicate a CAS Registry Number |
batch_id | Indicates a unique identifier for drug products (drug substances and drug product intermediates) that are made as specified groups or amounts within a specific time frame from the same raw materials (for example, a single manufacturing run) Can be used to see what data was collected across many instruments for a specific batch of materials | Dynamic | In-folder/file-path label that's extracted by a pipeline | 20170301A |
sample_id | Indicates a unique identifier for a sample that's being tested during an assay, or with a specific test or experiment Can be used to search for data from a specific sample that uses a specific method Can be created with any combination of compound_id, batch_id, experiment_id, project_id, and/or descriptors of the applied experimental conditionNote: An assay can require more than one sample and samples can be split across many different assays. Each sample in a system should have a unique name or ID within its sample_id. The unique sample name or ID can be provided by the user or generated by a system, such as a registry in an ELN or laboratory information management system (LIMS). | Dynamic | In-folder/file-path label that's extracted by a pipeline | Glucose Control 1 |
Updated about 1 year ago