TechDocs/FellowshipHacks/Projects/Blog/ContentMigration

Blog content migration

This task is part of the FellowshipHacks/Projects/Blog project.

Goal

Find the way to migrate the content of the Fellows blogs from the current ez-publish platform to the new Wordpress MU platform.

People

People working on this task.

Volunteers are always welcome! Have a look at FellowshipHacks to know how you can help

Status

Last updated on: 090202

The migration procedure is based on exporting the blog content as RSS file from EZ and import it into WPMU. Since not all the information is exported from EZ, some data must be migrated from the EZ database to the WPMU one.

A migration route has been found for all components (posts, comments, tags, etc) and has been tested on all blogs.

Subtasks

TODO

DONE


Notes: discarded migration routes

Note: I've moved here the initial notes about other possible migration routes. These are no more relevant, since we've gone the RSS way.

Route #2: CSV

See Ivan s-h@ 081115.

Status

Ivan has installed one ez plugin to export in CSV, but it seems that only thing it can do is export from one database table.

Todo

Procedure

Route #3: EZ packages

Status

cri: I didn't try it, but I guess it could be useful to migrate other kinds of content: e.g. objects in Fellows home directories: create a package and upload it to the Fellow home page in the wiki.

Todo

Try it!

Procedure

(from the f-h@ archives)

  Via Administration you can create packages:
  http://ez.no/doc/ez_publish/technical_manual/3_8/features/packages
  these content object packages are tar.gz xml and Images etc.

Route #4: XML -> eXtended RSS

Status

Has anybody tried it?

Todo

cri: I would leave this as the last option, since it requires developing XSL code to transform EZ's XML into WP's XML; it's much more convenient for me to work with SQL...

Procedure

(from the f-h@ archives)

  The content in eZ can be exported as XML and then transformed into
  WordPress eXtended RSS.  eZ allows you to export all
  data as XML - transforming to another XML schema should be fairly
  straightforward.

  Reference:
  http://ez.no/doc/ez_publish/technical_manual/3_8/reference/modules/content

  But you can use the extension: http://svn.ez.no/svn/extensions/ezxmldesign/


Category/FellowshipHacksTasks

TechDocs/FellowshipHacks/Projects/Blog/ContentMigration (last edited 2016-03-21 17:50:53 by paul)