In my first post of this series, I showed you how to configure Content Organizer to run on your site. In this post, I will walk you through each of the Content Organizer settings options and explain what each option does.
To get to the Content Organizer settings, click on ‘Site Actions’ and select ‘Site Settings’. Under ‘Site
Administration’, click on ‘Content Organizer Settings’. (If you don’t see this option, refer back to the initial post in this series.)
The first setting forces users to utilize the Content Organizer when they submit to the Records Center documents that have one or more corresponding Content Organizer Rules. [Note - SharePoint 2010 allows you to use the Content Organizer to route documents to any Library or folder in your server farm and is not just limited to Records Center site Libraries. However, because this blog is focused on SharePoint Records Management, we will focus our attention on managing records in the Records Center.]
The second setting allows you to determine if you want to restrict the Content Organizer to Libraries and folders within the original site or open it to other sites across other site collections. (This setting will determine how you configure the Target Location in your Content Organizer Rules.)
The third setting, Folder Partitioning, allows you to create additional folders once specific number of records are created in a target folder. [Note - This feature may be particularly helpful to EU Records Managers subject to MoReq2 requirements.] If this setting is not enabled, SharePoint will ignore the number of records submitted to each folder.
The fourth setting, Duplicate Submissions, controls how SharePoint responds when a record with the same name already exists in the target Library or folder. The options are to create a SharePoint version of the record or append unique characters to the duplicate record name. Records Managers should determine which of these options is most appropriate for their organization’s requirements.
The fifth setting determines if audit logs and properties of the document are included with the document when it is declared a record into the Records Center. This is likely to be important metadata relevant to the record and should probably be preserved.
The last setting allows you to specify your designated Rule Managers. These are any users who should be granted authority to create Content Organizer Rules.
The next installment of this series will describe how to leverage these settings to create Content Organizer Rules.
[This is the second installment of an occasional series of posts on this subject.]
In the initial installment of this series I explained what cloud computing was and why it is likely to have a profound effect on how Records Managers do their jobs. In this post, I will describe some of the risks and concerns you are likely to encounter as you and your organization begin to consider leveraging a cloud-based solution infrastructure for your organization’s SharePoint Enterprise Content and Records Management solution.
Regulatory Compliance – This should be the primary cloud computing concern for Records Managers. The legal and regulatory requirements applicable to your records repository located at your headquarters may be very different from the requirements that apply to your records repository hosted in another state. And things can get even more complicated if your hosting service is in a completely different country.
Security – Ask any information technology solution architect to give you their top five concerns about cloud computing and ‘Security’ is likely to be their first three. The thought of maintaining your records repository offsite and accessing it over the Internet can be frightening to anyone. And it should be. Issues like user authentication, data encryption and privacy are just three examples of the many security concerns that you should be aware of if you are considering a move to cloud computing.
Backup and Disaster Recovery – No operations center is completely safe from potential disaster, despite what the hosting service may tell you. A proven backup and recovery plan is a critical component of any cloud computing solution.
Performance – As any experienced Records Manager knows, if your end users are not able to access their records quickly, easily and reliably, they will find a way to circumvent your system completely – such as storing records locally or copying them to external storage devices. This loss of control could quickly make efficient records management next to impossible. Any move to a cloud computing environment must not have a negative effect on the performance of your SharePoint repository.
Data Ownership – This is an issue that probably doesn’t get as much attention as it should. Records Managers must safeguard the integrity of their data. This includes ensuring that there is a clear understanding of who owns the records maintained by the hosting service, as well as guaranteeing that your organization will be able to easily migrate its records to another hosting service given unsatisfactory performance by the current provider.
This isn’t a complete list of everything you should be concerned with when considering a move to a cloud computing environment, but it is a good start. Mention these risks to a potential hosting service and they should have good answers for each of them. If they don’t, you probably find another vendor.
In the next installment of this series, I will discuss the benefits of hosting your SharePoint records repository in the cloud and why it may be the right solution for your organization.
Administration’, click on ‘Content Organizer Settings’. (If you don’t see this option, refer back to the initial post in this series.)
