



CONTENT MANAGEMENT AND DOCUMENT MANAGEMENT
Overview: There is a need to reconcile the differences in workflow practice associated with content and document management activities. The challenge is to ensure workflow automation occurs in a way that embraces all aspects of user behaviour across the whole life cycle of electronic publishing and document management, including source documents. The inclusion of print workflow and other traditional activities such as records management and archiving will prove to be fundamentally important.
The difference between content management and document management
Document management is an older tradition than content management. The need for document management has arisen from the transition from hard copy file and records management to the management of large numbers of digital documents within organisations. The focus is primarily concerned with whole documents and usually involves the saving and archiving of native file formats. Files are normally generated on PCs or laptops.
In contrast, content management has its origins in website and intranet publishing. There is a strong focus on dynamic links between elements of content. The content management system manages the interconnections between small units of information.
Demarcation between content and document management
Historically, these two domains of practice have remained quite separate. The demarcation has been based on different mark up practices. Document management primarily involves the use of visual markup (the paradigm of the printed page) that is enshrined in software systems such as word processing and publishing packages. In contrast, content management systems have drawn on structural mark up practices that have arisen first from the use of standardised general markup language (SGML), then with hypertext markup language (HTML) and now extensible markup language (XML – the paradigm of the structured document).
Will the workflows of content and document management converge?
The use of extensible markup language (XML) within the document and text processing industries, such as those used each day by knowledge workers is a journey that has hardly begun. Knowledge workers and organisational managers everywhere are beginning to grapple with the challenges as they consider how best to integrate web publishing systems with other activities such as document management, data management, records and archiving management and print on demand. But the shift to fully enabled XML workflow of all documents and information represents a challenge as significant as the invention of the printing press itself in the mid 1400s. As this transformation accelerates almost every aspect of work will be transformed by these new developments.
Enterprise-wide publishing systems as the foci for convergence
In developing new solutions for their customers, media and publishing organisations need to become more aware of the particular strengths of their own traditions. In the years ahead, there will inevitably be a process of mixing and matching the skills associated with the different domains of practice encompassing both content management and document management. Enterprise-wide publishing systems will become the foci through which the domains of content and document management will converge.
Even though these trends are very embryonic, some of the differences as these are beginning to appear today are outlined as follows.
| Content management | Enterprise-wide publishing | |
| System design |
|
|
| Data entry |
|
|
| Data storage |
|
|
| Data schemas and XML standards |
|
|
| Search |
|
|
| Alerting and agent based processing |
|
|
| Style sheet rendering |
|
|
| Presentation management |
|
|
| Pre-press and renderings |
|
|
| Management |
|
|
KEY IMPLICATIONS