Rhino FCP allows you to easily and securely import datasets that you can use in your project. This article explains how you can import datasets from the following:
- Tabular Data files that are in the Rhino Client File System (such as a CSV or Parquet file) or a supported database.
- File Data that is in the the Rhino Client File System such as a client mount directory (or subdirectory) rhino_data directory (or subdirectory). These files are typically non-tabular files, such as code, images, or generic data in files or a folder.
- DICOM Data stored on a DICOM Server or DICOM files that are in the Rhino Client File System.
NOTE: If you'd like to import datasets using Rhino SDK, see Creating a New Dataset or Dataset Version.
Prerequisites
Before you import your dataset, you’ll need to do the following:
- If you are planning to import your dataset directly from a database, make sure that the database is supported (see Import Tabular Data from an SQL Server for more details.) If not, you can export the file from your database and import it as a flat file. You’ll also need database access credentials like the database username and password for your account, as well as your database name, port, and URL.
- If you are planning to import from one or more files (tabular, DICOM, or other files), you’ll want to upload them to the Rhino Client File System.
- If you are planning to import from a DICOM Server, you’ll need the host, port, and prefix, as well as your username and password.
You will also need to determine whether you have sensitive data in your dataset. By default, sensitive data is selected; to learn more about how sensitive data is handled in Rhino FCP see Sensitive Datasets.
Open the Dataset Page
To open the Datasets page, do the following.
- Select Datasets from the left-side menu.
2. The Datasets page appears. The Overview link should already be selected.
The name of each dataset, along with the version, data schema, date created, number of rows (or failed import status), and creator appear for each version of the dataset. A three-dot menu appears to the right side of each version of each dataset entry.
| Item | Description | Notes |
| Name | Name of the Dataset. Dataset versions are auto-numbered sequentially in the order of creation. If you see gaps in version numbers, numbers that do not appear were deleted by a user. |
|
| Version | Version of the dataset, starting with 0. Also indicates whether the dataset has been marked as having sensitive data. An exclamation mark appears if an error occurred with importing the dataset. | Troubleshooting information can appear here. |
| Data Schema | Indicates the name of the data schema. If you’ve auto-generated, the name of the schema includes the version number. | |
| Date Created | Indicates the date the dataset was generated in Rhino FCP.. | |
| Number of Rows | Indicates the number of rows in the dataset. If there was an issue with import, a message appears instead. | |
| Creator | Indicates the name of the creator. | |
| Three-Dot Menu | Provides additional actions that can be performed on the dataset record. |
Open the Import New Dataset Page
To open the Import New Dataset Page, do the following.
- In Datasets page, select Import New Dataset to open the Import New Dataset screen.
- Enter your name and a description of your dataset.
- Select your workgroup.
- Indicate whether you want to auto-generate the schema from the data or select one from the list (if there is one available).
- Indicate the location of the dataset that you want to import.
- Use the table below for the next step.
| To do this ... | Go to the following subsection .... |
| Select tabular data from a SQL Server, like data from a SQL table. To use this option, you'll need the database type, name, URL, port, and access credentials. | Import Tabular Data from an SQL Server |
| Import data from the Rhino Client File System. To use this option, you'll need to know the path to the file. | Import Tabular Data from the Rhino Client File System |
| Import non-tabular file data such as images or other types of data. To use this option, you'll need to know the path to the file. | Import File Data (Non-Tabular) |
| Import DICOM Data. To use this option, you'll need to know the credentials to the DICOM system. | Import DICOM Data |
Import Tabular Data from an SQL Server
You can import tabular data from a SQL Server. Supported databases are: IRIS, MariaDB, MSSQL (Microsoft SQL), MySQL, Oracle, PostgreSQL, and SQLite.
To import tabular data from a SQL database, do the following.
- Open the Import New Dataset page.
- Enter your name and a description of your dataset.
- Select your workgroup.
- Indicate whether you want to auto-generate the schema from the data or select one from the list (if there is one available).
- In the Import New Dataset section, in the Location section, slide the Tabular Data to the right, then select SQL Server.
- Enter the following details so that Rhino FCP can connect to your database.
- Database Type - Select the type from the drop down list.
- Database Name - Enter the database name.
- Database Port - Enter the port.
- Database URL - Enter the database URL.
- Username - Username to gain access to your database.
- Password - Password to gain access to your database.
- Timeout Seconds - The number of seconds for the timeout. The default number is typically adequate, but you can adjust this as needed.
- Enter a SQL query to pull data from the database. You will want to create a simple query that will enable you to test your credentials, such as SELECT * FROM [enter_table_name_here] LIMIT 10; Note that other types of queries, such as determining the name of the database that you are connecting are not supported.
- Select the Import New Dataset button. The Import New Dataset page closes, and the dataset appears in the Datasets page.
- If you click on the three-dot menu, there are several options that are available.
Import Tabular Data from the Rhino Client File System
To import tabular data from a CSV or Parquet file, complete the following steps.
- In the Import New Dataset section, in the Location section, slide the Tabular Data to the right, then select File.
- Enter the path to your file. The path should be in the Rhino Client File system. For more information, see: Mounting Storage to Your Rhino Client, Importing to and Exporting Datasets from Your Network Storage, and Example 2: Defining a Dataset with File Data.
- Select the Import New Dataset button. The Import New Dataset page closes, and the record of the dataset appears in the Datasets page.
Import File Data (Non-Tabular)
To import file data from non-CSV files, complete the following steps.
- In the Import New Dataset section, in the Location section, do the following:
- Slide the Tabular Data to the right and select Rhino Client File System. The File Data and DICOM Data sliders become active.
- Slide the Tabular Data slide to the left.
- Next, slide the File Data slider to the right. The File Data section opens.
- Enter the path to your file. The path should be in the Rhino Client File system. For more information, see: Mounting Storage to Your Rhino Client, Importing to and Exporting Datasets from Your Network Storage, and Example 2: Defining a Dataset with File Data.
- Select the Import New Dataset button. The Import New Dataset page closes, and the record of the dataset appears in the Datasets page.
Import DICOM Data
To import DICOM Data, complete the following steps.
- In the Import New Dataset section, in the Location section, slide the DICOM Data slider to the right. You can choose to provide the path to the DICOM Files or connect to the DICOM Server.
- By default the Files option appears. If you want to import DICOM files by specifying the file path, enter the path in the DICOM PATH text box. You’ll need to have already downloaded the files to a path that is part of the Rhino Client File system. For more information, see: Mounting Storage to Your Rhino Client, Importing to and Exporting Datasets from Your Network Storage, and Example 2: Defining a Dataset with File Data.
- If you would prefer to enter the DICOM Data from the DICOM Server, select the DICOM Server button.
- Enter the Host, DICOM Web Port, DICOM Web Prefix, as well as the Username and Password for access.
- Select the Import New Dataset button. The Import New Dataset page closes, and the record of the dataset appears in the Datasets page.
Troubleshooting Dataset Imports
To troubleshoot data imports, complete the following steps.
- Hover the pointer over the exclamation point to view the error message. The error message provides information that can help you troubleshoot.
- Select the three-dot menu, then select Show dataset configuration to view the setup information.
- Check your configuration:
- Is your username correct?
- Are your connection details correct?
- Are your file paths correct?
- If you are connecting using a SQL query, make sure that table names and fields are spelled correctly. If needed, try a different query.
- If a SQL query seems to be correct, try connecting to the database directly using the same credentials that you used in Rhino FCP. Also, try running the query against the database to ensure that the credentials and queries are correct.
- If needed, try creating a new version of the import and running it again.
- Contact us if you have any other issues.
Importing Datasets at a Collaborating Site
Given the right permissions, it is possible for users to import Datasets at other sites (and not just their own site). This is useful in case collaborators prefer to only prepare the data and not perform the Dataset import operation on the Rhino FCP.
To perform a remote Dataset import, a user’s role must have the “Import and export Datasets” permission for that site. For example, if you are the Workgroup Admin of the site that created the project (hence you are the Project Lead Admin, or PLA), then the collaborating site must enable the “Import and export Datasets” permission for the PLA persona.
To trigger the Dataset import at the collaborating site via the UI, follow the same process for importing a Dataset to your own site via the UI, and in the Select Workgroup dropdown, select the Workgroup of the collaborator. Make sure to input the data file locations on the collaborator’s Rhino Client.
To trigger the Dataset import at the collaborating site via the SDK, follow the same process for importing a Dataset to your own site via the SDK, and in the “workgroup_uid” field pass in the UID of the collaborator’s workgroup.
Related Topics
- Creating a New Dataset or Dataset Version Using Rhino SDK and SQL
- Sensitive Datasets
- Exporting a Dataset