Crossref export plugin does not export the data in the original language


In OJS, when manually exporting Crossref to XML does not export the data in the original language.

Our magazine works with 3 languages (en, en and es) and it is necessary to export the Crossref XML in the original language of the article.

For example: have a definite article with Language in Portuguese (Indexation), time to export the title is in English.

Another thing is that the summaries of articles, both Portuguese, Spanish and English are all in English.

I tried to change the OJS language to Portuguese before exporting and yet the title is in English.

Thank you for your help.


Hi @tiago_agostinho,

I wonder if the submission locale is English. During the submission process, the author should be able to choose what the submission language is. The quickest way to check would be to look at the articles table and see what the locale column is set to for the submissions you’re trying to export.

Alec Smecher
Public Knowledge Project Team

Hi @asmecher,

thanks for the answer.

I did as suggested and really the article locale that should be pt_BR, was in en_US. I made the change and at the time of generating the XML the title was correct.

However, the abstract continues to export in English. Analyzing the OJS code in ojs-2.4.8\plugins\importxport\crossref\classes\, line 341, I saw that the abstract language has reference to the journal’s primary language ($journal->getPrimaryLocale()).

The correct would not be the abstract to have the article locale.



Hi @tiago_agostinho,

Have you modified your installation of OJS? I don’t see the code you quote at the location you specified.

Alec Smecher
Public Knowledge Project Team

This is probably one of the biggest problems of OJS :slight_smile: We dont have one data in metadata: original language.
It is very embarrassing - example:
Primary location of my journal is Polish
Original text of my article is French
Additional file with the text in English
And…. metadata (title, abstract, keywords) in German, English, Polish and French…… :slight_smile:
I dont have information that the French language is the language of the original.
Now, I register DOI and export metadata
If started to develop metadata from the Polish language I will have Title in Polish and Abstract in Polish
If I started from English – I will have Title in English and Abstract in Polish

/* Titles */
$titlesNode =& XMLCustomWriter::createElement($doc, ‘titles’);
XMLCustomWriter::createChildWithText($doc, $titlesNode, ‘title’, $article->getTitle($article->getLocale()));
XMLCustomWriter::appendChild($journalArticleNode, $titlesNode);

/* Abstracts */
if ($article->getAbstract($journal->getPrimaryLocale())) {
$abstractNode =& XMLCustomWriter::createElement($doc, ‘jats:abstract’);
XMLCustomWriter::createChildWithText($doc, $abstractNode, ‘jats:p’, String::html2utf(strip_tags($article->getAbstract($journal->getPrimaryLocale()))));
XMLCustomWriter::appendChild($journalArticleNode, $abstractNode);
and where information about the original ?
The same problem occurs when WorldCat downloads metadates…

Hi @karwas,

This is tricky – we’ve tried to figure out a multilingual model that works for most of our users, but there is very little agreement in how multiple languages should be handled amongst the various other systems we interoperate with. Many of them have only come recently to support multiple languages at all, and some still don’t. For the moment, our base assumption is that each submission will have a single language in which the required fields are available. That way there will always be a known way in which article titles and abstracts, journal titles, etc. will always be presentable. Overall that assumption has worked well for us – in your case you may need to make some site-specific adjustments.

Alec Smecher
Public Knowledge Project Team

Joining the discussion… We have a similar problem at where articles are mostly both in English and Croatian (primary language being Croatian), but we would like to export metadata to CrossRef in English for visibility. Is there a way to force the CrossRef plugin to do this?

Kind regards,

Hi @jmvezic

No, currently there is no generic way to do that – currently we only export/consider one language for the metadata export, so it would need an option to select preferred language the metadata should be exported into. I will double check with Crossref how the metadata in different languages could be registered and how they deal with that in general. Else, you could eventually do some code modification for your installation, if that is what you would like to.


Hi @bozana,

Is there some possible way to export metadata in all languages available?

Tarcisio Pereira.

CrossRef is considering adding support for multilingual metadata, if this is important for you, please upvote it here: Trello

It’s sad the multilingual metadata in OJS appear to be only for human consumption – it doesn’t seem to be indexed by Google nor deposited in CrossRef.

Related posts:

Hi @fgnievinski,

I’ve noticed that you’ve posted on this on several older posts drawing attention to this issue. Please note that we discourage cross-posting on multiple topics (see here: Forum Guidelines and Code of Conduct - under “Keep the forum tidy”). A better approach would be to start a new topic and post your comments there - please be mindful of this when posting in the future.

Best regards,

PKP Team