In our last post, we introduced the concept of Information Management Policies in the 2007 release of the Microsoft Office System, and the different capabilities that can be implemented using these policies.
In this post, we’re going to discuss how policies can be used to manage both records spaces and collaborative spaces. (This will be especially helpful when we start looking at the different policy features, because many of them will be applicable in both collaborative and records scenarios.) Also, it will help explain why we built the information management policy re-use/administration capabilities into the 2007 release of Office SharePoint Server, since many of these are focused on retention management of content in collaborative spaces.
Information Management Policies in records spaces:
First, let’s talk about a scenario near and dear to most records managers – how information management policies can be used to enforce retention schedules in a records space. Since these spaces are generally controlled by records managers each list, document library, or content type can be manually configured with an appropriate policy to control a records retention schedule and disposition. However, even in records spaces, it may be the case that there are several record series whose retention requirements are the same -- for example, because the retention schedule for each is driven by a common regulation or legal requirement.
For these types of scenarios (and others that we'll see shortly), the 2007 release of Microsoft Office SharePoint Server includes a Site Collection Policies gallery -- this is a central gallery of policies that can be authored once and then re-used across multiple lists, document libraries, and content types. The benefit of this re-use is that, should that policy ever need to be modified (for example, if a new legal interpretation of a regulation occurs), then that change can be made once to the policy in the gallery, and all of the locations using that policy will be updated accordingly. Here is an image showing the Site Collection Policies gallery (Note: Clicking on this image should bring up a larger version):
You author a site collection policy in the same way you author a policy for an individual list, library, or content type. And once a site collection policy has been created, it can be used in lists, document libraries, and content types by selecting the policy by name in the appropriate “Information Management Policy Settings” page, as shown below:
(Note that the description for the currently selected policy is shown on this settings page… that will be a particularly important point for the re-use of site collection policies in collaborative spaces.)
Now let's look at how policies (and in particular, the capabilities of the site collection policy gallery) can be applied & used within collaborative spaces, which are generally not as tightly controlled by a records manager.
Information Management Policies in collaborative spaces:
Although the records manager usually controls each document library, list, and content type in a records space, that isn't true for most collaborative spaces in an organization. However, these spaces still need some level of "retention management", to ensure that work-in-progress content is kept for an appropriate period of time, that any required audit trails are recorded for important content, and that other best practices are implemented. For this reason, we've made all of the information management policy capabilities available in all types of sites in Office SharePoint Server 2007 -- not just sites used to manage records.
In sites in collaborative spaces, the re-use of site collection policies are especially important because they allow records managers to define centrally the appropriate policies for different types of content in a way that collaborative space owners can easily incorporate into their own document libraries, lists and content types. In this way, site owners need only make the minimal decision of "which of the pre-defined policies is appropriate" for each location or type of content... and this policy still remains “transparent” to end-users, who just use the content types, lists, and document libraries to go about their regular work without needing to know about the information management policy.
In our next few postings we'll examine each of the different policy features that can be incorporated into a policy, including how each is relevant to both collaborative and records spaces.
Thanks for reading!
- Ethan Gur-esh, Program Manager