elifesciences / elife-vendor-workflow-config

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

<permissions> #44

Open Melissa37 opened 9 years ago

Melissa37 commented 9 years ago

There are two alternative permissions that we publish our content under. What is output from the submission system must be retained and not changed. The alternatives are one of either:

<permissions>
<copyright-statement>&#xa9; 2012, Alegado et al</copyright-statement>
<copyright-year>2012</copyright-year>
<copyright-holder>Alegado et al</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
<license-p>This article is distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution License</ext-link>, which permits unrestricted useand redistribution provided that the original author and source are credited.</license-p>
</license>
</permissions>

OR:

<license license-type="open-access" xlink:href="http://creativecommons.org/publicdomain/zero/1.0/">
<license-p>This is an open-access article, free of all copyright, and may be freely reproduced, distributed, transmitted, modified, built upon, or otherwise used by anyone for any lawful purpose. The work is made available under the Creative Commons CC0 public domain dedication.</license-p>
Melissa37 commented 9 years ago

We sometimes have figures that are not original and not originally published under a CC-BY or CC0 license. These require additional permissions tagging within the figure legend.

ghost commented 9 years ago

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