Content Management

Content Management
PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Thu, 13 Oct 2011 04:20:14 UTC
Contents
Articles
Digital asset management Digital asset Web content management system Enterprise content management Content management 1 3 4 8 22
References
Article Sources and Contributors 25
Article Licenses
License 26
Digital asset management

Digital asset management (DAM) consists of management tasks and decisions surrounding the ingestion, annotation, cataloguing, storage, retrieval and distribution of digital assets. Digital photographs, animations, videos and music exemplify the target-areas of media asset management (a sub-category of DAM).[1] Digital asset management systems (DAMS) include computer software and hardware systems that aid in the process of digital asset management. The term "digital asset management" (DAM) also refers to the protocol for downloading, renaming, backing up, rating, grouping, archiving, optimizing, maintaining, thinning, and exporting files. The "media asset management" (MAM) sub-category of digital asset management mainly addresses audio, video and other media content. The more recent concept of enterprise content management (ECM) often deals with solutions which address similar features but in a wider range of industries or applications.[2] Smaller DAM systems are easier to categorize as to content and usage since they normally operate in a particular operational context. This would hold true for systems attached to audio or video production systems. The key differentiators here are the type of decoders and I/O (input/output) used for the asset ingest, use and outgest. Since metadata describes the essence (and proxy copies), the metadata can serve as a guide to the playout decoders, transcoders, and channels as well as an input to access control rules. This means that the essence can be treated as a non-described storage object except when being accessed for viewing or editing. There is relevance to this when considering the overall design and use of larger implementations. The closer the asset is to the ingest/edit/playout tool, the greater the technical architecture needs to accommodate delivery requirements such as bandwidth, latency, capacity, access control, availability of resources, etc. The further the asset moves into a general storage architecture (e.g. hierarchical storage management [HSM]) the more it can be treated as a general blob (binary large object) that is typically held in the filesystem, not the database. The impact of this set of needs means that it is possible and reasonable to design larger systems using smaller, more expensive performance-systems at the edge of the network where the essence is being used in its intended form and less expensive systems further back for storage and archival. This type of design exemplifies Infrastructure Convergence Architecture, where the line-of-business operations technology and IT technologies depend on one another for functional and performance (non-functional) requirements.
Assets
Generally the "asset" being managed is collected and stored in a digital format. There is usually a target version referred to as "essence" - generally the highest-resolution and highest-fidelity representation. The asset is detailed by its metadata. Metadata is the description of the asset and the description depth can vary depending on the needs of the system, designer, or user. Metadata can describe, but is not limited to, the description of: asset content (what is in the package?); the means of encoding/decoding (e.g. JPEG, tar, MPEG 2); provenance (history to point of capture); ownership; rights of access; as well as many others. There exist some pre-defined standards and template for metadata such as Dublin Core and PBCore. In cases of systems that contain large-size asset essences, such as MPEG 2 and JPEG2000 for the cases of images and video, there are usually related "proxy" copies of the essence. A proxy copy is a lower-resolution representation of the essence that can be used as a reference in order to reduce the overall bandwidth requirements of the DAM system infrastructure. It can be generated and retained at the time of ingestion of the asset simultaneous or subsequent to the essence, or it can be generated on the fly using transcoders.
Types of digital asset management systems

The following broad categories of digital asset management systems may be distinguished: Brand asset management systems, with a focus on facilitation of content re-use within large organizations. Here the content is largely marketing- or sales-related, for example, product imagery, logos, marketing collateral or fonts, to give a few examples. Library asset management systems, with a focus on storage and retrieval of large amounts of infrequently changing media assets, for example in video or photo archiving. Production asset management systems focus on managing assets as they are being created for a digital media production (video game, 3D feature film, animation, visual-effects shots, etc.) They usually include work-flow and project-management features coupled with the storage, organization and revision control of frequently changing digital assets. Digital supply chain services, pushing digital content out to digital retailers (e.g. music, videos and games). DAM software may be open source or proprietary.
Providers
Enterprise-level solutions often involve scalable and configurable products that can handle vast numbers of assets (files) as well as large numbers of simultaneous users, workflows, or use cases (multiple applications simultaneously operating against the system). Enterprise systems may, but do not necessarily, include customized products or features added on to the base system or custom-developed to match an organization's workflow. In many cases these systems enter an organization in one department and eventually expand to others or to the entire enterprise as its utility becomes proven, understood and valued. Enterprise systems are offered as installed software - called on-premise - or as Software as a Service hosted, web-based offers managed and maintained externally. Some image viewers and other media-management applications provide some DAM functionality for individual users, including backing up, organizing, and reading/writing metadata and keywords.
References
[1] van Niekerk, A.J. (2006). The Strategic Management of Media Assets; A Methodological ApproachAllied Academies, New Orleans Congress. [2] Intro to Digital Asset Management: Just what is a DAM? (http:/ / cmswatch. com/ Feature/ 124-DAM-vs. -DM) by Magan Arthur
Further reading
Jacobsen, Jens; Schlenker, Tilman; Edwards, Lisa (2005). Implementing a Digital Asset Management System: For Animation, Computer Games, and Web Development. Focal Press. ISBN0-240-80665-4. Krogh, Peter (2009). The DAM Book, Second Edition. O'Reilly Media. ISBN0-596-52357-2. Krogh, Peter (2005). The DAM Book: Digital Asset Management for Photographers. O'Reilly Media. ISBN0-596-10018-3. Austerberry, David (2006). Digital Asset Management, Second Edition. Focal Press. ISBN0-240-80868-1. Mauthe, Andreas and Thomas, Peter (2004). Professional Content Management Systems: Handling Digital Media Assets. Wiley. ISBN0-470-85542-8.
External links
Digital Asset Management Services For Your Global Web Operations (http://globalmarketingops.com/) Digital Asset Management and Museums: An Introduction (http://www.pro.rcip-chin.gc.ca/ sommaire-summary/gestion_contenus_numeriques-digital_assets_management-eng.jsp) Open Source Digital Asset Management (http://www.opensourcedigitalassetmanagement.org/) - Overview of open source DAM systems available.
Digital asset
A digital asset is any item of text or media that has been formatted into a binary source that includes the right to use it. A digital file without the right to use it is not an asset. Digital assets are categorised in three major groups which may be defined as textual content (digital assets), images (media assets) and multimedia (media assets) (van Niekerk, A.J. 2006).[1]
Definitions
Defining and distinguishing the different types of digital assets can aid in understanding the management of digital assets. There are a number of management systems related to digital asset management (Austerberry, 2004) including: 1. 2. 3. 4. 5. 6. Digital asset management (DAM) Digital content management (DCM) Enterprise content management (ECM) Digital media management (DMM) Media asset management (MAM) Web-content management (WCM)
Art assets
An art asset (media assets [2] ), in computer graphics and related fields (particularly video game and visual effects production), is an individual piece of digital media used in the creation of a larger production. Art assets include synthetic and photographic bitmaps (often used for texture mapping), 3D models consisting of polygon meshes or curved surfaces, shaders, motion captured or hand-animated animation data, video and audio samples. The term "art" is used to distinguish the creative (or real-world) elements of a production from the software or hardware used to create it, but there is no requirement that the data represents anything artistic.
Digital learning assets

Digital learning assets (DLAs) are digital assets focused on "learning". DLAs are any form of content and/or media that have been formatted into a binary source which include the right to use it for the purpose of "facilitating learning". DLAs are most commonly found in online learning (academic course work, corporate training, etc). [3]
The future
Digital asset management is expected to be a multi-billion dollar industry as corporations and individuals migrate traditional graphic, broadcast and print assets to the digital format. Companies including Apple, Oracle, Microsoft, Getty Images and others are aggressively expanding their enterprises to provide third-party digital asset management via web-based repositories. This trend will continue as business and consumers evolve from traditional analog
Digital asset materials.
References
[1] van Niekerk, A.J. (2006) The Strategic Management of Media Assets; A Methodological Approach. Allied Academies, New Orleans Congress, 2006 [2] an Niekerk, A.J. (2006) The Strategic Management of Media Assets; A Methodological Approach. Allied Academies, New Orleans Congress, 2006 [3] Larson-Daugherty, C., February 2009. an update to van Nierkerk, A.J. (2006) that focused solely on digital assets. With tremendous growth in online learning an update and new nomenclature is necessary
Web content management system

A web content management system (WCMS)[1] is a software system that provides website authoring, collaboration, and administration tools designed to allow users with little knowledge of web programming languages or markup languages to create and manage website content with relative ease. A robust WCMS provides the foundation for collaboration, offering users the ability to manage documents and output for multiple author editing and participation. Most systems use a database to store page content, metadata, and other information assets that might be needed by the system. A presentation layer displays the content to website visitors based on a set of templates. The templates are sometimes XSLT files.[2] Most systems use server side caching to improve performance. This works best when the WCMS is not changed often but visits happen regularly. Administration is typically done through browser-based interfaces, but some systems require the use of a fat client. A WCMS allows non-technical users to make changes to a website with little training. A WCMS typically requires a systems administrator and/or a web developer to set up and add features, but it is primarily a website maintenance tool for non-technical staff.
Capabilities
A WCMS is a software system used to control a dynamic collection of Web material (HTML documents, images, and other forms of media).[3] A CMS facilitates document control, auditing, editing, and timeline management. A WCMS typically has[4] [5] : Automated templates Create standard output templates (usually HTML and XML) that can be automatically applied to new and existing content, allowing the appearance of all content to be changed from one central place. Access Control Some WCMS systems support user Groups. User Groups allow you to control how registered users interact with the site. A page on the site can be restricted to one or more groups. This means if an Anonymous User (someone not logged on) or a Logged on User who is not a member of the Group a page is restricted to, the user will be denied access to the page. Scalable expansion Available in most modern WCMSs is the ability to expand a single implementation (one installation on one server) across multiple domains, depending on the server's settings. WCMS sites may be able to create microsites/web portals within a main site as well.
Web content management system Easily editable content Once content is separated from the visual presentation of a site, it usually becomes much easier and quicker to edit and manipulate. Most WCMS software includes WYSIWYG editing tools allowing non-technical individuals to create and edit content. Scalable feature sets Most WCMS software includes plug-ins or modules that can be easily installed to extend an existing site's functionality. Web standards upgrades Active WCMS software usually receives regular updates that include new feature sets and keep the system up to current web standards... Workflow management Workflow is the process of creating cycles of sequential and parallel tasks that must be accomplished in the CMS. For example, one or many content creators can submit a story, but it is not published until the copy editor cleans it up and the editor-in-chief approves it. Collaboration CMS software may act as a Collaboration platform allowing content to be retrieved and worked on by one or many authorized users. Changes can be tracked and authorized for publication or ignored reverting to old versions. Other advanced forms of collaboration allow multiple users to modify (or comment) a page at the same time in a collaboration session. Delegation Some CMS software allows for various user groups to have limited privileges over specific content on the website, spreading out the responsibility of content management.[6] Document management CMS software may provide a means of collaboratively managing the life cycle of a document from initial creation time, through revisions, publication, archive, and document destruction. Content virtualization CMS software may provide a means of allowing each user to work within a virtual copy of the entire Web site, document set, and/or code base. This enables changes to multiple interdependent resources to be viewed and/or executed in-context prior to submission. Content syndication CMS software often assists in content distribution by generating RSS and Atom data feeds to other systems. They may also e-mail users when updates are available as part of the workflow process. Multilingual Ability to display content in multiple languages. Versioning Like Document Management Systems CMS software may allow the process of versioning by which pages are checked in or out of the WCMS, allowing authorized editors to retrieve previous versions and to continue work from a selected point. Versioning is useful for content that changes over time and requires updating, but it may be necessary to go back to or reference a previous copy.
Types
There are three major types of WCMS: offline processing, online processing, and hybrid systems. These terms describe the deployment pattern for the WCMS in terms of when presentation templates are applied to render Web pages from structured content.
Online processing (called "frying" systems)

These systems apply templates on-demand. HTML may be generated when a user visits the page or pulled from a cache. Most open source WCMSs have the capability to support add-ons, which provide extended capabilities including forums, blog, wiki, Web stores, photo galleries, contact management, etc. These are often called modules, nodes, widgets, add-ons, or extensions. Add-ons may be based on an open-source or paid license model. Different WCMSs have significantly different feature sets and target audiences. Longtime WCMS research and evaluation firm Real Story Group (formerly CMS Watch) identifies five different tiers of WCMS vendors and open source projects.[7]
Hybrid systems
Some systems combine the offline and online approaches. Some systems write out executable code (e.g., JSP, ASP, PHP, ColdFusion, or Perl pages) rather than just static HTML, so that the CMS itself does not need to be deployed on every Web server. Other hybrids operate in either an online or offline mode.
Advantages
Low Cost Some CMSs are free like Drupal, TYPO3, Joomla, and WordPress. Others may be affordable based on size subscriptions.[8] Although subscriptions can be expensive, overall the cost of not having to hire full-time developers can lower the total costs. Plus software can be bought based on need for many CMSs. Easy Customization A universal layout is created, making pages have a similar theme and design without much code. Many CMS tools use a drag and drop AJAX system for their design modes. It makes it easy for beginner users to create custom front-ends.[9] Easy to use CMSs are designed with non-technical people in mind. Simplicity in design of the admin UI allows website content managers and other users to update content without much training in coding or technical aspects of system maintenance. WorkFlow management CMSs provide the facility to control how content is published, when it is published, and who publishes it. Some WCMSs allow administrators to set up rules for workflow management, guiding content managers through a series of steps required for each of their tasks.
Disadvantages
Cost of implementation Larger scale implementations may require training, planning, and certifications. Certain CMSs may require hardware installations. Commitment to the software is required on bigger investments. Commitment to training, developing, and upkeep are all costs that will be incurred for enterprise systems.[10] Cost of maintenance Maintaining CMSs may require license updates, upgrades, and hardware maintenance. Storage Volume Volume of files may be large in HTML-based systems. A site that contains many files leaves itself open to errors. For example, a client updating the site may create errors; large amounts of files can cause issues with updating. Trying to find the right file may take time, and may be hard to find. Latency issues Larger CMSs can experience latency if hardware infrastructure is not up to date, if databases are not being utilized correctly, and if cache files that have to be reloaded every time data is updated grow large. Load balancing issues may also impair caching files. Tool Mixing Because the URLs of many CMSs are dynamically generated with internal parameters and reference information, they are often not stable enough for static pages and other Web tools, particularly search engines, to rely on them.
References
[1] Mike Johnston. "CMS or WCM - Which is Which?" (http:/ / www. cmscritic. com/ cms-or-wcm-which-is-which/ ). cmscritic.com. . Retrieved 2011-09-07. [2] Woric Faithfull. "Using XSLT to Make Websites" (http:/ / woric. net/ wsg_presentation/ Part1_using_xslt. xf). woric.net. . Retrieved 2007-11-08. [3] Mike Johnston (2009). "What is a CMS?" (http:/ / cmscritic. com/ what-is-a-cms). CMS Critic. . Retrieved 2009-02-13. [4] GOSS Interactive (2009). "8 Things to consider when starting a WCM project - A best practice guide" (http:/ / www. gossinteractive. com/ CHttpHandler. ashx?id=254& p=0). GOSS Interactive website. . Retrieved 2010-07-28. [5] Multiple (wiki). "Content management system" (http:/ / docforge. com/ wiki/ Content_management_system). Docforge. . Retrieved 2010-01-19. [6] Jovia Web Studio (2009). "Is a Content Management System Right for You" (http:/ / www. joviawebstudio. com/ index. php/ blog/ is_a_content_management_system_right_for_you/ ). Jovia Web Studio Blog. . Retrieved 2009-02-13. [7] Real Story Group "Real Story Group CMS Categories" (http:/ / www. realstorygroup. com/ Research/ Channel/ CMS/ Vendors) 2010. Retrieved 2011-01-17. [8] "SharePoint" (http:/ / articles. techrepublic. com. com/ 5100-22_11-5975781. html). . Retrieved 17 March 2011. [9] "AJAX - WordPress Codex" (http:/ / codex. wordpress. org/ AJAX). . Retrieved 17 March 2011. [10] "The 5 hidden costs of running a CMS" (http:/ / thinkvitamin. com/ web-industry/ the-5-hidden-costs-of-running-a-cms/ ). . Retrieved 17 March 2011.
Enterprise content management

Enterprise Content Management (ECM) is a formalized means of organizing and storing an organization's documents, and other content, that relate to the organization's processes. The term encompasses strategies, methods, and tools used throughout the lifecycle of the content.[1]
Definition
The Association for Information and Image Management (AIIM) International, the worldwide association for enterprise content management, defined the term Enterprise Content Management in 2000. AIIM has refined the abbreviation ECM several times to reflect the expanding scope and importance of information management: Late 2005 Enterprise content management is the technologies used to Capture, Manage, Store, Preserve, and Deliver content and documents related to organizational processes. Early 2006 Enterprise content management is the technologies used to Capture, Manage, Store, Preserve, and Deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists. Early 2008 Enterprise Content Management (ECM) is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists. [1] Early 2010 Enterprise Content Management (ECM) is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM covers the management of information within the entire scope of an enterprise whether that information is in the form of a paper document, an electronic file, a database print stream, or even an email [1] The latest definition encompasses areas that have traditionally been addressed by records management and document management systems. It also includes the conversion of data between various digital and traditional forms, including paper and microfilm. ECM is an umbrella term covering document management, web content management, search , collaboration, records management, digital asset management (DAM), work-flow management, capture and scanning. ECM is primarily aimed at managing the life-cycle of information from initial publication or creation all the way through archival and eventually disposal. ECM applications are delivered in three ways: on-premise software (installed on the organizations own network), Software as a Service (SaaS) (web access to information that is stored on the software manufacturers system), or a hybrid solution composed of both on-premise and SaaS components. ECM aims to make the management of corporate information easier through simplifying storage, security, version control, process routing, and retention. The benefits to an organization include improved efficiency, better control, and reduced costs. For example, many banks have converted to storing copies of old checks within ECM systems versus the older method of keeping physical checks in massive paper warehouses. Under the old system a customer request for a copy of a check might take weeks, as the bank employees had to contact the warehouse to have someone locate the right box, file and check, pull the check, make a copy and then mail it to the bank who would eventually mail it to the customer. With an ECM system in place, the bank employee simply searches the system for the customers account number and the number of the requested check. When the image of the check appears on
Enterprise content management screen, they are able to immediately mail it to the customerusually while the customer is still on the phone.
History
Enterprise Content Management, as a form of content management, combines the capture, search and networking of documents with digital archiving, document management and workflow. It specifically includes the special challenges involved in using and preserving a company's internal, often unstructured information, in all of its forms. Therefore, most ECM solutions focus on Business-to-Employee (B2E) systems. As ECM solutions have evolved, new components have emerged. For example, as content is checked in and out, each use generates new metadata about the content, to some extent automatically; information about how and when the content was used can allow the system to gradually acquire new filtering, routing and search pathways, corporate taxonomies and semantic networks, and retention-rule decisions. Email and instant messaging are increasingly employed in decision-making processes; ECM can provide access to data about these communications, which can be used in business decisions. Solutions can provide intranet services to employees (B2E), and can also include enterprise portals for Business-to-Business (B2B), Business-to-Government (B2G), Government-to-Business (G2B), or other business relationships. This category includes most former document-management groupware and workflow solutions that have not yet fully converted their architecture to ECM, but provide a web interface. Digital asset management is a form of ECM concerned with content stored using digital technology. The technologies that comprise ECM today are the descendants of late 1980s and early 1990s electronic document management systems (EDMS). The original EDMS products were stand-alone products, providing functionality in one of four areas: imaging, workflow, document management, or COLD/ERM (see components below). The typical early EDMS adopter deployed a small-scale imaging and workflow system, possibly to just a single department, in order to improve a paper-intensive process and migrate towards the mythical paperless office. The first stand-alone EDMS technologies were designed to save time and/or improve information access by reducing paper handling and paper storage, thereby reducing document loss and providing faster access to information. EDMS could provide online access to information formerly available only on paper, microfilm, or microfiche. By improving control over documents and document-oriented processes, EDMS streamlined time-consuming business practices. The audit trail generated by EDMS enhanced document security, and provided metrics to help measure productivity and identify efficiency. Through the late 1990s, the EDMS industry continued to grow steadily. The technologies appealed to organizations that needed targeted, tactical solutions to address clearly defined problems. As time passed, and more organizations achieved "pockets" of productivity with these technologies, it became clear that the various EDMS product categories were complementary. Organizations increasingly wanted to leverage multiple EDMS products. Consider, for example, a customer service departmentwhere imaging, document management, and workflow could be combined to allow agents to better resolve customer inquiries. Likewise, an accounting department might access supplier invoices from a COLD/ERM system, purchase orders from an imaging system, and contracts from a document management system as part of an approval workflow. As organizations established an Internet presence, they wanted to present information via the web, which required managing web content. Organizations that had automated individual departments now began to envision wider benefits from broader deployment. Many documents cross multiple departments and affect multiple processes. The movement toward integrated EDMS solutions merely reflected a common trend in the software industry: the ongoing integration of point solutions into more comprehensive solutions. For example, until the early 1990s, word processing, spreadsheet, and presentation software products were standalone products. Thereafter, the market shifted toward integration.
Enterprise content management Early leaders already offered multiple stand-alone EDMS technologies. The first phase was to offer multiple systems as a single, packaged "suite", with little or no functional integration. Throughout the 1990s, integration increased. Beginning in approximately 2001, the industry began to use the term enterprise content management to refer to these integrated solutions. In 2006, Microsoft (with its SharePoint product family) and Oracle Corporation (with Oracle Content Management) joined established leaders such as EMC Documentum and entered the entry-level "value" market segment of ECM.[2]
[3]
10
Open source ECM products are also available, including Campsite, WebGUI, Alfresco, LogicalDOC, Sense/Net, eZ Publish, KnowledgeTree, Jumper 2.0, Nuxeo, and Plone. Government standards, including HIPAA, SAS 70, BS 7799 and ISO/IEC 27001, are factors in developing and deploying ECM. Standards compliance may make outsourcing to certified service providers a viable alternative to an internal ECM deployment. Today, organizations can deploy a single, flexible ECM system to manage information in all functional departments, including customer service, accounting, human resources, etc.
Todays Adoption Drivers

There are numerous factors driving businesses to adopt an ECM solution, such as the need to increase efficiency, to improve control of information, and to reduce the overall cost of information management for the enterprise. ECM applications streamline access to records through keyword and full-text search allowing employees to get to the information they need directly from their desktops in seconds rather than searching multiple applications or digging through paper records. These management systems can enhance record control to help businesses to comply with government and industry regulations such as HIPAA, Sarbanes-Oxley, PCI DSS, and the Federal Rules of Civil Procedure. Security functions including user-level, function-level and even record-specific security options protect your most sensitive data. In fact, even information contained on a specific document can be masked using redaction features, so the rest of the document can be shared without compromising individual identity or key data. Every action taken within the system is tracked and reportable for auditing purposes for a wide variety of regulations. ECM systems can reduce storage, paper and mailing needs, make employees more efficient, and result in better, more informed decisions across the enterpriseall of which reduce the overhead costs of managing information. SaaS ECM services can convert expensive capital outlay for servers and network equipment into a monthly operating expense, while also reducing the IT resources required to manage enterprise records.
Characteristics
Content management includes ECM, Web content management (WCM), content syndication, and media asset management. Enterprise content management is not a closed-system solution or a distinct product category. Therefore, along with Document Related Technologies or Document Lifecycle Management, ECM is just one possible catch-all term for a wide range of technologies and vendors. The content and structure of today's outward-directed web portal will be the platform for tomorrow's internal information system. In his article in ComputerWoche,[4] Ulrich Kampffmeyer distilled ECM to three key ideas that distinguish such solutions from Web content management: Enterprise content management as integrative middleware ECM is used to overcome the restrictions of former vertical applications and island architectures. The user is basically unaware of using an ECM solution. ECM offers the requisite infrastructure for the new world of web-based IT, which is establishing itself as a kind of third platform alongside conventional
Enterprise content management host and client/server systems. Therefore, EAI (enterprise application integration) and SOA (service-oriented architecture) will play an important role in the implementation and use of ECM. enterprise content management components as independent services ECM is used to manage information without regard to the source or the required use. The functionality is provided as a service that can be used from all kinds of applications. The advantage of a service concept is that for any given functionality only one general service is available, thus avoiding redundant, expensive and difficult to maintain parallel functions. Therefore, standards for interfaces connecting different services will play an important role in the implementation of ECM. enterprise content management as a uniform repository for all types of information ECM is used as a content warehouse (both data warehouse and document warehouse) that combines company information in a repository with a uniform structure. Expensive redundancies and associated problems with information consistency are eliminated. All applications deliver their content to a single repository, which in turn provides needed information to all applications. Therefore, content integration and ILM (Information Lifecycle Management) will play an important role in the implementation and use of ECM. Enterprise content management is working properly when it is effectively "invisible" to users. ECM technologies are infrastructures that support specialized applications as subordinate services. ECM thus is a collection of infrastructure components that fit into a multi-layer model and include all document related technologies (DRT) for handling, delivering, and managing structured data and unstructured information jointly. As such, enterprise content management is one of the necessary basic components of the overarching e-business application area. ECM also sets out to manage all the information of a WCM and covers archiving needs as a universal repository.[5]
11
Components
ECM combines components which can also be used as stand-alone systems without being incorporated into an enterprise-wide system.[5] The five ECM components and technologies were first defined by AIIM as capture, manage, store, preserve, and deliver.
Capture
Capture involves converting information from paper documents into an electronic format through scanning. Capture is also used to collect electronic files and information into a consistent structure for management. Capture technologies also encompass the creation of metadata (index values) that describe characteristics of a document for easy location through search technology. For example, a medical chart might include the patient ID, patient name, date of visit, and procedure as index values to make it easy for medical personnel to locate the chart. Earlier document automation systems photographed documents for storage on microfilm or microfiche. Optical scanners now make digital copies of paper documents. Documents already in digital form can be copied, or linked to if they are already available online. Automatic or semi-automatic capture can use EDI or XML documents, business and ERP applications, or existing specialist application systems as sources.
Enterprise content management Recognition technologies Various recognition technologies can be used to extract information from scanned documents and digital faxes, including: Optical character recognition (OCR) Converts images of typeset text into alphanumeric characters handprint character recognition (HCR) Converts images of handwritten text into alphanumerics. Gives better results for short text in fixed locations than for freeform text. Intelligent character recognition (ICR) Extends OCR and HCR to use comparison, logical connections, and checks against reference lists and existing master data to improve recognition. For example, on a form where a column of numbers is added up, the accuracy of the recognition can be checked by adding the recognized numbers and comparing them to the sum written on the original form. Optical mark recognition (OMR) Reads special markings, such as checkmarks or dots, in predefined fields. Barcode recognition Decodes industry-standard encodings of product and other commercial data. Image cleanup Image cleanup features include rotation, straightening, color adjustment, transposition, zoom, aligning, page separation, annotations and despeckling. Forms processing In forms capture, there are two groups of technologies, although the information content and character of the documents may be identical. Forms processing is the capture of printed forms via scanning; recognition technologies are often used here, since well-designed forms enable largely automatic processing. Automatic processing can be used to capture electronic forms, such as those submitted via web pages, as long as the layout, structure, logic, and contents are known to the capture system. COLD Computer Output to Laser Disc (COLD) records reports and other documents on optical disks, or any form of digital storage for ongoing management by ECM systems. Another term for this is enterprise report management (ERM). Originally, the technology only worked with laserdiscs; the name was not changed after other technologies supplanted the laserdisc. Aggregation Aggregation combines documents from different applications. The goal is to unify data from different sources, forwarding them to storage and processing systems in a uniform structure and format.
12
Enterprise content management Indexing components Indexing improves searches, and provides alternative ways to organize the information. Manual indexing assigns index database attributes to content by hand, typically used by the database of a "manage" component for administration and access. Manual indexing may make use of input designs to limit the information that can be entered; for example, entry masks may use program logic to restrict inputs based on other information known about the document. Both automatic and manual attribute indexing can be made easier and better with preset input-design profiles; these can describe document classes that limit the number of possible index values, or automatically assign certain criteria. Automatic classification programs can extract index, category, and transfer data autonomously. Automatic classification or categorizing, based on the information contained in electronic information objects, can evaluate information based on predefined criteria or in a self-learning process. This technique can be used with OCR-converted faxes, office files, or output files.
13
Manage
The Manage category includes five traditional application areas: Document management (DM) Collaboration (or collaborative software, a.k.a. groupware) Web content management (including web portals) Records management Workflow and business process management (BPM)
The Manage category connects the other components, which can be used in combination or separately. Document management, web content management, collaboration, workflow and business process management address the dynamic part of the information's lifecycle. Records management focuses on managing finalized documents in accordance with the organization's document retention policy, which in turn must comply with government mandates and industry practices.[6] All Manage components incorporate databases and access authorization systems. Manage components are offered individually or integrated as suites. In many cases they already include the "store" components. Document management Document management, in this context, refers to document management systems in the narrow sense of controlling documents from creation to archiving. Document management includes functions like: Check in/check out For checking stored information for consistency. Version management To keep track of different versions of the same information with revisions and renditions (same information in a different format). Search and navigation For finding information and its associated contexts. Organizing documents In structures like files, folders, and overviews. However, document management increasingly overlaps with other "Manage" components, office applications like Microsoft Outlook and Exchange, or Lotus Notes and Domino, as well as "library services" for administering information storage.
Enterprise content management Collaboration Collaboration components in an ECM system help users work with each other to develop and process content. Many of these components were developed from collaborative software, or groupware, packages; ECM collaborative systems go much further, and include elements of knowledge management. ECM systems facilitate collaboration by using information databases and processing methods that are designed to be used simultaneously by multiple users, even when those users are working on the same content item. They make use of knowledge based on skills, resources and background data for joint information processing. Administration components, such as virtual whiteboards for brainstorming, appointment scheduling and project management systems, communications application such as video conferencing, etc., may be included. Collaborative ECM may also integrate information from other applications, permitting joint information processing. Web content management The scope of Enterprise content management integrates web content management systems. WCM as ECM component is used to present information already existing and managed in the ECM repository. However, information presented via Web technologies - on the Internet, an extranet, or on a portal uses the workflow, access control, versioning, delivery and authorization modules of the WCM instead of own integrated ECM functionality. There are only few examples of successful implementations whereby a shared repository for documents and web content are managed together.. Records management (file and archive management) Unlike traditional electronic archival systems, records management refers to the pure administration of records, important information, and data that companies are required to archive. Records management is independent of storage media; managed information does not necessarily need to be stored electronically, but can be on traditional physical media as well. Some of the functions of records management are: Visualisation of file plans and other structured indexes for the orderly storage of information Unambiguous indexing of information, supported by thesauri or controlled wordlists Management of record retention schedules and deletion schedules Protection of information in accordance with its characteristics, sometimes down to individual content components in documents Use of international, industry-specific or company-wide standardized metadata for the unambiguous identification and description of stored information Workflow/business process management Workflow and business process management differ substantially. Workflow There are different types of workflow: production workflow uses predefined sequences to guide and control processes, whereas in an ad-hoc workflow, the user determines the process sequence on the fly. Workflow can be implemented as workflow solutions with which users interact, or as workflow engines, which act as a background service controlling the information and data flow. Workflow management includes the following functions: Visualisation of process and organization structures Capture, administration, visualization, and delivery of grouped information with its associated documents or data Incorporation of data processing tools (such as specific applications) and documents (such as office products) Parallel and sequential processing of procedures including simultaneous saving Reminders, deadlines, delegation and other administration functionalities
14
Enterprise content management Monitoring and documentation of process status, routing, and outcomes Tools for designing and displaying process The objective is to automate processes as much as possible by incorporating all necessary resources. Business process management Business process management (BPM) goes a step further than workflow. Although the words are often used interchangeably, BPM aims to completely integrate all of the affected applications within an enterprise, monitoring processes and assembling all required information. Among BPM's functions are: BPM offers complete workflow functionality, providing process and data monitoring at the server level. Enterprise application integration is used to link different applications. Business intelligence, with rule structures, integrates information warehouses and provides utilities that assist users in their work.
15
Store
Store components temporarily store information that isn't required, desired, or ready for long-term storage or preservation. Even if the Store component uses media that are suitable for long-term archiving, "Store" is still separate from "Preserve." The Store components can be divided into three categories: Repositories as storage locations, Library Services as administration components for repositories, and storage Technologies. These infrastructure components are sometimes held at the operating system level (like the file system), and also include security technologies that work in tandem with the "Deliver" components. However, security technologies, including access control, are superordinated components of an ECM solution. Repositories Different kinds of ECM repositories can be used in combination. Among the possible kinds are: File systems File systems are used primarily for temporary storage, as input and output caches. ECM's goal is to reduce the data burden on the file system, and make the information generally available through Manage, Store, and Preserve technologies. Content management systems This is the actual storage and repository system for content, which can be a database or a specialized storage system. Databases Databases administer access information, but can also be used for the direct storage of documents, content, or media assets. Data warehouses These are complex storage systems based on databases, which reference or provide information from all kinds of sources. They can also be designed with global functions, such as document or information warehouses. Library services Library services are the administrative components of the ECM system that handle access to information. The library service is responsible for taking in and storing information from the Capture and Manage components. It also manages the storage locations in dynamic storage, the actual "Store," and in the long-term Preserve archive. The storage location is determined only by the characteristics and classification of the information. The library service works in concert with the Manage components' database to provide the necessary functions of search and retrieval.
Enterprise content management While the database does not "know" the physical location of a stored object, the library service manages online storage (direct access to data and documents), nearline storage (data and documents on a medium that can be accessed quickly, but not immediately, such as data on an optical disc that is present in a storage system's racks but not currently inserted in a drive that can read it), and offline storage (data and documents on a medium that is not quickly available, such as data stored offsite). If the document management system does not provide the functionality, the library service must have version management to control the status of information, and check-in/check-out, for controlled information provision. The library service generates logs of information usage and editing, called an "audit trail." Storage technologies A wide variety of technologies can be used to store information, depending on the application and system environment: Magnetic online media Hard drives, typically configured as RAID systems, may be locally attached, part of a storage area network (SAN), or mounted from another server (network-attached storage). Magnetic tape Magnetic tape data storage, in the form of automated storage units called tape libraries, use robotics to provide nearline storage. Standalone tape drives may be used for backup, but not online access. Digital optical media Besides the common Compact Disc and DVD optical media in write-once or rewritable forms, Storage systems may use other specialized optical formats like magneto-optical drives for storage and distribution of data. Optical jukeboxes can be used for nearline storage. Optical media in jukeboxes can be removed, transitioning it from nearline to offline storage. Cloud computing Data can be stored on offsite cloud computing servers, accessed via the Internet.
16
Preserve
Preserve involves the long-term, safe storage and backup of static, unchanging information. Preservation is typically accomplished by the records management features of an ECM system and many are designed to help companies comply with government and industry regulations. Eventually, content ceases to change and becomes static. The Preserve components of ECM handle the long-term, safe storage and backup of static information, as well as the temporary storage of information that does not need to be archived. Electronic archiving, a related concept, has substantially broader functionality than ECM Preserve components. Electronic archiving systems generally consist of a combination of administration software like records management, imaging or document management, library services or information retrieval systems, and storage subsystems. Other forms of media are also suitable for long-term archiving. If the desire is merely to ensure information is available in the future, microfilm is still viable; unlike many digital records, microfilm is readable without access to the specialized software that created it. Hybrid systems combine microfilm with electronic media and database-supported access. Long-term storage systems require the timely planning and regular performance of data migrations, in order to keep information available in the changing technical landscape. As storage technologies fall into disuse, information must be moved to newer forms of storage, so that the stored information remains accessible using contemporary systems. For example, data stored on floppy disks becomes essentially unusable if floppy disk drives are no longer readily
Enterprise content management available; migrating the data stored on floppy disks to Compact Discs preserves not only the data, but the ability to access it. This ongoing process is called continuous migration. The Preserve components contain special viewers, conversion and migration tools, and long term storage media: Long term storage media WORM optical disc Write Once Read Many (WORM) rotating digital optical storage media, including the 5.25-inch or 3.5-inch WORM disc in a protective sleeve, as well as CD-R and DVD-R. Recording methods vary for these media, which are held in jukeboxes for online and automated nearline access. WORM tape Magnetic tapes used in special drives, that can be as secure as optical write-once, read-many media if used properly with specially secured tapes. WORM hard disk drive Magnetic disk storage with special software protection against overwriting, erasure, and editing; delivers security similar to optical write-once, read-many media. This category includes content-addressable storage. Storage networks Storage networks, such as network-attached storage and storage area networks, can be used if they meet the requirements of edit-proof auditing with unchangeable storage and protection against manipulation and erasure. Microform Microforms like microfilm, microfiche, and aperture cards can be used to back up information that is no longer in use and does not require machine processing. It is typically used only to double-secure originally electronic information. Paper Paper still has use as a long-term storage medium, since it does not require migration, and can be read without any technical aids. In ECM systems, however, it is used only to double-secure originally electronic information... Long term preservation strategies To secure the long term availability of information different strategies are used for electronic archives. The continuous migration of applications, index data, metadata and objects from older systems to new ones generates a lot of work, but secures the accessibility and usability of information. During this process, information that is no longer relevant can be deleted. Conversion technologies are used to update the format of the stored information, where needed. Emulation of older software allows users to run and access the original data and objects. Special viewer software can identify the format of the preserved objects and can display the objects in the new software environment. Standards for interfaces, metadata, data structures and object formats are important to secure the availability of information.
17
18
Deliver
The Deliver components of ECM present information from the Manage, Store, and Preserve components. The AIIM component model for ECM is function-based, and doesn't impose a strict hierarchy; the Deliver components may contain functions used to enter information into other systems (such as transferring information to portable media, or generating formatted output files); or for readying information, such as by converting its format or compressing it, for the "Store" and "Preserve" components. The Deliver category's functionality is also known as "output"; technologies in this category are often termed output management. The Deliver components break down into three groups: transformation technologies, security technologies, and distribution. Transformation and security, as services, are middleware and should be equally available to all ECM components. For output, two functions are of primary importance: layout and design, with tools for laying out and formatting output, and publishing, with applications for presenting information for distribution and publication. In short, ECM delivery provides information to users. Secure distribution, collaboration, and version control take the forefront. In some cases, these components are still deployed as stand-alone systems without being incorporated into an enterprise-wide ECM system. Delivery Methods On-premise ECM was developed as a traditional software application that companies implemented on their own corporate networks. In this scenario, each individual company manages and maintains both the ECM application, and the network storage devices that store the data. Many on-premise ECM systems are highly customized for individual organizational needs. A note about Capture: since paper document capture requires the use of physical scanning devices, like scanners or multi-function devices, it is typically performed on-premise. However, it can be outsourced to businesses that provide scanning services. Known as Service Bureaus, these companies complete high-volume scanning and indexing and return the electronic files to organizations via web transfer or on CDs, DVDs, or other external storage devices. Software as a Service SaaS SaaS ECM means that rather than deploying software on an in-house network, users access the application and their data online. It is also known as cloud computing, hosted, and on demand. As SaaS distribution technologies mature, businesses can count on receiving the same features and customization capabilities they have come to expect from on-premise ECM applications. SaaS delivery allows companies to more quickly begin using ECM, since they do not have to purchase hardware or configure the applications, databases, or servers. In addition, organizations trade the capital costs associated with a hardware and software purchase for a monthly operating expense and storage capabilities that grow automatically to accommodate company growth. Hybrid In some scenarios, companies find a hybrid composed of both SaaS and on-premise software work best for their situation. For example, hybrid ECM systems are being used to bridge the gap during company moves or to simplify information exchange following an acquisition. Hybrid is also being used when companies want to manage their own ECM on-premise, but also provide easy web access to certain information for business partners or customers using a SaaS model. Hybrid makes the most sense when the two technologies are provided by the same manufacturer, so that features and interfaces are an exact match.
Enterprise content management Transformation technologies Transformations should always be controlled and trackable. This is done by background services which the end user generally does not see. Among the transformation technologies are: Computer Output to Laser Disc (COLD) Unlike its use in the Capture stage, when used for delivery COLD prepares output data for distribution and transfer to the archive. Typical applications are lists and formatted output (for example, individualized customer letters). These technologies also include journals and logs generated by the ECM components. Unlike most imaging media, COLD records are indexed not in a database table, but by absolute positions within the document itself (i.e. page 1, line 82, position 12). As a result, COLD index fields are not available for editing after submission unless they are converted into a standard database. Personalization Functions and output can be customized to a particular user's needs. XML (Extensible Markup Language) A computer language that allows the description of interfaces, structures, metadata, and documents in a standardized, cross-platform manner. PDF (Portable Document Format) A cross-platform print and distribution format. Unlike image formats such as TIFF, PDFs permit content searches, the addition of metadata, and the embedding of electronic signatures. When generated from electronic data, PDFs are resolution-independent, allowing crisp reproduction at any scale. XPS (XML Paper Specification) An XML specification developed by Microsoft, describing the formats and rules for distributing, archiving, rendering, and processing XPS documents. Converters and viewers Serve to reformat information to generate uniform formats, and also to display and output information from different formats. Compression Used to reduce the storage space needed for pictorial information. Syndication Used for presenting content in different formats, selections, and forms in the context of content management. Syndication allows the same content to be used multiple times in different forms for different purposes. Security technologies Security technologies are available to all ECM components. For example, electronic signatures are used not only when documents are sent, but also in data capture via scanning, in order to document the completeness of the capture. Public key infrastructure is a basic technology for electronic signatures. It manages keys and certificates, and checks the authenticity of signatures. Other electronic signatures confirm the identity of the sender and the integrity of the sent data, i.e., that it is complete and unchanged. In Europe, there are three forms of electronic signatures, of different quality and security: simple, advanced, and qualified. In most European states the qualified electronic signature is legally admissible in legal documents and contracts. Digital rights management and watermarking are used in content syndication and media asset management, to manage and secure intellectual property rights and copyrights. Digital rights management works with techniques like electronic watermarks that are integrated directly into the file, and seeks to protect usage rights and protect content
19
Enterprise content management that is published on the Internet. Distribution All of the above technologies serve to provide an ECM's contents to users by various routes, in a controlled and user-oriented manner. These can be active components such as e-mail, data media, memos, and passive publication on websites and portals where users can get the information themselves. Possible output and distribution media include: The Internet extranets intranets E-business portals Employee portals E-mail Fax Data transfer by EDI, XML or other formats Mobile devices, like mobile phones, PDAs, and others Data media like CDs and DVDs
20
Digital TV and other multimedia services Paper. The various Deliver components provide information to users in the best way for the given application, while controlling its use as far as possible.
ECM market development

Vendors recognized by the 2010 Gartner ECM Magic Quadrant include Adobe, Alfresco, Autonomy, EMC, Ever Team, Fabasoft, HP, Hyland Software, IBM, Laserfiche, Microsoft, Newgen Software Technologies, Objective Corporation, Open Text, Oracle, Perceptive Software, Saperion, Siav, SpringCM, SunGard, Systemware, Xerox and Xythos Software[7] Prior to 2003, the ECM market was dominated by a number of medium-sized independent vendors that fell into two categories: those who had originated as Document Management companies (Advanced Processing & Imaging, Documentum, Laserfiche, FileNet, OpenText, Db technology) and had begun adding on management of other enterprise content, and those who had started as Web Content Management providers (Interwoven, Vignette, Stellent) and had begun trying to branch out into managing other types of content such as business documents and rich media. Larger vendors, such as IBM and Oracle, also had offerings in this space, and the market share remained largely fragmented. In 2002, Documentum had added collaboration capabilities with its acquisition of eRoom while Interwoven and Vignette countered with their respective acquisitions of iManage and Intraspect. Similarly, Documentum purchased Bulldog for its Digital Asset Management (DAM) capabilities while Interwoven and OpenText countered with acquisitions of MediaBin and Artesia. OpenText also acquired European companies IXOS and Red Dot to shore up its software portfolio. In October 2003, EMC Corporation acquired Documentum. Soon EMC's primary competitors in the database space responded as IBM purchased FileNet and Oracle purchased Stellent in 2006. OpenText also purchased Hummingbird in 2006. Hewlett-Packard (HP) entered the ECM space with its acquisition of Australian company Tower Software in 2008. In March 2009, Autonomy purchased Interwoven, in July 2009 Open Text acquired Vignette, and in February, 2011 OpenText acquired MetaStorm. Most recently, OpenText acquired Global 360 in July 2011[8] , and HP made an agreement to purchase Autonomy in August 2011.[9] In April 2007, independent analyst firm CMS Watch noted that "some of the biggest names in this business are undergoing substantial transformation that will lead to shifting road maps and product sets over the next few
Enterprise content management years".[10] In addition, 2007 saw the emergence of open-source options for ECM supplied by Nuxeo and Alfresco, along with a Software-as-a-Service offering from Spring CM. In 2008, Sense/Net released Sense/Net 6.0, an open source ECM and EPS solution. [11] There are a number of software companies that have sprung up to develop applications to complement ECM with specific functions and features. There are companies that provide third party document and image viewers such as LEAD Technologies, MS Technology, and Accusoft. There are companies that provide workflows such as Office Gemini, SpringCM, and docAssist. There are also several companies that provide plugins for ECMs. The Web 2.0 wave brought new players to the market with strength in web-based delivery. Koral, Box.net, and EchoSign, all available on the Salesforce.com AppExchange platform, are representative of this trend.[12] Web 2.0 was also instrumental in bringing Cygnet ECM, an entirely web-based ECM product, to the market.[13] Enterprises are increasingly implementing analytics tools to help present targeted content to users in order to improve productivity, sales and user engagement. This has been referred to by some as "web engagement management". [14]
[15]
21
Gartner estimated that the ECM market was worth approximately $3.3 billion in 2008; this was expected to grow at a compound annual growth rate of 9.5 percent through 2013. After a plethora of industry consolidation, only three or four major companies are left in this space, and the industry as a whole is undergoing a significant transformation as Microsoft commoditizes content-management components.[7] According to Gartner's 2009 report, 75 percent of Global 2000 companies were highly likely to have a desktop-focused, process-focused content management implementation by 2008, and ECM would continue to absorb other technologies, such as digital asset management and e-mail management. Gartner also predicted that there will be further market consolidation, acquisition, and separation of vendors into platform and solution providers.[7] Currently, enterprise information management (EIM) is gaining more interest from organizations trying to approach information management (whether structured or unstructured) from an enterprise perspective. EIM combines ECM and business intelligence. Cloud content management is emerging as a web-based alternative, combining the content focus of ECM with the collaborative elements of social business software.
Footnotes
[1] "What is Enterprise Content Management (ECM)?" (http:/ / www. aiim. org/ What-is-ECM-Enterprise-Content-Management. aspx). AIIM. Association for Information and Image Management. . Retrieved September 20, 2010. [2] Microsoft launched its ECM strategy with MOSS 2007; Oracle, with Oracle 10g and the acquisition of Stellent, both in late 2006. [3] Evolving Electronic Document Management Solutions: The Doculabs Report, Third Edition. Chicago: Doculabs, 2002. [4] Ulrich Kampffmeyer, "ECM Herrscher ber Informationen". ComputerWoche, CW-exktraKT, Munich, September 24th, 2001. [5] Trends in Records, Document and Enterprise Content Management. Whitepaper. S.E.R. conference, Visegrd, September 28th, 2004 PDF (http:/ / www. project-consult. net/ Files/ ECM_Handout_english_SER. pdf) original source of this Wikipedia article by the German consulting company Project Consult Unternehmensberatung [6] Kampffmeyer, Ulrich (2006). "ECM: Enterprise Content Management" (http:/ / www. project-consult. net/ Files/ ECM_White Paper_kff_2006. pdf) (in English, French, and German). DMS EXPO 2006, Kln. Hamburg: PROJECT CONSULT. ISBN978-3-936534-09-8. . Retrieved September 20, 2010. [7] Bell, Toby; Shegda, Karen M.; Gilbert, Mark R.; Chin, Kenneth (November 16, 2010). "Magic Quadrant for Enterprise Content Management" (http:/ / www. gartner. com/ technology/ media-products/ reprints/ microsoft/ vol14/ article8/ article8. html). Gartner.com. Gartner. . Retrieved August 25, 2011. [8] "OpenText profiting from acquisitions as it extends reach" (http:/ / www. therecord. com/ news/ business/ article/ 562424--opentext-profiting-from-acquisitions-as-it-extends-reach). July 13, 2011. . Retrieved August 25, 2011. [9] "HP to Acquire Leading Enterprise Information Management Software Company Autonomy Corporation plc" (http:/ / www. hp. com/ hpinfo/ newsroom/ press/ 2011/ 110818xc. html). August 18, 2011. . Retrieved August 25, 2011. [10] Manoj Jasra (April 17, 2007). "CMS Watch Releases Enterprise CMS Comparison Report" (http:/ / www. webanalyticsworld. net/ 2007/ 04/ cms-watch-releases-enterprise-cms. html). . Retrieved September 21, 2010. [11] Open Source ECM continues to grow (http:/ / www. cmswatch. com/ Trends/ 996-Open-Source-ECM-continues-to-grow)

[12] Ismael Ghalimi (2007-04-10). "First Koral, then ThinkFree and EchoSign" (http:/ / itredux. com/ blog/ 2007/ 04/ 10/ first-koral-then-thinkfree-and-echosign/ ). ITRedux. . [13] DM, Rank and file: A case study. Retrieved 10 November 2010 from http:/ / www. document-manager. com/ articles/ reviews. asp?a_id=336 [14] Brice Dunwoodie, "What is Web Engagement Management (WEM)?" (http:/ / www. cmswire. com/ cms/ web-engagement/ what-is-web-engagement-management-wem-007400. php), CMSWire, 2010-05-05 [15] Elcom, "Web Engagement Management (WEM)" (http:/ / www. elcom. com. au/ Products/ Web-Engagement-Management), Elcom, 2010-11-22
22
Bibliography
Kampffmeyer, Ulrich (2006). "ECM: Enterprise Content Management" (http://www.project-consult.net/Files/ ECM_White Paper_kff_2006.pdf) (in English, French, and German). DMS EXPO 2006, Kln. Hamburg: PROJECT CONSULT. ISBN978-3-936534-09-8. Retrieved September 20, 2010. Fray, Michael (2008). "ECM - Enterprise Content Management" (http://www.globe.dk/alle/ 314-ecm---enterprise-content-management-9788779008311-9788779008311.html) (in Danish). Denmark: Forlaget Globe. ISBN978-8-779008-31-1. Retrieved May 23, 2011.
References
Content management
Content management, or CM, is the set of processes and technologies that support the collection, managing, and publishing of information in any form or medium. In recent times this information is typically referred to as content or, to be precise, digital content. Digital content may take the form of text, such as documents, multimedia files, such as audio or video files, or any other file type which follows a content lifecycle which requires management.
The process of content management

Content management practices and goals vary by mission and by organizational governance structure. News organizations, e-commerce websites, and educational institutions all use content management, but in different ways. This leads to differences in terminology and in the names and number of steps in the process. For example, an instance of digital content is created by one or more authors. Over time that content may be edited. One or more individuals may provide some editorial oversight thereby approving the content for publication. Publishing may take many forms. Publishing may be the act of pushing content out to others, or simply granting digital access rights to certain content to a particular person or group of persons. Later that content may be superseded by another form of content and thus retired or removed from use. Content management is an inherently collaborative process. It often consists of the following basic roles and responsibilities: Creator - responsible for creating and editing content. Editor - responsible for tuning the content message and the style of delivery, including translation and localization. Publisher - responsible for releasing the content for use. Administrator - responsible for managing access permissions to folders and files, usually accomplished by assigning access rights to user groups or roles. Admins may also assist and support users in various ways. Consumer, viewer or guest- the person who reads or otherwise takes in content after it is published or shared. A critical aspect of content management is the ability to manage versions of content as it evolves (see also version control). Authors and editors often need to restore older versions of edited products due to a process failure or an
Content management undesirable series of edits. Another equally important aspect of content management involves the creation, maintenance, and application of review standards. Each member of the content creation and review process has a unique role and set of responsibilities in the development and/or publication of the content. Each review team member requires clear and concise review standards which must be maintained on an ongoing basis to ensure the long-term consistency and health of the knowledge base. A content management system is a set of automated processes that may support the following features: Import and creation of documents and multimedia material. Identification of all key users and their roles. The ability to assign roles and responsibilities to different instances of content categories or types. Definition of workflow tasks often coupled with messaging so that content managers are alerted to changes in content. The ability to track and manage multiple versions of a single instance of content. The ability to publish the content to a repository to support access to the content. Increasingly, the repository is an inherent part of the system, and incorporates enterprise search and retrieval. Content management systems take the following forms: a web content management system is software for web site management - which is often what is implicitly meant by this term the work of a newspaper editorial staff organization a workflow for article publication a document management system a single source content management system - where content is stored in chunks within a relational database Content management expert, Marc Feldman defines three primary content management governance structures -localized, centralized, and federated: each having its unique strengths and weaknesses.[1] Localized Governance: By putting control in the hands of those closest to the content, the context experts, localized governance models empower and unleash creativity. These benefits come, however, at the cost of a partial-to-total loss of managerial control and oversight. Centralized Governance: When the levers of control are strongly centralized, content management systems are capable of delivering an exceptionally clear and unified brand message. Moreover, centralized content management governance structures allow for a large number of cost-savings opportunities in large enterprises, realized, for example, (1) the avoidance of duplicated efforts in creating, editing, formatting, repurposing and archiving content, (2) through process management and the streamlining of all content related labor, and/or (3) through an orderly deployment or updating of the content management system. Federated Governance: Federated governance models potentially realize the benefits of both localized and centralized control while avoiding the weaknesses of both. While content management software systems are inherently structured to enable federated governance models, realizing these benefits can be difficult because it requires, for example, negotiating the boundaries of control boundaries with local managers and content creators. In the case of larger enterprises, in particular, the failure to fully implement or realize a federated governance structure equates to a failure to realize the full return-on-investment and cost-savings that content management systems enable.
23
Content management
24
Implementation
Content management implementations must be able to manage content distributions and digital rights in content life cycle. Content management systems are usually involved with Digital Rights Management in order to control user access and digital rights. In this step the read only structures of Digital Rights Management Systems force some limitations on Content Management implementations as they do not allow the protected contents to be changed in their life cycle. Creation of new contents using the managed(protected) ones is also another issue which will get the protected contents out of management controlling systems. There are a few Content Management implementations covering all these issues.
External links
Boiko, Bob (2004-11-26). Content Management Bible. Wiley. pp.1176. ISBN0764573713. Rockley, Ann (2002-10-27). Managing Enterprise Content: A Unified Content Strategy. New Riders Press. pp.592. ISBN0735713065. Hackos, JoAnn T. (2002-2-14). Content Management for Dynamic Web Delivery. Wiley. pp.432. ISBN0471085863. Glushko, Robert J.; Tim McGrath (2005). Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services. MIT Press. pp.728. ISBN0262572451. content manager informations [2]
References
[1] http:/ / www. clickz. com/ clickz/ column/ 1715089/ governance-issues-content-management [2] http:/ / www. content-manager. org/
Article Sources and Contributors
25
Article Sources and Contributors

Digital asset management Source: http://en.wikipedia.org/w/index.php?oldid=455047464 Contributors: Adoniscik, Anaines0210, Andrew Kelly, Aqeelbilal, Bigmartyn, Bigrich73, Bmartel, Bobo192, BradyGirl, Brightinteractive, Bsauls, Bsheeran, Calltech, Chaser, Cicada, Connectionfailure, Craigb81, Craigwb, Crossmr, Cybercobra, Daminfoguy, Dancter, Danhuby, Darigan, Daydream rw, Debu@emetaworks, Dhapp, Dialectric, Drvannie, Ecms-guru, Edward, Efe, Ehegdahl, ErikWarmelink, Fotofan, G vom s, Gcm, Glamptey, Glux, Gregbedford, Heron, Hkhorlos, HumanCyclist, Intgr, JFreeman, Jaeger5432, Jamelan, Jathey, JimDelRossi, Jlegue, Joe Decker, JonHarder, Jordanrgray, Julieriley, Juliewh, KJGD7424, Knightfilm, Kuru, Leolaursen, LilHelpa, Louistasse, Lucyhill, MER-C, Madbuy, Mahalie, Mallanox, Marklclemente, Maurreen, Mazi, Mgonnering, Mike Linksvayer, Mrdave1981, Mrecomm101, Mydogategodshat, Nsarwan, Ohnoitsjamie, Oicumayberight, Orangemike, Orchcorp, Peterkrogh, Plingsby, Rapsar, Ronz, Ruud Koot, Sampei73, Schanul, Scottc12, Shoeboxes, Shourick, Skapur, Stephenb, Swish7, Sworthy, Sworthy246, Tclaxton, Thingg, Titan1000, Venache, Vivicia, Volphy, WaldoJ, Webtechscout, Winterst, Wipe, Wittylama, Zingari, 243 anonymous edits Digital asset Source: http://en.wikipedia.org/w/index.php?oldid=444709562 Contributors: Biscuittin, Buridan, CTZMSC3, Dchuckable, Drcindylarson, Drvannie, Jmchuff, Kappa, Malcolma, Mattgirling, Nurg, Oicumayberight, Radagast83, Remuel, Rjwilmsi, Severo, TBarregren, Taelus, Winterst, Woohookitty, 8 anonymous edits Web content management system Source: http://en.wikipedia.org/w/index.php?oldid=450828839 Contributors: 16x9, 2mcm, Adamkessler, Akfick, Alansohn, Alexeliades, Alirobe, Allforhim23, Amalve, American Eagle, Anamanfan, Andypandy.UK, Anna Lincoln, Aschrage, AtlanticWebfitters, Avbidder, Bazzargh, Beetstra, Belmond, BenSwivel, Bkraft, Boyd Reimer, Bozena83, Brmwk, CMSnerd, Can't sleep, clown will eat me, Carrielle, Celestianpower, Chatfecter, Chouchin11, Cirrus Editor, Civinext, Corti, Craigb81, Csumner, D2s, Dan vella, Daniel Callejas Sevilla, Danim, David, David0811, Dawnseeker2000, Disambigutron, Dkcreatto, Dlohcierekim, Drew R. Smith, Dukespukem, Dyun, Ebbrock, Ehn, Emurphy42, Epbr123, Excirial, Farkasattila, Fishwristwatch, G-salwiki, Galapagos999, Gdruce, Giaguara, Gogo Dodo, Graham87, Grepkapil, Grey Shadow, Greyskinnedboy, Grutness, Hayk, HenrySchreinerIII, J04n, JLaTondre, Jafreund, Jamestochter, JanHart, Jdlh, Jhalbrecht, Johnmunsch, Jon-ecm, Kablerc, Kozuch, Kuru, Kyle.Lindsay, LAAFan, Lamuk69, Lancedknight, Lethanek93, Leujohn, Liempt, Linclark, Linforest, Longhair, Lou Sander, MER-C, MainFrame, Malcolmxl5, Mamma duck, Martarius, Masonben, Matt Schwartz, Mdd, Meskalyto, Michael Hardy, Michfan2123, Mike Rosoft, Mikelowndes, MiltonRapport, Mion, Mitaphane, Mkamensek, Mrzaius, Mud4t, Mulad, Mydoggnarley, NEtechno, Nekohakase, Nevst, Ngroot, Nnehaa, Nurg, Octahedron80, OhSqueezy, Ohnoitsjamie, Oicumayberight, Omegatron, Oo64eva, Optikos, Paquettg, Paulmnguyen, Peachey88, PerlDreamer, Petri Krohn, Philip Trueman, Piano non troppo, Prodoc, R.c.mcd, RAM, RAult, RainbowOfLight, Rasmus Faber, RedLavaLamp, Rich.C07, Rio517, Riyajshaikh09, Rjwilmsi, Roccobarbi, Rodii, Ronz, S.K., SFElisaW, SacredCheese, Sadhya, Samberesford, Ses4j, Sgottlieb, Shadowjams, Shell Kinney, Silvermask007, Sklapro, Smb1001, Smjg, Smyth, StanfordProgrammer, Steinsky, Stephen, Sunil1234b, Sunsaturn, TAG2010, Tbyrne, Terrym, TheParanoidOne, Thefeed32x, Themfromspace, Toddst1, Tranquilflames, Uncle Milty, Vardhanw, Vaughanreed, Venache, Versageek, Vl'hurg, Vrenator, Webmanagement, Webmistress25, Wikibofh, WorldlyWebster, Wosne, Xionbox, Yansky, Yueni, Zhoukaimagic, Zzyzx11, 365 anonymous edits Enterprise content management Source: http://en.wikipedia.org/w/index.php?oldid=454524775 Contributors: 16x9, Aaronbrick, Accounting4Taste, Alanps, AlphaMatrix, Alusayman, Andrewpmk, Andy Dingley, Ankursen, Anna Lincoln, Antonrojo, Archite, Ash H., Ashleymayer22, Asocall, Avicennasis, Barek, Bazzargh, Bctg23, BenjaminNeale, Bloodshedder, Bobrayner, Bonadea, Cameron Scott, Can't sleep, clown will eat me, CanisRufus, Capricorn42, Car031, Casper2k3, CatSchley, Catfoo, Ceefour, Ceptorial, Chaojoker, Chophe, Chris the speller, Clinton0, Cmg07068, Cmosso, Cmstester, Colonies Chris, Correogsk, CraigBailey, Craigb81, Crusio, Cynical, DDerby, DabMachine, Danielchalef, Danieljames, Danim, DaveJohnsonSD, Dawnseeker2000, Deejmer, Docmgmt, Dougsey, Dragan Varagic, Dyun, ECM Dan, ECMExpert, ECMgirl, Ecm2006, Ecmguru, Ecmondemand, Edward, Elagatis, Eloi.gerard, EncMstr, EoGuy, Epbr123, Equendil, Evolve2k, Farkasattila, Favonian, Fdigital2011, Fmccown, Fotofan, Fratrep, Fred Bradstadt, Funandtrvl, F, Gary.goldsmith, Gdm, Gedman, Gioto, GoodDamon, GraemeL, Grafen, Gvanrensburg, Gwern, Haakon, HaloProcess, Harvey the rabbit, Hebsgaard, Herbythyme, Hessamnia, Ian Pitchford, Info.abstracta, Iridescent, J.delanoy, J04n, JHunterJ, JLaTondre, Jaeger5432, Jauerback, Jmancini77, John Seward, Johnkmetha, Johntex, JonHarder, Jonverve, Joshuaklind, Jpbowen, Jsloey, Kaitlin510, Katiem222, Kevinxml007, Kff, Klsmith88, Kraftlos, Kuru, Kyle.Lindsay, Lambiam, Lee1872, Lfstevens, LilHelpa, Lkinkade, Longshot14, Luna Santin, Macwhiz, Maglish, Mahanchian, Manwichosu, MarkPDF, Marqoz, Mathisfenne, Matslats, Mattousai, MaxHund, Mbrousseau1, Merana, MichaelFrayDK, Mikelawrence1, Mild Bill Hiccup, Miyagawa, Mkmcconn, Mkuehn10, Monirugg, MrOllie, Muhandes, Mushroom, Napwilson, NawlinWiki, Nbvsrk, Ncw0617, Nick Number, Nmaquaire, Noq, Nurg, OBJECT1VE*CORPORATION, Ohnoitsjamie, Oicumayberight, OnePt618, Opagecrtr, Palapa, PaulHanson, Paulawalka, Pbaan, Peak, Pearle, Petrb, Pganza, Pippa007, PowerFlower, PriscillaBerry, Puneeta prose, Ray3055, RedLavaLamp, ReynoldLeming, Rich Farmbrough, Rjwilmsi, Rob smith 06, Rodamaker, Rogerbowne, Ronz, Rosiestep, Roystonea, Rwwww, S.K., Satori Son, Sebastian Pikur, Sharnden, Signalhead, Sindri, SiobhanHansa, Skellison, Spliffy, Sprmw7, Squids and Chips, StevenBirnam, Storkk, Sunsaturn, Sworthy246, Tbyrne, The Thing That Should Not Be, Thehelpfulone, Therealpowerflower, Thingg, Thumperward, Tide rolls, Timc, Tjcoppet, TommyG, Trust2520, Ttallaksen, Ubiscope, UnitedStatesian, Van der Hoorn, Venache, Vendettax, VernoWhitney, Versageek, Vikramsetia, Vivicia, Voidxor, Volphy, Walkingbeard, Webmistress25, Welsh, Winterst, Wyatt Riot, Ytee25, ZimZalaBim, 469 anonymous edits Content management Source: http://en.wikipedia.org/w/index.php?oldid=452107552 Contributors: Adjamir, Anoopa, AspectusPR, Bonadea, Bongoramsey, Boworr, Chuckrussell, Cirrus Editor, Cjacobs001, ClementSeveillac, Cmdrjameson, DOSGuy, Davidp, DigitalJanitor, Ebbrock, Ehheh, El C, Eloquence, Ericjs, GHusman, GMGershon, Gifford Watkins, Goingin, Guyzero, Harryboyles, Hu12, IW.HG, Imtheyaz, Iness it, JonHarder, Jredmond, Jrgetsin, Keegscee, Kevin, Kff, Kgrr, Kieff, Kingpin13, Lcarscad, LeeHunter, Lucky 6.9, Lujan3011, Luna Santin, Malcolmxl5, Martijn faassen, Mathias-S, Mehrotra-rahul, Michal Jurosz, Mike Rosoft, Monado, My76Strat, Mydogategodshat, Neocodesoftware, Nick, Nixdorf, Nurg, Objectify, Ohnoitsjamie, Oicumayberight, OntarioCanada01234, Pdm1, PeterBrooks, Petrias, Phil reagan, PowerFlower, Ragnarev, Rasmus Faber, Requestion, ReynoldLeming, Rlliii, Rodii, Ronz, Rsocol, Ruv, Securiger, Semifreddo, Skqi, SlimVirgin, Slysplace, Suffusion of Yellow, Taholder, Veinor, Venache, Versageek, Wiki alf, Wookipedian, Zingari, Zzuuzz, , 182 anonymous edits
Image Sources, Licenses and Contributors
26
License
Creative Commons Attribution-Share Alike 3.0 Unported //creativecommons.org/licenses/by-sa/3.0/

Content Management

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Content Management

Transféré par

Droits d'auteur :

Formats disponibles

Content Management

Digital asset management

Digital asset management

Digital asset management

Types of digital asset management systems

Digital asset management

Digital learning assets

Digital asset materials.

Web content management system

Web content management system

Online processing (called "frying" systems)

Web content management system

Enterprise content management

Enterprise content management

Todays Adoption Drivers

Enterprise content management

ECM market development

Enterprise content management

The process of content management

Article Sources and Contributors

Article Sources and Contributors

Image Sources, Licenses and Contributors

Vous aimerez peut-être aussi