Changes between Version 18 and Version 19 of quintagroup.transmogrifier
- Timestamp:
- Dec 29, 2010 9:32:11 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
quintagroup.transmogrifier
v18 v19 1 1 = quintagroup.transmogrifier = 2 2 3 [[PageOutline]] 3 4 4 quintagroup.transmogrifier package was designed to enable content migration between Plone sites. Common task for quintagroup.transmogrifier package is migration of content from old Plone version to a new one.5 quintagroup.transmogrifier package provides easy Plone Migration Tool for migrating content from one Plone site to another. Common task for quintagroup.transmogrifier package is migration of content from old Plone version to a new one. 5 6 6 To perform its tasks, quintagroup.transmogrifier basically uses: 7 * [http://pypi.python.org/pypi/collective.transmogrifier collective.transmogrifier package] 8 * [http://plone.org/products/marshall Products.Marshall product] 7 Its functionality binds to Plone via portal_setup (!GenericSetup) import/export interfaces. This package overrides !GenericSetup ``Content`` step, so it can be used out-the-box to migrate site content. 9 8 10 Quintagrop transmogrifier functionality binds to Plone via portal_setup (!GenericSetup) import/export interfaces.9 To perform its tasks, quintagroup.transmogrifier uses [http://pypi.python.org/pypi/collective.transmogrifier collective.transmogrifier] package and [http://plone.org/products/marshall Products.Marshall] product. 11 10 12 You can manage import/export procedure by configuring pipeline and appropriate blueprints in collective.transmogrifier configlet, which appears after products installation. 11 quintagroup.transmogrifier package includes Plone blueprints for collective.transmogrifier pipelines that allow to: 12 13 * return queried items from the catalog 14 * create pipeline items from contents of Plone site folders 15 * walk through different !GenericSetup import contexts and yield items for every folder 16 * generate and parse manifest files - listings of objects contained in some foldere in XML format 17 * migrate properties for objects that inherit from OFS.!PropertyManager.!PropertyManager mixin class 18 * use context sensitive components (adapters) to do needed corrections in data generated in previous sections 19 * set references for content objects 20 * migrate comments for site content 21 * extract data from Archetypes file fields 22 * apply stylesheet to some XML data stored on item. 23 24 You can manage import/export procedure by configuring pipeline and appropriate blueprints in quintagroup.transmogrifier configlet that appears after products installation. 13 25 14 26 == How-to Guides on common Use Cases == … … 24 36 * Releases - http://plone.org/products/quintagroup.transmogrifier/releases 25 37 * PYPI - http://pypi.python.org/pypi/quintagroup.transmogrifier 38 39 == Note == 40 41 quintagroup.transmogrifier package was primarily developed for allowing content migration from Plone 2.1 to Plone 3.2 website. The principle of content migration between sites of different Plone versions is that you have to create buildouts for old Plone 2 site and new Plone 3 site. These buildouts should include several extra packages, since transmogrifier tool is used for Plone content migration.