1. MIGRATION PLANNING Planning the move from Polopoly to Drupal Bruce Darby 10.7.2014

2. Polopoly content Currently in Polopoly – 309 web sites – 46,254 published pages Sites range from – Less than 10 pages – Greater than 7,000 pages

3. Web site complexity Need to map sites to releases – Dependant on functionality Site complexity ranges from – Single sites – Sites made up of 25+ sub sites Not just migrating sites – But also migrating people Identify interdependences – Online org structure and site dependences – Polopoly connections to other systems – Other CMS hosting content

4. Site audit Potential site moves mapped to releases – By functionality – By URL grouping Site sizeNumber of pages Count Small0-50175 Medium51-15069 Large150+65 Of the total number of sites: 166 sites have special HTML articles 94 sites have proxy content 60 sites have forms

5. Site audit ReleaseRelease date Earliest migration date No of sitesNo of pages R1 (Beta)Jul 14Aug 141121 R2 (MVP)Oct 14Oct/Nov 14 14 7 early adopters confirmed 708 R3Jan 15Feb 1542*5330 R4Apr 15May 15174*19949 R5Jun 15July 1577*20146 *These migration dates have not been confirmed with site managers

6. University Website Programme No. of sites MVM - 1 SCE - 7 SAS - 3 HSS - 2 CSG - 1 Potential migrants - TBC Sample migration planning chart MVP – Minimal Viable Product

7. Release phase 2 – Minimal Viable Product (MVP) MVP sites: MVM - The Dermatology Service SCE - Biochemistry, MSc Bioinformatics, MSc Biotechnology, MSc Drug Discovery & Translational Biology, Online postgraduate programmes in drug discovery, Synthetic Biology and Biotechnology, MSc Systems & Synthetic Biology, SAS - Communications & Marketing, Chaplaincy, Labyrinth HSS - CHSS web team, The Centre for the Study of Modern Conflict CSG - Printing Services Feb 2014 - Consultation started May 2014 - Migration time agreed June 2014 – Initial site migration support given

8. Migration planning Contact key site managers for releases 3 - 5 – Identify sub site relationships and dependencies Agree outline migration plan with managers – To December 2015 Migration plan completed – End of September 2015

9. Considerations for migration planning Functionality Site size Business cycle and priorities Availability Fit of bigger picture

10. Activity timeline for migration planning AugSeptOctNovDec Engage with site managers Complete draft migration planning chart Migration planning times agreed R2 Migration starts Jan Feb Engagement starts with R3 migrants R3 Migration starts Engagement starts with R4 migrants Beta release R2 releaseR3 release

11. Summary Key site managers will be contacted – Starting August 2014 Full migration plan – Completed end September 2014 Migration process with site managers – 3 months before agreed migration time