We are pleased to inform you that an MVP version of the Dataverse plugin for OPS 3.x is now available.
For this initial MVP version, the aim was to reimplement the plugin based on the version for OJS 2.x. This MVP version only works for OPS. We intend to make it compatible for OJS in future releases – any help is much appreciated!
Given that the task here was to make a new implementation of the plugin, we didn’t worry about making adaptations, but considering how much OJS has changed, a few adaptations may be needed, such as Supplementary Files from OJS 2.x that have been replaced in favor of a list of customizable components.
We would like to request feedback from the community before we can move forward.
We list below our main points of attention. We would welcome your feedback.
How should the interoperability of metadata between OPS/OJS and Dataverse behave? Currently, the metadata is copied over to Dataverse once the submission to OPS/OJS is completed, but metadata changes in OPS/OJS or Dataverse will not reflect in either of them.
Is that the expected behavior, or should metadata be updated if there are changes? If yes, when is it the best time to do it: as soon as it’s changed in either one of them or only if/when submission gets accepted?
Currently the datasets uploaded via OJS/OPS are transferred to Dataverse but a copy remains in OPS/OJS available for download at the user interface, as components of the preprint. Is this the expected behavior or should we center it all on Dataverse? If not, how should we deal with extra large file uploads (can OPS/OJS handle it?)? What about versioning or file edits?
Given that the data and metadata duplicity brings a great deal of complexity to the OJS/OPS integration with Dataverse, we recommend that this should be avoided.
With this approach, Dataverse would be the only source of information about the datasets. Any operation that changes the state of these resources should be forward to Dataverse. In this way, we intend to make the integration loosely coupled, referencing the resources held in the Dataverse with links, and replicating as little information (data or metadata) as possible in OJS/OPS.
Previously published research data
While we think it is important to maintain the integration with Dataverse, allowing the submission of research data via OJS/OPS along with the manuscript submission process, another change from the original plugin that we would like to have is to be able to receive research data that is previously published in other sources (either a different Dataverse than the one that is linked to the OJS/OPS installation, or a different system altogether, like Zenodo). Eventually, a submission can also have research data from more than one repository.
Allow the authors to inform links to other datasets published in different data repositories.
This initiative is being led by SciELO Brazil as part of its strategy to adopt Open Science practices to the global research communication workflow. The development is being executed by Lepidus. Once again, we appreciate any volunteers that would like to participate.
You can learn more about the current state of this development by watching the presentation that Lepidus made about the plugin in November at the Open Publishing Fest 2021: