Glossary

    A
  • See TIBCO Data Science – Team Studio analytics model.
  • A flow of connected operators. Created and developed in the Workflow Editor.
  • Associating a dataset makes that data available to the workspace under the Data tab. These are datasets that are not a part of the sandbox schema. You can use these datasets to import data that is not contained within the main data source of the workflow.
  • C
  • User can comment on anything in the Activity pane in the workspace overview.
  • It is a generated table created by a join or select statement on a database data source. It is stored locally on the application database.
  • One can integrate their own algorithms and processes into the TIBCO Data Science – 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.
  • D
  • On the homepage of TIBCO Data Science – Team Studio after logging in, a user can customize their view to create a dashboard of important information. Click the gear icon on the home page to customize widgets.
  • An external data provider, either a Hadoop database or a relational database.
  • This has been disabled by an administrator and cannot be used until it is turned back on. Users may not open workflows or run jobs using this data source.
  • A user has begun to add this data source but has not completed the connection parameters. Users can save some data sources as incomplete. The data source is not usable until the rest of the data is provided.
  • This indicates that this data source is having trouble connecting properly. Verify connection parameters and try again.
  • This has correct connection information and can be used in TIBCO Data Science - Team Studio.
  • 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.
  • The actions a person takes before running an operator or workflow. They are designing/customizing the operator's parameters. This is an important concept to understand when learning about custom operators.
  • E
  • An operator that is at the end of a subflow workflow and is used to connect output to the parent workflow.
  • I
  • Insights are pieces of information that are deemed important to a particular workspace or a workflow. User can add an insight directly or promote a note or a comment to an insight. One can also attach workflow results, files, datasets, and other files uploaded from the desktop to support the importance of the finding.
  • J
  • 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.
  • L
  • Creates a workflow using the architecture of TIBCO Data Science – Team Studio version 6.6.0, including access to all custom operators built for version 6.6.0.
  • M
  • A section of work that a team member or group of members works on. Milestones include a due date that enables the user 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.
  • N
  • Creates a workflow using the architecture of TIBCO Data Science – Team Studio version 7.0.1, including access to all new operators developed to run in Apache Spark 3.2.
  • User can make notes on a workspace or any workfile within that space. Notes show under the Activity pane in the workspace overview and are viewable to those with access to the workspace. Notes can be promoted to Insights and commented on by other user.
  • It can be promoted to Insights and commented on by other user.
  • Notifications alert the user 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.
  • O
  • 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). User can filter the operators based on the intended operation such as Load, Explore, Transform, Model, Predict, and Tools.
  • P
  • An option that you set to control an algorithm.
  • R
  • Running a workflow runs the entire workflow, running all operators and data sources. Users cannot run a whole workflow with invalid operators. Alternatively, they can use a Step Run to run operators that have not run before. To rerun everything from scratch, select Clear Step Run Results from the contextual menu.
  • S
  • A place on the Data tab where a user 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.
  • An account that can be used to provide access to a database data source for multiple members of an organization. This means that the user shares a single set of credentials for the data source.
  • An operator that starts a workflow. Contrast with terminal operator.
  • User can run only the operators and data sources needed to get up to the selected operator for step run in a workflow. This allows for faster iteration so that the user does not need to run the entire workflow again.
  • User can use the sub-flow operator to run another workflow from the current workflow.
  • T
  • 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.
  • A model that is generated from a Legacy 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.
  • An operator that no other operator can directly follow in the workflow. Contrast with source operator.
  • Displays the list of Touchpoints published by the team members.
  • Adds a Touchpoint to the catalog so that it is available to all the members of the application. Depending on the Touchpoint’s settings, it can be run either as the creator or the person.
  • Removes a Touchpoint from the catalog so that it is no longer available publicly for people in the application to view or run them. It is restricted to the members of the workspace from where the Touchpoint originated.
  • Touchpoint wrap the functionality of complex workflows in an interactive application that can be consumed by the business analyst.
  • W
  • 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, a user can upload files (such as images or .zip files) to make them part of the workspace.
  • 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 TIBCO Data Science – Team Studio.
  • User 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. To set the workflow variables, click Actions > Workflow Variables from the workflow user interface. All workflow variables start with the character @.
  • 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 a track of progress on a project. A workspace can be either public or private. User can create a workspace from the workspace page.