Asset-level licensing

[fred-atherden]

Description

We need to be able to support separate licenses for assets within the article as these (particularly figures) may reproduce material from other articles not published under CC-BY licenses.

User Stories

Author

• (1) As an author, I want to be able to see any permissions information associated with an asset in my article so that I check this information is correct.

Production staff

• (2) As production staff, I want to be able to add permissions information to an asset so that I can accommodate assets that must be published under a license different from the article-level license.
• (3) As production staff, I want to be able to edit the permissions information associated with an asset so that I can correct errors.
• (4) As production staff, I want to be able to remove permissions information from an asset so that I can correct errors.
• (5) As production staff, I want to be able to add multiple sets of permissions information (copyright statements and license paragraphs) to an asset so that I can properly license assets created from multiple sources.

But what if . . . ?

Considerations [UPDATED: 03/06/2019]

• eLife allows for licensing/permissions information at the level of an asset e.g. a figure. This is to account for images that have been reproduced/adapted from previously published work that is not available under a CC-BY creative commons or similar license.
• Since figures may contain multiple images taken from different non-CC-BY sources, we also allow multiple sets of permissions per asset so that we can cover the licensing requirements for all the component parts. (At the moment, eLife does not support multi-image figures; however, even if we did, individual panels within figures may contain images taken from multiple sources for comparison and each of those images may have been published under a different license.)
• If an item is public domain/CC0, there will be no copyright holder or copyright year, so these fields and the copyright statement need to be optional rather than required.
• Example of multiple licenses on a figure: Figure 2 in https://elifesciences.org/articles/27041/figures#fig2.

XML requirements

JATS4R recommendation

Licensing information (for each license) is captured inside a permissions element as a child of the asset (whether that be table-wrap, media [for videos], or fig - although it is most likely to be only used for fig with eLife content). This holds the 4 following child elements:

• copyright-statement
• copyright-year
• copyright-holder
• license (which also contains a license-p).

The @xml:lang attribute can be used to specify a language. An asset must be able to have more than one permissions element.

<fig id="fig1">
    ...
    <permissions>
        <copyright-statement xml:lang="en">© 2015 MIT Press</copyright-statement>
        <copyright-year>2015</copyright-year>
        <copyright-holder xml:lang="en">MIT Press</copyright-holder>
        <license xml:lang="en">
            <license-p>Panel A reprinted from <xref ref-type="bibr" rid="bib42">Sterling and Laughlin, 2015</xref> with permission.</license-p>
        </license>
    </permissions>
    <permissions>
        <copyright-statement xml:lang="en">© 2019 Smith et al.</copyright-statement>
        <copyright-year>2019</copyright-year>
        <copyright-holder xml:lang="en">Smith et al.</copyright-holder>
        <license xml:lang="en" xlink:href="http://creativecommons.org/licenses/by/4.0/">
            <license-p>Panel B is licensed under a <ext-link  xlink:href="http://creativecommons.org/licenses/by/4.0/"  ext-link-type="uri">Creative Commons Attribution 4.0 International License</ext-link> <inline-graphic xlink:title="Creative Commons License" xlink:href="https://i.creativecommons.org/l/by/4.0/88x31.png" /></license-p>
        </license>
    </permissions>
</fig>

@xlink:href or <ali:license_ref> can be used as a attribute/child (respectively) of <license> to contain the URI which defines the license.

Example:

 <license xlink:href="http://creativecommons.org/licenses/by/4.0/">
     <license-p>Figure 1A 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 use and redistribution provided that the original author and source are credited.</license-p>
 </license>

or

<license>
      <ali:license_ref start_date="2014-02-03">http://creativecommons.org/licenses/by/4.0/</ali:license_ref>
      <license-p>Figure 1A 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 use and redistribution provided that the original author and source are credited.</license-p>
 </license>

license-p must be able to contain inline-graphic

Mock ups

This is not required, but if you have mock ups of what you would like to see please provide them here.

Proposal

This will be added by the Texture team after the feature request is discussed and agreed.

[fabiobatalha]

Including one example with inline-graphic to support creative commons icons.

<permissions>
    <license-p>
        <inline-graphic xlink:title="Creative Commons License" xlink:href="https://i.creativecommons.org/l/by/4.0/88x31.png" />This work is licensed under a <ext-link  xlink:href="http://creativecommons.org/licenses/by/4.0/"  ext-link-type="uri">Creative Commons Attribution 4.0 International License</ext-link>.
    </license-p>
</permissions>

[fred-atherden]

Thanks @fabiobatalha! - this was also included at the end of the license-p in the second permissions element in the example above

<permissions>
        <copyright-statement xml:lang="en">© 2019 Smith et al.</copyright-statement>
        <copyright-year>2019</copyright-year>
        <copyright-holder xml:lang="en">Smith et al.</copyright-holder>
        <license xml:lang="en" xlink:href="http://creativecommons.org/licenses/by/4.0/">
            <license-p>Panel B is licensed under a <ext-link  xlink:href="http://creativecommons.org/licenses/by/4.0/"  ext-link-type="uri">Creative Commons Attribution 4.0 International License</ext-link> <inline-graphic xlink:title="Creative Commons License" xlink:href="https://i.creativecommons.org/l/by/4.0/88x31.png" /></license-p>
        </license>
    </permissions>

I've added the following to the ticket to make this more explicit:

license-p must be able to contain inline-graphic

[JGilbert-eLife]

I've updated the considerations here to account for public domain licenses where there will be no copyright holder. This means copyright-holder, copyright-year and copyright-statement need to be optional, even if they will be there for most cases.