search

elifesciences / elife-vendor-workflow-config

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

<fn-group content-type="competing-interest"> #70

Open Melissa37 opened 9 years ago

Melissa37 commented 9 years ago

Each author conflict is output form the submission system as a separate item. If no authors have a conflict, the vendor is required to convert this to:

<fn-group content-type="competing-interest"><title>Competing interests</title><fn fn-type="conflict" id="conf1"><p>The authors declare that no competing interests exist.</p>

If an author has a conflict and the others do not, the author with the conflict will have one conflict id and all the others will have one other. The vendor is required to replicate what the author with the conflict has provided, making no changes to the text, but add his/her initials to the start followed by a colon and this will be the first conflict displayed: <p>JC: Reviewing editor, <italic>eLife</italic>.</p>

For the other authors the general text is: The other authors declare that no competing interests exist.

If there are multiple authors with conflicts follow the rules.

<fn-group content-type="competing-interest"><title>Competing interests</title><fn fn-type="conflict" id="conf1"><p>JC: Reviewing editor, <italic>eLife</italic>.</p></fn><fn fn-type="conflict" id="conf2"><p>The other authors declare that no competing interests exist.</p>

This is not contained within a footnote group tag

ghost commented 8 years ago

This is added in Bugzilla http://bugzilla.exetercs.com/show_bug.cgi?id=4021