/
User Profiles and Metadata Integration

User Profiles and Metadata Integration

 

User Profiles for Confluence is integrated with Metadata for Confluence. Therefore you can use the following functionality when both add-ons are installed on your Confluence.

Metadata Fields of Type User Profile Element

since Metadata version 3.0.4 since User Profiles version 2.1

If the Metadata and User Profiles add-ons are both installed, it is possible to use existing single- and multi-select user profile elements for metadata fields. This for example allows you to create a multi-select profile element "location" holding all the locations of your company and reuse it in a metadata field which defines for which locations the information on a page is relevant. When adding a new location you only have to do it in the user profile element. It will be automatically available as a value for the metadata field.

To create such a metadata field choose "User Profile Element" as type. Afterward, select one of the suggested single- and multi-select user profile elements. If you don't see any suggestion you will have to add a user profile element first. The created metadata field can be used in metadata sets like any other field. When assigning a value to it you will be presented with the options of the user profile element. If the user profile element is single-select, the metadata field will be single-select too.

To prevent unintentional loss of data it is not possible to delete a user profile element that is used in a metadata field. You will receive an error message when trying to do so. For the removal to work you will have to delete the metadata field first.

 

Caution should be taken when editing user profile elements that are used in metadata fields while the metadata add-on is disabled or uninstalled. In this scenario modifications like deletion of options or the whole element won't be tracked. This can lead to inconsistent metadata values if the metadata add-on is reenabled or reinstalled later on.

User Profile CQL Integration

since Metadata version 3.0.4 since User Profiles version 2.1

The macros metadata-overview and content-by-metadata have a new parameter "User Profile Field Mapping". This parameter is shown if there is at least one metadata field of type "User Profile Element" assigned to a set in the confluence system. By selecting a field the macro automatically matches content with the same value as it is defined in the current user's profile.

The new parameter "Expert filter criteria (CQL)" in the metadata-overview and content-by-metadata macro is now able to handle a metadata field mapping with the current user profile. Here is an example

MYEXAMPLESPACE.metadatafield.metadataprofilefield = "upc.currentUser"

MYEXAMPLESPACE is the space key of a metadata field on the side of this space. Because the metadata field is mapped to a profile field CQL knows how to match these two.

 

Related Articles

 

 

Related content

SubSpace and Metadata Integration
SubSpace and Metadata Integration
Read with this
Integration of Metadata and Comala Publishing
Integration of Metadata and Comala Publishing
Read with this
Does Metadata work with Comala Workflows
Does Metadata work with Comala Workflows
Read with this
Filtering date fields does not work as expected
Filtering date fields does not work as expected
Read with this
Metadata search does not work
Metadata search does not work
Read with this