A Team Approach to Information Architecture

A case study of a team approach to information architecture at Duke University by graduates of the Duke Continuing Studies Technical Communication Certificate program.

Olson, Amy , Sangita Koli and Dino Ruggiero. Carolina Communique (2008). Articles>Business Communication>Information Design>Content Management

Avoiding the Content Silo Trap™, Enterprise Content Management  

Organizations frequently fall into the content silo trap, multiple authors creating similar information, in many areas of the organization. Authors rarely share their information (they work in silos) or are even aware that this information already exists elsewhere in the organization. Technical communicators have been single sourcing for years, this session looks at how to move beyond technical publications to assist your organization with enterprise content management. This session includes a case study from Eli Lilly.

Rockley, Ann and Jodee Clore. STC Proceedings (2002). Design>Content Management>Information Design

Better Content Management through Information Architecture

Content Management Systems promise so much: content is easier to publish, easier to update, and easier to find and use. Lots of promises, but do CMSs really deliver? Masood Nasser examines why Content Management Systems often fail and shows how Information Architecture can come to the rescue.

Nasser, Masood. Boxes and Arrows (2007). Articles>Content Management>Information Design

Blog 101: An Overview of Weblog Technologies  

A weblog or 'blog' is a Web site with content consisting of a series of discrete postings added sequentially and presented in reverse chronological order. Historically used for personal Web sites, blogs in fact represent a form of lightweight content management that can be adapted to virtually any topic, including technical communication. The recent explosion of blogs is in part a result of the availability of publishing tools that simplify their creation. These tools vary significantly in capability, setup, and ease of use, and each offers advantages and disadvantages.

Berry, Robert R. STC Proceedings (2004). Articles>Content Management>Information Design>Blogging

CMS Wiki

CMS Wiki is a knowledge base for Content Management.

CMS Wiki. Resources>Content Management>Information Design>Wikis

Companies Struggling with Unstructured Content

Firms wrestling with unstructured data such as emails and spreadsheets don't see enterprise content management as the answer to their problems.

Milne, Janine. Computer Business Review (2008). Articles>Content Management>Information Design>Metadata

Content Management and Information Architecture

Content management is information architecture writ large.

Boiko, Bob. ASIST (2001). Presentations>Content Management>Information Design

A Content Management Project Presents Unique Challenges

At a basic level, implementing a content management system (CMS) is like deploying any other large software package. Fundamental project management principles must be followed, along with best practice technical guidelines. Beyond this, however, a CMS project presents a number of unique challenges. These must be recognised and addressed for the project to be successful.

Robertson, James. Step Two (2003). Design>Content Management>Information Design

Defining 'Value-Adding Work' of In-House Information Development Groups  

Many in-house information development groups are redefining their role (or seeking to justify their existence) around the concept of 'value-adding work.' But which tasks are value-adding? Finding an answer to this question is critical for the survival of information development groups. Unfortunately, there is no easy, 'one size fits all' answer, because the response depends largely on your point of view. Thus, deciding what is and isn't value-adding may require technical communicators to do more project-by-project task, audience, and media analysis than ever before.

Collins, William L. STC Proceedings (1998). Careers>Content Management>Information Design

Enterprise Architecture Essentials, Part 6: Manageability

Organizations today face the challenge of two important enterprise architecture requirements: the need for agility and the overhead of regulatory governance. These requirements can be seen as mutually antagonistic -- if business processes must be flexible, then governance of those processes may be difficult. This article, part six in a six-part series, explores the notion of using manageability as a key enterprise architecture (EA) quality attribute to solve this problem. EA development is an ongoing process, and the central idea of this article is that by applying manageability as an EA attribute, the organizational processes, systems, and software become manageable.

Morris, Stephen B. IBM (2007). Articles>Content Management>Information Design>Regulation

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

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>User Centered Design

Information Modeling  

Information models are a critical component of single-sourcing, enterprise content management, and dynamic content management. 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 (2002). Design>Content Management>Information Design>Metadata

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

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

The Meaning of Knowledge Management

We hear the term knowledge management bandied about. It sounds suspiciously like a trendy new phrase for what we used to call 'documentation.' In truth, knowledge management is more than documentation. It encompasses documentation, data management, library management, and information design. Knowledge management is increasingly important; as the amount of content has increased, the task of locating the information in the content has become more difficult. You see, information is different from content. And knowledge is something that derives from information.

HyperWrite (2004). Articles>Knowledge Management>Information Design>Content Management

Moving from Information Transfer to Knowledge Creation: A New Value Proposition for Technical Communicators    

This article first reviews the current literature that addresses the value of the technical communicator. Whereas those discussions focus on what is delivered to the user (reader), this article examines the value the technical communicator adds by creating organization (internal) knowledge. The article then examines the philosophical underpinnings that support any discussion of knowledge and defines the role of technical communicators as creators of knowledge. Finally, it offers an expanded value proposition for technical communicators and examines its practical implications.

Hughes, Michael A. Technical Communication Online (2002). Design>Information Design>Content Management>SMEs

Requirements of Content Management Systems: Definition According to Need

In all companies, the requirements of an editorial system are worked out individually from the analysis of existing functioning and the definition of editorial and publication processes required in the future. The first important criteria for analysis are change frequencies and degree of reuse of the published information. The description of the information types as well as translation sequences constitute another starting point for the definition of a modular work process (single-source principle) and publication options (cross-media publishing).

Ziegler, Wolfgang. tekom (2005). Articles>Content Management>Information Design>Workflow

Reusable Information Object Strategy: Definition, Creation Overview, and Guidelines  

Cisco Systems recognizes a need to move from creating and delivering large inflexible training courses, to database driven objects that can be reused, searched, and modified independent of their delivery media. This effort is called the Reusable Information Object Strategy. This strategy defines the standards and process for designing and developing Reusable Information Objects (RIOs) at Cisco Systems.

Cisco Systems (1999). Books>Information Design>Content Management>White Papers

Storage and Enterprise Content Management  

Almost one-third of the users reported that more than 40 percent of the storage spending is for unstructured documents and information--I think that percentage will continue to grow annually. Further, AIIM President John Mancini, who prepared the report, found that larger organizations especially are aggressively pursuing consolidation and rationalization of their storage and archiving strategies--but that cost is not the prime motivation behind those activities.

McKellar, Hugh. KMworld (2006). Articles>Content Management>Information Design

Structured Content Management in the Enterprise  

As other areas within organizations begin to consider structured content for the same reasons as technical communication departments, technical communicators have a golden opportunity to assist others in their move toward structured CM.

Rockley, Ann. Intercom (2007). Articles>Content Management>Information Design

Structuring Your Documents for Maximum Reuse  

A major topic among information development managers these days is single sourcing--writing information once and using it many times. Structured documents are critical for single sourcing. So, let's explore: what we mean by structuring documents; why structuring is useful; some of the concerns that writers have about structuring documents.

Redish, Janice C. 'Ginny'. Center for Information-Development Management (2005). Articles>Content Management>Information Design>XML

To Structure or Not to Structure

Behind all the questions about how to model something is a bigger question: do you model it at all? When is it obvious to structure some content, and when do you just throw it into the 'WYSIWYG pile'?

Gadgetopia (2008). Articles>Content Management>Information Design

XML Repositories: An Idea Whose Time has Finally Come

This white paper discusses the role of an XML repository into today’s enterprise infrastructure. Virtually every database and repository provide some degree of XML support; however, there are important distinctions between support for XML as a data type and the role of a repository whose architecture and operations are optimized to support the broad family of XML recommendations and standards. Specifically, this white paper will explore: The nature and extent of XML use across the enterprise, cost and quality of service implications of an infrastructure with, and without, an XML repository, the evolution of XML repositories from both a technology and a market segment perspective, criteria to determine when an XML repository would add significant value to an existing infrastructure, and capability and packaging recommendations for XML repository functionality that can be used to evaluate specific offerings.

Holst, Sebastian. Gilbane Report (2004). Articles>Content Management>Information Design>XML