In the Tetra Data Platform (TDP), an artifact is a digital object, such as the following:

• Intermediate Data Schemas (IDSs): Consist of schemas that are applied to raw instrument data or report files, which are then used to map vendor-specific information (like the name of a field) to vendor-agnostic information
• Protocols: Contain processing steps and configuration information
• Task scripts: Contain the code for the business logic needed to process the data
• Connector artifacts: Contain the definition, assets, and code for Tetra Connectors.

Artifact Requirements

Each artifact instance must include the following information:

• A namespace that the artifact belongs to (common, client-orgslug, or private-orgslug)
• A slug, such as lcuv-empower
• A version number, such as v3.1.0

The combination of the namespace, slug, and version number indicates where the artifact is stored in the Tetra Data Lake, and who has permissions to access it. This same combination of information is also used to identify and organize artifacts within the TDP.

Documentation Feedback

Do you have questions about our documentation or suggestions for how we can improve it? Start a discussion in TetraConnect Hub. For access, see Access the TetraConnect Hub.

📘

NOTE

Feedback isn't part of the official TetraScience product documentation. TetraScience doesn't warrant or make any guarantees about the feedback provided, including its accuracy, relevance, or reliability. All feedback is subject to the terms set forth in the TetraConnect Hub Community Guidelines.