Public Product Roadmap

Owned by Former user (Deleted)
Last updated: May 21, 2014
1 min read

Core Systems Preparation

Develop systems necessary for content migration to occur.  Meet minimum levels of specification compliance and sub-optimal system architecture.  Important components include:

  • Content Management
  • Document Management
  • Events Management
  • Form Management

Authentication and Authorization

Build out Shibboleth integration and complete the UW Communities System.  Important components include:

  • Shibbolize
  • UW Communities
  • Page Security Model
  • User Management Systems

Secondary Systems and Enhancements

Enhance existing systems to meet all specification requirements, finalize plugin architecture, implement centralized plugin architecture, develop new system for delivering new content.  Develop new systems based on user feedback.  Important components include:

  • Plugin Aggregation
  • Enhanced Content Management Systems
  • New User Support Systems and Help Desk
  • User Feedback

Server Tuning and Preparation

Begin to prepare the new Shared Hosting L4 account for production.  Work with DoIT SALT to perform load testing and tune the L4 caching system.  Schedule DNS cut-overs with Hostmaster and redirect handlers with OIS.  Important components include:

  • IAA WiscFed
  • Firewall Configuration
  • L4 Cache Configuration
  • Load Testing

Training and Documentation

Build training materials and system documentation for upcoming training sessions and content migration.  Important components include:

  • Knowledgebase Development
  • Training Material
  • User Support Standard Operating Procedures

User Training

Users will undergo training sessions and one-on-one sessions to build skills for migrating content and working in the new CMS.

User Content Migration

Users will work to migrate their sites to the new CMS at preview.wisconsin.edu.  Users will seek support and additional training as needed.

User Content Enhancement

Users will work at their own pace to develop new content and utilize better information architecture, improved content systems, and the full feature set of version one.

End User Support

We will provide ongoing end user support and continue to develop the knowledgebase–building a strong self-help system.