After a great deal of hard work by some very dedicated and very bright people at GimmalSoft, the US Department of Defense has officially certified the GimmalSoft Compliance Suite for SharePoint 2010 against the US DoD 5015.2 Records Management Application Standard.

As I’ve noted on this blog before, I am a member of the team that produced this product.  I am extremely proud of this solution and I’m very excited about its future.  Having said that, I don’t want to jeopardize the independence of this blog by excessively reporting on this one particular solution.  If you are interested in learning more about the Compliance Suite, I would be happy to talk to you offline or you can contact GimmalSoft directly through their website.

Applying  a Hold in SharePoint 2010

There are a number of ways to apply holds in SharePoint 2010.  We’ll try to address each of them before this series is through, but I’ll show you the ‘standard’ (manual) process here.

(Just a note.  Our friends at Microsoft kinda dropped the ball on applying holds in one respect.  The idea that you would have to apply a hold to each individual record you want to preserve really doesn’t make a lot of sense.  Discovery orders can produce thousands of items that must be preserved.  Sometimes more.  There should really be a mechanism to apply holds to records aggregates – entire libraries, folders, etc. – along with a means to apply them to individual records.)      

To apply a hold, navigate to the record you wish to perserve and open its Compliance Details dialog box. 

In the Compliance Details dialog box click on ‘Add/Remove from hold’ and the ‘Item Hold Status’ window opens.

Select the ‘Add to a hold’ option and use the drop-down selection box to choose the relevant hold to apply to this record.  The ‘Comments’ field is not required, however, I strongly encourage its use.  For litigation purposes, it is a good idea to explain the purpose for the hold and add any other information that might provide value in a legal or regulatory investigation.

Click on ‘Save‘ and the hold will be applied.  The record cannot be deleted and will not be destroyed through its Information Management Policy until the new hold is removed.

It also worth noting that SharePoint 2010 allows you to apply multiple holds to the same record.  Sadly, given our litigious society, multiple holds on the same record is not terribly uncommon.  If a record has multiple holds applied to it, SharePoint 2010 will not allow the record to be destroyed until all the holds are removed.

Anyone who has followed this blog for any length of time knows I work for Gimmal, a consulting, integration and solutions firm based out of Houston, Texas.  I joined Gimmal over three years ago because I was convinced they were positioned to become the leading SharePoint records and information management consultancy worldwide and I wanted to be a part of it.

That said, I make every effort to keep this blog independent of my professional career.  I have even posted some very positive articles about organizations who could be considered direct competitors to Gimmal.  On the other hand, if I am aware of any information I think our readers will find useful, I am going to post it - even if it could be interpreted as showing partiality toward my employer. 

GimmalSoft’s announcement earlier this week of their new partnership with Microsoft and Iron Mountain is one of those cases.  The three companies have teamed up to develop a SharePoint 2010 based solution for managing both electronic and physical records.  This solution has the potential to be a game changing development for true enterprise content and records management, allowing companies to manage all their  content across the organization more consistently and efficiently than ever before.  Here’s a link to their recent joint press release.  Check it out.

Creating a Hold

Creating a hold in SharePoint 2010 is a simple process and hasn’t changed much from MOSS 07.  Login to SharePoint as a user with administrator privileges.  Click on Site Actions and select Site Settings.  From the ‘Hold and eDiscovery’ category, click on ‘Holds’. 

Click on ‘Add new item’ and the ‘Holds – New Item’ dialog opens.

Enter a Title for the hold.  (This is the only required field.)  The Title should be brief, but connect the hold to the reason for preserving the records.

The Description should expand on the information provided in the Title.  If your organization is in a particularly litigious industry (and who’s isn’t?), the Description field is a good place to clarify some of the legal issues that might be relevant to the reason for applying the hold. 

For Managed By, enter a user or group responsible for managing the hold.

Click on ‘Save’ and the new hold is created and available to be applied to records.

The next post in this series will describe how holds are applied to records.

A number of the major ECRM vendors – OK, I’ll be honest, all of the major ECRM vendors – have worked tirelessly to downplay the records management functionality provided in SharePoint. I know this to be true because I have worked for some of these companies. For many of them this has become a matter of survival. They recognize that their solutions can no longer openly compete with SharePoint in the traditional ‘document management’ space, so they desperately cling to the notion that SharePoint is incapable of managing records and only their solution can meet the customer’s records management needs. (And, their marketing message continues, ‘if you are going to buy our product to manage the records repository, you might as well implement our entire solution for just a few dollars more’.)

For some ECRM vendors, this is the last compelling argument their sales staffs can make. Unfortunately for them, it is simply untrue. Mike Alsup, my boss at Gimmal Group, has written a terrific article on the AIIM SharePoint Expert blog that details the myths perpetuated about SharePoint records management and explains why each of them is wrong. If you are revaluating your organization’s records management strategy or you are considering which ECRM solution would best suit your records management needs, I would highly encourage you to read Mike’s article.

« Previous PageNext Page »

Follow

Get every new post delivered to your Inbox.

Join 35 other followers