SharePoint Scanning Software and Standardization
This is a great overview of document scanning software that provides control of the standardization process when scanning to SharePoint libraries.
Wednesday, May 22, 2013
Monday, March 21, 2011
What is SharePoint Governance?
SharePoint Governance Definition
So what exactly is governance as it pertains to SharePoint 2010? Governance in general can be defined as the exercise of authority or control, and a method or system of management. So why do you need a plan when it comes to Microsoft SharePoint?
We can all find an example of technology abused on our own file servers...end users, if left to their own devices will store, file and name to their own liking. Most organization never implemented a governance plan on file servers as their really aren't technologies to enforce how users name and build folder structures.
With the Microsoft SharePoint system, the rich feature set, capabilities and overall dimensions can build an unmanageable beast, if end users are left to build as they see fit.
A plan, and an overall architectural vision is required to manage all the layers of a SharePoint implementation: farms, site collections, individual sites, document libraries, content types, columns, lists...and it goes on and on. One of my favorite examples would be a SharePoint Scanning / SharePoint Capture implementation. Any process that places files en masse into SharePoint requires control and standardization through technology. Most of the document capture technologies provide the ability to enforce file naming, folder structuring and now with SharePoint capture, the ability to dynamically build libraries and sites. A process like this can get quite out of control without a governance plan, and overall control.
More to come on the overall governance of Microsoft SharePoint.
So what exactly is governance as it pertains to SharePoint 2010? Governance in general can be defined as the exercise of authority or control, and a method or system of management. So why do you need a plan when it comes to Microsoft SharePoint?
We can all find an example of technology abused on our own file servers...end users, if left to their own devices will store, file and name to their own liking. Most organization never implemented a governance plan on file servers as their really aren't technologies to enforce how users name and build folder structures.
With the Microsoft SharePoint system, the rich feature set, capabilities and overall dimensions can build an unmanageable beast, if end users are left to build as they see fit.
A plan, and an overall architectural vision is required to manage all the layers of a SharePoint implementation: farms, site collections, individual sites, document libraries, content types, columns, lists...and it goes on and on. One of my favorite examples would be a SharePoint Scanning / SharePoint Capture implementation. Any process that places files en masse into SharePoint requires control and standardization through technology. Most of the document capture technologies provide the ability to enforce file naming, folder structuring and now with SharePoint capture, the ability to dynamically build libraries and sites. A process like this can get quite out of control without a governance plan, and overall control.
More to come on the overall governance of Microsoft SharePoint.
Subscribe to:
Posts (Atom)