1
|
termsOfAgreementForResearcher = <h5>Terms of Agreement for Authors requesting APCs from the OpenAIRE2020 FP7 post-grant \
|
2
|
gold Open Access Pilot fund.</h5><p>By applying for funding for an Open Access publication via this service, you abide \
|
3
|
by the following terms of agreement:</p><h6>Technical Requirements</h6><div>1. The information you have provided on the \
|
4
|
publication and the associated payment is complete and correct to the best of your knowledge.</div><div>2. The funded \
|
5
|
publication will be made available under an open content licence, preferably Creative Commons CC-BY or CC-BY-SA. As an \
|
6
|
exception, a CC-BY-NC license will be acceptable for monographs during the first year.</div><div>3. The funded publication \
|
7
|
will be assigned a Digital Object Identifier (DOI) or equivalent persistent identifier as early as possible in the \
|
8
|
publication process, ideally when a publication is accepted. It must be assigned and provided to OpenAIRE before the \
|
9
|
invoice gets paid.</div><div>4. The published version of the funded publication must be made available by the publisher \
|
10
|
in PDF/A format. Additional formats that allow better use of text and data mining techniques are strongly encouraged such \
|
11
|
as XML (see http://www.biomedcentral.com/about/datamining for an example) or HTML.</div><h6>Depositing in an Open Access \
|
12
|
Repository</h6><div>6. The final publisher copy of the publication (i.e., PDF/A file or their TDM-able equivalents) must \
|
13
|
be deposited in an OpenAIRE-compliant repository, or Zenodo - https://zenodo.org, with a CC-BY license. If this deposit \
|
14
|
is not carried out by the publisher or your institution, you need to take care of doing the deposition yourself.</div><div>\
|
15
|
7. The licensing information must be included in the metadata for the deposited item.</div><h6>Acknowledgment</h6><div>8. \
|
16
|
The funded publication must acknowledge the original FP7 project according to FP7 model grant agreement rules . Additional \
|
17
|
acknowledgment information on the specific Open Access funding can be added. The acknowledgment must be included in the \
|
18
|
bibliographic metadata of the deposited publication whenever possible.</div><h6>Supplementary or related material and \
|
19
|
data</h6><div>9. The funded publication must include a statement where applicable on how underlying research materials, \
|
20
|
such as research data, samples or models, can be accessed.</div><h6>Fair Use of the Pilot Funding</h6><div>10. Due to \
|
21
|
the limited number of publications this Gold OA Pilot will fund per project, in case you are not the Principal Investigator \
|
22
|
(PI) of the FP7 project on behalf of which you are applying for funding, you must make sure the project PI is aware of \
|
23
|
this funding request in advance. In case you are the FP7 PI, you commit to disseminate this funding opportunity to the \
|
24
|
remaining project partners and to keep them informed of the number of project Open Access publications still eligible \
|
25
|
to be funded by the Gold OA Pilot.</div><div>11. You confirm that OpenAIRE has not been involved in any way in the choice \
|
26
|
of journal and publisher for the publication for which you are requesting this funding.</div>
|
27
|
whatIsThisServiceAbout = <div class="alert"><span class="strong">WARNING</span> - Once the first year of the FP7 Post-Grant \
|
28
|
Open Access Pilot has been completed and the initiative has been widely disseminated, an updated and more strict project \
|
29
|
eligibility time-window will apply. As of June 1st, 2016, finished FP7 projects <u>will remain eligible for up to two months \
|
30
|
after the nominal 2-year window after its end-date</u>. Once these two months are over, the project will be shown as non-eligible \
|
31
|
in the system and it will no longer be possible to submit any funding request.</div>\
|
32
|
<p>Use this service to request and monitor funding for Open Access publishing fees as described \
|
33
|
in the <a href="https://www.openaire.eu/postgrantoapilot" target="_blank">EC FP7 post-grant Open Access \
|
34
|
Pilot</a>.</p><div style="margin:20px 0px 30px 0px;"><ul><li>\
|
35
|
<span class="strong" style="letter-spacing:2px">Researchers: </span>request funding through a guided process</li><li>\
|
36
|
<span class="strong" style="letter-spacing:2px">Project Coordinators: </span>see funding opportunities and monitor \
|
37
|
project results</li><li><span class="strong" style="letter-spacing:2px">Institutions: </span>claim funding on behalf \
|
38
|
of your researchers, monitor your institution’s FP7 post-grant traffic</li><li><span class="strong" style="letter-spacing:2px">\
|
39
|
Publishers: </span>deliver information on APCs, manage invoices, monitor journal FP7 post-grant traffic</li></ul></div><p>\
|
40
|
<h6>Some important info</h6><span class="emphasis">Only publications that fulfill <a \
|
41
|
href="https://www.openaire.eu/fp7-postgrantoapilot-policy-guidelines" target="_blank">our guidelines and technical \
|
42
|
requirements</a> will be funded. Please read carefully before you proceed.</span><span class="emphasis">Our service \
|
43
|
integrates data from various sources (<a href="http://cordis.europa.eu/projects/home_en.html" target="_blank">CORDA</a>, \
|
44
|
<a href="http://www.openaire.eu" target="_blank">OpenAIRE</a>, <a href="http://search.crossref.org/" target="_blank">CrossRef</a>, \
|
45
|
<a href="http://hdl.handle.net/10864/10717" target="_blank">"Open access article processing charges May 2014" database \
|
46
|
by Heather Morrison</a>) so as to make the process as user-friendly as possible. <a class="contactUs">Let us know how \
|
47
|
we can improve.</a></span></p>
|
48
|
needMoreInfoOnThePilot = Visit our <a href="https://www.openaire.eu/postgrantoapilot" target="_blank">information \
|
49
|
pages</a> and <a href="https://www.openaire.eu/postgrantoapilot-faq" target="_blank">FAQs</a>. If you still have more questions \
|
50
|
please contact us via the OpenAIRE <a href="https://www.openaire.eu/support/helpdesk" target="_blank">helpdesk</a>.
|
51
|
infoForResearchers = Use this service to claim APCs for your post-grant FP7 publications. Before you do so, please \
|
52
|
<span class="strong">make sure you check with your institution</span> for potential agreements with OpenAIRE and/or \
|
53
|
with publishers that will make the whole funding request process easier for you. If you decide to use this system, \
|
54
|
you need to <span class="strong">register first</span> and the system will guide you through the process.
|
55
|
infoForInstitutionsFirstText = A number of universities and research centres across Europe are collaborating in the Pilot \
|
56
|
kick-off stage by aligning their strategies and reporting standards. These institutions will implement and test the \
|
57
|
workflows for collecting funding requests and managing APC payments, and will provide continuous feedback to improve the service..
|
58
|
infoForInstitutionsSecondText = If you want to know how to get involved <a class="contactUs">contact us</a>. You can always \
|
59
|
<a href="https://www.openaire.eu/contact-noads" target="_blank">contact an OpenAIRE National OA Desk (NOAD)</a> to see \
|
60
|
what is happening in your country.
|
61
|
infoForPublishersFirstText = Publishers are a key component to this initiative to ease out the funding workflows and ensure \
|
62
|
that the technical requirements are met for collecting the funds. This service provides a <span class="strong">publisher user profile</span> \
|
63
|
to allow the monitoring of all funding request submissions collected for a particular journal portfolio.
|
64
|
infoForPublishersSecondText = Please <a class="contactUs">get in contact</a> in order to express your interest and get \
|
65
|
more information about collaboration venues.
|
66
|
|
67
|
|
68
|
#####################################################
|
69
|
######## ERROR, WARNING AND SUCCESS MESSAGES ########
|
70
|
#####################################################
|
71
|
|
72
|
#error that appears when trying to get the list of requests in accounting/monitor/existing funding requests
|
73
|
errorGettingListOfFundingRequests = Error retrieving requests.
|
74
|
#warning message that appears when there are no available requests in accounting/monitor/existing (or no available requests for the user's selection)
|
75
|
warningNoFundingRequestsAvailable = No requests found.
|
76
|
#error message that appears when opening a specific request (error retrieving request information)
|
77
|
errorGettingSpecificRequestInfo = Error getting request information.
|
78
|
|
79
|
#error message marking a request as paid (in accounting monitor)
|
80
|
accountingErrorPayingRequest = Error while marking request as paid.
|
81
|
#success message marking a request as paid (in accounting monitor)
|
82
|
accountingSuccessPayingRequest = Request marked as paid.
|
83
|
#error message marking a request as on hold (in accounting monitor)
|
84
|
accountingErrorPuttingRequestOnHold = Error while putting request on hold.
|
85
|
#success message marking a request on hold (in accounting monitor)
|
86
|
accountingSuccessPuttingRequestOnHold = Request put on hold.
|
87
|
#error message marking a request as denied (in accounting monitor)
|
88
|
accountingErrorDenyingRequest = Error while denying request.
|
89
|
#success message marking a request as denied (in accounting monitor)
|
90
|
accountingSuccessDenyingRequest = Request denied.
|
91
|
|
92
|
#monitorFundingRequestsActions
|
93
|
monitorErrorApprovingRequest = Error while approving request.
|
94
|
monitorSuccessApprovingRequest = Request approved.
|
95
|
monitorErrorRejectingRequest = Error while rejecting request.
|
96
|
monitorSuccessRejectingRequest = Request rejected.
|
97
|
|
98
|
#error message that appears when retrieving the list of budgets (monitor/accounting/existing budgets)
|
99
|
errorGettingListOfBudgets = Error while retrieving budgets.
|
100
|
#warning message that appears when there are no budgets available (monitor/accounting/existing budgets)
|
101
|
warningNoBudgetsAvailable = No budgets found.
|
102
|
#error message approving a budget (by moderator)
|
103
|
monitorErrorApprovingBudget = Error while approving budget.
|
104
|
#error message rejecting a budget (by moderator)
|
105
|
monitorErrorRejectingBudget = Error while rejecting budget.
|
106
|
|
107
|
errorRetrievingHelpText = Error while retrieving help text.
|
108
|
errorSavingHelpText = Error while saving help text.
|
109
|
successfullySavingHelpText = Help text has been stored.
|
110
|
|
111
|
#warning that appears when clicking submit changes on the monitor help, but no help item is selected
|
112
|
warningNoHelpItemSelected = You must select a help item first
|
113
|
|
114
|
#for monitor users and monitor user roles
|
115
|
errorRetrievingUsers = Error while retrieving users.
|
116
|
warningNoAvailableUsers = No users found.
|
117
|
errorAcceptingUserRole = Error while accepting user role.
|
118
|
successAcceptingUserRole = User role accepted.
|
119
|
errorRemovingUserRole = Error while removing user role.
|
120
|
successRemovingUserRole = User role removed.
|
121
|
errorRejectingUserRole = Error while rejecting user role.
|
122
|
successRejectingUserRole = User role rejected.
|
123
|
|
124
|
#warning message in monitor users when trying to do an action (activate/deactivate) but no users are selected
|
125
|
warningNoUsersSelected = You haven't selected any user(s).
|
126
|
|
127
|
errorActivatingSingleUser = Error wile activating user.
|
128
|
successActivatingSingleUser = User activated.
|
129
|
errorActivatingSelectedUsers = Error while activating selected user(s).
|
130
|
successActivatingSelectedUsers = Selected user(s) activated.
|
131
|
errorDeactivatingSingleUser = Error while deactivating user.
|
132
|
successDeactivatingSingleUser = User deactivated.
|
133
|
errorDeactivatingSelectedUsers = Error while deactivating selected user(s).
|
134
|
successDeactivatingSelectedUsers = Selected user(s) deactivated.
|
135
|
|
136
|
errorGettingEligibleProjectsByOrganization = Error while getting eligible projects for this organization.
|
137
|
warningNoAvailableEligibleProjects = No projects matched your criteria.
|
138
|
|
139
|
#forgot password form
|
140
|
#error resetting password because the email provided does not exists
|
141
|
errorResetPasswordEmailNotExists = Reset password failed - Wrong email
|
142
|
#error resetting password failed for some other reason
|
143
|
errorResetPasswordGeneral = Error while resetting your password.
|
144
|
successfullyResetPassword = Resetting your password was successful. You will soon receive an e-mail with your new password.
|
145
|
resetWarningNoEmailProvided = You need to provide a valid email address
|
146
|
|
147
|
#user login form
|
148
|
loginErrorBothEmailAndPassRequired = Login failed - Both email and password fields are required.
|
149
|
loginErrorWrongEmailOrPassword = Login failed - Invalid username or password.
|
150
|
loginErrorAccountNotYetActivated = Login failed - Your account has not yet been activated. An e-mail has been sent to you with instructions on how to activate it.
|
151
|
loginErrorGeneral = Login failed - Something went wrong, please try again.
|
152
|
|
153
|
#user registration / account edit form
|
154
|
registerErrorPassFieldsDoNotMatch = The two password fields do not match.
|
155
|
registerErrorAllFieldsAreRequired = All asterisk (*) fields are required.
|
156
|
registerErrorCaptchaMissing = You need to fill in the captcha challenge.
|
157
|
registerErrorUserAlreadyExists = Registration failed - A user with this e-mail address already exists.
|
158
|
registerErrorGeneral = Registration failed - System error.
|
159
|
registerSuccessGeneral = Registration succeeded. You will receive an e-mail to activate your account.
|
160
|
#this messages is concated to the one above
|
161
|
registerSuccessExtraRoles = Your extra roles (other than researcher) must be approved by the OpenAIRE team.
|
162
|
updateAccountInfoError = Error while updating account information.
|
163
|
|
164
|
#contact us form
|
165
|
errorContactFormIncorrectCaptcha = Incorrect captcha.
|
166
|
errorSubmittingContactForm = Error while submitting contact form.
|
167
|
errorContactFormMissingCaptcha = You need to fill in the captcha challenge.
|
168
|
errorContactFormAllFieldsRequired = All asterisk (*) fields are required.
|
169
|
|
170
|
#new budget request
|
171
|
#### we need to revisit this page
|
172
|
|
173
|
#eligibility widget
|
174
|
errorGettingEligibility = Error while retrieving eligibility criteria.
|
175
|
|
176
|
#Funding Wizard
|
177
|
errorSavingFundingRequest = Error while saving your request.
|
178
|
errorSubmittingFundingRequest = Error while submitting your request.
|
179
|
successfullySubmittedFundingRequest = Your request has been submitted.
|
180
|
errorGettingExistingRequestInfo = Error while getting the existing request's info.
|
181
|
|
182
|
#Funding Wizard - accounting step
|
183
|
invoiceUploadErrorAllFieldsRequired = All asterisk (*) fields are required.
|
184
|
invoiceUploadedSuccessfully = Upload completed.
|
185
|
projectParticipationNotValidPercentage = Project participation must be a number greater than 0 and less or equal than 100.
|
186
|
discountNotValidPercentage = Discount must be a number greater than 0 and less or equal than 100.
|
187
|
apcNotPositiveNumber = APC must be a number greater than 0.
|
188
|
fundingRequestedNotPositiveNumber = Requested funding must be a number greater than 0.
|
189
|
chargesErrorFieldsRequired = You need to complete both the Project Participation and the Requested Funding fields.
|
190
|
|
191
|
#Funding Wizard - Project step
|
192
|
#This message appears when the user has selected a non eligible project but clicks next either way
|
193
|
projectNotEligibleError = This project is not eligible for funding.
|
194
|
#This message appears when the user clicks next without having selected a project first
|
195
|
projectNotSelectedError = You need to select a project first.
|
196
|
errorGettingProjectInfo = Error while retrieving project information.
|
197
|
|
198
|
#Funding Wizard - Publication step
|
199
|
errorGettingJournalInfo = Error while retrieving journal information.
|
200
|
journalFormErrorAllFieldsRequired = All asterisk (*) fields are required.
|
201
|
journalErrorNotSelected = You need to select a journal.
|
202
|
publicationFormErrorAtLeastOneAuthorEmail = At least one author's email is required.
|
203
|
publicationFormErrorAllFieldsRequired = All asterisk (*) fields are required.
|
204
|
failedToResolveDOIError = Failed to resolve DOI.
|
205
|
bothPublicationAndJournalRequired = You need to complete both publication and journal info.
|
206
|
bothPublicationAndPublisherRequired = You need to complete both publication and publisher info.
|
207
|
errorSavingPublicationAndJournal = System error saving publication and journal info
|
208
|
errorSavingPublicationAndPublisher = Error while saving publication and publisher info.
|
209
|
publisherNotSelectedError = You need to select a publisher or complete your publisher's name.
|
210
|
|
211
|
#Funding Wizard - Researcher step
|
212
|
researcherFormWarningAlreadyExists = This researcher already exists - we will use the existing information.
|
213
|
researcherFormErrorSaving = Failed to save the researcher's info - system error.
|
214
|
researcherFormSuccessfullySaved = Researcher's information saved.
|
215
|
researcherFormErrorAllFieldsRequired = All asterisk (*) fields are required.
|
216
|
#This user is not a researcher and the extra roles that s/he has requested have not yet been approved
|
217
|
researcherStepErrorUserNotYetAuthorized = You are not yet authorized to make a funding request.
|
218
|
|
219
|
#Funding Wizard - Summary step
|
220
|
errorRetrievingEligibility = Error retrieving eligibility for this request.
|
221
|
needToAgreeToTermsOfAgreement = You need to agree first to our Terms Of Agreement.
|