Barry Schaeffer

1
Authoring and managing content for single source
publication

• Barry Schaeffer
• X.Systems

2
First, Some Working Definitions

• Single-source publication creation of multiple
  intellectual products from a single content base
  Without manual rework or enhancement
• Repurposing transformation of content for use
  in a new output form
• Reuse inclusion of the same content in multiple
  output products without change
• Common source effectivity - use of content
  tagging to support creation of multiple output
  products from a single source

3
Goals of Single Source Publishing

• Creation of an editorial environment allowing
  subject matter experts to achieve high
  productivity
• Generation of multiple intellectual products from
  a single authoring effort and without
  post-processing or enhancement
• Minimization of redundant content across the
  repository and published work
• Maintenance of a simple, scalable and easily
  managed content and production environment

4
Why is single source publishing important?

• The growing appetite for electronic delivery
  demands audience and situation-targeted
  information products
• Historical approaches to multiple audience
  support can be cumbersome and error prone
• Authoring for multiple audiences can seriously
  degrade editorial productivity

5
Approaches to Single Source Publishing

• Individual content for each output variant
• Fragmentation and recollection of highly granular
  content elements
• Embedded database queries to create output
• Common-source effectivity for multiple outputs
• Strategic combination of 2 and 3

6
Individual content bases
A
A-1
A-3
A-2
A-4
A-5
Publish
Publish
Publish
Publish
Publish
A-1
A-3
A-2
A-4
A-5
7
Data Reuse via Fragmentation
A
Fragment
C
C
3
3
3
4
C
1
1
3
1
2
3
4
4
5
4
1
5
2
5
5
1
3
4
5
5
5
2
2
5
1
2
3
C
3
3
1
Map
Map
Map
Map
Map
Publish
Publish
Publish
Publish
Publish
A-1
A-3
A-2
A-4
A-5
8
Data Reuse via Fragmentation

• Data reuse aims at storing content only once,
  then using it in multiple places
• Works well for inherently sharable data, like
  warnings, introductions, etc.
• Use of smaller chunks to achieve flexibility,
  increases volume and complexity
• Use of larger chunks to avoid complexity,
  increases redundant content and reduces
  visibility
• Creation and revision of content in chunks can
  degrade editorial productivity

9
Approaches Database queries to create content
A
Replace content variations with queries to DBMS
contents
Resolve output for database content
Data base
Replace queries
Publish
10
Database queries

• Inclusion of database queries as part of document
  structure enables inclusion of dynamic data in
  publication
• Use of queries breaks down when it replaces
  document content and structure
• Maintenance of content outside document structure
  can complicate editorial tasks

11
Common Source Effectivity
A
Tag and maintain master content for output
variants
Process master, selecting content for desired
output variant
Resolve
Publish
12
The History of Common Source Effectivity

• Initially used in the aircraft and aerospace
  industries to document different blocks of
  airplanes, hulls, etc..
• Usage growth driven by evolution of the
  multi-media information world and proliferation
  of delivery options.
• Can be valuable for any content type from which
  multiple but similar output products are
  required, including
• Model or type of device versions
• Timed versions of documentation (year, quarter,
  etc.)
• Media versions, product inclusion versions
• Grammar versions (American vs. British, etc.)
• User skill level versions (expert, novice, etc.)
• Usage environment versions (flight line vs.
  Hanger, etc.) . .
  .And so on.

13
Common Source Effectivity - Key Benefits

• Keeps common data common.
• Minimizes data fragmentation and associated
  management problems
• Allows unified planning for customization of
  output versions and components
• Works well without specific (or any) content
  management software resources
• Frees physical data architecture from data reuse
  needs
• Ties content usage to logical content model
  design
• Expands usefulness of external data sharing

14
Combination approach
A
Shared Content
Resolve
Replace queries
Data base
Publish
15
A Single Source Illustration
The Challenge
Document A
Document A
Version 2
Version 1
A B C
A B C
3a
4
A-4
A-4
1
3b
A-5
8
2
A-5
3a
A-5
(largely common content A, B, C with a few
differences and external shared content and
database elements)
(different content with a a second external
shared element
Database containing items for inclusion in some
output products
16
A Combination Approach to Single Source Publishing
A B C
4
A-4
3a
8
2
3a
A-5
3b
A-4
A-5