{"id":3585,"date":"2019-03-11T00:00:00","date_gmt":"2019-03-11T00:00:00","guid":{"rendered":"http:\/\/pl-asapbio.local\/eon-transpose\/"},"modified":"2025-03-28T21:37:52","modified_gmt":"2025-03-28T21:37:52","slug":"eon-transpose","status":"publish","type":"post","link":"https:\/\/asapbio.org\/eon-transpose\/","title":{"rendered":"Just published: examining the breadth of journal preprint policies in TRANSPOSE"},"content":{"rendered":"

Those who have been following ASAPbio for a while know that journal policies on preprinting are always in flux. As adoption of preprints\u2014and editors\u2019 comfort with them\u2014increase, these changes are typically positive. However, one potential downside to a rapidly-evolving policy landscape is the potential difficulty authors may face in finding their footing, especially when preprint policies are not as clear.<\/p>\n

We describe some of this variation in an article published in the current issue of the International Society of Managing and Technical Editors\u2019s<\/a> magazine Editorial Office News, <\/em>which you can read here<\/strong><\/a>.<\/p>\n

<\/p>\n

\n
\"\"
Via https:\/\/transpose-publishing.github.io\/usecases.html<\/figcaption><\/figure>\n<\/div>\n

In order to create this survey of current preprint policies, we relied on TRANSPOSE<\/a>, a collaborative database that aims to promote clarity in journal policies on both peer review and preprinting. While anyone can create and add to records, we especially encourage contributions from journal representatives, who are responsible for many of the hundreds of records currently in TRANSPOSE. We hope that the exercise of filling out the intake form not only helps make it easier to view preprint policies in aggregate, but also prompts discussions of desired policies\u2014and their presentation\u2014among editorial teams.<\/p>\n

For a broader survey of preprint data in TRANSPOSE, please see the preprint policy resource hosted here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Those who have been following ASAPbio for a while know that journal policies on preprinting are always in flux. As adoption of preprints\u2014and editors\u2019 comfort with them\u2014increase, these changes are […]<\/p>\n","protected":false},"author":2,"featured_media":2391,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[41,49,44],"tags":[],"class_list":["post-3585","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-asapbio-news","category-peer-review","category-preprints"],"acf":[],"_links":{"self":[{"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/posts\/3585","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/comments?post=3585"}],"version-history":[{"count":1,"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/posts\/3585\/revisions"}],"predecessor-version":[{"id":3586,"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/posts\/3585\/revisions\/3586"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/media\/2391"}],"wp:attachment":[{"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/media?parent=3585"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/categories?post=3585"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/asapbio.org\/wp-json\/wp\/v2\/tags?post=3585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}