You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
> This documentation is deprecated. Only the parts for Morph are still current. For the new documentation see: https://github.com/metafacture/metafacture-documentation
Metafacture comprises three main parts: Framework, Morph and Flux. It can be extended with modules.
Metafacture comprises three main parts: Framework, Fix (or Morph) and Flux. It can be extended with modules.
# Framework
The framework includes the interfaces and abstract classes which form the foundation of the data processing pipelines. This part of Metafacture is only relevant for you if you plan to use Metafacture as a Java library or if you wish to add pipe elements to Flux.
For more information see the [[Framework User Guide]].
# Fix
Fix is the transformation module and recommended instead of using Morph: https://github.com/metafacture/metafacture-fix#metafacture-fix
# Morph
Morph is the original transformation module and it is recommended to use Fix instead of Morph.
Metafacture Morph or short Metamorph is a domain specific language for metadata transformation. The Metamorph object performing the transformation is used as part of a processing pipeline. If you are using Metafacture as a Java library, just create a `Metamorph` object and add it to your pipeline (see also the [[Framework User Guide]]). If you are using the Flux scripting language to build and run pipelines, use the `morph` command.
The transformation itself is declared in XML. For more information on how to declare transformations see [[Metamorph User Guide]].