You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an author, I want to be able to see the license information for an article so that I can confirm the correct license is being used.
Production staff
As production staff, I want to be able to change the license information for an article so that I can switch the license if required.
But what if . . . ?
At the end of the year the copyright year should be updated if the article is first published in the following year, however, the typesetter has provided the content to Texture and so their auto/validation steps will no longer be applied
Considerations
License information usually consists of the copyright statement (copyright holder, copyright year) and the license paragraph (human readable description of the terms of the license), plus in many cases a URL associated with the license.
However, under Public Domain licenses like CC0, there is no copyright holder or year (these articles are perforce free from copyright restrictions). Only the license paragraph and license link are required.
eLife publishes two licenses, CC-BY-4.0 Creative Commons Attribution License used for most articles and the Creative Commons CC0 public domain dedication used for articles produced by employees of the United States Government (e.g. NIH employees).
Other publishers will need other license options.
In most cases, it is expected that the license text will be boilerplate and not require manual editing. For eLife, this means that while the details for the copyright holder and year will change for each article (CCBY) or not exist at all (CCO), the text for each of the 2 license paragraphs will stay the same.
At eLife, logic is applied to the copyright information during the production process:
One author, remove the et al from the <copyright-holder> text
Two authors remove the et al from the text but add "and" and second author surname.
The author et al text remains stable for papers with 3 or more authors and it's the first author's surname text
Other publishers sometimes simply use 'The Authors' in place of a more specific copyright holder.
Captured in article/front/article-meta/permissions
CC-BY-4.0
<permissions>
<copyright-statement>© 2019, Tobin et al</copyright-statement>
<copyright-year>2019</copyright-year>
<copyright-holder>Tobin et al</copyright-holder>
<ali:free_to_read/>
<licensexlink:href="http://creativecommons.org/licenses/by/4.0/">
<ali:license_ref>http://creativecommons.org/licenses/by/4.0/</ali:license_ref>
<license-p>This article is distributed under the terms of the <ext-linkext-link-type="uri"xlink:href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution License</ext-link>, which permits unrestricted use and redistribution provided that the original author and source are credited.</license-p>
</license>
</permissions>
CC0 licenses have no copyright, and so should be captured in the following way (or similar).
<permissions>
<ali:free_to_read/>
<licensexlink:href="http://creativecommons.org/publicdomain/zero/1.0/">
<ali:license_ref>http://creativecommons.org/publicdomain/zero/1.0/</ali:license_ref>
<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 <ext-linkext-link-type="uri"xlink:href="http://creativecommons.org/publicdomain/zero/1.0/">Creative Commons CC0 public domain dedication</ext-link>.
</license-p>
</license>
</permissions>
In the event that there are separate licenses for different languages, this should be captured using @xml:lang on the license element (@xml:lang is not allowed on license-p) in the permissions.
Érudit include the license logo in license-p (where possible):
<!-- Link to the license text and to the license button. Permission with a "license-p" element only -->
<permissions>
...
...
<licensexlink:href="https://creativecommons.org/licenses/by/4.0/deed.fr">
<license-p>
<mediaxlink:href="http://licensebuttons.net/l/by/4.0/88x31.png"/>
</license-p>
</license>
</permissions>
<!-- Link to the license text and to the license button. Permission with a "ali:license_ref" and a "license-p" -->
<permissions>
...
...
<license>
<ali:license_refxmlns:ali="http://www.niso.org/schemas/ali/1.0/">
https://creativecommons.org/licenses/by/4.0/deed.fr</ali:license_ref>
<license-p>
<mediaxlink:href="http://licensebuttons.net/l/by/4.0/88x31.png"/>
</license-p>
</license>
</permissions>
Mock ups
Proposal
The text was updated successfully, but these errors were encountered:
Description
License and copyright details for the article.
User Stories
Author
Production staff
But what if . . . ?
Considerations
<copyright-holder>
textxmlns:ali="http://www.niso.org/schemas/ali/1.0/"
namespace in the header XML (https://github.com/elifesciences/TextureRequirements/issues/1)If the article is in french: https://creativecommons.org/licenses/by/4.0/deed.fr
If the article is in english: https://creativecommons.org/licenses/by/4.0/deed.en
license
containing the CC-BY button image, e.g. https://mirrors.creativecommons.org/presskit/buttons/88x31/svg/by-sa.svg or http://licensebuttons.net/l/by/4.0/88x31.png. Each button is tied to the license used, so this likely needs to be dealt with in configuration.XML requirements
There is a JATS4R recommendation for this tagging:
https://jats4r.org/permissions
Captured in
article/front/article-meta/permissions
CC-BY-4.0
CC0 licenses have no copyright, and so should be captured in the following way (or similar).
In the event that there are separate licenses for different languages, this should be captured using
@xml:lang
on thelicense
element (@xml:lang
is not allowed onlicense-p
) in thepermissions
.Érudit examples:
license
needs to be optional for Érudit:Érudit include the license logo in
license-p
(where possible):Mock ups
Proposal
The text was updated successfully, but these errors were encountered: