Mercy built Baggot Street using open-source technology and had previously selected Drupal as its web content system. Drupal provided a high-end framework with extensible functionalities and was satisfactory until Mercy needed to migrate documents into Baggot Street. Out of the box, Drupal didn't provide a document management solution flexible enough to meet Mercy's business requirements.
In need of a content repository, Mercy compared SharePoint and Hyland's Alfresco platform, evaluating ease of integration, ability to support the enterprise, usability and cost. Mercy determined that Alfresco was the best document repository to serve as its backend content repository for all of its Drupal web properties.
Mercy worked with Alfresco partner Appnovation to leverage its Canopy solution, which provides a set of services and APIs used to accelerate the integration of Drupal and Alfresco in an enterprise environment. Canopy combines the flexibility of Drupal as a front-end web development platform with the power of Alfresco as an enterprise content management and workflow system.
The Appnovation team developed the foundation for Baggot Street, which required setting up an inventory of Canopy modules and CMIS integration points. Appnovation developed several custom REST-based web scripts to batch certain operations, serving as a bridge for synchronizing group nodes, group members, taxonomy terms and department/sub-department nodes between Drupal and Alfresco. As a result, content is able to be synchronized in real time.
To provide a faceted search on documents through Alfresco, Mercy embedded the Apache Solr module. For Apache Solr to index documents from Alfresco, the CMIS API was used to retrieve documents in Alfresco. Once the documents are available in Drupal, they are saved as an Alfresco document node and indexed by Apache Solr.
To provide users the ability to upload documents from Drupal to Alfresco, a CMIS API was created. Form documents required custom web scripts to initiate the workflow in Alfresco. Using CMIS to upload either document types triggers a workflow rule to establish the metadata. The reviewer can then specify multiple users to review, with the department head getting final approval. Once complete, the document can be published on the portal.