The Point Of The Content Interoperability Services (CMIS) Standard
It's not the first time we talk about CMIS as one of the most interesting features of Nuxeo about interoperability with other ECMs. For you to meet specific use cases where this feature may be of interest as important for an organization, here you leave a very enlightening presentation that Laurence Hart left on her blog some time ago.
I transcribe for use cases to have it even clearer. What follows is a literal translation of use cases that appear on Laurence's blog:
Repository to Repository (R2R): This occurs when content repositories need to talk directly with each other.
- Managing records in other repositories that are stored centrally. This is called Federated Records Management, although it is different from the Land Use Case, to be discussed later.
- Publication of contents of a repository to another. A common scenario is the publication of content from a collaborative systema / ECM directly to a WCM system for publishing on an Intranet / Extranet.Application to Repository (A2R): This occurs when an application that uses content is attached to a content repository to manage all content-related services.* Sharepoint as a front-end. If implemented, Sharepoint can become a front-end and any other repository can be used as back-end. In this way problems could be solved Sharepoint scalability without the user being affected.
* Collaborative systems. All Systems Enterprise 2.0, and current collaborative applications could use a robust backend to provide features such as the uniqueness of content and records management. This is the same as the previous example, but widespread.
* Business Software Applications. It could be a process manager (BPM), a manager of customer relations (CRM), or any type of application used by an organization, the content is fast becoming a large part of these systems. It is becoming critical to have a centralized place to manage the content and apply consistent rules.
* Vertical Applications that use Content (CEVASA). As discussed before, CMIS can make life easier for manufacturers of CEVA. Let the experts in each domain to build an application to the relevant industry and allow them to associate with a system to manage content. This frees the manufacturer from CEVA have to worry about the content or keep as many different interfaces. That means more money to invest in R & D in real functionality.
* Productivity applications. Why not link to Word, Excel, Open Office or any other type of application to a repository using CMIS? Seems like a good way to make a portable integration, similar to what was attempted with ODMA (provided by @ billtrippe via twitter on 8/17/09)Federated Repositories: This occurs when an application needs to talk to many different repositories using a single user interface.* Federated search. This basically means what you can see in the demo iECM. Someone could do a search in multiple repositories.
* Federation rather than migration. An application can interact with multiple repositories. Rather than migrate all content from an old repository immediately, you might have to interface with the old repository interaactuando until completely migrated or completely outdated. The application can store the new content in the new default repository.
As can be seen, the use cases are spectacular. In most cases we may find some need of the kind described in one or another point in the lifecycle of a document management platform.
Interoperability is made possible. Although much remains to be done. Soon we will give more news about the Java implementation of this specification, Apache Chemistry, as well as other existing implementations.
This post was previously posted by Daniel Téllez in our blog in spanish.