Use Cases are folder-like containers inside of DataRobot Workbench that allow you to group everything related to solving a specific business problem—datasets, models, experiments, No-Code AI Apps, and notebooks—inside of a single, manageable entity. You can share whole Use Cases as well as the individual assets they contain.
The overarching benefit of a Use Case is that it enables experiment-based, iterative workflows. By housing all key insights in a single location, data scientists have improved navigation and a cleaner interface for experiment creation, and model training, review, and evaluation.
Specifically, Use Cases allow you to:
Organize your work—group related datasets, experiments, notebooks, etc. by the problem they solve.
Find everything easily—removing the need to search through hundreds of unrelated projects or scraping emails for hyperlinks.
Share in collections—you can share the full Use Cases, containing all the assets your team needs to participate.
Manage access—add or remove members to the Use Case to control their access.
Monitor changes—receive notifications when a team member adds, removes, or modifies any asset in your Use Case.
See the associated FAQ for important additional information.
When you launch Workbench, you are brought to the Use Case directory. If it is your first visit, the page will be empty. After your first Use Case is started, the directory lists all Use Cases either owned by or shared with you. Use Case contents is provided in tiles and in a table:
The tiles display the six last-modified Use Cases. Each tile provides an at-a-glance count of the Use Case's assets.
The table displays all Use Cases in your directory. Initial pagination defaults to five Use Cases, but you can change the display from the dropdown on the right:
For each Use Case, the table displays:
- Assets: The number of associated datasets, experiments, apps, and notebooks.
- Metadata: The creator, last modification, and membership.
Click the arrows to the right of a table column to sort the table by those entries. Click the three dots to the right to delete the Use Case.
To create a new Use Case:
From the Workbench directory, click Create Use Case in the upper right.
Provide a name for the Use Case and click the check mark to accept. You can change this name at any time by opening the Use Case and clicking on the existing name.
Click Add new:
From here you can begin adding assets or create a new Use Case.
To work with an existing Use Case:
From the Workbench directory, click on any tile or table entry. Both methods resolve to the same location—inside the selected Use Case.
Review the assets associated with the Use Case:
Element Description1 Asset summary Provides a total count for each asset type associated with the Use Case.2 Display controls Sets the "last modified" criteria for the list-format asset display.3 Asset metadata Reports the asset type, last modification date, and Use Case member who made the modification.4 Asset control Provides options for working with the asset. Options are dependent on the asset type:
- Experiment: Delete from Use Case.
- Dataset: Explore (preview data), wrangle (if applicable), start modeling (create a new experiment), remove from Use Case (remains in Data Registry).
Click Add new to begin adding assets or create a new Use Case.
Managing a Use Case includes:
|Rename the Use Case||Click on the existing title and enter the new name. The change is immediately reflected on the page and in the Use case directory. It also changed for all members.|
|List only specific assets||Click on the asset tab to filter the contents of the table below. Table content is dependent on asset type.|
|Manage team members||View the teammates with access, and their roles. Click Manage members to share a Use Case with other team members.|
|Delete the Use Case||Click the three dots to the right to delete the Use Case.|
With Workbench, when you share a Use Case, the recipient gets access to all the associated assets.
To share a Use Case:
From the Use Case info pane on the right, click Manage members.
A sharing modal opens. Enter one or more team member email address(es), click the name on the associated dropdown, and set the desired permissions level (role).
From here, you can: