search

elifesciences / JATs-xml

eLife upgrade to JATS xml
1 stars 2 forks source link

HW specific tagging #10

Open Melissa37 opened 10 years ago

Melissa37 commented 10 years ago

journal-id journal-id-type="hwp">eLife

Melissa37 commented 10 years ago

subj-group subj-group-type="display-channel"> For article type

Melissa37 commented 10 years ago

subj-group subj-group-type="heading"> For major subject area

Melissa37 commented 10 years ago

contrib-group content-type="section"> For editors

Melissa37 commented 10 years ago

Boxed text for insights - related article tagging not tagged properly, eg:

Related research article Pretto P, Bresciani J-P, Rainer G, Bülthoff HH. 2012. Foggy perception slows us down. eLife ``` 1 :e00031. doi: 10.7554/eLife.00031

Image Measuring motion perception in a driving simulator

Melissa37 commented 10 years ago

File naming convention:

BUCKET: elife-articles-hw TNQ deliver HW compatible files here for articles from Dec 1st 2014 on. Graham will load the archive here too, for TNQ will download archive files to their server, according to the schedule of the archive transition. The archive will also remain here as an eLife store. For supplement and video files these will be supplied in zipped video file (eg elife_2014_03703.inline-media.zip )

BUCKET: elife-articles PMC/Lens compatible files, including: Gifs for Lens R1, R2 suffixes on file names when revisions submitted For supplement files these will be supplied in zipped suppl file (eg elife_2014_03703.suppl.zip) For videos these will be will be supplied in zipped video file (eg elife_2014_03703.video.zip)

Melissa37 commented 9 years ago

Images - Lens required JPEGS, TIFF is HW-specific requirement. Could stop TIFF if no HW requirement. gifs for small images and jpegs for large images on HW site, they do some conversion we think from the one file TNQ sends

Melissa37 commented 9 years ago

Versioning with DOIs. Can be done at PubMed:

F1000:

We don’t wait for the final version to be ready because we have no way of knowing what the final version of a paper is – the author can publish another version as and when they chose.

Once an article reaches the “indexed” status on our site (when it has at least two Approved referee reviews, or one Approved plus two Approved with Reservations reviews) we send it to PubMed. After that, any time the article gets further referee reports, or we publish further versions of it, we automatically send those off as well.

PubMed are able to tie the different versions of an article together at their end as the dois have a consistent stem with only the version indicator changing with each new version – see the bold below:

Version 1: 10.12688/f1000research.5878.1 Version 2: 10.12688/f1000research.5878.2

Melissa37 commented 9 years ago

Related article tagging for external relations - advances and RP:CB

Melissa37 commented 9 years ago

Can we remove all full stops HW add - eg at end of each date in publication history