search

elifesciences / elife-vendor-workflow-config

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

<custom-meta> #53

Open Melissa37 opened 9 years ago

Melissa37 commented 9 years ago

Where possible eLife avoids the use of this tag. However, it does have some uses.

The custom-meta foe eLife is collected into one group and it contains the version of the elife xml in use as well as the Author impact statement. See XX re the Author impact statement.

With changes in the eLife xml tagging the version in use is iterated. When we swapped from NLM to JATS we changed the version to 2.0.

<custom-meta-group>
                <custom-meta>
                    <meta-name>elife-xml-version</meta-name>
                    <meta-value>2.0</meta-value>
                </custom-meta>
                <custom-meta specific-use="meta-only">
                    <meta-name>Author impact statement</meta-name>
                    <meta-value>The chemical nature of RIF-1 may reveal a new class of bacterial signaling molecules.</meta-value>
                </custom-meta>
            </custom-meta-group>
ghost commented 9 years ago

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