#22081
Definition of Information Management Terms
There is considerable confusion in the marketplace regarding the definition of various information management terms. The scope and role of specific information systems is particularly blurry, in part caused by the lack of consensus between vendors. With the aim of lessening this confusion, this briefing provides an at-a-glance definition of terms for a range of information systems.
Robertson, James. Step Two. Articles>Content Management>Single Sourcing>Glossary
#25983
Delivering Content That Makes a Difference 
Local control facilitates informed decision-making by giving users access to highly relevant and timely information.
Trippe, Bill. Gilbane Report (2004). Articles>Content Management
#29638
Demonstration of an XML-Based Content Management System Implementation
The impact of XML and content management on the field of technical communications is no longer just a speck on the horizon. This paper presents techniques and observations from the trenches of a real-world XML-based content management system implementation that is being used to develop and publish print and online documentation at a prominent software company.
Bookless, Jody, Annette Marx and Scott Davis. STC Proceedings (2005). Articles>Content Management>XML
#20747
Designing an Information Set for Single-Sourcing
The single source in a robust single source system is not any one of the outputs that may be created from that source. The single source is an information set from which many outputs may be created. Designing an information set is different from designing a document. Greater structure is required, and that structure must be available to the process that creates information products as output, not simply to the reader. A good information set design involves creating a data model, mapping information relationships, and defining patterns of change.
Baker, Mark. STC Proceedings (1999). Design>Content Management>Single Sourcing
#28085
Designing and Planning Modular Content Projects
Modular writing involves writing, labeling, storing, and assembling content modules. Read about how to design and plan a modular writing project and how this writing system affects traditional roles and responsibilities within a publications team.
O'Connor, Virginia. Intercom (2006). Articles>Content Management>Workflow
#23818
Many technology companies, consultants, and academics are hyping the future of Web services. But how will this background transfer of data between applications affect the user experience?
Lombardi, Victor. New Architect (2002). Design>Web Design>Content Management>User Experience
#13679
Designing Single Source Materials
Timelines for developing documentation are getting shorter and budgets are getting smaller. This means that we have to find more efficient ways of developing documentation. One way is to consider single-sourcing your information for multiple media (paper, online), multiple types of documentation (user documentation, Help, training), multiple users and reuse of information for multiple products. While this process takes a lot of up-front planning it can significantly decrease your costs and development times. This session looks at the process for designing and creating single-source materials for multiple media, users, or types of documentation.
Rockley, Ann and JoAnn T. Hackos. STC Proceedings (1999). Presentations>Content Management>Single Sourcing
#14246
Designing Wearable Performance Support: Insights from the Early Literature 
According to Gery (1991), an electronic performance support system (EPSS) is an electronic environment available to and easily accessible by employees that is structured to provide online access to all information to permit them to do their jobs with minimal intervention by others. Why do we assume that this support must be provided on a computer? If effective performance support must be 'available' and 'easily accessible,' how can designers provide support to people whose jobs require mobility? Such jobs include (but certainly are not limited to) supervising a manufacturing operation, inspecting foods, and repairing equipment. A designer for any EPSS being developed to support jobs such as these would have to take the employees' mobility into account.
Gobert, Danielle. Technical Communication Online (2002). Design>Content Management>Wireless Web
#23936
Developing a Content Management Team for Your Intranet 
What is the overall process? Who are the players? What are their best uses?
Boiko, Bob. SLA (2002). Presentations>Content Management>Collaboration
#22156
Developing a Content-Management Strategy: Implications in a Multi-Language Environment
Why we went to a single-source CMS and how we went about it.
Douma, Barbara. ComTech Services (2001). Articles>Content Management>Single Sourcing>Case Studies
#19823
Developing a Database Publishing System: A Demonstration
We developed a database publishing system that uses raw data from a database and produces camera ready copy using Microsoft Access, FrameMaker, and Brio Publish. This type of project requires a project plan that defines the scope of the project, a complete understanding of the various relationships in the database, selection of the right tools for the task, and a sensitivity to the needs of the users who face dramatic change in their environment. This demonstration focuses on all aspects of this effort.
Cantoni, Georgina C. and Judith L. 'Judy' Glick-Smith. STC Proceedings (1995). Articles>Content Management>Single Sourcing>Microsoft Access
#20302
Developing and Maintaining a Large Document for Publication in Multiple Media
This paper outlines the development of the Software Technology Reference Guide—a 500-page directory of software technologies— from the planning phase to its publication in both hard copy and HTML. It explores the problems of coordinating multiple, remotely located authors; producing frequent drafts when material is changing rapidly; managing a large documentation project; maintaining a source document for publication in multiple media; and handling the conversion of a complex hard-copy document to a usable online document.
Brune, Kimberly. STC Proceedings (1998). Articles>Content Management>Single Sourcing
#19912
Developing Information for Multiple Formats: You Can Get There from Here
This paper describes the experiences of SAS Institute Inc. in developing single-source software documentation for presentation in multiple formats. The project is an ongoing team effort from all areas of the Publications Division. Our main goal is to develop online and hardcopy reference documentation. Toward this end, we set goals of using single-source files, reusing information, and tracking all information chunks and the relationships among them. To accomplish these goals we had to make decisions about the tools we are going to use, what information we are going to include, how we will design and present the modular information, linking and indexing strategies, and testing. This paper discusses the choices we made in light of our goals.
Moell, Patricia G. and Helen F. Weeks. STC Proceedings (1996). Articles>Content Management>Single Sourcing
#24922
Device Indepenence: Single Sourcing's Other Side
Considers the possible ramifications for technical communicators of device-independent publishing.
Perlin, Neil E. Intercom (2005). Articles>Content Management>Single Sourcing
#22505
Digital Asset Management Resources
A collection of dozens of digital asset management resources available online.
#14227
The Dilemma of Credibility vs. Speed
CoRRs implicitly constrained but officially open acceptance policy for submitted papers raises concerns about both censorship and credibility. To avoid refereeing incoming papers yet still help readers assess their merits, CoRR could use coordinated public comments and ratings in the manner of some online auctions and booksellers.
Prekeges, James G. Journal of Computer Documentation (2002). Articles>Content Management>Online
#23644
Distributed Workgroups Employing Single-Sourcing Techniques Around the Globe
Single sourcing, which is increasingly used at the technical writer's workplace, has now reached the classroom of Technical Communication programs. This paper examines the impact of working on an XML-based single-sourcing solution on a geographically diverse graduate student team whose partners were all singlesourcing novices. It shows that managing communication within the virtual team is superordinate to managing the publication process. The paper discusses best-practice strategies for transient start-up publication teams, which rely solely on online communication, pointing to the differences between teams in the classroom and in business organizations.
Kaempf, Charlotte. STC Proceedings (2003). Articles>Content Management>Single Sourcing
#31749
Single sourcing is good, I’m sure most of us can agree on that, but I’ve recently been wondering if perhaps DITA isn’t quite good enough?
McLean, Gordon. One Man Writes (2007). Articles>Content Management>XML>DITA
#26180
DITA Resources Online (Darwin Information Typing Architecture)
If you need to learn more about the Darwin Information Typing Architecture (DITA), look no further. Links to a few of the most useful DITA resources available on the web today.
Rockley Group, The (2005). Resources>Content Management>Metadata>XML
#29751
Do Staff Make Use of Personalisation Features?
Organisations around the world have already made their first forays into personalisation, however many more organisations are questioning what to personalise and how to go about it. So who is using personalisation and how effective is it?
Grenfell, Catherine. Step Two (2007). Articles>Content Management>Personalization>Usability
#19641
Do-It-Yourself Single-Sourcing
In recent years, countless articles and conference workshops have touted single sourcing as the Holy Grail of technical writing. Countless articles and conference workshops have also told us that XML is our means to achieving the Grail. However, in the absence of any off-the-shelf products that facilitate XML and single sourcing in our current work environments, I suspect that most people, particularly in smaller companies, believe that implementing XML is too technically daunting, too expensive, or both.
Wersan, Fred. Intercom (2003). Design>Content Management>Single Sourcing
#10423
Document (re)Presentation: Object-orientation, Visual Language, and XML
This article demonstrates how the combination of object-orientation and Horn's notions of visual language morphology, syntax, semantics, and pragmatics may be used to analyze and describe the mapping of marked-up XML files onto user documents. The article also raises the question of whether—or to what extent—the coupling of object-orientation and visual language might be exploited more directly for design purposes in a document production paradigm based on XML.
Johnsen, Lars. Technical Communication Online (2001). Design>Content Management>XML>Metadata
#19609
A directory of online resources about document management.
#10071
Documentation Without Documents -- The COIL Model
A description of a Canadian content-management system from the early days of the emerging knowledge management industry. COIL is a document management system that manages the information held in documents, rather than the documents themselves. By integrating more than 1,500 hardcopy pages of legacy documentation into one on-line information resource, COIL provides chart producers with an effective way of consulting the standards and procedures for their GIS, and of managing revisions to those standards and procedures.
#29747
Does Your CMS Vendor Have Product Expertise?
Choosing a content management system (CMS) is not just about finding the product with the right functionality. It's also about dealing with a vendor who can support your needs for the lifetime of the solution. This briefing explores the way most CMS vendors have evolved, what this means for the way they work, and what you should be looking for when purchasing a solution.
Robertson, James. Step Two (2007). Articles>Content Management>Assessment
