WHO: Production/Production Vendor
WHEN: Between Export from EJP/xPub and delivery to production vendor
WHERE: In eLife bot processes
WHAT: Permission statement
WHY: We'd be giving the vendor clean metadata with fewer conversion requirements and it gets us closer to the end goal of converting author word files to JATS XML for publication
Proposed solution
XML sample exported from EJP:
<permissions><copyright-statement>Copyright © 2018, Gluth et al</copyright-statement><copyright-year>2018</copyright-year><copyright-holder>Gluth</copyright-holder><license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/"><license-p>This article is distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use and redistribution provided that the original author and source are credited.</license-p></license></permissions>
Final XML sample:
<permissions><copyright-statement>© 2018, Gluth et al</copyright-statement><copyright-year>2018</copyright-year><copyright-holder>Gluth et al</copyright-holder><ali:free_to_read/><license xlink: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-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></permissions>
Differences:
Remove text "Copyright" from start of <copyright-statement> exported from EJP
Add <ali:free_to_read/>
Change <license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/"> to <license xlink:href="http://creativecommons.org/licenses/by/4.0/">
Add <ali:license_ref>http://creativecommons.org/licenses/by/4.0/</ali:license_ref>
Clarification needed and assumptions
EJP is the source of the license statement version, so if there is a CC-BY update it will originate here
Therefore it cannot really be boiler plated
CCO license may also be used and must be converted as appropriate
Tasks
[ ] Think how this can be dealt with ie if bolier plated then make sure updates are communicated between editorial and production (they are so not too worried about this)
[ ] AIf not bolier plate then how to deal with it?
Problem / Motivation
WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: Permission statement WHY: We'd be giving the vendor clean metadata with fewer conversion requirements and it gets us closer to the end goal of converting author word files to JATS XML for publication
Proposed solution
XML sample exported from EJP:
<permissions><copyright-statement>Copyright © 2018, Gluth et al</copyright-statement><copyright-year>2018</copyright-year><copyright-holder>Gluth</copyright-holder><license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/"><license-p>This article is distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use and redistribution provided that the original author and source are credited.</license-p></license></permissions>
Final XML sample:
<permissions><copyright-statement>© 2018, Gluth et al</copyright-statement><copyright-year>2018</copyright-year><copyright-holder>Gluth et al</copyright-holder><ali:free_to_read/><license xlink: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-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></permissions>
Differences: Remove text "Copyright" from start of
<copyright-statement>
exported from EJP Add<ali:free_to_read/>
Change<license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/4.0/">
to<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
Add<ali:license_ref>http://creativecommons.org/licenses/by/4.0/</ali:license_ref>
Clarification needed and assumptions
EJP is the source of the license statement version, so if there is a CC-BY update it will originate here Therefore it cannot really be boiler plated CCO license may also be used and must be converted as appropriate
Tasks
Technical notes
@gnott
User interface / Wireframes
NA