Closed silpol closed 9 years ago
what is even more interesting - if I do not change anything and just type in different DOI, literally 10.1016/j.rser.2015.02.031 for another existing article - it goes just fine
silpol@hostname:/tmp/mendeley-api-python-catalog-example$ python mendeley-catalog.py
Enter a DOI: 10.1016/j.rser.2015.02.031
"Early adopters boosting the diffusion of sustainable small-scale energy solutions" has 0 readers.
silpol@hostname:/tmp/mendeley-api-python-catalog-example$
and just as matter of a fact. both DOI - 10.1145/1815961.1816021 and 10.1016/j.rser.2015.02.031 make perfectly resolved to original pages by simple DOI verification tool, so now it looks more like bug to me.
Hello silpol,
Receiving a 'Catalog document not found' error is a valid response as our catalog may not have that particular DOI.
Using CrossRef to check if it's a valid paper is OK but it does not mean it will be in our catalog as we don't have all CrossRef papers.
I have now made your paper "Debunking the 100X GPU vs. CPU myth: ..." available in our catalog.
We are trying to plan some catalog improvements so stay tuned.
ah, ok, so it is exception on lack of record in your DB. ok, case closed.
I have fetched git repo and made "pip install -r requirements.txt" and checked that everything has installed.
Then I re-used OAuth credentials from previous test. Then launched script as described in readme. It looks like OAuth passed just fine. Then I get prompt
Enter a DOI:
for which I provide DOI for existing document 10.1145/1815961.1816021
and then I get exception
Is this expected behaviour or malfunction?