Hello,
I am currently developing an export plugin for OJS 3.4.x
The goal is to export articles alongside their metadata, as well as reviews, decisions, submission files etc. for long term archiving.
I am trying to take inspiration from existing plugins, as to not reinvent the wheel, but am struggling to reverse engineer the whole process.
Deployments
Many of the existing export plugins have “Deployment” Classes, i.e.:
NativeImportExportPlugin.php
NativeImportExportDeployment.php
I don’t quite understand what the Deployment Classes are for and how they are used. It seems like they store configuration information, but I’m not quite clear on when this information is populated and if it is necessary to have these classes.
Filters
Exporting seems to be handled by filters, which are registered into the Database and called in the plugins.
I can see that Filters are handy if stuff needs to be changed out, but is it necessary to use the complete infrastructure behind it?
I have found some documentation around Plugins and how to make them, but it is very superficial. Is there any more deep documentation?
Thank you!
Best Regards,
Karl Bodarwé