Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

TERMINALFOUR t44u 2009 - University of Oxford Case Study


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

TERMINALFOUR t44u 2009 - University of Oxford Case Study

  1. 1. Implementing Site Manager in UAS at University of Oxford Tony Stark – Project Manager [email_address] Ruth Mason – Technical Lead [email_address] November 2009
  2. 2. The University <ul><li>Collegiate University </li></ul><ul><li>17,200 full-time students </li></ul><ul><li>16,000 students on part-time courses </li></ul><ul><li>7,000 staff excluding those employed by the colleges </li></ul><ul><li>39 colleges </li></ul><ul><li>6 permanent private halls </li></ul><ul><li>160 academic and other departments </li></ul><ul><ul><li>Includes faculties, departments, schools, libraries and museums </li></ul></ul>t44u 2009
  3. 3. What is UAS? Central Administration Departments of The University. They work to support the Academic Departments. Approximately 1,000 staff in UAS t44u 2009
  4. 4. Umbrella url’s we are migrating <ul><li>Admin Web - </li></ul><ul><li>Includes some high profile sites: </li></ul><ul><ul><li>Vice Chancellor’s Office </li></ul></ul><ul><ul><li>Clarendon Trust Fund </li></ul></ul><ul><ul><li>Academic Administration – student facing </li></ul></ul><ul><ul><li>Staff facing </li></ul></ul><ul><li>Ox Web - </li></ul><ul><li>Main public facing web site of University. </li></ul><ul><li>Top pages with links to everything else </li></ul>t44u 2009
  5. 5. Some Numbers t44u 2009 Oxweb Admin Web Web Pages 12,000 7,000 Gb’s served / day 3.8 1.6 No. of files 16,000 15,000 Visitors / week 85,000 55,000 Web Applications 0 17+ Site Manager users 6 150+
  6. 6. Current / Legacy position <ul><li>Creating and Managing HTML pages </li></ul><ul><ul><li>Using Word to Web macros </li></ul></ul><ul><ul><li>Other applications make up the ‘web publishing toolkit’ </li></ul></ul><ul><ul><li>SFTP to development (preview) and then to live web servers </li></ul></ul><ul><li>Oxweb is using proprietary CMS </li></ul><ul><li>Training is 4 days and once a term </li></ul><ul><li>Ruth’s team is fire -fighting </li></ul>t44u 2009
  7. 7. Objectives <ul><li>Easier creation, editing, previewing, publishing and management of content </li></ul><ul><ul><li>Web Publishers concentrate on content quality not how to publish it </li></ul></ul><ul><li>Training reduced to less than a day and more frequently </li></ul><ul><li>Same look and feel across all sites </li></ul><ul><li>Ruth’s team pro-active so can concentrate on helping site owners to do better things </li></ul>t44u 2009
  8. 8. Where we are now and plans <ul><li>Occupational Health first site </li></ul><ul><ul><li>Learnt about Site Manager and what is involved in implementing sites </li></ul></ul><ul><ul><li>Developed styles and templates </li></ul></ul><ul><ul><li>Developed training course </li></ul></ul><ul><ul><li>Left out some technical things until later </li></ul></ul>t44u 2009
  9. 9. Where we are now and plans - 2 <ul><li>Sites on Site Manager 5 (3 are new sites) </li></ul><ul><li>Special Projects Category 3 currently – more on these later </li></ul><ul><li>Next Group 5 started with an initial list to cut our teeth on </li></ul><ul><li>Tranche 1 16 </li></ul><ul><li>Tranche 2 11 </li></ul><ul><li>Tranche 3 5 </li></ul><ul><li>Don’t mind when 14 </li></ul><ul><li>In or out of scope? 14 </li></ul><ul><li>Total 73 sites </li></ul>t44u 2009
  10. 10. Challenges <ul><li>Small team. Just lost a key member. Please apply if you are interested in joining us </li></ul><ul><li>Steep learning curve – have been and still are on one </li></ul><ul><li>Need solutions to technical problems </li></ul><ul><li>Managing user expectations – they known it is coming, they want it but: </li></ul><ul><ul><li>Pressure to implement new sites so not migrating old ones </li></ul></ul><ul><ul><li>Pressure to do things quickly v we want to do things sensibly and at an appropriate pace </li></ul></ul><ul><ul><li>Planning and setting dates for individual sites is difficult </li></ul></ul>t44u 2009
  11. 11. Special projects and technical solutions <ul><li>Special Projects </li></ul><ul><li>Statutes & Regulations </li></ul><ul><ul><li>Complicated versioning </li></ul></ul><ul><ul><li>Granular requirement so can use part of Statute/Regulation in other database systems </li></ul></ul><ul><li>Examination Regulations </li></ul><ul><ul><li>Complicated versioning but different from Statutes & Regulations </li></ul></ul><ul><ul><li>Web Publishing and Hardcopy printing from same content </li></ul></ul><ul><li>University Gazette </li></ul><ul><ul><li>Review of business processes </li></ul></ul><ul><ul><li>Web Publishing and Hardcopy printing from same content </li></ul></ul>t44u 2009
  12. 12. Special projects and technical solutions - 2 <ul><li>Technical Solutions </li></ul><ul><li>Oxonly or intranet content </li></ul><ul><ul><li>Content published on external web site </li></ul></ul><ul><ul><li>Need to restrict access </li></ul></ul><ul><ul><li>Implement GSA to replace ://htdig </li></ul></ul><ul><li>Framework for integrating web applications </li></ul><ul><ul><li>Delivery through Site Manager </li></ul></ul><ul><ul><li>Provide a wrapper to give same look and feel to pages </li></ul></ul><ul><li>Solution for non-contributors to preview but not edit their content </li></ul><ul><li>Authentication through University single sign on - Shibboleth </li></ul>t44u 2009
  13. 13. Terminal Four and Site Manager <ul><li>Looking for a partner not just a supplier </li></ul><ul><li>Took T4 a while to realise what they had taken on but never flinched and are meeting promises </li></ul><ul><li>Happy with selection of Site manager </li></ul><ul><ul><li>T4 seem to be able to make it do the majority of what we want it to do </li></ul></ul><ul><ul><li>Not perfect but what system is </li></ul></ul><ul><ul><li>Version 7 seems to support we have made the right choice </li></ul></ul><ul><li>Overall pleased with both Terminal Four and Site Manager. </li></ul>t44u 2009
  14. 14. <ul><li>Ruth Mason </li></ul><ul><li>Selections from the Oxford implementation </li></ul>t44u 2009
  15. 15. Selections from the Oxford implementation <ul><li>‘ In-page’ Table of Contents template </li></ul><ul><li>Publishing .htaccess files </li></ul><ul><li>Statutes and Regulations I: publishing multiple versions concurrently </li></ul><ul><li>Statutes and Regulations II: publishing pages as ‘rolled-up’ content </li></ul>
  16. 16. Pilot site – Occupational Health t44u 2009
  17. 17. Prototype approach <ul><li>A full spec exercise used Occupational Health site as a prototype </li></ul><ul><li>e.g. to build 18 </li></ul><ul><li>global templates : </li></ul>4.0 Global Content Templates 4.1 Gl Page Content Main 4.2 Gl Further Content 4.3 Gl Page Code 4.4 Gl Page Callout 4.5a Gl FAQ Start List 4.5b Gl FAQ 4.5c Gl FAQ End List 4.6 Gl Contact Details 1 - Main Office 4.7 Gl Contact Details 2 - Category 4.8 Gl Contact Details 3 - Person 4.9 Gl News 4.10 Gl Policy Documents 4.11 Gl Main Section Index Box 4.12a Gl Photo Gallery 4.12b Gl Photo 4.13a Gl Table of Contents 1 – Children 4.13b Gl Table of Contents 2 – Sibling 4.14 Gl Table of Contents 3 – In-page 4.15a Gl Google Map Template 4.15b Gl Google Map Point Template 4.16 Gl Media Inclusion 4.17 Gl Meta Data 4.18 Gl Search Box
  18. 18. Gl Table of Contents – In-Page <ul><li>Extends the standard Children and Sibling ToC options to provide an In-Page ToC </li></ul><ul><li>The template uses a nav object to populate a list of in-page links to content items of the current section </li></ul><ul><li>text/li formatters are provided for templates whose content we wish to be included in the ToC listing – only content authored in these templates are included = flexibility </li></ul><ul><li>Content must be built using a new instance of a compatible template for each section of content which has a ToC entry </li></ul><ul><li>The In-Page template has a text/top formatter associated with another nav object which provides the Back to Top links </li></ul><ul><li>e.g. </li></ul>
  19. 19. Using .htaccess for custom 404 pages <ul><li>.htaccess file is published via SM using File Upload </li></ul>
  20. 20. Other .htaccess use cases <ul><li>Custom 404, 403 etc pages </li></ul><ul><li>Rewrites </li></ul><ul><li>Pages requiring auth and authz </li></ul><ul><ul><li>to use Oxford’s SSO system, WebAuth </li></ul></ul><ul><li>Redirect/RedirectMatch </li></ul><ul><li>Other, unanticipated requirements </li></ul><ul><li>Use SM to devolve config management in specific use cases, </li></ul><ul><li>e.g. to apply SSO protection to pages </li></ul>
  21. 21. Using SM to publish .htaccess <ul><li>Challenges </li></ul><ul><li>usability vs. utility: templates must be simple enough for users to understand and apply – checkboxes </li></ul><ul><li>multiple uses must be combined into one file </li></ul><ul><ul><li>One template with lots of unconnected config options? </li></ul></ul><ul><ul><li>Combine checkboxes added to existing templates? </li></ul></ul><ul><li>.htaccess needs its own channel – multiple file extensions can’t be published into the same directory </li></ul><ul><li>Media Library – ‘protected’ category + section with output uri </li></ul><ul><li>extensibility </li></ul>
  22. 22. Statutes and Regulations I: publishing multiple versions concurrently <ul><li>Old site publishes current versions of University legislation </li></ul><ul><li>An unusual new requirement: Future, Current, and Previous versions </li></ul><ul><li>Concurrency meant couldn’t use SM’s versioning system, as only latest versions are published </li></ul><ul><li>Duplicate Branch used to create new Version Releases below a specific Statute or Regulation parent section </li></ul><ul><li>‘ version’ templates hold version metadata </li></ul><ul><li>All versions are published as both webpages and in a single XML file </li></ul><ul><li>A webserver script queries the XML and writes out version statements and a version history page explaining the relationship between the different online versions </li></ul>
  23. 23. XML Output (simplified) <ul><li><statute number=&quot;XV&quot; subject=&quot;UNIVERSITY DISCIPLINE&quot;> </li></ul><ul><li><version release=&quot;2009-06-01&quot;> </li></ul><ul><li><title>College Contributions Scheme and College Accounts</title> </li></ul><ul><li><inforce>2009-06-01</inforce> </li></ul><ul><li><gazettehref></gazettehref> </li></ul><ul><li><gazettehreftext>Gazette Vol. 133. p 1335, 29 May 2009</gazettehreftext> </li></ul><ul><li><!-- statute contents --> </li></ul><ul><li></version> </li></ul><ul><li><version release=&quot;2009-01-01&quot;> </li></ul><ul><li><title>College Contributions Scheme and College Accounts</title> </li></ul><ul><li><inforce>2009-02-01</inforce> </li></ul><ul><li><gazettehref></gazettehref> </li></ul><ul><li><gazettehreftext>Gazette Vol. 130. p 1124, 18 Dec 2008 </gazettehreftext> </li></ul><ul><li><!-- statute contents --> </li></ul><ul><li></version> </li></ul><ul><li></statute> </li></ul>
  24. 24. Online version log page <ul><li>Statute XV: University Discipline </li></ul><ul><li>Version History </li></ul><ul><li>Current version , in force since [In Force Date] ([Gazette link text, linking to Link URL to Gazette]) </li></ul><ul><li>Future version , to come into force from [In Force Date] ([Gazette link text, linking to Link URL to Gazette]) </li></ul><ul><li>Future version , subject to the approval of Her Majesty in Council ([Gazette link text, linking to Link URL to Gazette]) </li></ul><ul><li>Past version , in force from [In Force Date] to [ next most recent In Force Date –1] ([Gazette link text, linking to Link URL to Gazette]) [most recent] </li></ul><ul><li>Past version , in force from [In Force Date] to [ next most recent In Force Date –1] ([Gazette link text, linking to Link URL to Gazette]) </li></ul><ul><li>Past version , in force from [In Force Date] to [ next most recent In Force Date –1] ([Gazette link text, linking to Link URL to Gazette]) [oldest version] </li></ul>
  25. 25. Statutes and Regulations II: publishing pages as ‘rolled-up’ content <ul><li>Legislation governing elections required content to be trackable at paragraph level </li></ul><ul><li>Each paragraph entered as a separate content item! </li></ul><ul><li>Also had a prescribed 6-level paragraph numbering scheme, e.g. Statute XXI, Part A, 1. (1) (a) (i) </li></ul><ul><li>After discussing 4 alternative methods with T4, decided to use the numbering scheme as the basis of the site structure hierarchy: </li></ul><ul><ul><li>usable for authors! – familiarity, re-numbering follow addition/deletion </li></ul></ul><ul><ul><li>inclusion in XML output made this available in a useful, structured way to the Elections Database </li></ul></ul>
  26. 26. Site structure hierarchy in SM <ul><li>> Statutes </li></ul><ul><li>> Statute XXI </li></ul><ul><li>> 2009-01-01 </li></ul><ul><li>> Part A </li></ul><ul><li>> 1. </li></ul><ul><li>> (1) > (a) </li></ul><ul><li>> (i) </li></ul><ul><li>BUT, sections no longer = pages ?? </li></ul>
  27. 27. ‘ Page’ template and ‘rollup’ nav object <ul><li>‘ Page’ template holds the ‘rollup’ nav object </li></ul><ul><li>The ‘rollup’ nav object includes all the paragraphs for a given page </li></ul><ul><ul><li>pulls in all content at and below the section it is in </li></ul></ul><ul><ul><li>follows the order of the Site Manager section hierarchy and the content within those sections </li></ul></ul><ul><li>‘ Page’ template can be added at any level of the hierarchy – so pages can be whole document or a part of </li></ul><ul><li>‘ Page’ template can’t be nested </li></ul><ul><li>Can specify alternative formatters to use at different levels </li></ul><ul><li>‘ Rollup’ nav object can also be used to generate in-page ToCs </li></ul>
  28. 28. Questions? ?