#14590
The goal of having a comprehensive collection of science information easily available to researchers and students has been expressed repeatedly for decades. These reports reiterate that our concept of a comprehensive collection of information has been attractive to the physical science community for decades.
OSTI (1999). Articles>Content Management>Scientific Communication
#20337
Hit the Bull's Eye with Targeted Information 
Four years ago, the Publications department at J.D. Edwards was challenged with delivering documentation for a global customer base in both print and on-line media. Based on the principle, 'Write it once, use it many times,' they developed a single repository that contained information about 38 multiple-platform software products translated into seven languages. By managing each paragraph of information through a relational data manager, J.D. Edwards has leveraged this database to deliver user guides, training manuals, on-line helps, and CD-ROMs that provide users with targeted software information that is both high yield and just in time.
Uhl, Cyndi. STC Proceedings (1998). Articles>Content Management>Single Sourcing
#19470
How I Survived XML Single Sourcing
In Ontario Systems’ applications, customers can install various components and can change the user interface and data storage. Further, they can modify the system’s automated work flow and add custom features. To remain accurate, Ontario Systems’ documentation must dynamically change to reflect the changing application configuration. This session discusses how Ontario Systems implemented an XML-based single source system to create dynamic documentation and provides guidelines on this process.
Cantrell, Charles and Ann Rockley. STC Proceedings (2001). Articles>Content Management>Single Sourcing
#14169
How To Evaluate a Content Management System
Selecting and implementing a content management system (CMS) will be one of the largest IT projects tackled by many organisations. With costs running into the millions of dollars, it is vital that the right CMS package be selected. This article outlines some of the lessons that we have learnt when assisting clients to chose a CMS. It offers ideas and tips, and provides an approach for identifying your business' actual requirements for a CMS.
Robertson, James. Step Two (2002). Articles>Content Management>TC
#13625
How to Keep the Content Coming: Five Tips
Maintaining a steady flow of high-quality content can be a major challenge for any online venue. Shifting priorities, unexpected crises, ebbing resources, and just plain burnout can (and probably will) take its toll on your content plans. These tips can help you prevent or compensate for problems with your supply of fresh online content.
Gahran, Amy. Contentious (2002). Articles>Content Management>Writing
#22099
How to Revive a Zombie Content Management System
Without care and attention, a CMS can slide into a state of living death. Such systems can be revived by implementing a number of practical (and non-technical) activities.
Robertson, James. Step Two (2002). Articles>Content Management>Collaboration
#20973
How to Write Information So You Can Use It Again
You have written a user’s manual for Microsoft Word for Windows. Now you have been asked to write a user’s manual for Microsoft Word for the Macintosh. The two word processors are essentially the same; the primary differences emerge from the differences between Windows and Macintosh systems. You feel that you should be able to prepare the second manual in next to no time, because you can essentially use the information you wrote for the Word for Windows manual again, with some technical changes. This is an example of re-using information and it is a common task among technical communicators. As the demand for information grows faster than the availability of people to develop that information, technical communicators are showing increasing interest in reusing information.
Carliner, Saul. Saul Carliner Studio (2003). Articles>Content Management>Single Sourcing
#31897
How XML Enables Information Sharing and Reuse — Interview with Joe Gollner
XML, a way of tagging and structuring your content, can help solve a number of problems, including storing, mining, reusing, and sharing content. XML helps enable the interoperability of information between systems, allowing you to export and import your content from one application to another. XML is behind much of the collaboration and information sharing Web 2.0 technologies, such as RSS (really simple syndication) and blogs. By storing content in XML, technical writers can ensure greater flexibility among technologies for authoring and publishing their content.
Gollner, Joe and Tom H. Johnson. Tech Writer Voices (2008). Articles>Interviews>Content Management>XML
#24653
LaTeX and DocBook (and for that matter any manner of XML editors), which could be considered excellent single-sourcing tools, are almost never discussed.
Meyerding, Henry. KeyContent.org (2004). Articles>Content Management>LaTeX>DocBook
#23633
Identifying the Components of Your ROI
Identifying Return on Investment (ROI) for your content management business case begins with a thorough analysis. This article reviews the information you need to gather to identify ROI for an effective business case for content management.
Rockley, Ann. Rockley Bulletin (2004). Articles>Content Management>Assessment>Business Case
#28561
Implementing a CMS: A Game-Changing Corporate Initiative
The success of a CM project depends not just on process management, but on change management as well. Discover the ways that an organization can help its staff overcome initial resistance to change.
Hamer, Emma C. Intercom (2007). Articles>Content Management>Project Management
#28559
Implementing a Content Management System
Before you begin a pilot project using a CMS, you must understand how it will work. Read on to learn how to define your information model, set up your folder structure, create a metadata scheme, assign roles and responsibilities, define your workflow, and measure results.
Hackos, JoAnn T. Intercom (2007). Articles>Content Management>Project Management
#24700
Implementing a Document Control System
Document control is a major component of any quality system. To implement a document control system, first establish Policies/procedures for generating, approving, issuing, and revising documents. The next step is to design and implement forms and a filing system/data base for managing quality documents. Teamwork and established guidelines can help ease the complexities of implementing a document control system.
Matthews, Diane L. STC Proceedings (1994). Articles>Documentation>Content Management
#19809
The Implications of Single Sourcing for Technical Communicators 
Surveys four books that examine methods of single sourcing, including publishing tools, XML, and content management systems. Reviews articles describing the roles of writers and editors, the tool set and its implementation, and ways to make dynamic content more effective
Williams, Joe D. Technical Communication Online (2003). Articles>Content Management>Single Sourcing>XML
#19808
The Implications of Single Sourcing for Writers and Writing
Argues that single sourcing puts pressures on the workforce and the very conception of 'writer' and 'document. Examines literature on change management for clues into managing the impacts of single sourcing on writers.
Carter, Locke. Technical Communication Online (2003). Articles>Content Management>Single Sourcing>Rhetoric
#23637
Incorporating Usability into Content Management
This article describes the importance of incorporating usability into all stages of implementing content management, including assessing your needs, assessing your users (of both the content and the content management system), and assessing your content. It questions the emphasis of technology in many of the current discussions about content management, and instead, advocates looking to the field of usability to form the basis of a content management implementation.
Rockley, Ann. Rockley Bulletin (2004). Articles>Content Management>Usability
#22414
Information Architects and Their Central Role in Content Management
The process of content management begins when an organization comes to the realization that it needs a system to manage content. While the interpretation of the term content management (CM) can be as simple as a set of guidelines for organizing and maintaining content, more typically today it means a sophisticated software-based system. A full-featured content management system (CMS) takes content from inception to publication and does so in a way that provides for maximum content accessibility and reuse and easy, timely, accurate maintenance of the content base.
Warren, Rita. ASIST (2001). Articles>Content Management>Information Design>Content Strategy
#23636
Information Architecture of Content Management
When people think about content management, they generally think about it from a systems perspective, focusing primarily on tools and technology. While it is true that content management usually requires a technological solution, it also requires that content be designed for reuse, retrieval, and delivery to meet your authors' and customers' needs. Content management requires that tools be configured to support authoring, reviewing, and publishing tasks, but first, those tasks must be designed. Designing content and the processes to create, review, and publish it is what information architecture is all about. The Information Architecture section of The Rockley Report will focus on the different aspects of information architecture for content management. This article introduces you to some of the components of information architecture that we will cover in The Rockley Report over time.
Rockley, Ann. Rockley Bulletin (2004). Articles>Content Management>Information Design>Content Strategy
#22871
Information Delivery: Single Source Documentation for Multiple Delivery Mechanisms
Information for a software product is often presented in multiple places and in multiple formats, including printed manuals, quick-reference cards, online Help, online tutorials, online product information, and training materials. Delivery formats can include Acrobat Portable Document (.pdj files, he&n ( hlp) Jiles, HTML ( htm) files, PostScript Jiles, Write (wri) files, text files, and document book$les. Delivery media can include CD-ROM, floppy diskettes, magnetic tape, Web pages, and paper.
Flanders, Melanie G. and Nicole Y. Smart-Wycislo. STC Proceedings (1997). Articles>Content Management>Single Sourcing
#29913
Information Modeling: A Practical Approach
Information models are a critical component of single sourcing, enterprise content management, and dynamic content management. The information model is your blueprint for the effective writing, structuring, and delivery of reusable content. This session explains how to design information models, including information product models and element models. It also explains the role of metadata and how to effectively design it.
Rockley, Ann. STC Proceedings (2003). Articles>Information Design>Content Management>Project Management
#14175
Integrating Content Management with Portals: Meeting Enterprise Information Needs
Effective communication is a top priority for most businesses. To help create, manage, and access information that is used to conduct e-business, technologies such as content management (CM) and enterprise information portals (EIP) are dominating IT and CIO discussions. We will review how these rapidly evolving technologies come together to provide benefits for enterprise implementers. Given the historical deployment of these technologies, many associate the application of content management solutions to externally facing sites, serving transactional e-business needs; and the application of portals to internally facing sites for general employee access to a wide range of information sources and applications. However, both technologies can provide support for the complete information lifecycle, from information creation to management to delivery.
CAP Ventures. Articles>Content Management>Information Design>Content Strategy
#25576
Introducing a Strategic Approach to Outstanding Content Development
Great content doesn't happen by accident. By taking a rational approach that includes careful planning, diligent implementation, and well-tested delivery, vendor teams can ensure a successful project that satisfies client needs, budget constraints, and schedule demands while meeting the business objectives of both the client and the vendor.
#25279
In order to improve this situation, the "Integrated Documentation" project was started in the fall of 2002. Our goal was to place the entire documentation of a system in a convenient manner (on CD or via Internet) at the disposal of Unaxis Displays service technicians and customers. Special attention should be paid to the linking of important information which is required again and again during maintenance and service work. The project derived benefit from the fact that Unaxis has been shipping electronic versions of operating instructions and spare parts catalogs to a number of customers for several years. The required internal processes and the software had been developed by CPTec GmbH. To be consistent, the same company was hired in order to extend the existing spare parts catalog solution to an overall solution named "DocuCat".
Ratz, Günter. CPTec GmbH (2003). Articles>Content Management
#14688
Introduction to Single Source, Part 1
In the first of a two-part article, Butland examines the arguments for and against single sourcing, a method of producing documentation for several media from a single source. He also discusses the differences between manuals and help, and offers suggestions on how to conduct single source projects involving these media.
Butland, Philip. Intercom (2001). Articles>Content Management>Single Sourcing
#14700
Introduction to Single Source, Part 2
In the second installment of a two-part article, Butland discusses obstacles to single sourcing and how to overcome them. Part 1, which explored the advantages of single sourcing and discussed the differences between manuals and help, was published in the February 2001 issue of Intercom.
Butland, Philip. Intercom (2001). Articles>Content Management>Single Sourcing
