(1) As an author, I want to be able to see any source data files associated with my article so that I can make sure none are missing.
(2) As an author, I want to be able to download any source data files associated with my articles so that I can check the files themselves are correct.
(3) As an author, I want to be able to update a source data file so that I can fix errors in the file originally supplied.
(4) As an author, I want to be able to edit the title and caption of a source data file, so that I can correct any errors.
(5) As an author, I want to be able to add reference or asset citations to my source data title and legend so that I can cite other articles and assets in this context.
(6) As an author, I want to be able to adjust the type and placement of source data files so that I can ensure that they display correctly within the manuscript. [E.g. change a source data file to source code, or to change it to source data for a figure]
Production staff
(7) As production staff, I want to be able to add source data files so that I can include any missing assets.
(8) As production staff, I want to be able to remove source data files, so that I eliminate anything that has been incorrectly supplied.
(9) As production staff, I want to know why an author has changed a source data file so that I am aware of the reason for the change.
(10) As production staff, I want to provide an explanation for why I am replacing a source data file so that I can record the reason for the change.
But what if . . . ?
Considerations
The eLife labelling scheme for these files is
Source data 1
Source data 2
Labels will vary from publisher to publisher.
This is a variant of a supplementary file (outlined in this ticket), with a different labelling convention.
XML requirements
Captured as a supplementary-material in back/sec[@sec-type="supplementary-material"] element. The value of the label is 'Source data X.'
<back>
...
<sec sec-type="supplementary-material">
<title>Additional files</title>
...
<supplementary-material id="sdata1">
<label>Source data 1.</label>
<caption>
<title>RNA-seq data from dense aging time course.</title>
</caption>
<media mime-subtype="xlsx" mimetype="application" xlink:href="elife-39911-data1-v3.xlsx"/>
</supplementary-material>
<supplementary-material id="sdata2">
<label>Source data 2.</label>
<caption>
<title>MATLAB file containing resampled bilateral FOF model fits.</title>
</caption>
<media mime-subtype="mat" mimetype="application" xlink:href="elife-39911-data2-v3.mat"/>
</supplementary-material>
...
</sec>
...
<back>
Description
Source data for the whole article.
User Stories
Author
Production staff
But what if . . . ?
Considerations
XML requirements
Captured as a
supplementary-material
inback/sec[@sec-type="supplementary-material"]
element. The value of thelabel
is 'Source data X.'Mock ups
Proposal