Taxonomy: a powerful magnifier with a harsh lens

Joe Pairman

Who am I?

Was~ DITA for user education:

– business case– information model, – CCMS implementation– Training

~ Mobile content delivery platform

~ Localization / web delivery

~ Internal knowledge management

Now~ Structured content

consulting and coaching~ Requirements gathering

& solution design~ Pilots &

proofs of concept~ Taxonomy

implementations

What this session’s for~ If you already have a taxonomy, how it

could work harder for you

~ If starting to develop a taxonomy, why to look deeper than simple labelling

~ If interested in developing a taxonomy, some pitfalls to avoid

Typical taxonomy project

CIPD’s DITA content

CIPD needed to use metadata effectively~ For customers:

– better website navigation– discovery of relevant research and resources– searches, external & internal

~ For authors and editors:– reuse– consistent message– standardized terminology

Abstract metadata framework

Applied metadata framework

Taxonomy

Using taxonomy values to populate metadata for a map

Patrick Lambe’s definition of taxonomy

~ A classification system [grouping related items]

~ Semantic[readable terms]

~ A knowledge map [reflects the domain]

And what they’re good atTaxonomy structures

The simplest controlled vocabulary: a list

Appfacebookflashlightfm_radiofootprintsfriend_streamphotosgmail...

App taxonomy —started from a simple list~ Drove content management

App taxonomy —started from a simple list~ Drove content management~ Powered content improvement

– categorize search queries and support calls into the relevant apps

– compare the subject balance from customers with the effort spent on content development per app

Hierarchical-type structures: the backbone of many sites

Hierarchical-type structures: the backbone of many sites

A hierarchy, in the strict sense

A hierarchy, in the strict sense

A strict hierarchyprobably isn’twhat you need

A kind of wall plug

Not a kind of England

A tree works well if the relationshipsare clear

Kind of (generic > specific)

Part of (larger > smaller)

A thesaurus accommodates different terms

A thesaurus accommodates different terms

A thesaurus accommodates different terms

A thesaurus accommodates different terms- and specifies normative forms

A thesaurus accommodates different terms- and specifies normative forms

A thesaurus can guide content

A thesaurus can guide content

A thesaurus also allows associative relationships

Terms aren’t the only points of disagreement

Tree structures invite debate

Is capacity or RPM more important? Etc…

Facets stop the arguments?

Focusing and shaping content

When taxonomy exposes a mess

Possible drawbacks of facets~ Content not consistent (so gaps)~ May overlap~ Can reveal a lack of focus

Resist the urge to build complex organizational structures (straightaway)

Find the backbone of meaning~ What’s actually important?~ Do your groupings work for users?

Find the backbone of meaning~ What’s actually important?~ Do your groupings work for users?

Find the backbone of meaning~ What’s actually important?~ Do your groupings work for users?

~ Real-life utility is more important than structural purity

Taxonomy to create the right content in the first place~ Extension of HTC app taxonomy to make

contextual-ish support more relevant

Taxonomy to create the right content in the first place~ Too many results

Matrix to create the right content in the first place~ Extension of app taxonomy to make

contextual support more relevantApp Has hub topic?calendar yescamera nofacebook yesflashlight yesfm_radio no...

Matrix to create the right content in the first place~ Extension of app taxonomy to make

contextual support more relevantApp Has hub topic?calendar yescamera nofacebook yesflashlight yesfm_radio no...

Matrix to create the right content in the first place~ Extension of app taxonomy to make

contextual support more relevantHub topic

Matrices often bring clarity— e.g. taxonomy of info needs

~ VeryrelevantwhenthinkingaboutDITAtopictypesandstructuralspecialization

Taxonomy to shape the entire content set~ Medical device manufacturer’s taxonomy

dictated level of granularity– Couldn’t stop at high-level concepts, but– individual components

(e.g. on a PCB) too detailed– assemblies & sub-assemblies

were correct level of detail

Knowledge maps —not just for novices~ Every new product or fresh idea

is an unfamiliar domain

Taxonomy is a knowledge map~ For each chunk:

– For (purpose/audience)– Type (overview, troubleshooting, tutorial…)– Subject matter– You need it because… (you have x component)– The risks of not doing it include… (hazard)

Taxonomy is a knowledge map~ For each chunk:

– For (purpose/audience)– Type (overview, troubleshooting, tutorial…)– Subject matter– You need it because… (you have x component)– The risks of not doing it include… (hazard)

~ Rule of thumb: if you can’t tag it, either:– It shouldn’t be a separate chunk, or– It shouldn’t be there at all

Taxonomy is a knowledge map~ For each chunk:

– For (purpose/audience)– Type (overview, troubleshooting, tutorial…)– Subject matter– You need it because… (you have x component)– The risks of not doing it include… (hazard)

~ Rule of thumb: if you can’t tag it, either:– It shouldn’t be a separate chunk, or– It shouldn’t be there at all

~ Tagging the same as the parent chunk (e.g. a map) doesn’t count!

Taxonomy is a knowledge map~ For each chunk:

– For (purpose/audience)– Type (overview, troubleshooting, tutorial…)– Subject matter– You need it because… (you have x component)– The risks of not doing it include… (hazard)

~ Rule of thumb: if you can’t tag it, either:– It shouldn’t be a separate chunk, or– It shouldn’t be there at all

~ Tagging the same as the parent chunk (e.g. a map) doesn’t count! Avoid duplicating

any inferable info!

Tools and taxonomy

Taxonomy exposes the limits of our tools too~ Excel can only get you so far~ Simple CMS taxonomy support may be:

– Lists– Global trees, without distinguishing info type

or metadata field

Taxonomy management tools~ Essential for thesaurus structures and any

relationships beyond broader < > narrower– enforce rules– accommodate related terms, non-preferred

terms, scope notes

~ Pretty handy for simple trees too

CCMS: ingest or integrate?~ How faithfully can CCMS store relationships?

– SKOS, OWL, are good words to hear…– “Subject Scheme” can mean many things

~ How easy is it for authors to pick the right terms and apply them correctly?– display scope notes?– enforce appropriate controlled vocabularies, e.g.

for separate facets or lists?

~ Or, how easy is it to fully integrate an external tool?

Automatic tag suggestions– save effort for authors– also categorize search queries and call logs– check coverage

Not to forget delivering your reshaped content nicely…

And looking ahead to the next phase of web delivery~ Source DITA ~ Semantic Web

markup

And looking ahead to the next phase of web delivery —applications built across sites

Conclusion

Taxonomy’s harsh lens must shape content for the better

Users need Users may benefit from… Content is improved by…Groupings that make sense

DIY groupings (facets) • Correctly prioritizing subject areas

• Avoiding contradictionsA search featurethat works

A search feature that educates on preferred (or preferable) terms

• Using terminology consistently, but also…

• …including a range of familiar terms

A coherent overall structure

A structure that reflects the domain (a knowledge map)

• Filling in gaps in coverage• Making sense of the domain

Thoughts? Questions?Get in touch:@joepairmanjoe.pairman@mekon.com

Thank You!Remember to register for the IDEAS Conference