Is Scopus/Crossref Plugin compliant with Scopus policy?

Hello there!

I installed the Scopus/Crossref Plugin on my OJS 3.3.0-6. I setted it with Scopus’ API and I customized its look with some css. It works very nice.


But in Scopus’ Developer Portal I read they ask to observe some condition. For example:

  • Scopus cited-by counts/images must link to corresponding Scopus abstract page as described in the Scopus Attribution Guide

Unfortunately the only link in the plugin is the doi in any single references, but it redirects to the related article and it doesn’t concern Scopus. The plugin isn’t editable for each page in which it appears, and so it’s virtually unusable.

Did I misunderstand some point, maybe? What’s your experience with this plugin? What should I do to be policy-compliant, in your opinion?

Thanks for reading

1 Like

Maybe @RBoelter can tell me something more about this question? Sorry if I disturb you but I just noticed the plugin credits. Thanks in advance for your great job with this plugin!

Best regards,

chapter 1.3 in the “Scopus Attribution Guide” it says:

1.3 Cited by counts and other metrics or metadata
When Scopus cited-by counts and other metrics or metadata (such as title, author names, etc.) are displayed:

  • Scopus must be mentioned as the source of data on each individual web page where Scopus data appears.
  • If multiple cited-by counts are displayed (e.g. PubMed, CrossRef), Scopus citation counts must be clearly labeled and linked to the corresponding list of citing documents on at all visible instances.

The question is, what exactly means " *Scopus must be mentioned as the source of data on each individual web page where Scopus data appears."? There is a logo of Scopus, which (I guess) implies that it is mentioned, but I am not a lawyer.
The second bullet point doesn’t seem to be that important to you, because it looks like you only use Scopus as citation service. I might add the Scopus/Crossref logos for every single citation in the citation list in the next version to solve this.


In our publication repository (see Third party data in footer at ), we do as recommended by Scopus: “Scopus citation and affiliation data is powered by Scopus Search API” - having something similar in the footer of a journal would be task of the respective journal manager. On the item level, where we indicate the citation count, we link back to the Scopus record using Scopus® as link label, see e.g. Stress, dyadic coping, and relationship satisfaction: A longitudinal study disentangling timely stable from yearly fluctuations - Zurich Open Repository and Archive or screen shot. That (and storing the URL of the Scopus record) should be task of the plugin (which also displays Crossref citation counts, as I understand).


Thank you very much @RBoelter and @mpbraendle to fuel the topic.

I think that we can consider the plugin compliant if:

  1. It clearly mentions the source of data (the approach of third party data suggested from @mpbraendle is clever, but even the actual plugin’s job is ok).
  2. It includes a link “to the corresponding list of citing documents on”, as we read in the Scopus Attribution Guide.

I’d like to add this link to the features of the Scopus/Crossref Plugin. I spent some hours today trying to do it by myself, but my knowledge of php is limited and I failed. I share some notes to help anyone who want try it.

The file citations/classes/ includes the function getScopusCitedBy. It calls this url:


The result page (in the following screenshot) is used to take eid and citedby-count values.


BUT if we call this other url instead, we will obtain more info:



In particular, we will read the same eid and citeby-count values and, in addition, the URL of scopus-citedby page, that one we should link back.

In my example, for the doi 10.3280/ecag1-2021oa11549, it’s:

Then I tried to catch this URL automatically with a function, but I failed loudly. I paste it below humiliating myself just to demonstrate my good will. :clown_face:

	public function getScopusPageUrl($doi, $apiKey)
		if ($apiKey == null || $apiKey == '' || $doi == null || $doi == '') {
			return array();
		$url = "".$doi.")&httpAccept=application/xml&apiKey=".$apiKey;
		$xml = simplexml_load_string($data = $this->getAPIContent($url));
		$pattern = '/<link ref="scopus-citedby" href="([^"]*)/';
		preg_match($pattern, $xml, $matches);
		$scopusPageUrl = $matches[1];
		return $scopusPageUrl;

Would anyone deal with it?

Dear Michevole, I have installed the same plugin, but to me only Crossref is working, you can showed the code used in CSS, the key API was ubicated in the box Scopus Key API but don’t work.

Hi @czuniga, sorry for the delay in replying.

Actually the css code is just for the appearance. I can share it, but it’s not involved at all in the process and it doesn’t solve your problem.

.item.citations-container::before {
  content: 'Cited by';
  font-weight: 700;
  line-height: 1.2;
  display: block;
  padding: 3.5rem 0 1.5rem

.citations-count img {
  width: auto;
  height: 1.5em;

.citations-count {
  display: block;
  grid-template-columns: unset;
  text-align: left;

.citations-count-scopus {
  padding: 0 0 1em 0;

.citations-count-scopus br {
  display: none;
.citations-count-scopus .badge_total {
  margin: 0 0 0 1em;

.citations-list {
  margin-top: -0.5em;

.citations-list > div {
  margin: 1em 0 0 10.5px;
  display: list-item;

First of all: your journal is indexed in Scopus? Scopus collects data only for indexed journals.
Then you can try to check the plugin settings; the first field must show “Scopus & Crossref”.

Thanks for the information, our journal is not indexed in Scopus, so I understood the problem.