Just attended an excellent session called ECM for the Masses by Microsoft. They are taking a very pragmatic approach to ECM / Records Management now, understanding that tired options of "more money," "more complexity," "more features" or a magician aren't working in the ECM space — 50% to 60% of ECM projects are failing!
Instead, Microsoft spoke to the need for a "payback for participation" to engage users (a return of two or three to one for the time invested seems to be the target).
Notwithstanding the fact that (according to Microsoft) an approach of "more features" has not worked, Microsoft has added the following new features:
- Content Organizer — this is prevalent across the system and expands on the MOSS 2007 Records Center Routing concept. This allows document / record routing across the platform. End-users can fire content into a "Drop-off library," and it is organized (based on a pre-determined collection of metadata or tagging-driven rules) automatically into the correct location.
- Taxonomy-driven Document Center navigation — left-hand navigation can be automatically built based on tagging of metadata in the documents contained in the library.
- Records Management can now be "in archive" like the MOSS 2007 Records Center, "in place" (documents are declared as a record and the new record sits in the document library), or a mixture of the two. The presenter pointed out that in an eDiscovery scenario, there is no distinction made between documents or records (or notes, emails, tags, blogs or wikis for that matter) as EVERYTHING can be eDiscovered now. Does it really still make sense to hive-off records into a separate archive?
- Unique (and easy to access) Document IDs across the platform.
Microsoft has released File Server Resource Manager. This allows the interrogation of a file server, some (considerable amount of) setup and configuration and then automated migration of select files to SharePoint. Files that are moved out of filesharing are replaced with a link in the original folder that points to the file now residing in SharePoint.