This repository has been archived by the owner on Dec 16, 2019. It is now read-only.

Roadmap Tryggve Sensitive Data Archiving development

Jump to bottom

Niclas Jareborg edited this page Oct 31, 2018 · 2 revisions

Roadmap for "Local EGA" development in the Tryggve project

Note! This is currently a work in progress. Timelines and milestones might change

Last edited: 2018-10-11

before 2018-10

M3 REMS integrated for managing access permissions to datasets that are not part of the EGA
- Demonstrate request for dataset access in REMS, and access to archived dataset

before 2018-11

"Dataset access Service" / for NorTwinCan use case (non-EGA)
- Demonstrate dataset access from separate free-standing instances hosted in two different countries
  - Make it possible to Data API act as a htsget proxy

before 2018-12

Integrate "Local EGA" and EGA DATA API code bases fully for core functionality that supports the full process of "Data In" and "Data out"
- One Keyserver (EGA DATA API)
- One Database (EGA DATA API)
The integrated code bases deployed in at least one "production" environment
Support the archiving of a dataset before a local instance is part of the Federated EGA
- Minimal metadata handling support (also needed for LIMS integration)
  - validate metadata files
  - store metadata files separately
  - capture mapping between stored data files and metadata xml