handbook import and export is handled by classes in the handbook app since there is no system to extend the repository import/export classes for the moment.
handbook import/export does not only handle the content-objects themselves, but also
- all the alternatives for the content-objects (linked through the contextlinker)
- all the metadata
- the medatadata scheme and properties used
for now the only possibility is import "*new*" co's, where a handbook and it's children will only be imported when it doesn't exist yet on the system, but 2 extra possibilities will be implemented
- extend: if a handbook already exists but the importf-file contains more children, extra metadata or extra context-alternatives they will be added. existing co's will be left untouched
- full-update: extend + when content of existing co's has changed it will be updated with the content from the import-file.
these extra features should be implemented and when import/export has been refactored, the code should be moved to the appropriate place.
for now you should not import/export handbooks in the repository but directly in the app.