Why does each tag need an ID when importing a taxonomy?#
When creating a taxonomy via import, or updating one via re-import, the “id” column is required. In addition, it must be unique for every row. There are two reasons why such IDs are required.
Matching external systems/taxonomies#
Secondly, the IDs can be used to keep your taxonomy in sync with an external system.
For example, you could have an airports taxonomy:
ID |
Value |
ORD |
Chicago O’Hare International Airport |
LAS |
Harry Reid International Airport |
LAX |
Los Angeles International Airport |
BOS |
Boston Logan International Airport |
In this case, using the airport codes as the ID makes it easy to align the tags with other systems that reference airports, accounting for the fact that some airport names may be different (e.g. the Boston airport may be called “General Edward Lawrence Logan International Airport” or “Logan Airport”; the “Harry Reid International Airport in Las Vegas” was previously known as “McCarran International Airport”; etc.)
As another example, learning outcome standards often have unique identifiers assigned to individual concepts. For example, the mathematics skill “Extend The Properties Of Exponents To Rational Exponents” has the ID “HS.N-RN.A.1“, which can be used to cross-reference it across various systems and publications. If you are creating a taxonomy related to learning outcomes, you can use these unique identifiers as the IDs.
Maintenance chart
Review Date |
Working Group Reviewer |
Release |
Test situation |