150 likes | 286 Vues
The Resource Entitlement Management System (REMS) facilitates academic user access to research datasets, particularly in bioinformatics and social sciences. Supported by the ELIXIR ESFRI project, REMS integrates federated authentication allowing users to manage roles, apply for access, and commit to dataset licensing terms. The open-source Java application runs on Liferay with Vaadin framework, optimizing usability and operational costs while automating workflows for dataset access. It will also cater to linguistic research and expand availability to other ELIXIR nodes.
E N D
ResourceEntitlement Management System Mikael Linden CSC – IT Center for Science
Access to research datasets 0. Fullypublicaccess 1. Userhas a role/groupmembership • ”for academicusers” (IdPmanaged) • ”for archeologyresearchers in a goodstanding” (VirtualOrganisationmanaged) 2. Usercommits to datasets’ licenceterms 3. Userfills in and submits an application - Datasetownerapproves/rejects Oranycombination of 1, 2 and 3. REMS
The REMS concept 3. Circulate to approver 1. Apply for access DAC 1Approver IdP PrincipalinvestigatorApplicant 4. Approve Dataset 1 SP REMS IdP DAC 2Approver Workflow 2. Commit to licence terms Research groupMembers of the application Dataset 2 Reports Metadata on dataset 1&2 Entitlements IdP 5. Access
The REMS implementation • Funded by the ELIXIR ESFRI project • A Java portlet on Liferay, using Vaadin framework • Open source (LGPL) • Discipline-independent • Initially bioinformatics • Deploying also for social sciences • Piloting for linguistics in the EUDAT project • CSC is going to offer a REMS instance to other ELIXIR nodes • Subject to a positive funding decision
Design criteria • Automation/integration • To reduce operational cost • Usability • Simplicity for common users • Federated authentication • No local user accounts • Shared user identifier (eduPersonPrincipalName) • Modularity • Integration to the data archive’s other components
REMS integrates to the data archive Data archive’sportal/catalog Metadata 2. 1. 3. REMS SP AA 4. 5. Datasetdelivery SP Datasets 6.
REMS integration points 2. Data archive’sportal/catalog Metadata 1. REMS SP AA 3. Datasetdelivery SP Datasets
REMS integration points • Metadata import (JSON/REST): • Dataset’s • - Identifier (PID) • - Name (for the REMS UI) • - Approver(s) mail/ePPN • Licenseterms • REMS generatesworkflows and applicationformsautomatically 2. Data archive’sportal/catalog Metadata 1. REMS SP AA 3. Datasetdelivery SP Datasets
REMS integration points A simple URL in the portalwhichtriggers a new application in REMS e.g. https://rems.csc.fi/new?PID=1234 2. Data archive’sportal/catalog Metadata 1. REMS SP AA 3. Datasetdelivery SP Datasets
REMS integration points 2. Data archive’sportal/catalog Metadata 1. REMS Ordinaryattributequery Request: ePPN Response: list of PIDs SP AA 3. Datasetdelivery SP Datasets
CASE: Nordic Control Database • GWA data from 5500 samples from Estonia, Denmark, Finland and Sweden • Nordic Centre of Excellence in Disease Genetics NCoEDG • Dataset hosted by EGA, The European Genome-Phenome Archive (www.ebi.ac.uk/ega), a service of the European Bioinformatics Institute
CASE: process for applying access to the Nordic Control Database
Seealso the TNC2013 fullpaper in http://tnc2013.terena.org/getfile/870 Questions?