Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.

The CORSET Content Management Design Pattern

Over the past year, Zia has seen a noticeable uptick in engagements that utilize Content Management Interoperability Services (CMIS) to solve important business problems.  As a systems integrator that is heavily invested in open source and open standards, this is extremely exciting to us.

As with other technology standards, we have also run into a few challenges implementing capabilities over CMIS that we have resolved using a common architectural pattern.

Imagine you need to solve one of the following problems from a client system that is connected to a content management system (CMS) using one of the well-defined CMIS bindings (REST/AtomPub, SOAP or Browser):

  1. Email documents from the CMS to people defined by the sender.
  2. Allow users to create/find/update/delete users and/or groups in the content management system (and possibly an external directory that is synchronizing with the CMS).
  3. Initiate or participate in workflows provided by the CMS.
  4. When creating certain folders, we want template content hierarchies to be instantiated automatically.
  5. Send notifications when new content is created or when content changes states (as indicated by metadata on the content).
  6. Augment/enhance metadata for new or updated documents by querying external systems with content and/or metadata.


Investigating Alfresco’s SOLR Indexes and Resolving Issues

Having troubles with your Alfresco SOLR indexes? If so, this blog post might be able to help provide some helpful tips on how to identify problems with your Solr indexes and how to resolve them.  

The following content is only available to subscribers.

Sign up now!