Hi,
since upgrading to OJS 3.2.0.2 we have the weird problem that the DOI of entires issues of our journal resolves without problems, but the DOIs of the individual articles do not. (2020: Special Issue 7: Narratological Perspectives on Premodern Japanese Literature | Beiträge zur mediävistischen Erzählforschung )
Contact with Datacite did not yield results as everything appears to be installed correctly.
Has anyone else encountered this phenomenon? Any advice?
Thanks in Advance
kim
Ph_We
September 7, 2020, 12:21pm
2
What status do those articles have in the CrossRef XML Export Plugin?
Are you sure Datacite is appropriate for your journal? It is intended for registering datasets .
For journal articles we usually use Crossref per se .
primozs
September 7, 2020, 12:23pm
3
Their status is not delivered.
the reason we’re using datacite is that the German resolving service uses datacite. And up to the upgrade that worked well.
We’re not actively depositing our articles, never have. It happens automatically. Or used to.
Ph_We,
as an afterthought: our “provider” does of course work with CrossRef, getting the prefixes from them etc.
Regards
kim
Hi Primož,
I once more checked our export settings, and they all look correct to me.
Thanks
kim
Ph_We
September 8, 2020, 3:20pm
8
I think, this might really be related to your upgrade. So you might want to check your PHP-log. Something like this (?):
opened 10:16PM - 27 Mar 20 UTC
closed 10:20PM - 27 Mar 20 UTC
See https://forum.pkp.sfu.ca/t/call-to-a-member-function-savexml/59533.
For C… rossRef, the export gives the following fatal error:
> PHP Fatal error: Uncaught Error: Call to a member function saveXml() on null in D:\xampp2\htdocs\classes\plugins\PubObjectsExportPlugin.inc.php:372
Thanks Ph_We, I’ll look into that.