Transmogrifier is a powerful tool for creating transformation processes called “pipelines”.
Transmogrifier gives you the tools to create and share these pipelines but doesn’t provide
an easy way to run the pipeline. Mr.migrator aims to bridge that gap.

Mr.Migrator provides the following:

A buildout recipe with you can override a given pipeline and will also create a
the commandline script to run the pipeline.

A commandline script with help which lets you run pipelines and see their progress. This
is useful used in conjunction with transmogrify.ploneremote or other blueprints which
don’t need expect to be run inside the Plone process.

A Plone plugin which when installed lets you pick which pipeline you want to run,
provides a form to override the pipeline options and then provides progress on the running
pipeline. This is useful when you want to use plone.app.transmogrifier blueprints
which expect to be run inside the Plone process.

A pipeline is a concept from collective.transmogrifier where dictionary items pass there a series
of steps, each adding, removing or uploading information to an external source. A pipeline
is configured in configuration file using the INI style syntax. Mr.Migrator lets you run either
pipelines you built yourself, or

Pipelines are organised as a series of steps through which crawled items pass before eventually being
uploaded. Each step as one or more configuration options so you can customise import process
for your needs. Almost all imports will require some level of configurations.

The first part of each configuration key is the step e.g. crawler. The second part is the particular
configuration option for that particular step. e.g. url. This is then followed by = and value or values.

The configuration options can either be given as part of the buildout part e.g.

You might need to insert further transformation steps for your particular
conversion usecase. To do this, you can extend a plugins underlying
transmogrifier pipeline. mr.migrator uses a transmogrifier pipeline to perform the needed transformations and all
commandline and recipe options refer to options in the pipeline.

If you have decided you need to customise your pipeline and you want to install transformation
steps that use blueprints not already included in mr.migrator or transmogrifier, you can include
them using the eggs option in a mr.migrator buildout part

Some transmogrifier blueprints assume they are running inside a Plone
process such as those in plone.app.transmogrifier (see http://pypi.python.org/pypi/plone.app.transmogrifier). mr.migrator
doesn’t run inside a Plone process so these blueprints won’t work. If
you want upload content into Plone, you can instead use
transmogrify.ploneremote which provides alternative implementations
which will upload content remotely via XML-RPC.
transmogrify.ploneremote is already included in funnelweb as it is
what funnelweb’s default pipeline uses.