1 / 15

Resource Entitlement Management System

Resource Entitlement Management System. Mikael Linden CSC – IT Center for Science. Access to research datasets. 0. Fully public access 1. User has a role/group membership ”for academic users ” ( IdP managed )

louisal
Download Presentation

Resource Entitlement Management System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ResourceEntitlement Management System Mikael Linden CSC – IT Center for Science

  2. 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

  3. 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

  4. 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

  5. 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

  6. REMS integrates to the data archive Data archive’sportal/catalog Metadata 2. 1. 3. REMS SP AA 4. 5. Datasetdelivery SP Datasets 6.

  7. REMS integration points 2. Data archive’sportal/catalog Metadata 1. REMS SP AA 3. Datasetdelivery SP Datasets

  8. 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

  9. 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

  10. REMS integration points 2. Data archive’sportal/catalog Metadata 1. REMS Ordinaryattributequery Request: ePPN Response: list of PIDs SP AA 3. Datasetdelivery SP Datasets

  11. Case: NordicControldatabase

  12. 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

  13. CASE: process for applying access to the Nordic Control Database

  14. REMS demo

  15. Seealso the TNC2013 fullpaper in http://tnc2013.terena.org/getfile/870 Questions?

More Related