Skill Vendor 1 | Skill Vendor 2 |
---|---|
Python 3.12 (Programming) | Python |
Python 3.13 (Programming) | Python |
Power BI | Microsoft Power BI |
JavaScript (Web Development) | JavaScript |
Data Analytics | Data Analysis |
AI & Machine Learning | Machine Learning |
SQL Database Querying | SQL |
UX Design | User Experience Design |
python
, Vendor 2 only has
one. As we want both Vendor 1 skills to be correctly mapped, they both map to
the same skill for Vendor 2.
It is clear what should be done when we map from Python 3.12 (Programming)
to
Python
. The other way around is more complex, as a decision has to be made:
Python 3.12 (Programming)
Python 3.13 (Programming)
2.
in the scenario above).
Skill Vendor 1 Skill |
---|
Python 3.12 (Programming) |
Power BI |
JavaScript (Web Development) |
Data Analytics |
AI & Machine Learning |
SQL Database Querying |
UX Design |
Python 3.12 (Programming)
skill to Python
in Vendor 2. But now Lisa’s
profile is not following the most optimal mapping anymore! (that would be to
change her original profile to contain Python 3.13 (Programming)
, but that
would change Lisa’s original input).
Instead, when we harmonize, we keep track of all existing skills, and will opt
for using non-primary mappings when it drives consistency in profiles.