Records management in SharePoint 2010 – early thoughts

In SharePoint 2007 the records management functionality was very poorly thought through and consequently organisations were dependent on the ecosystem around SharePoint for help in either getting the records management functionality to work or in providing an alternative set of records management functionality so that records were managed outside of SharePoint.

The big question for SharePoint 2010 is to what extent will Microsoft provide records management functionality within the product that is coherent and robust enough for people to use without resort to the ecosystem around it?

SharePoint 2010 doesn’t go into beta test until next month. I am writing this post on the strength of the reports by bloggers of Microsoft’s presentations to the SharePoint 2009 Conference in Las Vegas last week – I haven’t seen the product itself .

Records management in SharePoint 2007

Let us start by reminding ourselves of the key problems with records management in SharePoint 2007:

  • to protect a document from deletion and amendment you needed to send it to a records library within a SharePoint records centre. In the records centre an administrator can set up records centre libraries to protect and apply retention rules to documents declared as records
  • you had to do an awful lot of work behind the scenes in order for a user to be able to right click on a document and send it to an appropriate records centre library. You would need to have set up a records centre library for that type of record; defined a content type that type of document; and specified a routing rule for the content type so that documents were routed to the appropriate records centre library
  • the records centre did not support a useable fileplan hierarchy. It did allow you to set up different records libraries inside the records centre, and each records centre could have a folder structure. However the folders themselves had no functionality. Records could not inherit metadata or rules from the folders. You could not route documents to a specific folder within a records library, only to the records library itself.

I know of no organisation that used the SharePoint 2007 records management functionality ‘out of the box’. The only book written about records management in SharePoint 2010 is a book about how to do custom development in order to adapt SharePoint for records management.

For a description of records management in SharePoint 2007 read these detailed blogposts from the Microsoft UK SharePoint team. Or read my evaluation of records management in SharePoint 2007.

The records management model in SharePoint 2010

The biggest claim made at Las Vegas for SharePoint 2010 is that it includes in-place records management functionality.

The use of the phrase ‘in-place records management’ is interesting because it is very close to the concept of Manage-in-place used by some of the big ECM system vendors (for example Autonomy/Meridio and Open Text) and by the ECM industry body AIIM.

Manage-in place as used by the ECM vendor community

Manage-in-place, as developed by the ECM community, involves:

  • keeping your records management classification (fileplan), retention rules, and access rules in one records management system
  • Setting up connectors from that records management system to the various environments in which colleagues collaborate (shared drives, SharePoint team sites, etc)
  • Using the records management system, to lock down, classify and apply retention and access rules to documents and information resources within the different systems that you set up connectors into, without moving the documents from their native system.

Manage-in-place is an acknowledgement that the attempt to persuade colleagues to keep all those documents/resources needed as records within one electronic document and records management system was doomed to fail. It is still in its infancy, and I have yet to find any advice on manage-in-place coming from any non-vendor sources. For example there is no advice emerging from the UK National Archives, which was the source of so much good advice on the traditional, pre-SharePoint 2007 EDRM system. Nor is there yet an established flag ship case study of manage-in-place for the records management community in the UK or world wide to discuss and learn from.

In-Place records management in SharePoint 2010

The In-Place records management capability for SharePoint 2010 appears to be more restricted in scope than manage-in-place. It appears that ‘In-Place records management’ simply means that a user can declare a document as a record within a team site, and it can be protected from amendment and deletion without having to be moved to a records centre.

Here is how Corey Roth described the feature

I know a handful of people that would say Records Management in MOSS 2007 was pretty much unusable. I think SharePoint 2010 will change their minds. The main issues were that you had to ship documents to an external library to manage them and the interface for applying holds was not very user friendly. Activating the In Place Records Management feature [in SharePoint 2010] will add a new button, Declare as Record, to the ribbon of document libraries. Clicking this marks the item as a record and I believe puts it in a read only state.

For it to qualify as ‘manage in place’ SharePoint 2010 would need to give us the ability to do the following tasks to a document or information resource without moving it from a Team Site:

  • allocate the record to a folder classified within a hierarchical fileplan
  • allow the document to inherit retention rules and/or access permissions from the folder it is contained in or the fileplan path that the folder is classified by.

On the basis of the reports I am reading I am not convinced that SharePoint 2010 will allow those two things to happen. it seems to me that SharePoint 2010 will support a fileplan within the records centre, but not across team sites (I would be happy to be proved wrong!)

Microsoft provide a useful explanation of managing records in SharePoint 2010 here. But it does not clarify the question as to whether or not a document declared as a record in the team site is linked to the fileplan kept in the records centre.

Elements of records management functionality in SharePoint 2010


The SharePoint 2010 records centre will support a fileplan hierarchy. This is good news and might actually make the records centre useable. However if I am right that a document has to move to the record centre in order for it to be governed by the fileplan then this is a weakness. I would rather the system allowed the fileplan to be applied to the document or information resource in its original context (usually the team site in which it was created or posted).


Folders will be given functionality in SharePoint 2010- this is a major change in Microsoft’s stance. SharePoint 2007 gave no functionality to folders. Microsoft, together with most SharePoint consultants, argued that using columns of metadata was a better way of organising document libraries than folders.

Sadalit Van Buren went to SharePoint Governance session at the Las Vegas and reported that

one surprising piece of the content for me was this recommendation:
• In SharePoint 2007, the best practice was: use metadata, not folders.
• In SharePoint 2010: use folders, inherit metadata

Document identifiers

SharePoint 2010 will support unique identifiers for documents

Investigation into the use of SharePoint by UK Higher Education Institutions: literature review

Eduserv have published the literature review on the usage of SharePoint by Higher Education Institutions (HEIs) written by myself and Julie McLeod. The review is available from here (PDF)

Here is an extract from the conclusions of the review:

Given the widespread use of SharePoint in HEIs there has been surprisingly little debate about its effectiveness or otherwise in this sector. This contrasts with vibrant debates within HE about Virtual Learning Environments (VLEs), and providers such as Blackboard and Moodle. (See for example the various sessions about VLE’s and the future of VLE’s in the September 2009 Alt-C conference).

The closest things to a forum for discussing SharePoint in HEI are the SharePoint User Groups provided by some JISC Regional Support Centres for both FE and HE institutions. However, not every region has one and they have mainly concentrated on further education rather than HE. They meet infrequently and there has been little in the way of outputs from them.

Many HEIs have given details of their implementations on their websites. Some have provided case studies or allowed vendors to provide case studies. Some, for example the University of Coventry and the University of Oxford, have provided information about their future plans for SharePoint. But no evaluations of specific SharePoint implementations have been found.

The lack of widespread debate on SharePoint, in comparison to the debate on VLE’s in general and on particular VLE providers, may stem from the fact that:

  • SharePoint’s functionality spans many different stakeholder groups within HE (webmasters, internal communications teams, knowledge managers, records managers, faculty administrators, learning technologists etc.). There are few, if any, forums that gather together this range of interested parties. In contrast, VLE’s are specific to the learning technology community and are fully debated and discussed by that community.
  • SharePoint 2007 is a proprietary system. The closest equivalents to SharePoint 2007 are Enterprise Content Management systems (ECM). However, SharePoint 2007 has had far more uptake in HE than any other ECM system. There are key features of SharePoint 2007 that differentiate it from other ECM systems. Unlike other ECM systems SharePoint is already available to many HEIs as part of their Microsoft Campus. Unlike other ECM systems SharePoint is a platform that is capable of being extended by custom development or by (often) custom integration with other third party products from the vast ecosystem that surrounds SharePoint 2007.
  • The rise of SharePoint has been relatively recent. SharePoint 2007 is vastly more powerful than its predecessor SharePoint 2003, and hence the last two years have seen a vastly increased take up of the product.