Brighthive Glossary

A

Agentic AI

Agentic AI is a breakthrough in artificial intelligence technology which allows the construction of custom built agents on top of industry leading LLM technologies. These agents are tooled to complete specific tasks through additional instructions and resources, helping the models to execute specific goals within custom parameters. Brighthive's Brightbot is built with an agentic architecture, allowing the primary Brightbot agent to call on a variety of additional agents trained in data analytics, governance, and code writing, just to name a few. Users can also create custom agents through the BrightBot Assistants custom agent builder. 

Airbyte

Our most commonly used data connection tool. Airbyte is an open source data integration engine that enables over 350 connections to third party data sources, automating the connection of external data to your Brighthive workspace. Your Airbyte connection details can be viewed in under Connect > Services > Connections.

API

API, or application programming interface, is a mechanism that allows two different softwares to communicate with each other. APIs are prolific in modern software, from your phone's weather app to corporate IT systems. Brighthive allows users to connect to APIs in the Projects page to integrate data products with external sources like dashboards or chat interfaces.

B

BrightBot

BrightBot is the agentic AI layer of the Brighthive workspace. BrightBot itself is the primary agent which interfaces with users. When a user makes a request, BrightBot passes requests to it's data team, which includes agents specializing in data analysis, governance, and transformations, to name a few. BrightBot can be seen as an extra member of your data team, helping you engage with your data to accelerate time to insight.

BrightBot Assistants

BrightBot Assists are custom agents created by users that help achieve specific user goals. BrightBot Assistants, like BrightBot's agentic team, use specific instructions, tool calls, and additional workspace context to tailor workflows to achieve a user's goals. BrightBot Assistants call from the data stored within the Brighthive workspace.

Brighthive

A company working to make every team a data team!

C

Collaborators

Collaborators is a member permission level within the Brighthive workspace. Collaborators have the access to the full workspace, but are restricted from editing workspace policies. Learn more about Collaborators permissions here: Roles & Permissions in Brighthive.

Contributors

Contributors is a member permission level within the Brighthive workspace. Contributors have the most limited access to Brighthive, and are only able to access Projects where they have been added as "Contributing Members". Contributors can view the Project Overview and add Data to the Project. Learn more about Contributor permissions here: Roles & Permissions in Brighthive.

Contributing Members

In Projects, Contributing Members is a role that specifies which members are able to edit or add data to a specific project. While Contributing Members can have any member permission level in the Brighthive workspace, Contributors are only able to access Projects where they have been added as "Contributing Members".

.CSV

CSV, or comma separated value, is a file format used by the Brighthive platform for uploads to the Data Asset Catalog and Projects. A CSV file is a plain text file format that stores data in a table-like structure, with each row separated by a comma. If your data contains commas within a single cell, simply enclose that cell with double quotation marks ("Insert Cell Contents Here") to be read as a single cell during upload. 

D

Data Asset

Data Asset refers to any structured data file uploaded to the Brighthive platform. Data Assets can be added through source connections (under Connect > Sources), through upload to the Data Asset Catalog (under Govern > Data Assets), or within individual Projects (under Build > Projects). Data Assets added through Sources can be set to refresh at a specific cadence, while Data Asset Catalog and Project uploads are static. Once data is uploaded, the uploader can add details including an overview of the asset, tags, and schema field descriptions.

Data Destinations

Data Destinations are the primary way to export final data assets from your Brighthive workspace. Users have the choice between downloading data and connecting to an API. Destinations can be configured in Project Flow page.

DBT

Our most commonly used data transformation tool. DBT, or data build tool, makes data engineering accessible by allowing data analysts with basic SQL knowledge to build full data transformation workflows. Your DBT connection details can be viewed in under Connect > Services > Transformation.

E

ETL

ETL, or extract, transform, and load, is a three-phase process where data is extracted from an input source, transformed, and loaded into an output data container or warehouse. Brighthive centralized the ETL process within a single workspace to accelerate time to insight and make it easier to work with your data.

F

G

Governance

Data Governance is a set of policies, practices, and tools that ensure an organization's data is accurate, secure, and usable. Governance is central to each step of the Brighthive workflow, from data validation at upload with target schemas to the creation of tailored policies for each workspace. Organizations' data is housed in separate data warehouses to minimize the security risks of cohabitation and anonymization policies can ensure accurate tagging and tracking of personally identifiable information (PII) and anonymization where required.

H

Help Desk

Center for information related to the Brighthive workspace! Navigate back to the Help Desk home page here. 

I

Input Data Asset

In Projects, Input Data Assets refer to the data loaded into a project from the Data Asset Catalog. Input Data Assets can be viewed in the Project Flow tab or the Input Asset tab, which shows a list of all data assets pulled from the catalog into a specific Project.

Input Data Asset Group

All Input Data Assets are organized into groups, cleverly called Input Data Asset Groups. These groups not only organize input data assets in a project, but can also be validated against a Target Schema to ensure that all data within the group fits a specific structure. Target Schemas can be pulled from the Schema Library in The Hive or created in Projects and added directly to Data Asset Groups.

J

K

L

LLMs

LLMs, or Large Language Models, are the engines behind BrightBot and BrightBot Custom Assistants. When creating Custom Assistants, you can choose between a variety of LLMs to power your agent. Learn more about Comparing LLMs for Custom Agents here.

M

Metadata

Metadata refers to data that describes data, or the context around a data asset. In Brighthive, metadata is captured in a variety of forms, including data asset descriptions, schema field definitions, and dates of upload and last update. Data asset descriptions are a key place for capturing and storing metadata, particularly around the data's source, means of collection, and purpose within a workspace. It is the responsibility of the data asset manager to enrich their data asset with metadata to provide context to others within their workspace. 

N

O

Organization

In Brighthive, each member belongs to an Organization, and each Organization can exist within one or multiple Workspaces. Organizations within a workspace can distinguish between departments within a company, or different companies or agencies collaborating within a broader initiative. Organizations are also the basis for data storage, and the data for each Organization is stored within a separate data warehouse to reduce the security risk of data cohabitation.

Output Data Asset

In Projects, Output Data Assets refer to the data created following a project's Transformation stage. Output Data Assets can be viewed in the Project Flow tab or the Output Asset tab, which shows a list of all data assets created by the Project Transformation step.

Output Data Asset Group

Similar to Input Data Asset Groups, Output Data Asset Groups organized data assets that are created by transformations in a project. Assets in this group can also be validated against a Target Schema to ensure the transformation output matches the target structure of the data product.

P

PII

PII, or Personally Identifiable Information, is relevant when working with any data that information about individuals. When uploading data to the Data Asset Catalog, the upload workflow automatically detects whether a row contains PII. These PII tags can be viewed and validated in the Schema tab within a Data Asset. 

Policies

Admin users are able to set workspace-wide policies to help members understand standards for compliance without delving into legal documents. While not all policies are enforced by the Brighthive platform, the Policies page provides a centralized place to onboard new workspace members to collaborative governance.

Projects

Projects are where the bulk of data work happens within Brighthive. Project Managers can define project goals and invite collaborative members, add input data sources and validate them against schemas, connect data transformations, and connect their data products to visualization tools. 

Q

R

RAG

RAG, or Retrieval Augmented Generation, is an LLM framework that allows agents to pull from additional sources beyond the language model itself. In Brighthive, creating a custom agent with RAG architecture allows users to upload files for the agent to reference while engaging with end users.

S

Schemas

A schema outlines the structure and organization of data within a data asset or database. In Brighthive, the schema for each data asset is automatically parsed during the upload process, and users can add additional details to schema fields. Schemas can also be created ahead of data upload, so schemas can be used to validate the structure of an incoming data asset. 

Services

Services detail the third party tools that underpin your Brighthive workspace. These include connection services, which allow live connections to data sources; warehouse services, which define where data is stored; and transformation services, which allow you to manipulate and prepare data for use in projects. Services are currently configured by the Brighthive team. Reach out to support@brighthive.io for assistance with service configuration.

Sources (or Source Connections)

Once connection services are configured, you can establish source connections to connect third party data sources to your Brighthive workspace. Learn more about Source Connections here.

T

The Hive

The Hive is the home to unstructured data within your Brighthive workspace. The Hive is split into three primary sections: Resources, Terms, and Schemas. These three pages can be utilized to add context that informs projects or data assets connected within Brighthive. External files and unstructured data can be added through Resources, while the Terms and Schemas pages allow users to view and enrich metadata in their workspace.

Transformation

Transformation refers to the process of converting raw data from one format to another by cleaning, validating, or structuring it to make the data ready for further analysis. Brighthive integrates the transformation process in the Transformation step of the Project Flow to create Output Data Assets. 

U

V

Validation

Validation refers to the act of checking or proving the validity or accuracy of something. In the Brighthive workspace, users can validate data assets or schemas by reviewing and confirming the metadata around that particular element. In addition to manual validation, data is validated in the Projects page through defined Input Schemas, which restrict upload of data that doesn't match the target schema within that project. 

W

Warehouse

Warehouses are where data is stored within the Brighthive platform. Each Organization has its own dedicated data warehouse to minimize the security risks of data cohabitation. Data uploaded to Brighthive does not live in the app layer of the Brighthive platform, and is only called directly from the warehouse when necessary in Projects or by BrightBot.

Workspace

In Brighthive, Workspace refers to the window where a user interfaces with Brighthive. One user can be a member of multiple Workspaces, but only needs to be a member of a single one. If a user joins multiple Workspaces, they can see the option to switch Workspaces under the name toggle on the upper right-hand corner of the platform. 

X

Y

Z