search

elifesciences / elife-vendor-workflow-config

capturing requriemtns and niggles for setting up the elife production workflow
0 stars 1 forks source link

More dodgy references require clean up: DOIs #108

Open Melissa37 opened 9 years ago

Melissa37 commented 9 years ago

First line is location of reference, second line is correction to DOI/comment:

elife00291 bib21: ‘10.184/jem.20100682’
10.1084/jem.20100682

elife00334 bib5: ‘01190410.1103/PhysRevE.71.011904’ 10.1103/PhysRevE.71.011904 Should not have page numbers, but elocation ID is 011904

elife00334 bib19: ‘10.1021/ bi992105o’
10.1021/bi992105o

elife00334 bib20: ‘10.1021/ bi011137k’
10.1021/bi011137k

elife00334 bib70: ‘e14910.1371/journal.pbio.0060149’
10.1371/journal.pbio.0060149 Should not have page numbers, but elocation ID is e149

elife00367 bib49: ‘10.1146/ annurev.earth.33.031504.103001’ 10.1146/annurev.earth.33.031504.103001

elife00380 bib54: ‘10.1126/science. 1068094’
10.1126/science.1068094

elife00792 bib70: ‘0162-0886/91/1302-0044$02.00’
10.1093/clinids/13.Supplement_4.S285

elife00961 bib72: ‘11200322’
From what I can gather, this paper does not have a DOI and so this should be removed completely

elife00994 bib40: ‘10.1017.S1355838201011074’
10.1017/S1355838201011074 The source is wrong, it is Rna whereas it should be RNA

elife01684 bib9: ‘10.1017.S1431927601010522’
10.1007/s10005-001-0020-4

elife04395 bib19: ‘10.156/NEJMp1409859’ 10.1056/NEJMp1409859

elife05826 bib38: ‘10.137/journal.pone.0110416’ 10.1371/journal.pone.0110416

elife05826 bib116: ‘10.137/journal.pbio.1001424’
10.1371/journal.pbio.1001424

gnott commented 9 years ago

Re: removing page numbers and the elocation-id: I don't find any <element-citation> so far that includes an <elocation-id> tag, so I will not be adding them - unless for these you'd like an <elocation-id> where specified

http://jats.nlm.nih.gov/publishing/tag-library/1.1d3/element/elocation-id.html

Melissa37 commented 9 years ago

Hi there

I suspect that might be TNQ tagging that has not been conforming to eLife requirements. See kitchen sink (https://github.com/elifesciences/elife-vendor-workflow-config/blob/master/elife-kitchen-sink.xml) example: line 3193.

Is that OK? I will ensure ExeterPremedia follow correct tagging requirements.

M

gnott commented 9 years ago

Added two elocation-id as indicated above!