Skip to main content

Workspaces

Workspace.png

The work of a team is organized in workspaces, allowing to structure collaboration. A workspace serves typically as a silo to store use cases linked to a particular topic, e.g. one may create a workspace for all use casess related to predictive maintanance.

The default workspace​

Each user's personal team contains a single workspace: the default workspace.

DefaultWorkspace.png

The default workspace shares all the same characteristics of a regular workspace, with two additional properties:

  • The default workspace cannot be deleted. It is always there, and though a user is not obligated to make use of it, it will keep existing withing their TIM environment.

  • The default workspace is on the default 'working directory' of the TIM Engine. If any requests are sent to TIM - from any platfrom, SDK or directly through the API - without specification of the relevant workspace, the resulting data will be handled in this default workspace, in the personal team of the user who made the request.

Workspaces in the navigation side bar​

The navigation side bar that is situated to the left side of the screen (see below) shows a list of locations defined as a combination of a team and its associated workspaces.

WorkspacesOverview.png

The side bar navigation gives a list of all locations that are available to a user. User may collapse teams that are not in use often and unfold only teams that user is interested in. Unfolding a team shows a list of workspaces of that team.

Workspace management​

WorkspacesAdding.png

  • Adding: New workspace may be added by navigating to team detail page (see screenshot above) and clicking on "Add workspace" action.

  • Editing: Editing a workspace allows you to update its name and its description (see the screenshot below later in the text).

  • Deleting: Be careful with deleting a workspace: deleting a workspace will also permanently delete any data contained in this workspace. This includes all datasets and use cases contained in it, the experiments contained in these use cases and the ML jobs contained in these experiments (see the screenshot below later in the text).

Inside a workspace​

There are two types of assets that sit in a workspace: datasets and their associated use cases.

WorkspaceDetail.png

From this page, a user can easily browse to a specific use case, experiment or dataset (version) of interest. A user can also create a new use case in the workspace, edit or delete an existing use case or import a use case into the workspace.

  • Creating: Creating a new use case allows the user to set its name and description, as well as the business objective, business value, business KPI and accuracy impact of the use case.

  • Editing: Editing a use case allows the user to update its name, description, business objective, business value, business KPI and accuracy impact.

  • Deleting: Be careful with deleting a use case: deleting a use case will also permanently delete any data contained in this use case. This includes the experiments contained in it and the ML jobs contained in these experiments.

  • Importing: Importing a use case empowers users to collaborate with people outside of the user group and even outside of their license. It also provides an intuitive way to start exploring exemplary templates from the Use Case Library.