Support for CMIS 1.0 Committee Draft 04 Specification
CMIS (Content Management Interoperability Services) is the upcoming specification from OASIS for content management interoperability. Recently, CMIS entered the public review phase with the latest version CMIS 1.0 Committee Draft 04. It is expected that CMIS will be released as an OASIS standard, CMIS 1.0, in early 2010.
In line with CMIS public review, Alfresco Community Edition 3.2r2 introduces support for CMIS 1.0 Committee Draft 04, providing an implementation of:
RESTful AtomPub Binding
Web Services Binding
CMIS sql-like Query Language
Apache Chemistry TCK
Abdera CMIS Extension
The previous Alfresco Community Edition 3.2r release provided support for CMIS 0.61. The CMIS specification has evolved since that time featuring the following changes between 0.61 and 0.62, 0.62 and 0.7, and 0.7 and 1.0cd04. Alfresco's CMIS implementation has tracked the CMIS specification and features the following implementation changes. The result is support for the following services in both RESTful AtomPub and Web Services bindings:
where <host> is the machine name (or localhost if accessing locally) and port is the port number (8080 by default) where Alfresco is installed.
For further information on Alfresco's CMIS Implementation, refer to CMIS.
The Alfresco 3.2r2 Community Release includes a DoD 5015.2 certified Records Management module. This enables you to create a Records Management site (RM) alongside other collaboration sites you may have, and manage records through the Share user interface.
In designing the Alfresco Records Management system, we aimed to achieve some key goals driven and informed by current records management practice and solutions. In looking at currently available products, they have typically been expensive to buy and implement, unfriendly and difficult to use, and in many cases disjointed from organizational requirements. This has resulted in systems which become the providence of the records management department and are used only to archive records.
The expense and complexity of such systems means that records management rarely extends out to the organizational departments where it needs to be. Leading on from this our key design goals were;
Simplicity: of use for occasional users
Reach: all users in an organization
Cost: deliver the first open source records management solution
Implementation: minimize the desktop footprint
Future proofing: provide a potential model and basis for future standards work