24
| Date post: | 10-Apr-2017 |
| Category: |
Technology |
| Upload: | oasis-dita-adoption-tc |
| View: | 45 times |
| Download: | 1 times |
Case Study: How USP moved from proprietary XML to DITAKate MeringoloInformation Architect, USP
Amber SwopeDITA Strategies, Inc.
Who we are
Who is USP
Project goal
Where USP started
What USP did
Consultant time
What Amber did
What USP did right
What USP could have done differently
What’s next?
3
Agenda
Master of Science in Technology Management Master of Business Administration Web Development certification 13 years with company
– Editor– Product Support– Information Architect– CCMS management administrator
4
Kate Meringolo
Over 20 years industry experience Consulting and implementation of best practices Information architecture for implementing DITA Masters in Professional and Technical Writing Conference speaker, co-author of the DITA
Maturity Model, author of numerous articles and whitepapers, webinar presenter
5
Amber Swope
The U.S. Pharmacopeial Convention (USP) is a scientific nonprofit organization that sets standards for the identity, strength, quality, and purity of medicines, food ingredients, and dietary supplements manufactured, distributed and consumed worldwide.
Content includes Monographs, Chapters, Reference Standards and more, each broken up into individual xml files– Totaling over 8000 files for our larger publication
Output xml to PDF and/or HTML
6
Who is USP
USP creates and maintains content in a standard XML information architecture that separates content from formatting and style.
7
Project Goal
Multiple proprietary DTDs
Proprietary tools
Deliverable-centric content
Deliverable generation took days
Manual process
No common source
No version control
8
Where USP started
Hired consultant to help with publishing strategy–EVERYTHING on the table
Selected DITA as base architectureSpecialized DITA to accommodate publishing needsSelected CCMS to address all of the source directories and version controlConverted smaller publication to start (about 2000 files)Published subset of product deliverablesEngaged DITA consulting support when I took on IA role
9
What USP did
We started with no knowledge of the DITA standard
Original DITA DTD created by one person with help from the DITA community
Many approaches to understanding the standard
Many approaches to creating specializations
Needed guidance for our business needs
10
Consultant time
Helped establish litmus test for success
11
Define success
12
Developed IA roadmap
13
Roadmap diagram
Diagrammed existing supportDiagrammed necessary supportMentored Kate on DITA from an IA perspective
14
Documented IA
15
Information Architecture Blueprint™
Parts
– Project Management
– Analysis
– Design
– Conversion
– Implementation
Templates
– Spreadsheets
– Diagrams
– Checklists
16
Example diagram for a USP structure
De-constructed specialized
support
Leveraged original design and
added support
Documented the specialization
17
Designed specialization update
18
Specialization diagram
Got help with strategy
Selected architecture before
getting tools
Performed pilot on smaller product
Used progressive implementation
Got training
19
What USP did right
Specialized to get the support we needed
Integrated with external database
Leveraged our internal expertise
Learned from first phase of implementation
20
What USP did right (continued)
Get DITA expertise earlier in projectHave a content-centric focus in the IA workBroader analysis exercise initiallyMade too many fields required in CCMS
21
What USP could have done differently
Conversion of larger product Implement sophisticated reuse (conditions/content references) Implement new delivery platform (user experience improvement)Train authors so they understand separation of content and styleCollaborate with consultant as needed
22
What’s next?
24
