Taxonomy development by Sudhir Subudhi
1
Taxonomy development
Prepared by:
Sudhir Subudhi, Lead Technical Writer, DITA Tra...
Taxonomy development by Sudhir Subudhi
2
Process of developing taxonomy in an organization
1. Find-out the names of all st...
Taxonomy development by Sudhir Subudhi
3
System profile System profile
Using systems User profile
User credentials
User pr...
Taxonomy development by Sudhir Subudhi
4
Escalating tickets
Providing feedback on
ticket
About feedback Feedback
Feedback ...
Taxonomy development by Sudhir Subudhi
5
Taxonomy for this “IT Support Management” module:
The taxonomy in the following t...
Taxonomy development by Sudhir Subudhi
6
Systems System Computers
Desktop
Acer
IBM
Laptop
Tab
Smartphone
All in one Printe...
Taxonomy development by Sudhir Subudhi
7
Risk mitigation
Architecture
List
System list
User list
User group list
Ticket li...
Taxonomy development by Sudhir Subudhi
8
So, you can use a subjectScheme map to define the taxonomy developed in the previ...
Taxonomy development by Sudhir Subudhi
9
subjectScheme map is used to define sets of controlled values for use in classify...
Upcoming SlideShare
Loading in …5
×

Taxonomy development

277
-1

Published on

This document explains what is taxonomy, necessity of taxonomy in an organization, points to consider while developing taxonomy, value adds from taxonomy, process of developing taxonomy in an organization, and taxonomy in DITA.

Published in: Software, Technology, Education
4 Comments
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total Views
277
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
6
Comments
4
Likes
0
Embeds 0
No embeds

No notes for slide

Taxonomy development

  1. 1. Taxonomy development by Sudhir Subudhi 1 Taxonomy development Prepared by: Sudhir Subudhi, Lead Technical Writer, DITA Trainer and Consultant, and Process Expert LinkedIn Profile: in.linkedin.com/in/sudhirsubudhi Email: sudhir.subudhi@outlook.com Skype Name: sudhir.subudhi What is taxonomy Taxonomy is a hierarchical structure of metadata or organizational vocabulary that represents the whole set of information used by different stakeholders in an organization. It makes the content, well organized, in-line with consumption pattern, focused, controlled, and searchable. On the part of an Information Architect, it’s a primary goal to develop an effective taxonomy that would represent the whole organizational content. Necessity of taxonomy You can imagine effort required to search a piece of information in a heap of files. So, it calls for a method to effectively author modular content and then tag the content with appropriate keywords, so that the modular information can be accessed through faceted searches and indexes. Points to consider while developing a taxonomy Taxonomy represents the way people in an organization consumes the information available across its products, process, communication channels, operational or business domain etc. Benefits of taxonomy can be achieved with the development and use of a controlled set of vocabulary that represents the whole set of information in an organization. The controlled vocabulary consists of a set of reusable information objects (or blocks of reusable information), arranged in a hierarchical order, that is referred in the organization in as-is format. The vocabulary should categorize the information objects according to multiple facets in which the information is looked at, so that the information can be accessible through faceted searches. When knowledge bases or content repositories are created in the organization, the information blocks are tagged with the matching keywords defined in the taxonomy only. The taxonomy needs upgrade as the information in the organization increases. Value-adds Any information can successfully be searched from a repository, thus realizing the value of the content. Reflects the information usage and consumption pattern followed in an organization in as-is format. Thus making the adoption easy. Information is neatly structured, designed and organized, thus promoting focused use, consistent use and reuse of information. It shows directions for how knowledge in an organization should be captured and used.
  2. 2. Taxonomy development by Sudhir Subudhi 2 Process of developing taxonomy in an organization 1. Find-out the names of all stakeholders/users of knowledge in an organization. 2. Analyze the use cases, scenarios, and tasks of the users. 3. Find-out what information they go through to complete these use cases, scenarios, and tasks. The information could span across its products, process, communication channels, operational or business domain etc. The following example shows the user’s information consumption pattern and the metadata involved. ------------------------------------------------------- I’m a support engineer. How do I install the Lync from a remote location using an Infrastructure Manager application version 2.0? I’m a voice support professional at a call center. How do I troubleshoot a Samsung M203 Washing Machine that fails to start while water pressure is low? I don’t know what I am. But I just want to… see navigation maps on my Nokia Lumia 925 using 3G network while I’m on the move to airport ---------------------------------------------------------------- 4. Derive facets, information objects, or metadata that are frequently used or reused to complete the scenarios and tasks. 5. Organize the information objects in a hierarchical structure, with a multi faceted approach. 6. Use it as the controlled vocabulary to structure, organize, and tag information that is developed for the organization. Example The following table shows an example of performing task analysis and deriving information objects on an organization module— IT Support Management. To keep the table short, tasks of only one user is analyzed. In the same way tasks of other users are analyzed before forming the taxonomy. Users Tasks they perform Content topics Information objects Employees Use systems in the network Types of systems System profile System type Systems list Systems list
  3. 3. Taxonomy development by Sudhir Subudhi 3 System profile System profile Using systems User profile User credentials User privileges User privileges Raise tickets if support needed on procurement, upgrade, system movement, improvement About tickets Ticket profile Ticket resolution process Ticket type Ticket workflow SLA SLA Ticket type Priority level Severity level Completion time History of tickets raised earlier by you Ticket list Ticket profile Raising a ticket Ticket profile Raising a procurement ticket Procurement ticket profile Raising a upgrade ticket Upgrade ticket profile Raising a system movement ticket Movement ticket profile Raising a improvement ticket Improvement ticket profile Track the raised tickets Tracking a raised ticket Ticket status Ticket history Ticket history Notify people pending ticket with Notification template Notification Notification guidelines Notification guideline Notifying people pending ticket with Raise flags for faster completion of tickets About flagging Flag Flagging guidelines Flag guideline Flagging a ticket Escalate tickets What is escalation Escalate ticket Escalation guidelines Escalation guideline
  4. 4. Taxonomy development by Sudhir Subudhi 4 Escalating tickets Providing feedback on ticket About feedback Feedback Feedback samples Providing feedback Feedback guideline Responding to notifications About notification response Notification response guidelines Responding to notifications Notification response Troubleshooting Trouble Trouble resolution . . .
  5. 5. Taxonomy development by Sudhir Subudhi 5 Taxonomy for this “IT Support Management” module: The taxonomy in the following table includes information objects for all users of the module. To keep the table short, only a part of the whole taxonomy is mentioned. Facets Lebel1 Level2 Level3 Unique Id Related keywords Users Employee Probation Permanent Operations Manager IT Support Administrator IT Support executive Auditor User groups Admin Regular Management Privileges Permissions Privilege Access Read Modify Write Procedures Using systems Raising tickets Notifying people Managing users Creating user Editing user Deleting user Assigning tickets Rules Guidelines Notification guidelines Notification response guidelines Flagging guidelines Escalation guidelines
  6. 6. Taxonomy development by Sudhir Subudhi 6 Systems System Computers Desktop Acer IBM Laptop Tab Smartphone All in one Printer Software Software OS Windows Collaboration software Skype Ticket Management App Process Ticket resolution process Output Result Ticket Procurement ticket Upgrade ticket Movement ticket Improvement ticket Maintenance ticket Audit ticket Escalated ticket Report Network check report Audit report Log User activity log System log Ticket log Management SLA Ticket priority Ticket severity Risk management
  7. 7. Taxonomy development by Sudhir Subudhi 7 Risk mitigation Architecture List System list User list User group list Ticket list Profile System User Ticket Priority Severity Status History Test Software Hardware Trouble Workflow Ticket workflow Flag Communication Notification Email Feedback In-ticket comment . . . Taxonomy in DITA DITA supports taxonomy through use of subjectScheme maps. A subjectScheme map is a specialized DITA map that defines a collection of controlled values rather than a collection of topics. A subjectScheme map is used to define sets of controlled values for use in classifying content. Ditamaps can reference the subjectScheme maps to make the controlled values or metadata available to its contents. Sets of controlled values can be bound to DITA attributes and the attribute values can be set through enumerations. Topics can be classified with the values defined in the subjectScheme maps. Relationships between subjects or values can be set using relationship tables in the subjectScheme maps.
  8. 8. Taxonomy development by Sudhir Subudhi 8 So, you can use a subjectScheme map to define the taxonomy developed in the previous section and use it through ditamaps. Example The following example defines linux, windows, and mac as three values for OS. It also links the values as enumeration to the attribute “platform”. Please refer DITA_1.2_Specification for complete information on subjectScheme maps and its elements. <subjectScheme> <subjectdef keys="os"> <subjectdef keys="linux"/> <subjectdef keys="windows"/> <subjectdef keys="mac"/> </subjectdef> <!-- Define an enumeration of the platform attribute, equal to each value in the OS subject. This makes the following values valid for the platform attribute: linux, windows, mac --> <enumerationdef> <attributedef name="platform"/> <subjectdef keyref="os"/> </enumerationdef> </subjectScheme> Classifying topics in ditamap with subjects from subjectScheme map: <map> <topicref href=”Installing Linux Operating System.xml”> <topicsubject> <subjectref keys=”os”/> <subjectref keys=”linux”/> </topicsubject> </topicref> </map> Conclusion Taxonomy is a hierarchical structure of metadata or organizational vocabulary that represents the whole set of information used by different stakeholders in an organization. It makes the content, well organized, in-line with consumption pattern, focused, controlled, and searchable. Taxonomy represents the way people in an organization consumes the information available across its products, process, communication channels, operational or business domain etc. To develop taxonomy for an organization, a person can find-out all users in the organization; analyze their use cases, scenarios, and tasks; find-out what information they go through to complete the tasks; derive information objects that are frequently used or reused across the tasks; and then organize the information objects in a hierarchical structure, with a multi faceted approach. DITA supports taxonomy through use of subjectScheme maps. A subjectScheme map is a specialized DITA map that defines a collection of controlled values rather than a collection of topics. A
  9. 9. Taxonomy development by Sudhir Subudhi 9 subjectScheme map is used to define sets of controlled values for use in classifying content. Ditamaps can reference the subjectScheme maps to make the controlled values or metadata available to its contents. Sets of controlled values can be bound to DITA attributes and the attribute values can be set through enumerations. Topics can be classified with the values defined in the subjectScheme maps. Relationships between subjects or values can be set using relationship tables in the subjectScheme maps.

×