Alation Glossary¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
- adjustable-order template¶
A type of template that allows users to adjust the order of fields on the catalog page. See About Templates and Fields for details.
- Agile Approval¶
A collaboration workflow enabling Alation users to request reviews and provide approvals for Article objects ensuring that articles are credible sources of information.
- Alation Analytics¶
A database that surfaces catalog usage data to provide a way for governance officers and analysts to implement better adoption of the Alation catalog and drive more value at their company from exploring ways their users interact with the data.
- Alation catalog¶
The component of the Alation software that serves to catalog and describe data sources offering several applications on top (such as Agile Approval or Stewardship Dashboard). This is often referred to as “the Catalog”. Also see Compose.
- Alation object¶
An entity in the Alation catalog that can have a dedicated catalog page. Almost everything you see in Alation is an object, for example: a data source object, a table object, a query object, or an article object.
- Alation role¶
When you hear Alation roles, it is usually one of the roles a user can be assigned when they join Alation: Viewer, Composer, Steward, Catalog Admin, or Server Admin. Also see Data Source Admin.
- Alation search¶
A set of features that allow searching and finding objects in the Catalog.
- Allie the Robot¶
Our mascot of the machine learning algorithm in Alation. Machine learning is used to suggest comprehensive titles for data objects. You can see Allie’s image in various messages in Alation, and you will also see the “robot head” icon next to an auto-suggested title.
- article¶
An object in the Alation catalog that can be used for data documentation. You can create an article to store some long-form written content. Articles can be added to article groups that help bind related pieces of information together. Articles and article groups are being replaced by Document Hubs.
- article group¶
An object in the Alation catalog that consists of a collection of articles that are based on the same custom article template. See Work with Article Groups for details. Articles and article groups are being replaced by Document Hubs.
- built-in field¶
Fields provided by Alation whose values can be edited by users with appropriate permissions. Some built-in fields can be removed from templates, while others cannot. See About Templates and Fields for details.
- Catalog Admin¶
A role in Alation granted to users whose primary task is curating the catalog and supervising the curation effort by other users.
- catalog page¶
A dedicated page for an Alation object that you see in the Alation Catalog. Catalog pages are based on customizable templates that have built-in and custom fields. Users enrich their catalog by providing field values—information describing the Alation object.
- catalog page template¶
See Template.
- catalog set¶
Alation object that enables you to group data objects together and perform bulk edit operations on custom fields. Bulk edits are done on the Catalog Sets page, rather than on the data object page.
- column lineage¶
Visual representation (a diagram) of how tables, views, and BI reports are derived from other tables, at the column level. Also see Lineage.
- Compose¶
This is the Alation query tool. You can access Compose either using your web browser or by downloading the Alation Compose app to your computer.
- conversations¶
Alation enables you to publicly ask and answer questions through Conversations, which live on any data object, query, result set, or user profile.
- custom field¶
A catalog field created by a user that can be added to catalog page templates. See About Templates and Fields for details.
- custom template¶
A template is a set of fields that are assembled into a page to deliver relevant information about a catalog object. If you have the Catalog Admin or Server Admin role, you can customize catalog pages by customizing the underlying templates. You can add, remove, rearrange, and group various fields to create custom templates that meet the needs of your organization. You can also create your own custom fields to add to templates. Templates can have a fixed order of fields, or they can have an adjustable order, depending on the object type. See About Templates and Fields for details.
- Customer Portal¶
An Alation-managed site for Alation admins. Accessible with a login you receive when you install Alation at https://customerportal.alationdata.com/.
- data source¶
An Alation object representing a database connection in the Alation catalog.
- Data Source Admin¶
A function at the data source level for accessing and editing the settings of a data source. Data Source Admins can view and edit the data source settings, including the connection properties and parameters for metadata extraction, profiling, and query log ingestion. See Access Tab.
- Data Steward¶
See Steward.
- date custom field¶
A type of custom field that stores a date value. See Custom Field Types for details.
- document¶
An object in the Alation catalog that can be used for data documentation, such as data terms, metrics, best practices, and so forth. You can create a document to store some long-form written content. See Document Hubs for details.
- document hub¶
An object in Alation that contains folders and documents. You can have multiple document hubs for different types of documentation, and you can customize how the hub, its folders, and its documents are named. See Document Hubs for details.
- dynamic profiling¶
When enabling dynamic profiling, profiles will be user specific and user initiated, profiling will use user’s database credentials, and automatic profiling will be disabled.
- filters¶
Alation learns from you every time you run a query. If you join tables or use a data expression, Alation will automatically pick it up and enable you to save it for quick reuse. On the table Catalog page, all previously used JOIN clauses are on the Joins tab. Data expressions are on the Filters tab.
- fixed-order template¶
A type of template that has a fixed order of fields on the catalog page. See About Templates and Fields for details.
- folder¶
An object in the Alation catalog that belongs to a document hub and contains documents. See Document Hubs for details.
- glossary¶
An object in the Alation catalog that consists of a collection of terms. You can have multiple glossaries in your Glossary Hub. Glossaries are being replaced by Document Hubs. When you enable Document Hubs, your existing glossaries will automatically become folders in the built-in Glossary document hub.
- Glossary Hub¶
An app in Alation that enables you to create and organize glossaries and terms related to your data. The Glossary Hub is being replaced by Document Hubs. When you enable Document Hubs, your existing Glossary Hub will automatically become a built-in Glossary document hub.
- joins¶
Alation learns from you every time you run a query. If you join tables or use a data expression, Alation will automatically pick it up and enable you to save it for quick reuse. On the table Catalog page, all previously used JOIN clauses are on the Joins tab. Data expressions are on the Filters tab.
- Lexicon¶
A system job that matches abbreviations found in the names of data objects with the comprehensive words, or expansions. Lexicon is used for auto-titling and creating Suggested Words for Article Groups.
- lineage¶
Diagram on the data object page that helps trace the origin of data in Tables and Columns and gives visibility into how data in a source moves and transforms over time. Input data for Lineage diagrams comes from QLI, queries in Compose, and can be added using the dedicated API.
- metadata extraction (MDE)¶
Extraction of metadata from a data source into the Catalog with the goal of synchronizing them and providing Alation users with a representation of the data contained in this source. Metadata extraction can be run manually or on an automatic schedule.
- multi-select picker custom field¶
A type of custom field where you can select multiple text values from a list. See Custom Field Types for details.
- NoSQL database¶
NoSQL databases are software systems that provide storage and query capabilities to support specific data models and access patterns for building modern applications using flexible schemas.
- obfuscate literals¶
When enabled, hides all literals in queries. Only the query owner will be able to see the full query.
- object set custom field¶
A type of custom field that can create references (links) between multiple catalog objects. See Custom Field Types for details.
- object template¶
See Template.
- object type¶
Property of an Alation object that describes what kind of object it is. Each specific Alation object has a type. For example, your MySQL data source is an object of type “data”, or your article “How to use JOINs in Alation Analytics Database” is an object of type “article”.
- Object-Defined Field¶
Object-defined fields are fields that are automatically provided by Alation based on information or functionality associated with a particular object type. Object-defined fields are read-only. Their values are derived automatically from the object itself. See About Templates and Fields for details.
- people set custom field¶
A type of custom field that can store a list of catalog users and groups. See Custom Field Types for details.
- picker custom field¶
A type of custom field where you can pick a single text value from a list. See Custom Field Types for details.
- popularity¶
An indicator of the intensity of use of a data object. Popularity is determined with an algorithm that accounts for both query ingestion (the number of data source accounts that used the object and the number of times the object was used) and Compose usage (the number of Alation users that used the object in Compose and the number of times the object was used).
- profiling/sampling¶
Creation of data samples for the cataloged data sources. When you perform data profiling in Alation, it scans the first 10,000 rows of a table. A data sample is a random sample of 100 rows out of the 10,000 scanned rows intended to provide you an insight to what kind of data is contained in the profiled table without the need to run a query.
- query collaboration¶
A collaborative workflow in Compose that lets users develop queries together. You can co-create queries leveraging the expertise of all Authors and the institutional knowledge. A query Owner can start the collaboration workflow by adding Authors to their queries. All Authors can take turns editing the query statement. They can also invite more Authors to contribute.
- query execution¶
The action and process of running a query using Alation. You may also encounter the term “query run” which is equivalent to query execution.
- query log ingestion (QLI)¶
The processing of the database query logs in order or to calculate Popularity, Lineage, Top Users, and to supply filter and JOIN information to the catalog.
- query result table¶
The results of the query execution. You can save the results of a query as the Result Table object in the Alation catalog.
- reference custom field¶
A type of custom field that can be used to create a reference (link) between two catalog objects. See Custom Field Types for details.
- rich text custom field¶
A type of custom field that stores a block of text. See Custom Field Types for details.
- Server Admin¶
A role in Alation that has access to the full scope of functionality in the Catalog and Compose, including the application settings.
See Query Collaboration.
- standard user¶
A role in Alation that has access to Compose and the main features of the Catalog, with the exception of admin settings and catalog customization tools (such as templates and custom fields).
- Stewards¶
A field on catalog pages of data objects that stores the names of users who are stewarding this data object in the Alation Catalog. The Stewards field can be used for filtering the reports on My Stewardship Dashboard and the curation reports (Curate menu > Curation Progress, Catalog Activity, Data Objects Without Stewards).
- template¶
A template is a set of fields that are assembled into a page to deliver relevant information about a catalog object. If you have the Catalog Admin or Server Admin role, you can customize catalog pages by customizing the underlying templates. See About Templates and Fields for details.
- term¶
An object in the Alation catalog that can be used to document terminology related to your data. Terms are being replaced by Document Hubs. When you enable Document Hubs, your existing terms will automatically become documents in the built-in Glossary document hub.
- Top Users¶
On Schema and Table catalog pages, Alation automatically lists Top Users through calculating expert status. Alation calculates expertise on a data object based on several factors: number of the user’s queries that mention the data object, number of times the user added comments, titles, or descriptions to the data object page, nomination by other users.
- tree table¶
A table-like element of the catalog interface with expandable rows revealing nested elements. Mostly used to represent complex data types, such as records, arrays, or structs.
- virtual data source¶
A type of source object in Alation that can be used to catalog data storage that is either unsupported by Alation with a built-in or custom driver or for some reason cannot be accessed from Alation using the URI (could be for security reasons). There is no automated MDE, Profiling and Sampling, or QLI for Virtual Sources, and the metadata should be uploaded using the API. One example of the use of a Virtual Data Source is to catalog Avro schemas from data streaming platforms. Virtual Sources can be used for querying in Compose if the database supports SQL dialects and if you choose to add the Compose connection information.