Multilanguage references

Hello. How can I make multilingual references?
I set multilingual=true for the “submission.citations” tag in submissionMetadataFormFields.tpl and got two fields for references in the submission form.
But the data entered in these fields, is not displayed correctly in the article preview. Maybe I need to change some script, that parses the output of the links on the page. OSJ version

Hello and welcome to the forum!

Can you share more detail about the result you were expecting vs. what you got? Do you mean like the links are broken or something? More detail or a screenshot would be helpful for sure…

I’ve not worked with a journal that collects a separate references list before so I want to be sure I understand…
Are you getting authors who are submitting an article in one language to submit two lists of references, one in the language of the article and one translated list? Not sure I understand what you’re hoping to achieve with the two lists…

Also I don’t think submission.citations shows up in submissionMetadataFormFields.tpl? (I looked up your version to be sure! ojs/templates/submission/submissionMetadataFormFields.tpl at stable-3_3_0 · pkp/ojs · GitHub)
As far as I can see it only shows up in workflow.tpl, authorDashboard.tpl, and article_details.tpl
So I’m not entirely sure where you’re changing these settings…? Apologies if I’m just missing something!

In case it’s useful I’m going to link these docs for reference for handling multilingual metadata in case you are dealing with more than just the reference list in a second language:

And these docs about extracting citations and CrossRef:

And this is more general/high-level but a recent webinar from PKP about multilingual publishing in case you haven’t seen it, maybe mostly things you already know but I learned some things! :slight_smile:

When adding an article, some metadata (abstract, keywords, etc.) can be entered in several languages:

In the published article, depending on the selected language of the site, the data is displayed in the corresponding language. It is necessary to enter and display references depending on the selected language. For this purpose, in the form submissionMetadataFormFields.tpl put the parameter multilingual=true for the tag “submission.citations”:

As a result, two input fields for reference appeared:

However, after entering and saving them, they are displayed incorrectly in the article data:

And they are also displayed on the site regardless of the selected language. Perhaps it is necessary to write or edit a script that parses data by language. I would like to know where to look for this script and is it the right way?

Hi! I’d be surprised if you needed to do any extra scripting, just because there are so many multilingual OJS journals, but maybe I am still misunderstanding the problem…

I found this journal that’s also both French and English, and includes references – is this sort of thing what you’re imagining?

When you enter metadata in multiple languages, it is entered in the original language and translated. When you change language of the site, the metadata title and its contents change. (example from the link above)


For the references, only the title is changed, because the content can be entered in one language.


It is necessary to change the contents of the references from the selected language. I assume to edit the form of entering the references for this purpose and write or edit a script that parses data by language. I would like to know where to look for this script and is it the right way?

Hi @xDrakarx,

Have you run into this issue?

There’s a discussion of whether/how to make reference lists multilingual, but on balance I’m not sure it’s a good idea – it would be easy to enter lists of different lengths, and hard to make sure each entry corresponds with a pairing in another language.

We’re working with a 3rd party who is contributing a plugin to manage and enrich reference lists using PIDs, and that might be a better approach; watch for the plugin to hit the plugin gallery in the next few months.

Alec Smecher
Public Knowledge Project Team