H2020Classification fix and possibility to add datasources in blacklist for propagation of result to organization
#108
Merged
claudio.atzori
merged 12 commits from miriam.baglioni/dnet-hadoop:master
into master
3 years ago
Loading…
Reference in New Issue
There is no content yet.
Delete Branch 'miriam.baglioni/dnet-hadoop:master'
Deleting a branch is permanent. It CANNOT be undone. Continue?
This PR fixes an issue while building the h2020classification action set. The name of two of the files changed as well as the name of the sheet to be red while getting topic information. THe sheet name is now a parameter and when missing an exception is fired.
2e70aa43f0
into master 3 years agoThe changes look ok, but please drop a comment to describe how the parameters should be changed from the workflow caller for both workflows
for the h2020classification the parameters are four:
The URL to download the project file
param name : projectFileURL
param value : https://cordis.europa.eu/data/cordis-h2020projects.csv
The URL to download the programme file
param name : programmeFileURL
param value : https://cordis.europa.eu/data/reference/cordisref-h2020programmes.csvt
The URL to download the topics file
param name : topicFileURL
param value : https://cordis.europa.eu/data/reference/cordisref-h2020topics.xlsx
The name of the sheet in the topic file to be read
param name. : sheetName
param value : Topics
for the propagation workflow, the added parameter is optional.
It allows to specify a set of institutional repository for which not to apply the propagation strategy
param name : blacklist
param value : the list of datasource id we want to add to the blacklist split by ;
2e70aa43f0
.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.