#14231
A Computing Research Repository: Why Not Solve the Problems First?
The Computing Research Repository (CoRR) described by Halpern is potentially a powerful tool for researchers in computing science. In its current form, however, shortcomings exist that restrict its value and that, in the long term, might strongly undermine its usefulness. Important aspects that have insufficiently been taken care of are (1) the quality and consequently the reliability of the material stored, (2) the still restricted submission of material,which implies that other sources have to be consulted by researchers as well, (3) the still unsound financial basis of the project, and (4) the confusion that may easily arise when a preliminary version is stored in the CoRR, while a different final version is published in a journal.
van Loon, A.J. Journal of Computer Documentation (2000). Articles>Knowledge Management>Research>Online
#18651
A postmortem is a meeting of all members of the project team at the end of the project to identify what went well and should be repeated on future projects; and what did not go well and how to avoid these situations on future projects. In addition, the postmortem should provide time for the members of the project team to thank one another for their contributions. Often during the course of a project, team members become so comfortable working with one another that they do not thank each other for their contributions or acknowledge exceptional work. As a result, team members might not realize that their colleagues appreciate their contributions. The postmortem provides a formal opportunity for team members to offer one another such recognition.
Carliner, Saul. STC Northeast Ohio (2002). Articles>Project Management>TC
#31975
Conducting Effective Team Technical Reviews
Mention team technical reviews to a group of tech writers and chances are good that you will either get a loud, collective groan, or the group will vie to tell the best review horror story. On the one hand, technical reviews are a vital part of our jobs because they help us to produce high quality product documents. On the other hand, technical reviews gone wrong are the bane of our existence. The good news is that we have the power to conduct consistently effective technical reviews. This article summarizes why we do reviews and what often goes wrong in reviews, and then summarizes steps to take before, during, and after technical reviews that can help you conduct effective team technical reviews. Although your process and team may differ from what's described here, you can apply the information in part or in whole to improve your current review process.
Brown, M. Katherine 'Kit'. TECHWR-L (2008). Articles>Project Management>Collaboration>Assessment
#28154
In the same way that the word 'truthiness' is not a real word but is gaining usage in our culture, so the word 'connectfulness' offers us in the professional arena a way to express an important aspect of our work. Just as truthiness says more than accuracy and is friendlier than truthfulness, so connectfulness says more than networked and is friendlier and more inclusive than connectedness.
Albing, Bill. Carolina Communique (2006). Articles>Content Management>Collaboration
#26497
Considering Open Source Content Management Systems 
Open source software content management systems (CMS) offer affordability, flexibility, and in many cases outstanding performance.
Still, Brian. IEEE PCS (2005). Articles>Content Management>Open Source
#28931
Many Web professionals consider content inventories critical parts of most projects. Are there certain specific things to look for during a content inventory? Fred Leise definitely thinks so. He proposes a set of content analysis heuristics and discusses how to utilize each one.
Leise, Fred. Boxes and Arrows (2007). Articles>Content Management>Taxonomy>Heuristic Evaluation
#26968
Con il termine Content management si indica una serie di processi e tecnologie a supporto del ciclo di vita evolutivo dell'informazione digitale (content o digital content).
#22622
Content Management and the Electronic Common Technical Document (eCTD)
The XML eCTD DTD (Document Type Definition) defines the overall structure of the submission. The purpose of the XML backbone is two-fold: (1) to manage meta-data for the entire submission and each document within the submission and (2) to constitute a comprehensive table of contents and provide corresponding navigation aids.
Rockley, Ann. Rockley Group, The (2004). Articles>Content Management>Standards>XML
#28563
Content Management and the Need for Change in Technical Communication 
Many technical communicators find it difficult to manage all of the corporate content that their organizations create. Learn how CM can work for you by providing value to your organization as well as your customers and shareholders.
Abel, Scott. Intercom (2007). Articles>Content Management>Project Management
#22360
Review: Content Management for Dynamic Web Delivery 
One comes away from the book with a feeling of an enormous challenge—technical, organizational, budgetary, and political. If you or your boss is considering developing and deploying a content management system at your place of work and you both want to know what you might be in for, get this book.
Hudak-David, Ginny. Technical Communication Online (2003). Articles>Reviews>Content Management>Personalization
#21692
Review: Content Management for Dynamic Web Delivery
Content Management for Dynamic Web Delivery provides background and process for implementing content management in an organization. You don't have to spend a lot of time researching the topic on the Web, because all the necessary information you need, from introduction to the subject, to a blueprint to implement your solution is provided here.
Frick, Geri. TECHWR-L (2004). Articles>Reviews>Content Management
#29761
Content Management from the Trenches
Moving your company to a content management system requires intense commitment and planning by everyone: management, writers, and vendors. Allow at least a year to define and develop the necessary tools, and provide training and support for the writers on an ongoing basis. As a writer, documentation department, or vendor, you should participate in the planning, development, and implementation. To ensure success, conduct rigorous testing, do a pilot project, and encourage teams to share information freely.
Pierce, Kathleen and Erin Martin. STC Proceedings (2004). Articles>Content Management
#26937
An interactive glossary of terms from content management systems.
Sapir, Rick. KeyContent.org (2006). Articles>Content Management>Glossary
#22442
Content Management is the Infrastructure of eBusiness
The basic nature of commerce has not changed but our ability to communicate quickly, widely, and deeply has. This document explores the changes and challenges that these new abilities bring to the conduct of business for all organizations. eBusiness, I contend, is the process of delivering any part of your business to any audience wherever they are.
Boiko, Bob. ASIST (2001). Articles>Content Management>Management
#19000
Manien har bredt sig. Ethvert professionelt website skal pr. definition være baseret på et Content Management System (CMS). Der er nok at vælge imellem, når næsten ethvert web bureau med respekt for sig selv har deres eget CMS, med alle dets fordele og ulemper. Men hvordan navigerer man som køber i denne jungle af systemer? Der er jo en del, her er en lille liste over hvad TheQuark har fundet på det seneste. Listen er sikkert overhovedet ikke dækkende, men den giver et rimeligt overblik på hvad man kan få.
Orgaard Larsen, Thomas. Quark, The (2003). (Danish) Articles>Content Management
#28944
Content Management Market Year in Review 2006
The Rockley Group takes a look back at the year 2006 in review. What happened in the CMS market? How is globalization changing the content management landscape? And, what about new communication vehicles like blogs, wikis, podcasts, and RSS feeds?
Rockley, Ann. Rockley Bulletin (2006). Articles>Content Management>Software
#22416
Content Management Market: What You Really Need to Know
Content management (CM) has been on the short list of initiatives for many organizations the past few years. The proliferation of Web-based content on corporate intranets, extranets and Web pages has provided a daunting array of challenges. Organizations must insure that posted information is relevant, authentic and appropriate. And, if you listen to all the analyst firms the industry numbers would bear this out.
Emery, Priscilla. ASIST (2001). Articles>Content Management
#27132
Content Management Problems and Open Source Solutions
With hundreds of applications to choose from, content management is one of the most active sectors of open source software. While these options present a great opportunity to leverage open source software, I.T. decision makers often find themselves disoriented by the number of choices, the lack of information, and the ineffectualness of their traditional software selection processes. This Optaros white paper 'Content Management Problems and Open Source Solutions' discusses strategies for understanding and selecting an open source content management system and describes fifteen of the more prominent options in the context of the business problems they are effective in solving.
Gottlieb, Seth. Hiveminds (2006). Articles>Content Management>Case Studies
#22648
In this White Paper, we examine the benefits of automated content management, and demonstrate where efficiencies can be gained within your organization. Web sites with more than a few information pages may benefit from content management systems (CMS). Content management systems are automated tools that allow for web site content to be created and administered on a recurring basis. The result puts the responsibility for content development into the hands of the authors (where it belongs) and out of the hands of the programmers.
Sloan, Brian and Scott Duffy. XGuru (2002). Articles>Content Management>Web Design
#23992
Content Management Systems: Don't Automate the Misery
Few organizations have seen much good come of content-management BPR initiatives so far. Of the many reasons for these failures, one stands out: these BPR initiatives—and the systems they spawn—are focused on realizing organizational objectives without sufficient regard for the context, habits, and goals of the people who will actually use the system.
Fore, David. Cooper Interaction Design (2001). Articles>Content Management>User Centered Design
#26741
Content Management: Reaching the Next Level
In spite of the ongoing efforts of vendors and user organizations, the management of non-structured data (content) continues to be a problem, with significant impact. Yet evidence indicates that content management (CM) is being deployed more widely within vanguard organizations, with major benefits. And among the lessons to be learned from their experiences, focusing on the quality of metadata and content standards continues to be a leading success factor.
Kittmer, Sarah. KMworld (2006). Articles>Content Management
#20388
Content Management: Web Publishing Needs Real Discipline
Too many organizations take an unprofessional approach to the content they publish on the Web. Many web managers still seem to believe that if they get the technology right the publishing will look after itself. Quality publishing requires skill and discipline. Unfortunately, discipline is something many web teams are lacking.
McGovern, Gerry. New Thinking (2003). Articles>Content Management>Content Strategy
#31169
Content Management: When Do We Need It?
By ensuring a document process is put in place and all people in your company know where to find information, how to request changes, update, and distribute new content, and who has the permission to manage the content you will be well on your way to having a viable content management system. Adding the software to automatically manage the content will only come when core principles of the organization require it.
Stuhlemmer, Barbara. ClearComm Information Design (2008). Articles>Content Management
#29634
Content Re-Use with the Tools at Hand
Frequent updates for a swarm of modular plug-ins were interrupting work on larger, higher-value projects. Worse, development was happening in a time zone 12 hours away, making communication a major bottleneck. Faced with fixed resources and growing commitments, our writing group extended existing tools to automate information gathering and rough draft creation, thereby halving the writer time each module required. This paper describes the user interface, tool extensions, and reusable information approach we used to solve the problem.
Carpenter, Cory, Samantha Lizak and Jeffrey Young. STC Proceedings (2005). Articles>Content Management>Collaboration
#28930
Content Strategy: The Philosophy of Data
As interactions proliferate, so does the content that supports them. Why should software professionals take a step back and examine their content from a philosophical perch? Rachel Lovinger takes a look at content strategy and the benefits of its perspectives.
Lovinger, Rachel. Boxes and Arrows (2007). Articles>Content Management>Theory>Content Strategy
