Mapping Microsoft SharePoint Managed Metadata
- Andrea Harvey
On This Page
Overview
Microsoft SharePoint products support managed metadata. When using DryvIQ to move content between SharePoint systems, you can map your managed metadata to ensure the informtion transfers. For more information about managed metadata, refer to Microsoft’s documentation for managed metadata in SharePoint.
Retrieving Managed Metadata
You can send a GET message through the REST API to retrieve the metadata for a SharePoint/Office 365/OneDrive for Business connection. You can retrieve the metadata for a file based on the path for the file. Note that the path should include the library name and file name: library/file.ext.
GET {{url}}v1/connections/{connectionID}/files/metadata?path=path
The call will return return the metadata for the file. Make note of the managed metadata column name and value GUID. Alternatively you can look up value GUIDs in the Term Store management tool in the SharePoint site settings. Once you have the column names and term values, you can create a job with a metadata map.
Adding Managed Metadata to the Metadata When Creating a Job
To set up content type metadata mapping when creating a job, you must create a choice map that maps the source values to destination the values using the information provided by the GET metadata_schema endpoint. This information is added to the metadat_map in the transfer block.
{
"transfer": {
"metadata_map": {
"schemas": [{
"mappings": [{
"source": {
"property": {
"name": "Source Managed Metadata column Name"
}
},
"destination": {
"property": {
"name": "Destination Managed Metadata column Name"
}
},
"choices": [{
"source": {
"value": "Source GUID"
},
"destination": {
"value": "Destination GUID"
}
}
]
}
]
}
]
}
}
}