Despite its power and fl exibility, SharePoint presents many challenges for building enterprise content
management (ECM) solutions. This is partly because of the inherently complex nature of application
development on the SharePoint platform in general, but mainly because the out-of-the-box tools that
SharePoint provides (such as content types, site columns, lists, etc.) are defi ned at such a low level that
it is often diffi cult for developers to fi nd the right balance between building reusable components that
capture the semantics they need when crafting their solutions and writing applications directly using
CAML and .NET code. These challenges are even greater for records management (RM) development
because the platform provides no built-in support for fi le planning or content life-cycle management.

Records management on the SharePoint platform relies on several different components that together
provide a comprehensive set of tools for building RM solutions, but each of these components can also
be understood as a separate and distinct technology. As an example, Information Policy plays an important
role in records management but also stands alone as a powerful component of any ECM solution.

download link