05 Oct 2011 5 Comments
Recently I’ve been using the Managed Metadata Store in SharePoint 2010 and been amazed by the lack of proper import/export functionality.
It feels like a blast from the past to be able to only import a CSV file… CSV?!? What happened to proper XML? What happened to Export? What happened to being able to transfer (meta)data between farms (like test and production) since the builtin Import insists on creating new TermSets and not update existing ones (and yes your managed metadata linked site columns do in fact store a strong reference, not just a name, so you’ll loose the link).
I couldn’t find any existing Powershell commandlets to the rescue either.
I couldn’t readily bing ;-) any usable scripts for this.
What I did
So I built a powershell script to take a CSV file and import it into the Term Store and merge it with any existing term store already there.
Point is then you can still use the CSV file you likely already hold. You can use the TermSetImporter to export CSV files from your existing environment.
If you are starting Greenfield, then I recommend to use excel with some macros to create the Term Sets (then your users can create them instead of you) or you might just let your users loose in the term store manager.
How to use
Second, fire up powershell (on a SharePoint server), write:
. ./MergeTermSets.ps1 csvfile groupname urlForASharePointSite
Do remember the “dot space” at the start of the line. The second “./” is just the path for the ps1 file in this case.
The urlForASharePointSite is optional and will default to http://localhost:2010 which likely corresponds to a valid SharePoint Central Admin site on 50% of all SharePoint installations. Watch the output log. If something goes wrong it’s likely that you should have a look in your CSV file for errors and/or whether or not the managed metadata store is connected properly.
- I’ve tried to do some tricks to handle encoding properly and I also trim spaces which really causes the term store to stumble (it will trim spaces and every subsequent comparison the script might do will fail).
- Note that LCID and the parent Terms need to be set on every line in the excel sheet. Don’t blame me I didn’t make that part ;-)
- Terms are only added not updated, i.e. I don’t try to keep stuff like descriptions in sync
- No fancy stuff, no merging, no deletions, deprecation etc.
Hope it’s useful for you too.