You need to specify tree arguments when running the script:
- id or identifier of the content class of the source objects
- id or identifier of the content class of new objects
- id of the node where new objects will be placed under
Attributes of the new objects are filled in based on a matching
attribute identifier and a matching datatype in the original object.
If no attribute matches, the script will issue an error and
shutdown.
Not all datatypes are currently supported. Non-supported datatypes
include ezidentifier and ezuser.
Future enhancements:
- option to delete source objects
- support for ezuser (only when source object gets deleted)
- re-use the nodes of the source object (only when source object gets
deleted), or place at the same location as the source object (the
third CLI argument will become optional)
- take over remote id from source object (only when source object gets
deleted)
- more filters to select source objects
People interested to contribute to this project can contact me at .
Please discuss and post any bug reports in this forum topic: