search

elifesciences / elife-vendor-workflow-config

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

non-eLife DOIs should have object-id #96

Open Melissa37 opened 9 years ago

Melissa37 commented 9 years ago

Example in correction: http://elifesciences.org/content/4/e08663.

However, in future examples we'd be able to publish the suppl file within the XML using eg:

`

Additional files 
        <supplementary-material id="SD3-data">
            <object-id pub-id-type="doi">10.7554/eLife.00013.031</object-id>
            <label>Supplementary file 1.</label>
            <caption>
                <title>This is the title of the supplementary file 1.</title>
                <p>A file containing underlying data.</p>
                <p>
                    <bold>DOI:</bold>
                    <ext-link ext-link-type="doi" xlink:href="10.7554/eLife.00013.031"
                        >http://dx.doi.org/10.7554/eLife.00013.031</ext-link>
                </p>
            </caption>
            <media mime-subtype="xlsx" mimetype="application" xlink:href="elife00013s003.xlsx"/>
        </supplementary-material>`

So it would have a landing page.

ghost commented 8 years ago

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