The Enterprise Wiki component of SharePoint 2010 grants users the ability to easily create a structure to share knowledge, manage projects, and collaborate across an Enterprise.

With the options to enter information as rich text or html, users can create content ranging from simple text to leveraging html to create more substantial wiki pages. Links can easily be inserted to tie together other SharePoint pages or reference external content. The process of linking within a wiki is core to creating structure. Documents, tables, images, video and audio may also be added to enhance wiki pages.

READ FULL POST at blog.concurrency.com

Microsoft SharePoint Server 2010 includes six permission levels by default. You can customize the permissions available in these permission levels (except for the Limited Access and Full Control permission levels), or you can create customized permission levels that contain only the specific permissions you need.

READ FULL POST at blog.concurrency.com

Developing the site hierarchy is only one aspect of a successful implementation. Understanding the boundaries and limits of SharePoint 2010 is critical to ensuring scalability, performance, and manageability. This is especially important in the planning of Content Databases as they naturally align to the site hierarchy and impact performance and usability. A site hierarchy with poorly planned Content Databases creates a situation where costly remediation is necessary in order to scale the platform properly.

READ FULL POST at blog.concurrency.com

Individual users in a SharePoint 2010 environment can create a My Site and begin the process of social networking across the Enterprise. Within this framework of social networking, a tangible business use can occur as users collaborate with other team members, locate individuals with skills required for projects, centrally organize their own information and share information with other users.

READ FULL POST at blog.concurrency.com

There is a debate brewing in the world of SharePoint Enterprise Records Management (ERM) between whether a preferred approach is In-Place Records Management or the use of a Records Archive. While I weigh heavily towards an “Archivist” approach with a central Records Center (based on my security/usability viewpoints), there is a time and place for using In-Place Records.

READ FULL POST at blog.concurrency.com

SharePoint 2010 has several built-in site templates which may meet you requirements. The chart below is a list of the available site templates and their intended purposes. Keep in mind that any of these core templates can be customized and re-templated!

READ FULL POST at blog.concurrency.com

Content types and site columns are the foundational elements of SharePoint, but they often get misused. Whether it’s creating too many content types, not enough, or recreating site columns that are already available out of the box, it is critical to remember some key aspects when instituting and managing these items:

Content Types

Content types are a core organizational feature of SharePoint 2010. They are designed to give users the ability to organize SharePoint content in a centralized and meaningful manner. Site columns (metadata) can be encapsulated within a content type to allow for reusable structure or independently added to sites and lists.

READ FULL POST at blog.concurrency.com

The Content Management Interoperability Services (CMIS) Connector for SharePoint has been released. The CMIS connector allows “SharePoint to interoperate with other ECM repositories through the CMIS Consumer Web Part”. More information about this tool and how to leverage it can be found at:

http://blogs.msdn.com/b/ecm/archive/2010/07/16/announcing-the-release-of-the-cmis-connector-for-sharepoint.aspx

READ FULL POST at blog.concurrency.com

Have you ever needed to share content, such as a list or document library, across SharePoint sites but found that the Content Query Web Part does not quite meet you requirements (such as offering filterable columns)? The answer to your quandary may be a global Web Part. This can be created using SharePoint Designer 2010 and the steps below:

READ FULL POST at blog.concurrency.com

One of the most powerful features within SharePoint 2010 for document management is the Content Organizer. This feature allows for the automatic routing of documents to different libraries and folders within those libraries based on pre-defined rules.

READ FULL POST at blog.concurrency.com