Share Point Portfolio


Published on

Demonstrates several of Keith Rimington\'s SharePoint development efforts.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Share Point Portfolio

  1. 1. SharePoint Portfolio<br />A Visual Summary<br />Keith B. Rimington<br />Application Developer<br />
  2. 2. Objective:<br />To implement SharePoint with Corporate colors, fonts, and themes enforced throughout all sites.<br />Solution:<br />Created replacements for default.master and application.master.<br />Rather than modify original SharePoint system files, and to decrease upgrade risks, implemented an HttpModule that configures site theme and master page at runtime.<br />Branding<br />
  3. 3. Objective:<br />To provide configurable navigation items across all sites.<br />Solution:<br />Implemented new SiteMapProvider, using a links list as a data source.<br />Added menu (green bar) to the master page connected to new provider.<br />Added page to Central Administration to configure the global links list on a per-application basis.<br />Navigation<br />
  4. 4. Objective:<br />To provide visual cues in a SharePoint list.<br />Solution:<br />Implemented new column data type, called the Dashboard Status Indicator.<br />Column type configuration included support for 16 icon sets, trending, text position, and alignment.<br />The column appears in forms as a drop-down list.<br />The column appears in spreadsheets as text which can be subject to conditional formatting.<br />Status Indicator Column<br />
  5. 5. Objective:<br />To facilitate sorting, filtering, and grouping by employee information.<br />Solution:<br />Implemented new column data type, called Personnel Information.<br />The column supported up to fourteen different employee attributes, stored in an external Oracle 10g database.<br />Adding a personnel information column also associated a list item event receiver to the list, responsible for retrieving the calculated data.<br />Personnel Information<br />
  6. 6. Objective:<br />To provide special-case reporting and visualization of SharePoint data.<br />Solution:<br />Implemented web part based loosely on the Open Source project, ChartPart, to present live data stored in a family of SharePoint lists.<br />The utilized the library, System.Data.Visualization, or MSChart, provided by Microsoft (now part of .NET 4).<br />This part supported a flexible set of configuration options via an editor part.<br />Business Intelligence<br />
  7. 7. Objective:<br />To provide insight into site usage and promote responsible disk consumption.<br />Solution:<br />Implemented a site usage dashboard to supplement the SharePoint storage manager.<br />The bar chart provides insight into current storage versus site quota.<br />The double-pie chart provides insight into storage size of the largest lists and libraries. The outer ring is image-mapped to the version settings page for each list. The red slices in the peppermint-candy inner pie represent old file versions.<br />Site Analytics<br />
  8. 8. Objective:<br />To provide unified search portal across multiple SharePoint farms.<br />Solution:<br />Led a geographically distributed, cross-organizational team to implement federated search.<br />Provided training and examples to assist administrators with their implementation.<br />Federated Search<br />
  9. 9. Objective:<br />To provide multiple columns on a lookup for use in list calculations.<br />Solution:<br />Developed a column type and list item event receiver to provide additional calculated columns based on an existing lookup field.<br />Multiple Column Lookup<br />
  10. 10. Objective:<br />To provide enterprise reporting of SharePoint list data.<br />To enable reports bound to the SharePoint lists service, it was necessary to resolve a conflict between SharePoint’s handling of null values in the Lists Web service, and Reporting Services method of inferring schema from XML data.<br />Solution:<br />Created an enhanced Lists Web service, allowing XML-bound reports such as is shown here.<br />Reporting<br />
  11. 11. Objective:<br />To increase effectiveness of SharePoint administration.<br />Solution:<br />Developed several STSADM extensions and PowerShell modules to automate repetitive tasks, including:<br />Bulk-starting workflows.<br />Copying menus between sites.<br />Bulk-purging list item and document versions.<br />Bulk-updating access request emails based on site owners.<br />Bulk-configuring search scopes across site collections.<br />…and many more.<br />Automation<br />
  12. 12. Objective:<br />To increase effectiveness of SharePoint administration.<br />Solution:<br />Developed PowerShell scripts managing a variety of automation tasks, including:<br />Packaging of .wsp solutions,<br />Staged solution installation and upgrades,<br />Migrating data to/from SharePoint lists,<br />Voice synthesis of SharePoint list data,<br />Scheduled maintenance,<br />Ad hoc SharePoint Ninjutsu. <br />Automation (cont’d.)<br />
  13. 13. Objective:<br />To reduce maintenance costs by consolidating legacy applications into SharePoint.<br />Solution:<br />Utilized PowerShell to migrate data from legacy databases to new SharePoint lists.<br />Designed lists, views, pages, and reports to replace and improve legacy application functionality.<br />Pictured at right is an application developed by a former intern, ported into SharePoint.<br />Applications<br />
  14. 14. Objective:<br />To provide effective training to end-users and administrators.<br />Solution:<br />Configured SharePoint site dedicated to ongoing training and user education.<br />Provided regular screencasts using Camtasia Studio.<br />Provided navigation to publicly available training from Microsoft and its partners.<br />Reviewed and published user submissions for training materials and topics.<br />Training<br />