Import from Journal of Cleaner Production

LiborA · November 25, 2017

Today I have imported a lot of articles from Journal of Cleaner Production from different issues. All articles have filled in issue "Supplement C". I think it is not correct. There is Debug ID from one import D1117577562

bwiernik · November 25, 2017

Can you give specific URLs that aren’t importing correctly?

LiborA · November 25, 2017

There are some examples of articles which I have imported today with issue Supplement C

http://www.sciencedirect.com/science/article/pii/S0308521X16304048
http://www.sciencedirect.com/science/article/pii/S187114131630035X
http://www.sciencedirect.com/science/article/pii/S0167880915000705
http://www.sciencedirect.com/science/article/pii/S0959652615000396

bwiernik · November 25, 2017

@adamsmith @zuphilip The ScienceDirect Translator seems to be adding "Supplement C" as the issue whenever no issue number is supplied (which is most Elsevier journals at this point).

Here's an example from Intelligence:
http://www.sciencedirect.com/science/article/pii/S0160289616303609

But see that this example from Personality and Individual Differences, which has an issue number, imports the supplied number:
http://www.sciencedirect.com/science/article/pii/S0191886903003398

adamsmith · November 25, 2017

We can try to fix this, but people should also be reporting this to Elsevier: they put "Supplement C" into the number field of the bibtex.

zuphilip · November 25, 2017

Okay, I emailed them.

LiborA · December 13, 2017

It seems that nothing changed

zuphilip · December 13, 2017

A month ago they "escalate the issue to Second line support for further assistance" and then "[t]he developers are starting to work in a solution but I cannot offer a resolution time yet." I wrote my next email...

zuphilip · December 15, 2017

Elsevier wrote today: "our developers team is working on a fix however they are not able to provide a timeframe for the implementation of a fix"

zuphilip · January 14, 2018

I got informed by Elsevier a few days ago, that this issue was fixed by their developer team and it looks fine AFAIS.