TERMINALFOUR t44u 2009 - University of Oxford Case Study
•
0 recomendaciones•710 vistas
The document summarizes the implementation of the Site Manager content management system at the University of Oxford. It discusses migrating over 70 university websites to Site Manager, challenges faced, special projects like statutes and regulations that require unique solutions, and overall satisfaction with the Terminal Four software and support.
![Implementing Site Manager in UAS at University of Oxford Tony Stark – Project Manager [email_address] Ruth Mason – Technical Lead [email_address] November 2009](https://image.slidesharecdn.com/14terminalfourt44u2009-universityofoxfordcasestudy-111201061423-phpapp01/85/TERMINALFOUR-t44u-2009-University-of-Oxford-Case-Study-1-320.jpg)
![The University ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],t44u 2009](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Más contenido relacionado
Destacado
Destacado (20)
Similar a TERMINALFOUR t44u 2009 - University of Oxford Case Study
Similar a TERMINALFOUR t44u 2009 - University of Oxford Case Study (20)
Más de Terminalfour
Más de Terminalfour (20)
Último
Último (20)
TERMINALFOUR t44u 2009 - University of Oxford Case Study
- 1. Implementing Site Manager in UAS at University of Oxford Tony Stark – Project Manager [email_address] Ruth Mason – Technical Lead [email_address] November 2009
- 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
- 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+
- 16. Pilot site – Occupational Health t44u 2009
- 28. Questions? ?
Notas del editor
- Apologise for bullet list slides and lack of demos
- Aim to re-use components on other sites, so built to be generic not for this site only.
- Point out the version sections under ‘Statute’ parent Point out that version release and inforce values can be the same or different – the bottom one was first published as a ‘future’ version, the top as a ‘current’ version Script compares today’s date with version release date to version currency status information
- Output of webserver script. Runs when page is called – always fresh, doesn’t need to know if a publish has just taken place, or if an update has been made: stateless Version links and field values are populated from the XML file (authored in the version template), other text is hardcoded in the script and written out directly by it Two anecdotes on Her Majesty in Council to illustrate Oxford context: Jim + script, T4 + Oxford queen?
- Not nesting pages is hopefully intuitive to users