23.11.2013 Aufrufe

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

MEHR ANZEIGEN
WENIGER ANZEIGEN

Sie wollen auch ein ePaper? Erhöhen Sie die Reichweite Ihrer Titel.

YUMPU macht aus Druck-PDFs automatisch weboptimierte ePaper, die Google liebt.

User Assistance<br />

UA 5<br />

Presentation<br />

Chaotic Wiki versus Structured Authoring<br />

Ulrike Parson, parson communication, Hamburg<br />

Problems in Company Wikis<br />

Many company wikis are set up with noble intentions, but many of them<br />

get chaotic over time. There are several reasons for this:<br />

––<br />

The content is unstructured.<br />

The core function of a wiki is collaborative authoring. In the best<br />

case, many people contribute to the company wiki. But these people<br />

have different backgrounds and different fields of expertise. That is<br />

why they write in different ways. In the end, every author structures<br />

and formats the information as s/he thinks best instead of keeping<br />

to a common layout. Task-oriented information is not separated from<br />

reference or conceptual information making it hard for the reader to<br />

understand the purpose of an article at first glance.<br />

––<br />

Navigation and access to content is insufficient.<br />

All wiki software products provide features such as categories, tags,<br />

and linking. But defining tags and setting links is solely up to the authors.<br />

What happens? When wikis grow larger over time, it is getting<br />

increasingly difficult to find the right article. Duplicate articles are<br />

created because authors cannot find existing articles.<br />

––<br />

The workflow functions are insufficient.<br />

Writing in a team requires defined workflows. In an unregulated wiki,<br />

every article is visible at once. Workflows are often a matter of negotiation<br />

rather than being enforced by controlled software processes.<br />

This results in wiki pages of highly deviating quality, making it hard<br />

for the users to rely on the content.<br />

Why Should We Use a Wiki and Not DITA?<br />

Technical writing in XML-based information structures, such as DITA,<br />

has solved many of these issues. Structured authoring solutions provide<br />

topic types (e.g. task, concept, reference), mechanisms for organizing<br />

information products in maps, relations between topics, as well as metadata<br />

for workflow status, target audience, product variant, etc. Content<br />

management systems or transformations (as available in the DITA Open<br />

ToolKit) generate well-navigable and searchable output formats. Many<br />

of these functions are not available in standard wiki software.<br />

Function comparison between CMS and wiki<br />

504<br />

<strong>tekom</strong>-<strong>Jahrestagung</strong> <strong>2012</strong>

Hurra! Ihre Datei wurde hochgeladen und ist bereit für die Veröffentlichung.

Erfolgreich gespeichert!

Leider ist etwas schief gelaufen!