Apr 132014
 

Natascha Gastera, Jorge S. Burnsb, Michael Gastera

aLaboratory of Molecular Physiology, Departments of Pathology and Endocrinology, Odense University Hospital, 5000 Odense, Denmark
bLaboratory of Cell Biology and Advanced Cancer Therapies, Department of Medical and Surgical Sciences for Children & Adults, University Hospital of Modena and Reggio Emilia, 41100 Modena, Italy

Received 13.01.2014, accepted 07.04.2014, published 13.04.2014

JUnQ, 4, 2, Article, 16-17, 2014

The ICMJE recommendations have recently been revised to include the addition of a fourth criterion to the Vancouver Protocol, the internationally recognized and globally applied standard for determining authorship on publications; authorship involves “Agreement to be accountable for all aspects of the work in ensuring that questions related to the accuracy or integrity of any part of the work are appropriately investigated and resolved”.[1] This development serves to prevent authors from delegating responsibility without further ado to another author should part of the article be questioned. In addition to accepting full responsibility for the parts he or she has done, the author should be able to identify which co-authors are responsible for other parts of the work. Herewith, we consider possible outcomes of this latest revision especially with regard to its broadest implications. Does this change mean we can expect a shift in authorship patterns?

Read more: Does the new ICMJE criterion stem co-author overflow?

  One Response to “Does the new ICMJE Criterion Stem Co-Author Overflow?”

  1. […] are usually supposed to offer answers instead. Personally, I took a great interest in the article of Natascha Gaster, Jorge S. Burns and Michael Gaster about the ICMJE recommendations and the problem of co-author overflow and honory authorships in […]

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)