Comments on: SharePoint 2010 Metadata and Taxonomy Management Overview http://www.endusersharepoint.com/EUSP2010/2010/04/19/sharepoint-2010-metadata-and-taxonomy-management-overview/ Just another WordPress weblog Fri, 23 Jul 2010 01:31:43 -0400 http://wordpress.org/?v=2.9.2 hourly 1 By: Claude Baudoin http://www.endusersharepoint.com/EUSP2010/2010/04/19/sharepoint-2010-metadata-and-taxonomy-management-overview/comment-page-1/#comment-34 Claude Baudoin Wed, 28 Apr 2010 15:48:21 +0000 http://www.endusersharepoint.com/EUSP2010/?p=369#comment-34 I studied Stephanie's previous writing on taxonomy (or "tagsonomy" as facetiously respelled by some authors) last year when doing a study for a client, and I found her arguments for having both a managed taxonomy and the freedom of a folksonomy compelling -- and also remarkably well written. It's good to see that MS is perhaps finally getting it right. Two concerns remain, IMHO: 1. It takes non-negligible human time to review the folksonomy additions, fix the errors including simple misspellings, and examine the terms added by users to promote some into the master taxonomy. The way companies act, this will be seen as overhead and will often not be resourced. Then the taxonomy will become a mess, and people will wonder why "findability" is not as improved by the tags as was promised. 2. There are all sorts of KM systems, including learning management systems, employee directories, etc., that require the same taxonomy. Does MOSS expose a service (through SOA) that allows another application to query the taxonomy? Otherwise, an enterprise will still end up having separate, uncoordinated taxonomies. Thanks for the article, and keep up the excellent work! I studied Stephanie’s previous writing on taxonomy (or “tagsonomy” as facetiously respelled by some authors) last year when doing a study for a client, and I found her arguments for having both a managed taxonomy and the freedom of a folksonomy compelling — and also remarkably well written.

It’s good to see that MS is perhaps finally getting it right. Two concerns remain, IMHO:

1. It takes non-negligible human time to review the folksonomy additions, fix the errors including
simple misspellings, and examine the terms added by users to promote some into the master
taxonomy. The way companies act, this will be seen as overhead and will often not be resourced.
Then the taxonomy will become a mess, and people will wonder why “findability” is not as
improved by the tags as was promised.

2. There are all sorts of KM systems, including learning management systems, employee
directories, etc., that require the same taxonomy. Does MOSS expose a service (through SOA)
that allows another application to query the taxonomy? Otherwise, an enterprise will still end up
having separate, uncoordinated taxonomies.

Thanks for the article, and keep up the excellent work!

]]>