The Problem with Leveraging SharePoint Records Management Services in Office365

The big question is, considering Office 365, where is Records Management fitting in? The old news is that SharePoint 2010 RM is not registering good performance within the e-discovery space. However, this is not considered a hindrance by most organizations.

SharePoint site migrationIt is a fact that IT is capable of pulling the objects which are essential to cater to the counsels’ expectations with respect to its own SOP or standard operating procedure, which generally incorporates a third party software. E-discovery has been performed by information technology more regularly and far longer than implementation of electronic retention by RM.

Automation is great
SharePoint 2010 RM services are capable of beautifully automating records declaration. They can be deployed successfully through mapping the records retention schedule across SharePoint 2010 RM.

The content types pertaining to the series can be holistically leveraged across site collections, followed by attachment of information policies. Then the indexing services to be run at particular intervals are recalculated.

The future hazards
Off-the-shelf SharePoint 2010 RM services are being trusted by corporate records programs. In an age where Records programs are entirely suspended or drastically squeezed, this is a quite inexpensive option for automated records declaration.

Since Office 365 lacks a related Records Center template, it is possible for the program to be vulnerable. The absence of automation can damage the program’s reputation. In case automated records declaration is leveraged in SharePoint also, the same might as well be in trouble.

What are the choices?
The necessities of the information architecture going beyond records policy amount to a textbook dilemma. Considering the case of information professionals, the design choice comes up with potentially long-term as well as negative connotations. In case an organization has automated records declaration through SP 2010 and its department of Information Technology is looking forward to embrace cloud services, it is a difficult choice. Deconstruction can be followed by manual records declaration implementation or the services of third party experts might be sought for devising something new.

Perhaps the best option in doing nothing in this particular case. First, something or the other will ultimately break. Secondly, this is a department that thinks forwardly and hence it cannot be visualized as restricting to one particular solution due to the lack of options. Thirdly, the employee turnover happens to be so high that the future administrator tends to lose all context pertaining to the architecture. Fourthly, retention schedules are subject to change and so unraveling of the Center for reconstruction in accordance with the new schedule is an enormous concern.

Manual records retention can also be considered as an option. However, it is an inferior one:

  • In-Place RM exists till today within Office 365, although it has been reduced to a mere status symbol. A one or a zero, which implies that either the record exists or it does not. In fact, the option for management of the same from the back-end is not available with the Administrator. The good news is that interaction with the end users is possible. On the other hand, the bad news is that until and unless the C-level stresses on and communicates its requirement, end users would definitely have to time for annual review. Destruction does not take place.
  • For devising out-of-the-box manual RM services within Office 365, the best way is the creation of a Records sub-site for each site collection. In every ways, the same folders should be used as are planned for the SP 2010 Records Center. The content types may be bypassed entirely and the same information policies may be used directly behind every folder.

Those objects which are required to be declared as records can be copied from the major site collection pages to the Records sub-site’s suitable folder. Since it is the case of a copy (wherein move is not available), the metadata changes should be noted and the peer should return to the original object for deleting it.

For initiation of a solution, the help of a third party may always be solicited. On one hand, it is being demonstrated that you need a compromise. Migration to the cloud cannot be hindered. On the other hand, you wish to make use of your cordial partnership with IT very meticulously at this point. Since Records is your project, it should not go to the backseat, being assigned with cleaning up legacy data.

On the positive side
In case you are going for RM in Office 365, the positive point is that it is convenient to edit retention periods. As discussions are held with each peer for planning of their folder structures, the maps need to be edited. It should be explained why and how folders pertaining to every site collection are a component of a bigger process-oriented schedule. Moreover, site permissions need to be unraveled for rebuilding them. After all, there is once more the opportunity to describe the mission as well as the significance of the program. As your IT department gears up for handling 2014 projects, it’s a great idea to seize the moment for RM in Office 365.

If you were to attempt a SharePoint site migration project to Office365, understanding of these choices and pros and cons would ensure a successful migration.

We provide SharePoint bespoke development services. If you would like to know more about the expertise of our SharePoint developers, please get in touch with us at Mindfire Solutions.