Go to file
Efstratios Giannopoulos 4d01fd1b9a add semantic publication date logic 2024-05-23 11:05:00 +03:00
core add semantic publication date logic 2024-05-23 11:05:00 +03:00
web get token fix 2024-05-21 12:21:42 +03:00
.gitignore
.gitingnore
Dockerfile
Dockerfile.Sonar
LICENSE.txt
README.md
THIRD-PARTY-NOTICES.txt
pom.xml update commons models 2024-05-22 17:38:19 +03:00
settings.xml

README.md

Using zenodo repository with Argos

The repository-deposit-zenodo module implements the https://code-repo.d4science.org/MaDgiK-CITE/repository-deposit-base interface for the zenodo repository.

Setup

After creating the jar from the project, environment variables should be set since they are used in the application.properties

  1. STORAGE_TMP_ZENODO - a temporary storage needed
  2. CONFIGURATION_ZENODO - path to json file which includes the configuration for the repository

JSON configuration file

The following fields should be set:
depositType - an integer representing how the dmp user can deposit in the repository,
a. 0 stands for system deposition meaning the dmp is deposited using argos credentials to the repository,
b. 1 stands for user deposition in which the argos user specifies his/her own credentials to the repository,
c. 2 stands for both ways deposition if the repository allows the deposits of dmps to be made from both argos and users accounts
repositoryId - unique identifier for the repository
accessToken - access token provided for the system type deposits
repositoryUrl - repository's api url e.g "https://sandbox.zenodo.org/api/"
repositoryAuthorizationUrl - repository's authorization url e.g. "https://sandbox.zenodo.org/oauth/authorize"
repositoryRecordUrl - repository's record url, this url is used to index dmps that are created e.g. "https://sandbox.zenodo.org/record/"
repositoryAccessTokenUrl - repository's access token url e.g. "https://sandbox.zenodo.org/oauth/token"
repositoryClientId - repository's client id
repositoryClientSecret - repository's client secret
redirectUri - redirect uri to argos after the oauth2 flow from the repository
hasLogo - if the repository has a logo