Archive for October, 2009|Monthly archive page

SharePoint Conference: Interesting stuff on ECM

The first day of the SharePoint Conference in Las Vegas offered a lot of interesting stuff on Enterprise Content Management in SharePoint 2010. With SharePoint 2010 a lot of capabilities are introduced that finally make SharePoint a serious alternative for true Enterprise Content Management.

I’ll try to blog about all this exciting new stuff later on, but these are the highlights I especially like:

  • With Managed Metadata Services SharePoint 2010 supports content types and taxonomies, not only across sites or site collections but also across server farms. The top-down taxonomy and bottoms-up social tagging (or folksonomy) can be combined to help improve search, navigation and people connections. Also taxonomies can multilingual
  • In SharePoint 2010 ‘Document Sets offer a way to manage a collection of documents as a single object for workflow, metadata, etc. Finally there’s a powerful out of the box solution to work with dossiers within SharePoint.
  • Records management is seriously improved and SharePoint 2010 will be a serious alternative for records management. These new records management features include location-based file plans, multi-stage dispositions, in-place records and e-discovery. Especially the in-place records management is great, because now you can leave the content item in its original context (with discussions, all the metadata en workflow history) etc. So now declaring for example SharePoint blogs or wiki-pages as records is very simple as well.
  • There will be an out of the box solution for managing file share content from within SharePoint that enables you to store metadata of a document in SharePoint and using workflow, etc.  while the original document stays on the file share. These capabilities also enables easier migration from file share to SharePoint and off course the coexistence of SharePoint and file shares.
  • Each document in SharePoint gets a unique ID that isn’t changed by renaming the document or moving it within the farm.
  • Document libraries will scale to tens of millions and archives to hundreds of millions of documents. Combined with out of the box metadata driven navigation users can go quickly to the content they’re looking for.This is key for high-end document and records management.
  • There’s also a lot of interesting stuff on enterprise search on which I’ll blog later on.
  • To be honest I expected a bit more of the improvements in Web Content Management. Although there are some important improvements, I was hoping for a robust solution for multi channeling, but unfortunately that’s missing. Nevertheless, there’s also some interesting new stuff like the new browser ribbon to speed site customization, content authoring and publishing tasks; improved digital asset management features like thumbnails, metadata and ratings for images as well as video streaming from SharePoint; Improved accessibility; Improved content deployment robustness from authoring to production for larger scale sites.

Some others are blogging from the SharePoint Conference as well, like:

Java specifications most heared about in content management

Last week CMS Watch analist Adriaan Bloem published a cheat sheet with the four Java Specification Requests (JSR) most heared about in content management, a useful list:

  • JSR-168, the Java Portlet Specification. This is the standard for the relation between a portlet container (portal software) and the portlets it can display. In theory, JSR-168 compliant portlets can be displayed in any JSR-168 compliant portal.
  • JSR-286, version 2.0 of the same specification (with several improvements, e.g. the standardization of how portlets communicate with each other).
  • JSR-170, the Content Repository API for Java. This is the definition of an API to access content repositories. Also known as JCR (the Java Content Repository). To confuse matters more, the standard only describes the API, but “JCR” is commonly used to refer to actual software. Such as Apache Jackrabbit, the JSR-170 reference implementation.
  • JSR-283, version 2.0 of the same specification (which adds several functions the original specification was lacking, such as improved versioning).

Alfresco first DoD 5015.02 compliant open source ECM product

CMS Wire reports Alfresco managed to become the first open source DoD 5015.02 approved records management solution:

Rather recently we learned that Alfresco has now become the first open source product to demonstrate compliance with the DoD 5015.02 STD spec.

Alfresco was aiming to win the DoD stamp of approval by September. The date apparently slipped a bit, as these things tend to. But back slapping time has arrived and sales force can stop chomping at the bit. Additionally, a more formal announcement is, we are assuming, just around the bend.

Alfresco’s chances for compliance were enhanced by an update in August that delivered a new records management functionality, included reporting tools and query capabilities.