Glossary

A

Alpine model: See Team Studio analytics model.
Analytic workflow: A flow of connected operators. Created and developed in the Workflow Editor.

comment: People can comment on anything in the Activity pane in the workspace overview.
custom operator: One can integrate their own algorithms and processes into Team Studio analytics engine using the Custom Operator Framework. Custom Operators are written using Scala or Java and can harness the power of Spark for advanced machine learning and transformations.

dataset: Datasets come from databases, HDFS, or uploaded files such as CSVs. Datasets are part of a workspace, and they are used within workflows, Touchpoints, and sandboxes in order to perform analyses.
data source: An external data provider, either a Hadoop database or a relational database.
design time: The actions a person takes before running an operator or workflow. He or she is "designing"/customizing the operator's parameters. This is an important concept to understand when learning about custom operators.

exit operator: An operator that is at the end of a subflow workflow and is used to connect output to the parent workflow.

job: A scheduled task that is created in a workspace. A job can be run on a regular time interval, or on demand. Jobs are useful for updating data automatically over time or run specific tasks overnight.

milestone: A section of work that a team member or group of members works on. Milestones include a due date that enables people to see at a glance the progress of a particular analytic project. Milestones are shown on the workspace page under the Milestones tab, and also on the workspace overview. One can also change the status of the project to one of the three available options: On Track, Needs Attention, or At Risk.

note: People can make notes on a workspace or any workfile within that space. Notes will show under the Activity pane in the workspace overview and will be viewable to those with access to the workspace. Notes can be promoted to Insights and commented on by other people.
notification: Notifications alert people of important changes in the application, such as job results or collaboration information. When someone adds another person to the workspace, that person gets a notification. Many types of activities can have notifications, which can be configured individually.

operator: An operator encapsulates some algorithm or transformation within a workflow. Operators show up as a list on the sidebar of the application within the workflow editor, and can be dragged to the canvas and connected to other operators or data sources. They are one of the main building blocks for workflows (the other being data sources). People can filter the operators based on the intended operation such as Load, Explore, Transform, Model, Predict, and Tools.

source operator: An operator that starts a workflow. Contrast with terminal operator.
shared account: An account that can be used to provide access to a database data source for multiple members of an organization. This means that people will share a single set of credentials for the data source.
sandbox: A place on the Data tab where people can bring in their training schema and perform simple explorations with the help of visualizations. One can also create external views from the sandbox datasets. Sandboxes are only available for database data sources.

tag: Tags can be used to categorize datasets or results within the application. Tags can be added to any work file. Selecting a tag brings up a view of all work files with that tag.
Team Studio analytics model: A model that is generated from a workflow and is saved as an .am file. This allows the portability of models from one workflow to the other without having to build the whole model again. The Alpine models are saved under the Work Files tab of a workspace.
terminal operator: An operator that no other operator can directly follow in the workflow. Contrast with source operator.
Touchpoints: Touchpoints wrap the functionality of complex workflows in an interactive application that can be consumed by business owners and people who are not data scientists.

workflow: A collection of datasets and operators that perform analytic tasks. A workflow is where data scientists build out models using the available operators and algorithms in Team Studio
workflow variable: People can override default parameters and define their own workflow-wide variables using a workflow variable. Workflow variables can be used to set default paths and parameters for HDFS, configure operator parameters, and enable input via Touchpoints.
workspace: Workspaces allow team members to collaborate on a data science project. Workspaces hold work files and can also have scheduled jobs, milestones, and associated database and Hadoop datasets under the Data tab to keep track of progress on a project. A workspace can be either public or private. People can create a workspace from the workspace page.
workfile: Any file that is within the Work Files section within the workspace. Work files can be workflows, SQL files, CSVs, Touchpoints, Alpine models , or result files saved to the workspace. In addition, people can upload files (such as images or .zip files) to make them part of the workspace.