Configure the HR500 CSV source
Provisioning tutorial · Step 1 of 10
Load the HR500 dataset and prepare its data model.
Add the HR500 CSV dataset, then prepare its keys and table relationships for the rest of the provisioning workflow.
Add the CSV source system
- Go to Systems > Overview.
- Click Add.
- Select CSV-File for System Type.
- Name the system
HR500. - Click Save.
- The new system is added to the Configured Systems pane.
- Click Configure.
- Select a Drive - share.
- In the Directories pane, navigate to the unzipped HR500 folder.
- In Files, select all five HR500 data files to import.
- Click Save.
- Click Collect, then open a table to confirm that data was collected.
Assign primary keys
The next step is to assign primary keys to tables. Primary keys should be stable, non-mutable, uniquely identifying fields.
- Expand this system's table list and go to the contracts table. Then go to the Columns tab.
- Select
contract_idas the table's Key and Display Name.
The display name can be a different column from the key. It is the value shown when NIM displays records from the table.
-
Click Save.
-
Repeat for the remaining tables:
Table Key Display name contracts contract_idcontract_iddepartments organizational_unitorganizational_unitemployees employee_idemployee_idemployments employment_idemployment_idjob_titles job_codejob_code -
Finally, collect this system's data again, by going to the Overview and clicking Collect.
Set up intra-system relations
Now, we need to establish relations between tables within this system, based on the primary keys we specified.
In NIM, keys do more than enforce uniqueness: they also enable intra-system relations, which determine the joins available in filters.
-
Open the contracts table and select the Relations tab.
-
Click Determine Relations Automatically to identify matching foreign-key and primary-key values.
NIM finds these relationships:
Foreign key Related primary key Cardinality employment_idemployments.employment_idN → 1 manager_idemployees.employee_idN → 1 departmentdepartments.organizational_unitN → 1 job_codejob_titles.job_codeN → 1 -
Enable all the checkboxes in the N-N Relations pane.
-
Click Save.
-
Repeat this process for the other data tables in this system (none of the other tables have N-N relations). -
departmentstable - Foreign keyparent( N ) → primary keyorganizational_unitofdepartmentstable ( 1 ) -employeestable - None -employmentstable - Foreign keyemployee_id( N ) → primary keyemployee_idofemployeestable ( 1 ) -job_titlestable - None -
Collect this system's data once again, by going to the Overview and clicking Collect.
We now have the following keys & relations configured:
If you want an ERD for your NIM tables, you'll need to draw one manually using an external tool. NIM does not currently auto-generate ERDs.