Records Center - A Place for Hierarchy, Driven By Metadata
Records Center - A Place for Hierarchy, Driven By Metadata
The Records Center was introduced in 2007 as a SharePoint site that served as a conventional records archive. Content from all over the enterprise can be submitted to a Records Center and then routed to the appropriate place where it picks up the right permissions and policies, such as expiration and auditing.
For SharePoint 2010, we know it's important to continue to invest here and add even more "traditional" archive features. When looking at the broad swath of features we had to choose from, our goals here really focused on providing features that allow you to extract the most value out of an archive and find the data you need. For instance, here are a few of the new features in a SharePoint 2010 Records Center:
- Document ID: Every document can be assigned a unique identifier, which stays with the document even when it's archived. This allows records to be easily referenced by an ID no matter where the document moves
- Multi-Stage Retention: Retention policies can have multiple stages, allowing you to specify the entire document lifecycle as one policy (e.g. review Contracts every year, and delete after 7 years)
- Per-Item Audit Reports: You can generate a customized audit report about an individual record
- Hierarchal File Plans: You can create deep, hierarchal folder structures and manage retention at each folder in the hierarchy (or inherit from parent folders)
- File Plan Report: You can generate status reports showing the number of items in each stage of the file plan, along with a rollup of the retention policies on each node in the plan
Here's the home page of the Records Center in SharePoint 2010 for a fictional government agency, the Joint Task Force.
Notice that the home page is a place for records managers to educate the organization on compliance policy, as well as a place to look up a record by its document identifier.
In addition to adding these traditional records management features to our archive, as product designers we made a big bet on the power of metadata to dive 21st century electronic records management. This manifests itself in several ways in the SharePoint archive:
- Taxonomy and Centralized Content Types: The archive will be a consumer of enterprise-wide taxonomies and content types, ensuring consistency and context transfer between the collaborative spaces and the archive. We'll be talking a lot more about our 2010 taxonomy investments in future posts
- Content Organizer: The records router can use metadata to route incoming documents to the right place in the hierarchical file plan. For instance, it enables you to automatically enforce rules on content that is submitted, like "If a Purchase Agreement is tagged with Project Alpha, send to the Alpha Contracts subfolder and apply that's folder retention policy to the item."
- Virtual Folders: The file plan is a great way to manage a repository but often time isn't what you want to use to navigate and find the content you are looking for. The SharePoint 2010 Records Center makes use of a new feature called metadata based navigation, which allows you to expose key metadata as virtual folders:
Notice that end users discover content in this Records Center by navigating virtual folders based upon metadata properties on the records.
This bet on metadata is all about empowering the end user, thus increasing the chance of successful adoption of the RM system. Instead of choosing a complicated node in a file plan, submitters just fill out a few pieces of useful metadata and they'll use that metadata when they need to find the content again.
Learn more about Sharepoint Interview Questions in this blog post.
Interested in mastering Sharepoint?
Check out this blog post to learn more Sharepoint Tutorials.
In Place Records Management - Injecting Records Management in the Content Creation Experience
With just about every customer engagement my team is involved in, we hear the same message again and again: records management doesn't start (or stop!) in the archive. Content isn't created there and it sure doesn't live there for the most interesting parts of its life.
There has been made a huge effort in 2010 to enable you to do effective records management in collaborative spaces. Auditing, Retention, Expiration, Reporting, Records Workflows, eDiscovery, Legal Hold and Recordization are all features you can use in collaborative space as you are striking a balance between SharePoint's value to end users and the need for information governance.
Holding all of this together is a new feature in SharePoint 2010 called In Place Records Management. This allows certain SharePoint documents (or blogs, wikis, web pages, and list items) to be declared records. The system can prevent such records from being deleted or edited, if necessary by your organization's definition of what a record is:
Note that some of the documents have locks, implying to the user that they are dealing with records. When selecting a record, the UI for editing and deleting the item is disabled.
This recordization process can be done either manually, as part of a larger process in a workflow, or as a scheduled part of a document's retention (e.g. after 2 years). The key here is that, when declared a record, the content doesn't move to an archive - it stays where it is so the end users can still find and interact with the content.
Once declared, the system knows about an item's record status, so you can do things such as create different retention policies for records or use record state when defining workflows in SharePoint Designer. We also enable a programmability model so you can perform custom processes and policies upon recordization to meet specialized compliance needs.
Is In Place Records a replacement for a traditional archive? The answer is, of course, sometimes - we'll find some customers who want to use an in place approach exclusively, some who will want the traditional hierarchy and centralization that an archive brings, and many who will want both. It'll be something we'll talk about a lot on this blog, and our documentation has already started discussing the pros and cons of both approaches.
Scale: We're Talking Big
with electronic information growing at a crazy pace and businesses spending billions on eDiscovery every year, records managers have enough to keep them up at night. The scale of their records/content management system shouldn't be another worry.
As the records management engineering team, we take this burden very seriously and a large part of our effort this release has been spent adding features to make it easier to scale to massive archives. Features such as Remote Blob Storage, database query optimizations, internal timer job processing improvements, new database indexing strategies and other engineering initiatives enable us to make a great leap forward this release and allow our customers to have:
- Tens of millions of records in a single Records Center
- Hundreds of millions of records in a distributed archive: We'll talk in more detail in future posts, but many of the features mentioned above light up to allow many Record Centers to bind together to act as one logical repository.
For Indepth understanding of SharePoint click on