Overview
Background
Project UWP007 deals with the Polopoly upgrade from version 9.16.1 to 10.0 FP5. UWP006 deals with the migration from Polopoly to the Drupal CMS. The final migration from Polopoly to Drupal will see all relevant data and data structures move to the new CMS.
This project has been commissioned to mitigate any editorial, compatibility or data structure issues that may arise when migrating between current versions of our systems and our new installation of the Drupal CMS. The project will also consider the best method for completing the migration, making sure that the content owners are utilising the new CMS as it was intended.
Scope
This project is closely related to UWP006 as the migration process delivered here will feed directly into the Drupal project. The migration process delivered will also be reviewed as part of the UWP006 project. Therefore a collective decision has been made to run this project where possible in an agile manner to match UWP006.
The consequence of this is that all stages after the initial Planning and Analysis will be run in an Agile manner. The Analysis phase will be used to gather information for the creation of High Level User Stories.
UWP009 will thoroughly analyse the data structures held within Polopoly and compare this to Drupal structures for migration purposes. This will build on and use the functionality developed in project uwp005 – using the BOXI reports to help understand in more detail what content, images, documents, structures, users, workflows, etc. make up websites in Polopoly.
Major points of analysis will include –
- The way the data is held structurally in both Polopoly and Drupal. (Include Content type, field data etc)
- The Analysis should look to highlight any relevant features of the current system that may have been overlooked and feed them into UWP006
- With reference to mappings for content, should we automate the export/import of content from Polopoly to the new CMS, and if so by what means can we achieve this?
- In the original Drupal prototype project what did they envisage using for the automated migration from Polopoly to Drupal? Did this include XML export to help with automating migration of content?
- Design any identified export/import process, and potentially implement some/all of this depending upon the complexity.
- Consider the role of the content owners and whether the migration should be delivered (whether in part or as a whole) by the users.
- The principle is to have content owners using the new Drupal system as the UWP team intend.
- Stocktake any currently outstanding issues within Polopoly.
- Process and training documentation to be put in place to cover any editorial or development steps required to be taken by users and developers of the system.
- A communication plan to end with the acceptance of the new system and successful closure of the project.
*******There has been a scope and budget increase to perfom additional BOXI report development. This is reflected in the following PICCL (28th March 2014) ********
Objectives
- To have content owners using the new Drupal system as the UWP team intend
- To this end the migration process must be clear and simple to follow for content owners.
- This project should eliminate or document any current unknowns that will impact on the migration process from Polopoly to the Drupal CMS.
- All content will be analysed for potential conflicts with the new CMS and potential opportunities to mitigate the pain of migration will be taken through modifications of our current data structures either in Polopoly or at the intermediate ‘Middle Station’ before the data is sent to Drupal.
- This project will provide comprehensive knowledge of migration and compatibility issues then feed them into future migration plans
- The project will facilitate end users and developers in any changes required
Deliverables
- A timetable of actions that will dovetail with projects UWP006 and UWP007
- Analysis of the current data structures by developers familiar with Polopoly and Drupal.
- A working method that dovetails with the Agile UWP006 project.
- High level stories for the systems and content owners after analysis allowing for a complete migration picture to develop through the project stages.
- If necessary a well-tested communication plan for content owners to assist them through the migration process.
- A record of the system side data changes to be completed in any migration process and a tested method for doing so.
- That our content owners migrating to Drupal are using the system as intended by the UWP Team
- A final migration process will be delivered to the UWP006 project for review.
Benefits
- A well-executed editorial migration will greatly assist the delivery of our enhanced CMS service.
- Competent migration will also enhance confidence which will assist future migrations.
Success Criteria
UWP006 will review the migration process delivered by this project.