#13651
The Intranet as Ecosystem: A Model for Sustaining Development
The complexity of the intranet and the interrelationship between it and the organization’s overall environment mean that traditional methods for supporting company information technology and communication (in which geographically and administratively separate groups determined company standards and guidelines) may not be adequate for the new medium. Available resources are also inadequate; material for web 'authors' (writers, information architects, graphic artists, and programmers) usually focuses at the site level, and most academic and trade articles on intranets focus on the central internal home page or on aspects of the physical infrastructure. Resources covering the whole intranet generally focus on management issues—hiring staff, setting goals, overseeing the design process, selling ideas to upper management, and getting people to use the system once it is deployed. But support groups tasked with the everyday design and maintenance of the intranet also need to “manage” it—that is, to envision the intranet’s role in the overall communication and technological structure of the organization, design and maintain its architectural structure, and sustain it by ensuring its content is accurate, timely, useful, and usable.
Wilder, Pam. University of Washington-Seattle (2000). Books>Content Management>Intranets
#29397
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
#13641
Single Sourcing, Content Management and the Otobase Project 
This report examines some of the issues raised by multiuse publishing in the context of the Otobase software documentation project at the University of Washington. In doing so, it aims to contribute to our understanding of how single sourcing and content management might help us better adapt to users, and also to view the impact of a structured approach to documentation on writers and editors. The report will also use these ideas to suggest both current and long-term improvements for the Otobase project. First, it will briefly describe the project and its current documentation, and then look at theories of single sourcing, content management and structured documents before applying these theories to the project itself.
Burner, Dell. University of Washington-Seattle (2002). Books>Content Management>Single Sourcing
