@@ -43,11 +43,11 @@ Article URL: https://zenodo.org/record/xxxxxx/file/article.pdf
43
43
You must also assign the issue, volume, and article numbers. Have a
44
44
look on the published articles and assign the next available number in
45
45
the same issue and same volume if your article is still in the same
46
- year. Otherwise, increment the issue number and start with
47
- volume 1. Post your numbers to [ this GitHub
48
- issue] ( https://github.com/ReScience/ReScience/issues/48 ) that serves
49
- to avoid that two editors assign the same numbers to two different
50
- articles.
46
+ year. Otherwise, increment the volume number and start with
47
+ issue 1. The issue number is only changed for accommodating special issues.
48
+ Post your numbers to [ this GitHub issue] ( https://github.com/ReScience/ReScience/issues/48 )
49
+ that serves to avoid that two editors assign the same numbers to two
50
+ different articles.
51
51
52
52
53
53
#### 2. Metadata update and creation of the final PDF
@@ -105,10 +105,12 @@ Local entry has been created in 10.5072_zenodo.xxxxx
105
105
A new git branch (10.5072_zenodo.xxxxx) has been created.
106
106
```
107
107
108
- This will create a new public record on Zenodo and this will also create a new
109
- local directory corresponding to the entry. This means you need to push this
110
- new branch on GitHub and make a pull request (the commit will have been created
111
- automatically).
108
+ This example uses the sandbox, replace ` --sandbox ` by ` --zenodo ` for
109
+ publishing to the Zenodo production site! This will create a new
110
+ public record on Zenodo and also create a new local directory
111
+ corresponding to the entry. This means you need to push this new
112
+ branch on GitHub and make a pull request (the commit will have been
113
+ created automatically).
112
114
113
115
114
116
#### Website update
0 commit comments