SharePoint Thomas

Seamless integrated and hidden from users Managing records is typically not every employee’s accountability. Putting obligations on users to do records management’s tasks will in most cases lead to failure. Users will find other – frictionless - ways of working with their content, resulting in unmanaged content. Aim to implement a records management solution within your SharePoint environment that is providing automatic records classification, auto-declaring documents as records (based on rules), enriching your content automatically with additional metadata, and performing other records management tasks automatically . The OOTB records management capabilities in SharePoint will not do this for you, so you need to use a third party tools or develop a solution (the “Records Management feature”) to provide this type of functionality. Extendable Content Type schema Create your content type schema with the goal of having as few content types as possible. The number of content types

“Microsoft SharePoint Server 2010 includes four information management policy features to help you manage your content: expiration, auditing, document labels, and document bar codes. - msdn.microsoft.c om” In this post I will focus on the audit capabilities in SharePoint 2010, more specifically how to enable the audit functionality. When the audit functionally is enabled it will automatically log events and activities that is done on your content. The content could be documents, records and other items, such as task list and calendars. Why Why would you enable auditing in SharePoint? There could be different reasons, and they often depend on which vertical (e.g. Public/Government) you are located in. Meet Regulatory and Legal requirements. Track how documents (and items) are used. Keep track of document history if documents are sent to the Content Organizer . When using the Content Organizer,  the document’s version history is deleted. The audit log will be your source to

This is a list of OOTB web parts in SharePoint. At this point the list does not indicate which edition of SharePoint and which feature the web part belongs to.

An exciting new feature in SharePoint 2013 is Managed Navigation. This feature allows us to design a site navigation that is driven by terms/topics rather than (site) structure.

Microsoft Access is a 20 year old product and there have been multiple attempts to integrate Access features in earlier versions of SharePoint. Is it better now?

Here is a cheat sheet of the OOTB Permission Levels in SharePoint 2010: (Click here to download the pdf version)