we started using OJS actively last year. One use case for our OJS is the publication of articles for OA-journals. As a library we can’t stop at the point of publication of a journal article or issue.
For the proper reuse of Metadata it is crucial to produce high quality Metadata. Many international efforts face this challenge right now (currently research data archiving systems or Campus Management systems) and tackle it with the
integration of unique person identifier systems. But if you are at the end of a chain, it is hard to identify authors. It costs us up to half an hour or even longer for journal articles per author and article to identify them, if even
possible. It is much easier, if you identify persons uniquely at the begin of the publication process, in OJS.
The solution is in my eyes the identification of authors in OJS at the begin and to deliver these via interfaces (OAI) to other systems.
Like mentioned, we plan to deliver the generated Metadata to our Shared catalog automatically. Currently we are doing this by hand, in the future we want to get harvested by the shared catalog system and maybe other harvester systems
(like BASE https://www.base-search.net/).
In Germany many norm data are maintained and are reused on national level. We use the GND person name data to uniquely identify authors. It is quite clear for us, that we are acting in an international setting. So it is not necessarily only one identifier system we know of and we have to reuse. Normally there is only one (or maximum two) person identifiers we catalog. The main point for us is, that there are unique identifiers for persons and to know the identifier system.
Concordances between these identifier systems, like VIAF, help to resolve them for the local context.
In my opinion it is not necessary to query the person identifiers in OJS, even if that would be very comfy
We would like to have one or maximum two additional fields, where one could specify which person name identifier system to use and the identifier itself. This identifier is also crucial for the export (for OAI harvesting). There might be
problems in the export, but as long as you do have the identifier system it is doable.
You mentioned that a Plugin might be a solution. Of course this keeps the main system neat. We are running repository systems for over 16 years now. We experienced many obstacles in the normal migration process with Plugins or
optional modules, which were developed outside the main branch. So maybe we are a bit conservative in the update policy. We want to keep up with the normal upgrade process of a software to not run into security problems and to be able to get the latest features available, if needed. So we would prefer to have a solution in the mainline of OJS. On the other hand: could you give us insights in the further development of OJS-plugins?