Crossref Reference Linking plugin – how to include references in XML for manual DOI deposit (OJS 3.5.0.3)

Software Support
1

Hello everyone,

We are using OJS 3.5.0.3 with PostgreSQL and Nginx , and we recently installed the Crossref Reference Linking plugin .

Our workflow does not use automatic DOI deposit . Instead, we:

  1. Generate the XML file
  2. Manually submit it to Crossref

After enabling the plugin, we are unsure if it is working correctly, because references are not appearing in the generated XML used for deposit.

Questions:

  1. Is the Crossref Reference Linking plugin supposed to automatically include references in the Crossref XML export?
  2. Is there any additional configuration required for references to be embedded in the XML?
  3. Does this only work with automatic deposit, or should it also work with manual XML generation?
  4. Are there specific metadata requirements (e.g., references entered in a specific field or format) for them to be exported correctly?

Current behavior:

  • Plugin is enabled
  • XML is generated normally
  • References are not included in the XML file

We would like to understand the correct procedure to ensure that article references are properly deposited to Crossref when using manual XML submission.

Any clarification or recommended steps would be very helpful.

Best regards,
Tarcisio Pereira

2

Hello @Tarcisio_Pereira …

Sorry for not having an answer to your question, but another question. I need to export the XML file to submit it to Crossref manually, but for some reason no XML file is generated.

I select the articles → Bulk action → Export DOI
But no XML is generated. Did you have to enable extra plugins or do something in the configuration to be able to download the files?

Thanks in advance

3

Hello @hilongo

No, I’m using the default installation only. I didn’t need to enable any extra plugins or special configuration for the XML export.

However, I also had some articles where the XML was not generated. In those cases, I had to investigate the server logs and fix them one by one.

Most problematic submissions came from a very old OJS installation. In many cases, the submission was still marked as being in the submission workflow stage while also being published at the same time — something older OJS versions apparently allowed.

Tarcisio Pereira