Taxonomy, Metadata and Information Architecture in SharePoint 2010 – Series Summary and Conclusions
Guest Author: Jeff Carr
Our enterprise systems themselves are only able to take us so far, and it’s crucial to be cognizant of the fact that there’s still a lot of outside work that needs to be done. The underlying foundation required to leverage our technological capability is derived from the establishment of strong publishing models, standard workflow processes, corporate governance, continuous taxonomy management and well trained users that have been included as key stakeholders throughout the design process.
The many great features and functionality offered as part of the SharePoint 2010 platform are sure to provide the foundation for better management of information in the organization. Even with the introduction of the Term Store Management Tool and many of the other areas discussed in this series, it’s important to return to the beginning and remind ourselves that SharePoint itself, at least at this point in time, is not intended nor should it be perceived as an enterprise-wide taxonomy management tool. SharePoint 2010 still lacks functionality in a number of key areas, such as the ability to perform auto-categorization and the management of complex relationships between terms.
SharePoint is one of many enterprise solutions we employ, and to make it effective we must ensure that we take the steps necessary to fully understand our domains of knowledge. Doing so provides us with the ability to design appropriate solutions that best describe in detail the world in which we operate. To fully leverage our technical capability, we must strive to implement solid processes around information architecture and ensure we understand conceptually how they need to be represented within our technological environments.
The development of enterprise taxonomy, as a concept in and of itself, is a technologically agnostic exercise. Its application to technology as an enrichment activity is where the rubber meets the road and the benefits are realized. Without a solid foundation, chaos in terms of findability and a good user experience are inevitable. With it, we stand an increased chance at success.
Guest Author: Jeff Carr
Jeff Carr is an Information Architect and Search Consultant with Earley & Associates specializing in user centered information design. Working with SharePoint since 2003, he has been involved in the design, development and integration of web-based solutions from intranets and extranets to public facing websites for a variety of large enterprises across a wide range of industries.
- SharePoint 2010 - What You Need to Know About Taxonomy, Metadata & Information Architecture
- SharePoint 2010 - Using Taxonomy & Controlled Vocabulary for Content Enrichment
- SharePoint 2010 - Using Social Features for Personal Classification & Improved Findability
- SharePoint 2010 - Using Taxonomy & Metadata to Improve Navigation & Browsing
- SharePoint 2010 - Using Taxonomy & Metadata to Improve Search & Discovery
- SharePoint 2010 - Share Content Types Across Site Collections
- SharePoint 2010 - Using Retention Stages to Manage the Lifecycle of Information
- SharePoint 2010 - Administering Taxonomy Using Term Store Management
- SharePoint 2010 - Importing Taxonomy Using the Managed Metadata Import File
- Taxonomy, Metadata and Information Architecture in SharePoint 2010 - Series Summary and Conclusions
Thanks for the series Jeff, as we move toward a 2010 upgrade, this has been very helpful!
Jeff,
I read your series with great interrest but can’t figure out
if the abilitity to navigate via Managed Metadata and use key filters etc… is limited to what is available OOTB on a list ‘view’.
Could the control, fields, tree type w/ expand and collapse, key filter w/ search as you type etc…
be available as a ’separate webpart you could drop on a page and connect to a DVWP or LVWP?
Thanks alot for sharing!
Greg