SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been given a task to import metadata from an external web service (which is itself interrogating a Trim CMS) into SharePoint 2010 list. I've been able to acheive the task by building a client application that uses the SharePoint 2010 client object model but now that I'm looking at options for deploying the application I'm wondering if there is a better option.

I've started reading about timer jobs, business connectivity services, content deployment paths and there are probably more options. Should I be doing my import using one of those approaches or something else rather than via an external application?

share|improve this question
up vote 0 down vote accepted

Firstly I would be using the managed meta data service to store all your enterprise metadata.

Secondly you will need to write custom code that runs in the context of a timer job that will maintain the Term Sets in your managed metadata service to be in line with the external web service.

As long as your web applications are consuming the metadata service then all of them will have access to the latest metadata coming from your Trim CMS.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.