Dual language journal

We are definitely interested in leveraging ORCID as the standard for author name disambiguation.

With regard to transliteration of names, we are planning on putting the weight of this on the authors and/or editors, rather than depending on an external Authority source.

User “Manoj Shyamalan” might elect to add a published-as name of “M. Night Shyamalan”, and might clarify for APA citation purposes that he wanted the name to appear as “Shyamalan, M.” if the default was “Shyamalan, M. N.”.

This has not been officially scheduled. I would anticipate this being added to the Pitt ULS’s development priorities for 2017, but don’t have a real timeline.

Hi @ctgraham,

Are there any news concerning proper name internalization. Has it been scheduled? Could we track it somehow? Thanks!

This is not currently scheduled. One of the next steps is enable longer locale names · Issue #1911 · pkp/pkp-lib · GitHub where we introduce script variants into locales. The differences of script variants will be one of the distinguishing characteristics of internationalized names.

1 Like

Hi @ctgraham,
Sorry for reminding, but is there any hope that name internationalization would be scheduled? The issue above seems to be closed now.

Hi @Ph_We,

The above issue is to allow encoding to be specified as part of the locale name, permitting the same language to be used in multiple encodings (e.g. Serbian in both Latin and Cyrillic). That was merged and will be included in OJS 3.1.

As for multilingual author names, this is still a priority for us and will be addressed in a future release. It hasn’t been scheduled specifically yet, however.

Regards,
Alec Smecher
Public Knowledge Project Team

1 Like

OJS 3 is not suitable at all for journals that publish articles in two languages. What are the technical arguments that do not provide a possibility to input in metadata the author’s name and References in the second language? Just do in the same way as title, affiliation etc.

Article landing page has 1 URL for different languages. And that had been the biggest problem for our multilanguage journal until we solved it.

I don’t think Google Scholar will index 2 different meta-data that are on the same URL.

@Vitaliy I like your solution using subdomains as a language prefix for multi-language OJS sites.

Probably, it would be good to have some sort of relation visible between the article landing pages across the language subdomains. There does not appear to be a standardized link relation for translations, however.

Do you have a public OJS site where this is already rolled out and you could see the result of this change in terms of Google Scholar indexing?

I had made appropriate modifications of google scholar and DC plugin only a few days ago. So, need to wait several weeks to see the changes in indexing. For now, 2 languages are indexed only in Google.
Our site:

Let’s first make OJS 3 working with DUAL LANGUAGE metadata (author’s names and references)! I agree the indexing is important but …

1 Like

Hi @ojsbsb

Now Google Scholar have started to index our 2 locales, i.e. part of our articles appear there 2 times - in Ukrainian and English with appropriate linking. Think, shortly all of content will be indexed this way.

1 Like

I am sorry to say this, but as far as I remember, Google Scholar does not allow to index multilingual metadata. And it is official :frowning:

So even if you have 2 different sets of metadata on 2 URLs, their crawler either randomly picks ONE set of metadata in ANY language, or may index both, but those would be TWO DIFFERENT descriptions/publications in Google Scholar (i.e. unconnected) :weary:

So those modifications to the plugins you did might be theoretically detrimental for indexing and any SEO purposes.

I might be mistaken, but @asmecher might have discussed this issue with them.

In our case, it’s like having two distinct sites. One for each subdomain. Google Scholar indexes both separately.

It worth to note that we have made one journal title for Ukrainian and English. So if one enters our journal’s name in Google Scholar, he/she would see all of our articles from 2 locales.

Yep, something like that. But still two descriptions in two languages would remain unconnected. One journal title for Ukrainian and English should be OK, but one PDF for two metadata sets may not be OK, since the crawler would choose the metadata set it would find first. So if you have two different PDFs for those two metadata sets, that would be good too.

All meta-data an exposed on article detail page. Galleys don’t have them. Moreover, few lines of code and PDF, XML links will point to the appropriate localized galleys.

As I said, we have adopted different URLs to our locales, including links to the galleys.

It is just a matter of adding if loops to the Google Scholar plugin. As an example for the article title:

if ($subDomain == 'some_subdomain') {
            $templateMgr->addHeader('googleScholarTitle', '<meta name="citation_title" content="' . trim(htmlspecialchars($article->getTitle("uk_UA"))) . '"/>');
        } else {
            $templateMgr->addHeader('googleScholarTitle', '<meta name="citation_title" content="' . trim(htmlspecialchars($article->getTitle("en_US"))) . '"/>');
 }

or it can be managed with AppLocale class, like below, for PDF links:

 if (is_a($article, 'PublishedArticle')) foreach ($article->getGalleys() as $galley) {
          if (is_a($galley->getFile(), 'SupplementaryFile')) continue;
          if ($galley->getFileType() == 'application/pdf') {
              if ($galley->getLocale() == AppLocale::getLocale()) {
                  $templateMgr->addHeader('googleScholarPdfUrl' . $i++, '<meta name="citation_pdf_url" content="' . $request->url(null, 'article', 'download', array($article->getBestArticleId(), $galley->getBestGalleyId())) . '"/>');
              }
          }
 }
1 Like

Dear friends,
I indeed need OJS with multilingual author/user names, so I spent some amount of time to study how other multilingual field are treated. As a result, I did some modifications of the code, which allows me the following:

  1. Regiser/add/modify user with multilingual name
  2. Go through all submission process with multilingual author names
  3. Correctly show the corresponding metadata on the frontend page in the current language
  4. Search authors in different locales
  5. Provide localized names in OAI interface
    Of course, this potentially breaks other functionality (import/export, various plugins etc.) but as a starting point is quite satisfactory for my meeds.

I would be glad to share my work, but I am not sure how to do it the best way. I am not very much familiar with github, so I need an advice if my work is intersting for somebody else.

I use OJS 3.1.0

Regards,
Vasyl