Importing content from other sources¶
There are various tools to help you import content from other systems into Plone
Rarely does a new website start all from scratch. Most of the time, you will have to import content from other systems. These may include:
- other CMS systems, sometimes based on PHP/MySQL
- legacy sites in plain HTML
- resources that exist on a filesystem, such as files and images
- other Plone sites, including older and unmaintained versions
While Plone even comes with an FTP service, that can serve as a last-ditch effort to get some pictures in, there are far more sophisticated tools available.
By far the most flexible tool available is something called collective.transmogrifier.
A transmogrifier is fictional device used for transforming one object into another object. The term was coined by Bill Waterson of Calvin and Hobbes fame.
In principle, what it does is to allow you to lay a 'pipeline', whereby an object (a piece of content) is transported. At each part of the pipeline, you can perform various operations on it: extract, change, add metadata, etcetera. These operations are in the form of so-called 'blueprints'.
In short: an object is gathered from a source you define. Then, it goes to one or more segments of the pipeline to let the various blueprints work on it, and in the end you use a 'constructor' to turn it into a Plone content object.
That's the basics, but by combining all your options you have an incredibly flexible and powerful tool at hand.
Various add-ons exist to make working with transmogrify easier:
- mr.migrator is a way to easily lay pipelines
- funnelweb helps to parse static sites, and crawl external sites
- parse2plone is meant to get HTML content from the file system into Plone
And a wide array of extra 'blueprints' exist, like
- transmogrify.sqlalchemy to get content out of just about any SQL database you can think of
- collective.jsonmigrator is good at migrating data via JSON format from very old Plone versions, going back all the way to 2.x