@@ -11,7 +11,14 @@ and from the [actual
11
11
server] ( https://zenodo.org/account/settings/applications/tokens/new/ ) .
12
12
13
13
The sandbox token is expected to be stored in the environment variable
14
- ` ZENODO_SANDBOX_TOKEN ` while the true token must be stored in ` ZENODO_TOKEN ` .
14
+ ` ZENODO_SANDBOX_TOKEN ` while the true token must be stored in ` ZENODO_TOKEN ` , e.g.:
15
+ ```
16
+ ZENODO_SANDBOX_TOKEN="access token"
17
+ ```
18
+ And to check it was set correctly:
19
+ ```
20
+ echo $ZENODO_SANDBOX_TOKEN
21
+ ```
15
22
We strongly advise you to ** first test the procedure** on the sandbox server
16
23
using the ` --sandbox ` switch.
17
24
@@ -71,7 +78,7 @@ Next, there are two situations:
71
78
- Otherwise, you give the authors the required information and
72
79
ask them to update their article and produce the final PDF file. You should
73
80
check that their PDF contains all the information you sent them.
74
-
81
+
75
82
You need to give this information back to author(s) such that they can update
76
83
the metadata file as well as the article that display the DOI in the left
77
84
margin (make sure they actually update this information). For the article
@@ -122,5 +129,3 @@ file on the website (you can do it directly from the GitHub interface). If you
122
129
previously added the entry to the
123
130
[ under_review.bib] ( https://github.com/ReScience/rescience.github.io/blob/sources/_bibliography/under-review.bib )
124
131
file, don't forget to remove it.
125
-
126
-
0 commit comments