Is Sharepoint 2010 A Good Option For Ecm?

By Author: Dylan Rodriguez
Total Articles: 131
Comment this article

SharePoint has been enhanced in a big way with the release of SharePoint 2010 and it now includes a host of new features that enable the use of the product as a platform for ECM and image storage.
Determining types of content in SharePoint 2010: It is important different types of content are developed to handle the documents that are being scanned into SharePoint. It is critical to categorize the different types of document that are encapsulated and thereby ensure that document policies, security, retention schedules, workflow and metadata requirements are completely defined.
Digital Asset Support for SharePoint 2010 development: SharePoint 2010 features a new asset library that has been specifically developed to share and handle different types of digital assets including video, audio, pictures and other rich media files. It features a new IMAGE content type that offers specialized functionalities and features to support different types of document images.
Scalability: SharePoint 2010 development counters many of the earlier limitations and ensures that it can be used as a platform for ECM. It is possible ...
... for a single library or list to hold tens of millions of items. It is also possible for hundreds of millions of items to be easily managed in a huge archiving scenario. It is important to find out if the present SharePoint farm can contain the volume of scanning that one may be planning to implement. It is also possible that one or maybe even more than one crawl servers are needed in a high volume-scanning scenario.
Remote Blob Storage: SharePoint 2010 development along with SQL Server 2008 had to rely on BLOBS but now it can store documents outside the database. This means that SharePoint 2010 does provide scalability and allows an organization to gain advantage from minimized cost storage for documents. ECM solutions with high volume and built on SharePoint should think of using remote blob storage. This will surely minimize the impact and as well as the costs for SQL Server and it will also allow to store documents on lower tier storage.
Information Management Policies: In SharePoint development 2010, it is possible to create separate retention policies for both documents and records. Some of the questions that can be asked include for how long document drafts need to be kept; how many versions have to be retained; what kind of eDiscovery requirement is there and what are file plan requirements.
Records declaration: SharePoint 2010 features records libraries and records management that allow scanned images to get converted into Records immediately. Since a scanned image cannot be altered, hence it is considered as a record as soon as it is added to SharePoint.
Workflow: SharePoint development 2010 features improvised Workflow capabilities that simplify the apply process automation to documents that are scanned into SharePoint. For instance, to understand through an example is the automatic trigger of an approval when a new invoice is scanned into the system.
In Place Records: This particular feature in SharePoint development 2010 allows the user the option of declaring a document as a record in its original position. This implies that the document gets the right kind of security, retention and disposition without requiring to be routed to a centrally managed location.
These are just some of the features that SharePoint 2010 offers to SharePoint developers and they can use these benefits to offer optimized SharePoint solutions to their clients.

For More Info :- Sharepoint 2010 Development || SharePoint Development