The SharePoint 2013 term store is a “farm” level repository of hierarchical term sets and terms used by SharePoint for both metadata and navigation.
If you are using the Office 2013 preview environment, by default the term store administrator is blank – this prevents anyone from creating new terms. You can change this by going into the SharePoint administration section and selecting term store:
In order to create new groups and then assign permissions to other people to manage the group and/or contribute term sets to the group:.
Once you have configured these settings, you should now be able to create and manage new groups and term sets.
To create a new term set hierarchy, you can first create your own group:
In this sample, we’re going to create a list of diseases for use in a medical term set. We create first a group called “Diseases” and then a Term Set called “Diseases”:
There are a few interesting settings in the term set configuration:
- Owner: This is the person who “owns” the Term Set
- Contact: email address of someone to contact about the Term Set
- Stakeholders: users assigned as Stakeholders will be notified when the Term Set changes
- Submission Policy: dictates whether end users can add new terms (for example, in a folksonomy context) or whether the term set is controlled by metadata managers
- Available for Tagging: the term set is available to end users for tagging content
- Use This Term Set for Site Navigation: makes this term set available to be used to site navigation
- Custom Properties: allows you to store additional metadata to describe your term set.
Creating Terms is easy – just start creating your terms as a hierarchy through the term store tool:
You can also add translations of these terms into multiple languages if you have turned on the working languages in the Managed Metadata settings:
Once you have turned on a new language, you can switch between languages in your term store and supply the translations to your terms:
One of the cool features in SharePoint 2013 will be the automatic translation feature – however, when I tried it in preview it failed to work: