CitationOverview's cc property unexpected Error.

[kosh-jp]

CitationOverview's cc property unexpected Error.

[Michael-E-Rose]

According to the Scopus search, this DOI belongs to EID 2-s2.0-84973517467 - but it apparently doesn't exist! See here: https://www.scopus.com/record/display.uri?eid=2-s2.0-84973517467&origin=resultslist

So the Scopus API should actually return 404. It's a problem in the Scopus database, which should be reported.

I value tremendously when people come up with a PR, but in this case I am hesitant to accept it. The PR would cover an apparent mistake in the Scopus database.

[kosh-jp]

I have created my PR based on your previous modifications.
If you could change it I would appreciate it.

[kosh-jp]

I understand that PR is not appropriate.

Thank you for your reply and response!!

[astrochun]

I have a similar issue with another record, 85185347473. However, upon reviewing it, it seems that the record exists:

{'@_fa': 'true', 'identifier': 'SCOPUS_ID:85185347473', 'url': 'https://api.elsevier.com/content/abstract/scopus_id/85185347473', 'pcc': '0', 'lcc': '0', 'rangeCount': '0', 'rowTotal': '0'}
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
...
     44 try:
---> 45     cites = [int(d['$']) for d in doc['cc']]
     46 except AttributeError:  # No citations
     47     cites = [0]*len(_years)

KeyError: 'cc'

https://www.scopus.com/record/display.uri?eid=2-s2.0-85185347473&origin=resultslist

[Michael-E-Rose]

Interesting case: Scopus.com says, the article actually was cited. I wonder whether this is a bug in scopus? Because the other keys in the citation matrix are present, and 0. Anyways, going over these kind of inconsistencies and irregularities in the Scopus API is the job of pybliometrics ^^

[Michael-E-Rose]

Let's hope this solves it

[astrochun]

Let's hope this solves it

Thanks. I'll wait for a new PyPI release to pull and try it out.