Gimmal Blog

Read the latest thought leadership and industry news from the experts at Gimmal!

All Posts

How to Manage Your Sprawling Content

Sprawling content, the spread of content across multiple repositories, has been a thorn in the side of records managers since the dawn of document management. Consolidation of repositories, which began in the early 2000s, at first looked to be the solution. However, it ended up highlighting the problems of content sprawl due to the high costs of consolidation as well as need for records managers to manage multiple file plans. Federated records management offers a solution to these problems but doesn’t offer the same locked-down approach with regards to regulation that consolidation can. Consolidation of repositories and federated records management both have pros and cons and, depending on your organization’s content management processes and repositories, one can be more beneficial than the other in the long term.

In the early 2000s, the occurrence of sprawling content coincided with the push to consolidate repositories. After the era of legacy systems, consolidation seemed to be the ideal way to handle records management at the time seeing as records were very difficult to manage. Consolidation seemingly only made the problems plaguing records managers worse due to the steep price and companies continuing to store content in other repositories.

Is Consolidation a Pipe Dream?

These problems regarding consolidation led to the realization that consolidation was unattainable, and instead another solution was needed. This led to the idea behind federated records management. Federated records management is made up of three key pieces:

  • The ability to manage content in place. This means that records managers can leave the content in the current repository eliminating the need to worry about content migration between repositories.
  • A single, unified file plan that controls the documents in all your repositories. This eliminates the need for records managers to stay on top of a separate file plan for every repository being used.
  • Repository-agnostic architecture, which means that where the information lives doesn’t matter since the single file plan reaches it no matter where it’s stored. Repository-agnostic simply means configuring your system so that your file plan and retention schedules live outside of any one system, but can reach into them all.

Ultimately, federated records management simplifies the document management process for all of those involved.

Simplify Information Management for Users

An increase in sprawling content can be confusing for your organization’s end-users. Increasing the number of repositories, processes, retention schedules, and systems of disposal can prove daunting to those in who need to understand how to use them. Despite the high costs, consolidation offers a more hands on approach when it comes to regulating your records. Federated records management, or the management of records in-place within the systems from which they originate, can offer a cost-effective solution that simplifies processes by taking users out of the equation in many vital information management processes.

There are pros and cons to both consolidation and federated records management. In reality, consolidating your records can be costly and time-consuming. Federated records management, on the other hand, presents a solution to many of the issues that consolidation cannot address.

New call-to-action

Related Posts

Creating a Framework for Classification

This is Part 2 in a series about creating and executing an effective file plan for your organization. Click here to read the previous post: Creating a Retention Schedule that Works.

3 Tips to Ensure KORA Compliance

There has been a spotlight on the Kansas Open Records Act (KORA) in the media lately, largely due to recent violations. Under KORA, any individual can request public records from government bodies. If all requested records are not provided within in a specific timeframe, these organizations are subject to significant repercussions. This is merely one example of a ‘sunshine law’. The purpose of sunshine laws is to provide transparency into government agencies by giving the public access to local government proceedings.

Creating a Retention Schedule that Works

Creating a usable, automated, and simple file plan is an important part of ensuring records are managed in a consistent manner and that you are protected from legal risks, such as failure to disclose information during a discovery proceeding or the unauthorized leakage of information. The first step in the process is creating a retention schedule, which outlines how long records are kept in accordance with the organization’s obligations and the law.