To assist in selecting a single, final candidate, the working group has scheduled demonstrations of the final candidates to gather feedback and take questions. After demonstration sessions conclude, the working group will submit a recommendation and draft implementation project plan to UWM's Web Steering Committee.
Subject matter experts have been invited to demonstrate final candidates to working group members and were interviewed about how well each met the requirements elicited from stakeholders at UWM.
Test installations of the candidates have been setup and working group members were provided the opportunity to try out each candidate to assess how well it satisfied UWM's Web content management requirements. Based on working group research and experience, the candidate field was further narrowed to Drupal and WordPress.
Working group members researched the initial candidates and narrowed the field to Drupal, Joomla, OpenScholar, Typo3 and WordPress. Satisfaction surveys have been sent to individuals from outside UWM who manage and administrate the candidates at their organizations. Working group members researched the candidates and held internal demonstrations of each being use for common content authoring activities. The candidates were further narrowed to Drupal, Joomla, OpenScholar, and WordPress
The working group surveyed the landscape of Web content management software packages and services and identified seven initial candidates to investigate as potential supplements to UWM's current CommonSpot Web content management software. Initial candidates included CommonSpot Cloud, Django CMS, Drupal, Joomla, OpenScholar, Typo3 and WordPress.
UWM.edu usage metrics have been produced for websites using UWM's current Web content management services. The metrics revealed UWM.edu hosts over 24,000 web pages with an average growth of over 200 pages per month, and over 16,000 documents such as PDFs and Microsoft Word docs. UWM has over 1,300 registered content authors. 70 percent of content authors serve the University in a non-technical role. Unique website visitors per day averages and information transferred per day averages were also calculated.
A survey was sent to all campus CMS authors asking for their level of satisfaction with current Web content management services. All campus CMS authors, web developers and members of the Tech Users group have been invited to attend open sessions to discuss their Web content management needs. With input from the working group and campus stakeholders, a requirements matrix was produced.
A Web Content Management Working Group consisting of representatives from UWM schools, colleges and administratie units was chartered to evaluate the effectiveness with which UWM provides web content management services to campus.