Hi Vitaliy,
I'm Monica Marziani from the development team at Archimede Informatica. Some members of our organization participated in the PKP Community Forum discussion about the future of this plugin for OJS 3.5 and beyond (forum thread).
Since we rely on JATSParser in production, we went ahead and ported the plugin to OJS 3.5. The port is currently running on our production instances and has been tested on OJS 3.5.0.4 / PHP 8.2.
The core parsing logic is unchanged. The work mainly covers PHP API migration (namespaces, Hook, Repo facade, class constants), the workflow UI rewrite from Smarty/Vue 2 to Vue 3, and a few library extensions.
We are aware that PKP is working on native JATS support, but given the uncertain timeline, we believe this port could be useful to the community in the meantime.
The code is in our private repository at the moment, but we are ready to make it available. If you're interested, we can follow up with full technical details, a detailed changelog, and discuss the best way to contribute (PR, fork, or however you prefer).
Best regards, Monica
Hi Vitaliy,
I'm Monica Marziani from the development team at Archimede Informatica. Some members of our organization participated in the PKP Community Forum discussion about the future of this plugin for OJS 3.5 and beyond (forum thread).
Since we rely on JATSParser in production, we went ahead and ported the plugin to OJS 3.5. The port is currently running on our production instances and has been tested on OJS 3.5.0.4 / PHP 8.2.
The core parsing logic is unchanged. The work mainly covers PHP API migration (namespaces, Hook, Repo facade, class constants), the workflow UI rewrite from Smarty/Vue 2 to Vue 3, and a few library extensions.
We are aware that PKP is working on native JATS support, but given the uncertain timeline, we believe this port could be useful to the community in the meantime.
The code is in our private repository at the moment, but we are ready to make it available. If you're interested, we can follow up with full technical details, a detailed changelog, and discuss the best way to contribute (PR, fork, or however you prefer).
Best regards, Monica