Content Management System (CMS) Implementation at SFU Feb 10, 2011 Frances Atkinson Director, Institutional, Collaborative & Academic Technologies IT Services
Items Day (Adobe) CQ5 installation Initial and longer term goals Implementation plan Support Issues Steering Committee: role, priorities
Day (Adobe) CQ5 Installation CQ5 was purchased by SFU after an 8 month evaluation and selection process SFU’s first comprehensive Web Authoring app - author.sfu.ca New Publish server delivers “activated” CQ content OR passes over to the old (current) Publish server and name.sfu.ca URLs handled Also external URLs for conferences, research groups etc.
Initial Goals Re-platform SFU’s official web presence Modernize content: - more engaging and interactive - more professional and consistent Build a community of content authors and support staff
Longer Term Goals Many possibilities. Input needed on priorities. Committees and other private sites Document retention Social & collaborative authoring Academic courses Faculty profiles Research groups Student clubs Individual sites for faculty, students, staff list archives Etc.
Longer Term Goals (advanced) Automating business processes (e.g. with fillable forms and workflows) Displaying official information automatically: enterprise systems websites Extending functionality with custom components Developing CQ as an application platform, integrating data and functionality from other systems
Achieving Goals in Phases
Implementation Plan Ongoing initiative – no end date Specific tracks, each 2-4 months duration, e.g. 1 and 2 are complete 3 (4,5,6, etc.) have started
Current Progress – live sites
Current Progress – exploration or underway Student Services Grad Studies VPs sites FENV – Archaeology PAMR, SF News SFU main pages – all campuses FASS – Philosophy, Linguistics, Humanities Teaching & Learning Centre Education – News blog, ISTLD FAS FCAT Continuing Studies VP Research + Selected use cases
Federated support approach Content authors are located throughout SFU (Future) site administrators, designers and developers are located throughout SFU IT Services supports the system & the above staff, and liaises with senior administration on strategic issues
Support Issues People ITS staff are already swamped (at 8/12,000 sites done = %) Much depends on building partnerships and self sufficiency Time People don’t want to wait while ITS builds the service Software Costs New vendor functionality = more money (e.g. mobile module)
Steering Committee Proposed TOR: To facilitate the implementation of new web authoring infrastructure at SFU along with associated support structures, with the aim of making it easier for authors and developers to deliver fresh, accurate, consistent, interactive and reusable web content. To identity key issues and barriers to success, and suggest solutions. To advise and assist in the development and implementation of a communication plan. To encourage operational groups in Faculties, Departments and other units to move key SFU websites to the new infrastructure. To advise on how support structures can best operate collaboratively, in a cost effective manner, emphasizing consistency and effectiveness of support, and avoiding the duplication of services. To advise on the reuse of official SFU information across diverse websites in powerful, automated ways, reducing manual duplication. To advise on how specific technical mechanisms, such as fillable forms with workflow, might be exploited to meet SFU needs.