Organize assets in a project
An project is a collection of assets that you use to achieve a particular data analysis goal.
Your project assets can include:
- RStudio files
- Data sets
You can also export or import a Watson Studio Local project as a ZIP or TAR.GZ file.
Watson Studio Local provides a sample project named dsx-samples, available to all users, with sample notebooks to help get you started. Although you can create new notebooks, models, scripts, and data sets, you cannot add jobs, collaborators, or SPSS Modeler flows.
Tasks you can perform:
- Create a project
- Manage collaborators
- Manage assets
- Add data sources
- Publish assets
- Export a project
- Rename a project
- Delete a project
- View all projects
- Create a script
- Set up runtime environments
- Run jobs in the background
Create a project
To create a project, go to the Projects list and click Add Project.
For a new blank project, click the New tab.
To import a preexisting project from your local device, click the From file tab and upload the ZIP or TAR.GZ.
To import your project from a GitHub, GitHub Enterprise, BitBucket, or BitBucket Server repository, click the From Git repository tab. To set up the connection to the repository, you must save a GitHub or BitBucket personal access token. See Import and commit projects on a Git repository for details on how to work with a Git repo.
|Project type||Collboration privileges||Master repository||Repository copy|
|Standard||Managed in Watson Studio Local||Master repository exists in the Watson Studio Local cluster file system||Each collaborator gets a copy|
|GitHub||Managed outside of Watson Studio Local||Master repository exists in GitHub||Each user gets a copy when the project is imported from GitHub|
|BitBucket||Managed outside of Watson Studio Local||Master repository exists in BitBucket||Each user gets a copy when the project is imported from BitBucket|
|Library||Managed in Watson Studio Local||No master repository||No repository copy|
Click Create. Your new project opens and you can start adding collaborators and assets to it.
If you have Admin permissions for a project, you can add collaborators, change collaborator permissions, or remove collaborators from that project on its Collaborators page.
The collaborator permissions are:
- Can view the project, accept changes, and commit changes to their own local copy of the project.
- Can control project assets. Can accept, commit, and push changes.
- Can control project assets, collaborators, and settings. Can accept, commit, and push changes.
From the Git Actions icon ( ) in the project action bar, an Admin or Editor can push and commit changes by clicking Push and Commit. A Viewer can add an asset but cannot push changes. An Admin, Editor, or Viewer can pull changes from the master repository by clicking Pull, or reset the project to what is currently in the master repository by clicking Reset next to the project.
You can click Leave next to a project to remove yourself from it. However, if you are the only collaborator with Admin permissions, you must give another collaborator Admin permissions before you can leave the project.
If you have Admin or Editor permissions on a project, you can add assets from its Assets page.
If you have Admin permissions on a project, you can delete an asset by clicking Delete next to it.
Add data sources
A data source provides data for your project. For example, a database table or data stream. A data source allows you to securely store information about your database and credentials. To add a data source, go to the Data Sources page in your project.
A project Editor or Admin can share a read-only copy of the asset either within the Watson Studio Local community or with people outside of Watson Studio Local (for example, a Jupyter notebook, HTML file, PDF, text file, or PNG graphic). To do so, go to the Assets page and click Publish next to the file. The publish action creates a read-only snapshot of the current version of the asset, copies it to a published content directory in the user-home file system (if the file already exists, then it is versioned), and automatically generates a URL (except for models) where the asset can be viewed.
The following assets can be published:
- "Static" content such as HTML files
- Jupyter notebook content
- "Local" data sets
- R Shiny web apps
You can set the following content visibility permissions for the published asset (except for models):
- All users with the URL (anyone outside of Watson Studio Local can view it).
- Any authenticated user (only signed in Watson Studio Local users can view it).
- Restricted to members in the selected project (only collaborators in the selected project can view it). You can only publish to projects that you have Admin access to, and you cannot publish an asset to a project that was imported from GitHub (because these are not Watson Studio Local managed projects).
If you publish a Jupyter notebook, then the published copy is automatically converted to HTML. You can publish the notebook with the following options:
- You can either rerun the entire notebook (might take awhile) or publish it as-is.
- You can either include code cells in the published copy, or hide the code cells so that only the output appears.
If you publish an R Shiny app, then the URL displays it as an interactive UI where users can dynamically input their own variables to explore trends.
Watson Studio Local then automatically generates a permalink URL to the published asset (except for models) that you can copy. Alternatively, Watson Studio Local users can view the published asset in the Published Assets page. Note that the Published Assets page only shows assets that the signed in Watson Studio Local user has permissions to. To unpublish a file, you can go to the Published Assets page and click Unpublish next to it.
Export a project
You can download a project as a ZIP or TAR.GZ file by clicking Export as next it. Note that the environments in the project do not get exported.
Rename a project
If you have Admin permissions on a project, you can rename it by clicking Rename next to it. This renames the project for all of the collaborators, and automatically stops the Admin's runtimes active for that project. When the renaming completes, any access to notebooks or RStudio will automatically start up the runtimes inside the context of the new project. The Admin can also choose to manually start them in the Environments page. Because the containers are not stopped for the collaborators, each collaborator must stop the runtimes associated with the old project name in the All Active Environments page. Any subsequent access to notebooks and RStudio would automatically bring up the runtimes with the correct project name context, or the collaborator can go to the page to manually start runtimes. Also, collaborators should verify that assets like notebooks and scripts do not directly specify the project name, for example, in any of the paths (the paths should always be relative for portability).
Delete a project
If you have Admin permissions on a standard project, you can delete it by clicking Delete next to it. This deletes the project for all of the collaborators, and deletes all assets (and the storage directories) associated with the project. If necessary, a Watson Studio Local admin can manually recover deleted projects from the Watson Studio Local system's recycle bin directory.
If an Admin deletes a GitHub project, then only the Watson Studio Local copy of the project will be deleted (not the remote repository on GitHub).
View all projects
Click the Tree View icon ( ) to view all projects in the system and expand their contents. You can click on any folder, Jupyter notebook, or CSV file to preview it.