The ROR plugin of OJS 3.3 (and 3.4) is compatible with the ROR core functionality integrated in 3.5? The data of the ROR plugin in 3.3 can be transfered to OJS 3.5?
I suppose that the answer is yes, but I wanted to check before investing time in adding RORs in OJS 3.3. I think that the 3.5 version have more and better functionalities than the plugin, but if the data can be transfered, it is more than OK for me.
We are in OJS 3.3.0.21, we will update to .22 next month. We are planning to move to 3.5 maybe in the summer of 2026. We have not installed the ROR plugin yet.
We are now mannually updating and activating the DOIs from our journals modifying the XML file exported by Crossref Plugin in order to add the affiliations and send them to Crossref, since affiliations cannot be exported in this plugin in the OJS 3.3 version.
If all the work we are doing now to search the RORs for the affiliation could be added to the metadata stored in OJS, and it can continue in the future, it will be wonderful.
The plugin is maintained by someone very close to PKP, and there’s no branch for 3.5 on the plugin’s repository. I’ve just skimmed the migration code, but I’m 99% sure your needs are covered.
ROR functionality has been moved into core in 3.5 and there is an upgrade script that takes care of the author affiliation data into the new structure. But, first now I see, that we check/search for the RORs again in the migration script, considering the affiliation setting and not considering the saved rorId setting. That should lead to the same results – having the same RORs for an author – because in the plugin if ROR is found both will be saved, affiliation and rorId but… I maybe need to think about it again… Will then come back…
