The issue under analysis here is how to handle non-unique IDs
This is one of a series of articles on solving common data issues derived from in-house experience of Consulting projects using OrgVue
| 5 Common Reasons for Duplicate IDs | Resolution | |
| 1 | True duplication of rows | Check that each property is identical and delete duplicates. |
| 2 | One position filled by multiple people | Link a position hierarchy to a people dataset by FTE (assuming a job share situation or similar). |
| 3 | One position/person sits in multiple departments or business areas | Make use of multiple reporting line functionality and/or comma separate the non-matching values |
| 4 | Vacancies/new positions have blank or common IDs | Create a standard system for these IDs e.g. “New-<row # in source >” (NB. track which IDs have been used by which tranches of positions) |
| 5 | Changes over time requires cloning of roles | Concatenate ID with start date of each row |
Steps to resolve non-unique IDs
| Check data quality | Use the Data Types & Patterns Dashboard in OrgVue to identify the number of duplicates. |
| Filter to duplicates | Filter the data to only the nodes with ‘Yes’ for the metadata property ‘Is Duplicate’ |
| Identify root cause(s) | Inspect the duplicates and identify the root cause and resolution from the list above |
| Resolve | Manipulate and cleanse the duplicate IDs: Excel Alteryx OrgVue |
| Upload working data | Re-upload the data to OrgVue in the amended format |
If you have any additional queries arising from the above, please select the Submit A Request link from the top right of this screen to contact OrgVue Support
This article was authored by Ben Marshall from the OrgVue Consulting team
Comments