easyDITA Ask the Expert Series: Taxonomy - why you need to move beyond standard metadata 2012-07-25

Preview:

DESCRIPTION

In the past, many teams relied upon index and search functionality to help users find information; however, to meet the changing user expectations for dynamic or personalized search, you need to implement taxonomy. In this webinar, Amber Swope addresses the following considerations: When is it time to invest in taxonomy? Who needs to be involved in the classification exercise? How do you define the classification values? How to you apply the classification values? How do you manage the taxonomy? One of the options Amber will discuss is using the DITA subjectScheme support for taxonomy definition and application. The webcast recording is available at https://www4.gotomeeting.com/register/520907039

Citation preview

easyDITA Ask the Expert Series:Taxonomy: When you need to move beyond standard metadata

Amber Swope

DITA Strategies

July 25, 2012

copyright DITA Strategies, Inc. 2012

AMBER SWOPE

JULY 25 , 2012

Taxonomy: why you need to move beyond standard metadata

<dita strategies>

2

Overview

IntroductionTaxonomy overviewDITA subjectScheme supportDefining classification valuesApply classification valuesManaging the taxonomyQuestions

copyright DITA Strategies, Inc. 2012

3

Introduction

Amber Swope DITA Specialist, DITA Strategies, Inc. Over 20 years of experience in the industry at multiple

companies of varying sizes and industries Supported information developers producing DITA

content in Rational group at IBM Author of numerous papers/presentations on

information development and information architecture, including the DITA Maturity Model (with Michael Priestley)

copyright DITA Strategies, Inc. 2012

4

Taxonomy overview

“A taxonomy is simply a hierarchical collection of categories used to organize

information.”

--“Building Enterprise Taxonomies” by Darin L. Stewart

copyright DITA Strategies, Inc. 2012

5

Taxonomy Example

copyright DITA Strategies, Inc. 2012

6

Haeckel microbe classification

3 main classes Protista (microscopic) Plantae (plants) Animalia (animals)

When to invest in taxonomy?

Users can’t find what they’re looking for on Web site or portal

Content creators can’t find content to edit or reuse

Processing requires controlled metadata values

Users want dynamic content delivery or personalized content

copyright DITA Strategies, Inc. 2012

7

When search isn’t enough

Search returns a list of items that simply contain the searched for word or phrase

With taxonomy search can return list of items that contains the searched terms, synonyms and related terms

copyright DITA Strategies, Inc. 2012

8

When index and keywords aren’t enough

Index lists items based on a defined set of labels (metadata) that applies to the content, usually based on keywords

Taxonomy is also a list of values, but has a richer set of relationships and can be used as authoritative source for index terms and other purposes (like search)

copyright DITA Strategies, Inc. 2012

9

Poll: How familiar are you with DITA?

copyright DITA Strategies, Inc. 2012

10

1. I am totally unfamiliar.2. I am familiar with the concept, but haven’t

used it.3. I have created DITA content.4. I’m writing a book about it.

When processing requires controlled values

Processing refers to transformation of DITA source into deliverables and uses metadata to profile and filter content

Use of <data> elements in DITA with manually typed values invites errors

Specialization of <data> elements requires updates to your module files every time you need to add a new value

Content management system configuration requires customization to your system

copyright DITA Strategies, Inc. 2012

11

When users want dynamic content delivery

Dynamic content allows users to specify context for information retrieval

Control display with classification by providing selectable faceted navigation and search values

Provide audience-specific labels or synonyms that are managed in the taxonomy

copyright DITA Strategies, Inc. 2012

12

What does DITA 1.2 provide?

subjectScheme support for defining and applying taxonomy values Definition using specialized DITA maps Application using topic references in maps or DITA

attributes Uses key referencing support

Relationships hasInstance hasPart hasKind hasNarrower hasRelated

copyright DITA Strategies, Inc. 2012

13

Why use subjectScheme?

It is available out-of-the-box (OOTB) with DITA 1.2.You can define the taxonomy in XML.You can control the taxonomy values in DITA maps

in your repository.You can update the taxonomy values without having

to update specialized files (versus specialized <data> elements).

You can apply the values in the maps and topics.You can do an initial implementation without making

a major investment into a taxonomy management tool.

It is tool-independent.copyright DITA Strategies, Inc. 2012

14

Defining taxonomy

Who creates the taxonomy? Understands content structure Knows how users will retrieve or search for content Is familiar with content subject matter Understands content relationships and taxonomy

principlesWho is involved as stakeholders?

Subject matter experts Product managers Usability experts Web site designers (or whoever controls user access to

content or deliverables) Terminology “masters”

copyright DITA Strategies, Inc. 2012

15

Poll: Are you currently using taxonomy for any of the following?

1. CMS metadata2. Indexing or keywords3. Search enhancement4. Not using5. Other

copyright DITA Strategies, Inc. 2012

16

Example: vehicles

Classifications Brand Model Year Type of vehicle Terrain for which it is designed to be used Famous vehicles …

copyright DITA Strategies, Inc. 2012

17

Defining taxonomy with subjectScheme

1. Create taxonomy classification and values in subjectScheme maps

2. Specify the relationship between the classes

copyright DITA Strategies, Inc. 2012

18

Relationship: hasInstance

copyright DITA Strategies, Inc. 2012

19

Class=brandValues

Audi BMW Cadillac Chevrolet Dodge Ford Kia Toyota Volkswagen

brandAudi

BMW

Cadillac

Chevrolet

Dodge

Ford

Kia

Toyota

Volkswagen

hasInstance Map

<subjectScheme processing-role="resource-only" toc="no"> <hasInstance> <subjectdef keys="brand"> <subjectHead> <subjectHeadMeta><navtitle>Brand</navtitle></subjectHeadMeta> </subjectHead> <subjectdef keys="audi"> <topicmeta><navtitle>Audi</navtitle></topicmeta> </subjectdef> <subjectdef keys="bmw">

<topicmeta><navtitle>BMW</navtitle></topicmeta> </subjectdef> <subjectdef keys="chevy"> <topicmeta><navtitle>Chevrolet</navtitle></topicmeta> </subjectdef> … </subjectdef> </hasInstance></subjectScheme>

copyright DITA Strategies, Inc. 2012

20

Relationship: hasKind

copyright DITA Strategies, Inc. 2012

21

Class=vehicle typeValues

ambulance compact convertible coupe crossover pickup truck sedan SUV van wagon

typeambulanc

e

compact

convertible

coupe

crossover

pickup truck

sedan

SUV

van

wagon

hasKind Map

<subjectScheme processing-role="resource-only" toc="no"> <hasKind> <subjectdef keys="type"> <subjectHead> <subjectHeadMeta><navtitle>Type</navtitle></subjectHeadMeta> </subjectHead> <subjectdef keys="ambulance"> <topicmeta><navtitle>Ambulance</navtitle></topicmeta> </subjectdef> <subjectdef keys="compact"> <topicmeta><navtitle>Compact</navtitle></topicmeta> </subjectdef> <subjectdef keys="convertible">

<topicmeta><navtitle>Convertible</navtitle></topicmeta> </subjectdef> … </subjectdef> </hasKind></subjectScheme>

copyright DITA Strategies, Inc. 2012

22

Relationship: hasNarrower

copyright DITA Strategies, Inc. 2012

23

Class=Transportation vehicles

Values airplane regional jet automobile van sedan train

Transportation vehicles

airplane regional jet

automobile

van

sedan

train

hasNarrower Map

<subjectScheme processing-role="resource-only" toc="no"> <hasNarrower> <subjectdef keys="transportation_vehicles"> <subjectHead> <subjectHeadMeta><navtitle>Transportation Vehicles</navtitle> </subjectHeadMeta> </subjectHead> <subjectdef keys="plane"> <topicmeta><navtitle>Airplane</navtitle></topicmeta>

<hasNarrower> <subjectdef keys="regional_jet">

<topicmeta><navtitle>Regional jet</navtitle></topicmeta> </subjectdef> </hasNarrower> </subjectdef> <subjectdef keys="auto">

<topicmeta><navtitle>Automobile</navtitle></topicmeta> …

</subjectdef> </hasNarrower></subjectScheme>

copyright DITA Strategies, Inc. 2012

24

Relationship: hasInstance

copyright DITA Strategies, Inc. 2012

25

Class=Famous automobiles

Values Batmobile Bullitt Christine Ectomobile (Ecto-1) The General Lee The Love Bug

(Herbie) KITT

Famous automobile

s

Batmobile

Bullitt

Christine

Ectomobile (Ecto-1)

The General

Lee

The Love Bug

(Herbie)

KITT

hasInstance Map

<subjectScheme processing-role="resource-only" toc="no"> <hasInstance> <subjectdef keys="famous_autos"> <subjectHead> <subjectHeadMeta><navtitle>Famous Automobiles</navtitle> </subjectHeadMeta> </subjectHead> <subjectdef keys="batmobile"> <topicmeta><navtitle>Batmobile</navtitle></topicmeta> </subjectdef> <subjectdef keys="bullitt">

<topicmeta><navtitle>Bullitt</navtitle></topicmeta> </subjectdef> <subjectdef keys="christine"> <topicmeta><navtitle>Christine</navtitle></topicmeta> </subjectdef>

… </subjectdef> </hasInstance></subjectScheme>

copyright DITA Strategies, Inc. 2012

26

Poll: Does your team use relationship tables?

1. No2. Yes, but in a limited manner3. Yes, we use them for all non-hierarchical

links

copyright DITA Strategies, Inc. 2012

27

Relationship: hasRelated

Goal is to relate hierarchies to each otherRelationships

Brand relates to vehicle type Type relates to terrain

subjectRelTable subjectRole – like relrow, relates subjects in the same

row subject – contains set of related subjects

copyright DITA Strategies, Inc. 2012

28

hasRelated in relationship table header

<subjectScheme> <subjectRelTable toc="no"> <title>VW Relationships</title> <subjectRelHeader> <subjectRole> <subjectdef keyref="brand"> <hasRelated> <subjectdef keyref="type"/> </hasRelated> </subjectdef> </subjectRole> <subjectRole"> <subjectdef keyref="type"> <hasRelated> <subjectdef keyref="terrain"/> </hasRelated> </subjectdef> </subjectRole> <subjectRole> <subjectdef keyref="terrain"/> </subjectRole> </subjectRelHeader>

Column 1

Column 2

Column 3

copyright DITA Strategies, Inc. 2012

29

hasRelated in relationship table

<subjectRel> <subjectRole> <subjectdef keyref="vw"/> </subjectRole> <subjectRole> <subjectdef keyref="wagon"/> </subjectRole> <subjectRole> <subjectdef keyref="highway"/> <subjectdef keyref="city"/> </subjectRole> </subjectRel> <subjectRel> <subjectRole> <subjectdef keyref="vw"/> </subjectRole> <subjectRole> <subjectdef keyref="suv“/> </subjectRole> <subjectRole> <subjectdef keyref="highway"/> <subjectdef keyref="dirt"/> </subjectRole> </subjectRel> … </subjectRelTable></subjectScheme>

Row 1

Row 2

copyright DITA Strategies, Inc. 2012

30

Applying taxonomy values

What roles are appropriate for the responsibility? Leads Information architects Subject matter experts (SMEs)

When do they apply values to content? At creation At review Upon completion

copyright DITA Strategies, Inc. 2012

31

Applying taxonomy values with subjectScheme

1. Apply to entire maps2. Apply to entire topics3. Apply to elements within topics

copyright DITA Strategies, Inc. 2012

32

Map and topic values

Whole map Value=car

Whole topic Within topic reference Value=brand Value=model Value=category Value=year

copyright DITA Strategies, Inc. 2012

33

Content Map

<map id="famous_autos"> <title>Famous Automobiles</title> <topicsubject> <subjectref keyref="car"/> </topicsubject> <topicref href="batmobile.dita"> <topicsubject> <subjectref keyref="ford"/> <subjectref keyref="futura"/> <subjectref keyref="convertible"/> <subjectref keyref="1955"/> </topicsubject> </topicref> <topicref href="bullitt.dita"> <topicsubject> <subjectref keyref="ford"/> <subjectref keyref="mustang"/> <subjectref keyref="fastback"/> <subjectref keyref="1968"/> </topicsubject> </topicref> …</map>

References value from brand classification

References value from model classification

References value from category classification

References value from year classification

copyright DITA Strategies, Inc. 2012

34

Element values

Based on conditional processing attributesRelates defined classification values to

processing attributes

copyright DITA Strategies, Inc. 2012

35

Managing taxonomy

Governance (it’s not a dirty word!) Authority and responsibility for classification Role in term definitions

Negotiation and collaboration

Communication

copyright DITA Strategies, Inc. 2012

36

Managing taxonomy values with subjectScheme

1. Create classification maps in repository2. Apply permissions control to the maps3. When values need to be added, check out

map, update values, and then check in.4. Apply new values to content.

copyright DITA Strategies, Inc. 2012

37

Summary

Create classifications to meet customer requirements

Get the right people involved from the beginning

Agree with stakeholders on who owns the classification definition and maintenance

Understand how the values will be applied

Communicate the plan

copyright DITA Strategies, Inc. 2012

38

Questions

<dita strategies>amber@ditastrategies.com

503.922.3038copyright DITA Strategies, Inc. 2012

39

Thank you for attending!

• Recorded webcast will be available soon through our website – you will get an email with the link or use this one:– https://www4.gotowebinar.com/register/520907039

• Anyone can register after the event to view the recording• Slides will be available on SlideShare

– www.slideshare.net/easydita

• Next webcast August 29, featuring Joe Gelb of Suite Solutions, discussing Dynamic Content Meets Social Engagement - Using DITA to Drive A Better Customer Experience. Please join us!

• Please take our survey on The State of Collaboration– http://ow.ly/cuyVU

• Joe Gelb presentation on Subject Scheme classification:– http://www.slideshare.net/IntelligentContent/dita-classificationandsubjectschemej-gelb

6/28/2012 40© Jorsek, LLC. All Rights Reserved.

Recommended