Understanding Legacy Traditional Knowledge Labels
User roles
Mukurtu manager, community manager, protocol steward
In Mukurtu 3, Traditional Knowledge labels were fully managed in-site. Local Contexts has since adopted the use of an API key that allows changes to labels and notices to be made in a centralized hub and pushed out to any content using those labels.
This means that if you were using Traditional Knowledge labels in a Mukurtu 3 site, you will no longer be able to customize them or apply them to content. They will migrate to Mukurtu 4 as “legacy” Labels, and will still display on any migrated content they're applied to.
You can either apply new labels to content using a Local Contexts API key or leave "legacy" labels on migrated content.
Information on managing "legacy" labels in Mukurtu 4 is forthcoming.
Tip
To learn more about Local Contexts, see Understanding the Local Contexts Hub. To get started on the Local Contexts Hub, see Manage Local Contexts Projects