Taxonomy development

March 28, 2012 - 10:36 GMT

I recently taught the Information Architecture for SharePoint class in Chicago.  Each time I teach this class, I gain more insights into how SharePoint content needs to be organized.  This last time, I had some new thoughts on how to consider a site map. 

December 15, 2011 - 11:43 GMT

SharePoint taxonomies are new and exciting. For the first time a widely adopted content management tool can manage and leverage taxonomies and provide for some semblance of vocabulary control.

December 15, 2011 - 10:56 GMT

This is a continuation of last month's post: What You Need to Know to End Information Chaos.

Business makes extensive use of taxonomy and metadata in a variety of scenarios including accounting, databases and inter/intra-net based applications to provide structure and organize information.  All this is normal and straightforward.  Chaos arises, however, when a business manager or executive asks questions that cut-across systems.  When, for example, they want to be able to integrate engineering data, customer-oriented product information, customer information, and customer service complaints to identify new product-lines and solution opportunities. 

To achieve the goal of visualizing a business problem by mining information repositories in a creative way to address complex issues involving multiple data repositories, taxonomies and metadata must be aligned to establish a comprehensive "single source of truth."  The concept of a single source of truth is the mantra in the drive to put Master Data Management (MDM) into practice.  However, the effort comes with certain practical and serious challenges.  The most significant being the fact that different and well-governed information systems have different semantics and different metadata standards.  Achieving semantic interoperability is a serious challenge, especially as business systems and network service architectures develop to meet organizational needs to adapt to a rapidly changing technology environment.

So what to do?  How do organizations find ways to capture, manage, and derive understanding from a wide range of sources including its internal expertise resources and the stream of information provided by social media channels?

June 29, 2010 - 2:51 GMT

Taxonomists never work in isolation: they collaborate with subject matter experts, content managers, systems integrators, information architects, and webmasters, among others. One type of professional whose area of expertise requires close work with taxonomists is usability or user experience professionals. Quite simply, usability professionals design user interfaces to software, websites, and information services, among other products and services, to make them easier to use. Since the objective of a taxonomy is to help users find information, and user professionals’ goal is to help users achieve their tasks and goals, there is obviously some overlap.

Experienced taxonomists are already familiar with usability issues, and usability professionals who work on website or online information systems usually have some familiarity with taxonomy. But each may not have full expertise in the other’s field, and thus it makes sense to collaborate.

Taxonomists and usability experts not only collaborate to achieve better results, but they can also learn from each other. I recently found this to be the case when I attended the UPA Boston Ninth annual Mini Conference on June 9. “Mini” is hardly the name for it, with 450 attendees, 32 speakers in four simultaneous tracks of sessions. Yet I was the only taxonomist among the hundreds of user interface designers, usability engineers, user experience experts, and the like.

What Usability Experts Can Learn About Taxonomies

December 07, 2009 - 9:05 GMT

Card sorting is a popular technique for getting at users' understanding of content structure, relationships and terminology. I often will break out a card sorting exercise early on in a taxonomy project using terms extracted from the client's content or pre-existing taxonomies to get a sense of what kind of organizing principles are important to the users. I also find it to be a great way of socializing the project and educating people in taxonomy and information architecture.

Recently, I've been doing a lot of digital asset management (DAM) projects, where our taxonomy is meant to help organize and give access to a collection of images or other visual assets, usually through faceted search. While the typical card sorting activity is still relevant, given that we'll be using words/labels to create the taxonomy for the assets, I've found it to lack a certain something in this context.

So during my current project with a global pharmaceutical company, I decided to try a different approach: a visual card sort.

The same rules apply here as they do with traditional card sorting: you can do an open card sort (no pre-defined categories given), or a closed card sort (established set of primary categories). The only real difference being you do it with pictures, not words. And it tends to be a bit easier and fun, as many people are inherently visual.

June 03, 2009 - 8:00 GMT

Thanks to my wife, I've been learning a little bit about systems engineering, a form of engineering that addresses the complex interactions of multiple systems. As she says, you need to consider systems engineering when the interrelationships between systems are as complicated as the systems themselves. For example, to reduce automotive traffic you need to research social behavior, road design, business, and the environment. To study ergonomics you need to study the human body, computer design, application design, and user efficiency needs. And don't get me started on the U.S. healthcare system.

The very first step of systems engineering is to understand the full scope. Ground transportation isn't about cars and trains, for example, but about the entire surface of the earth: population clusters, topography, climate, and distances. Taxonomy starts this way too, with facets like people, documentation types, product lines, and access levels.

October 06, 2008 - 1:03 GMT

Forget taxonomy, ontology, and psychology. Who knows why people do what they do? The point is they do it, and we can track and measure it with unprecedented fidelity. With enough data, the numbers speak for themselves." (1)

Recently Chris Anderson wrote an article for Wired magazine called the The End of Theory. The thesis of the article in a nutshell is that the impending petabyte era of data storage signals the end of the traditional scientific method of discovery. No longer are we bound to the outdated model of observation, hypothesis and measurement. Computers (developed by Google & IBM) "can throw the numbers into the biggest computing clusters the world has ever seen and let statistical algorithms find patterns where science cannot."

September 19, 2008 - 4:14 GMT

I was recently in a meeting where it was said that a lack of subject matter expertise is a disadvantage in taxonomy development. This is understandable; it makes sense to assume that the more domain expertise a taxonomist has, the better the final information product will be. However, my experience has shown that this is not always the case. So exactly how does the role of subject matter expert (SME) fit into taxonomy development?

September 05, 2008 - 10:34 GMT

The Other category: also known as General, Miscellaneous, My Stuff, or, too often, the shared drive.

The Other category is the junk drawer for all those taxonomy terms that just don’t seem to fit anywhere else. Reaching into it is taking a chance as you never know what you may find—the yo-yo you can’t seem to throw away, a pair of rusty scissors threatening to impale you when looking for loose change, batteries, baggy ties, the old cell phone with numbers in it of people you don’t even remember. When it’s time for cleaning up, you can either throw it all away or sort it out and put everything in a more appropriate place.