From c3b3c98354ce33b6024a8d32e3ad74cf0cfd0755 Mon Sep 17 00:00:00 2001 From: malloryfreeberg Date: Sat, 30 Jul 2022 16:36:19 +0100 Subject: [PATCH] Removed redundant index.md. Fixes #23 --- index.md | 78 -------------------------------------------------------- 1 file changed, 78 deletions(-) delete mode 100644 index.md diff --git a/index.md b/index.md deleted file mode 100644 index 36113fd..0000000 --- a/index.md +++ /dev/null @@ -1,78 +0,0 @@ ---- -layout: default -title: FEGA Knowledge Base -nav_order: 1 ---- - -Federated EGA logo, colored logo of storage disk with human figure emerging from behind and the text Federated European Genome-phenome Archive on the right. - -# Establishing a Federated EGA Node - -Welcome to this collection of onboarding materials for establishing a Federated EGA Node! - -## What am I doing here? - -If you are reading this, you are probably looking for information on how to join the Federated EGA Network. Great! There is a lot of information here for you. - -These materials provide guidance for establishing a node in the Federated EGA Network. The materials are based on the knowledge and experiences of current nodes and their use cases. Your node's development might differ depending on your use cases and mandates from stakeholders. Please view these materials as suggestions and best practices - not hard requirements! - -## What is Federated EGA? - -**The Federated EGA is the primary global resource for discovery and access of sensitive human omics and associated data consented for secondary use, through a network of national human data repositories to accelerate disease research and improve human health.** - -Over the last 10 years, most individual-level human omics data have been generated in the context of research consortia and shared via global repositories such as the European Genome-phenome Archive (EGA). Many countries now have emerging personalized medicine programmes which are generating data from national or regional initiatives. Thus, human genomics is undergoing a step change from being a research-driven activity to one funded through healthcare initiatives. - -Genetic data generated in a healthcare context is subject to more stringent information governance than research data and often must comply with national legislation. To address this need, the Federated EGA provides a network of connected resources to enable transnational discovery of and access to human data for research while also respecting jurisdictional data protection regulations. By providing a solution to emerging challenges around secure and efficient management of human omics and associated data, the Federated EGA fosters data reuse, enables reproducibility, and accelerates biomedical research. - -Summary of responsibilities of Central EGA nodes (EMBL-EBI & CRG) and Federated EGA nodes (national/local jurisdictions): - -| Central EGA Node | Federated EGA Node | -| ---------------- | ------------------ | -| Hosts data | Hosts and/or owns data | -| Shares metadata & allows global discovery | Shares metadata to allow global discovery | -| Accepts data from all around the world | Accepts 3rd party data from jurisdiction | -| Has Helpdesk for Central EGA data | Has Helpdesk responsible for own data/jurisdiction | -| Chairs the Federated EGA Committees | Participates actively in the Federated EGA Committees | -| No time commitment for FEGA | Expected to stay in FEGA for at least 4 years | - - -## How do I start? - -The [ELIXIR Federated Human Data Community (FHD)](https://elixir-europe.org/communities/human-data) provides a framework for the secure submission, archival, dissemination, and analysis of sensitive human data across Europe, and wider. All Federated EGA communications are sent through the following open channels, join us! - -| Entry point | Information | -| ----------- | ----------- | -| ELIXIR FHD Mailing list | [join us here](https://elixir-europe.org/intranet/join-groups), select "Human Data" | -| ELIXIR FHD Community Calls | [Agenda](https://docs.google.com/document/d/10OwVvHbJ7i1gI1Iw4zmVsOs8kDrG077Y52juehiFcmU/edit), 1st Tuesday of the month, 2pm CEST| - - -If you are involved in **governance or legal aspects** of establishing a Federated EGA node, we suggest starting by reviewing information [here](https://ega-archive.github.io/FEGA-onboarding/docs/topics/governance-legal/). Typically this information is most useful for data protection officers, data stewards, policy makers, and strategic decision makers. - -If you are involved in **technical or operational aspects** of establishing a Federated EGA node, we suggest starting by reviewing information [here](https://ega-archive.github.io/FEGA-onboarding/docs/topics/technical-operational/). Typically this information is most useful for software developers and engineers, bioinformaticians, and support officers. - -If you are involved in **data and metadata management** for establishing a Federated EGA node, we suggest starting by reviewing the information [here](https://ega-archive.github.io/FEGA-onboarding/docs/topics/data-metadata-management/). Typically this information is most useful for bioinformaticians, data stewards, and support officers. - -If you are involved in **outreach or training aspects** of establishing a Federated EGA node, we suggest starting by reviewing the information [here](https://ega-archive.github.io/FEGA-onboarding/docs/topics/outreach-training/). Typically this information is most useful for data stewards, support officers, outreach/communications officers, and training organisers. - -## What does the journey look like? - -Based on current experiences, governance and legal development of a node usually happens in parallel with technical and operational development. You may find your path differs slightly for a variety of reasons - that's ok! - -One typical path for becoming a full Federated EGA member: - -Colored diagram with icons and descriptions of technical and governance steps an interested Federated EGA node needs to complete to join the Network. - -These materials guide you through onboarding information from the experiences of other nodes. Take what you find useful to apply to your own node development. - -There is no time limit on establishing a Federated EGA Node. Onboarding will take more or less time depending on existing infrastructure and governance models, availability of funding and resources, user needs, and other factors. - -## Acknowledgements - -We would like to thank all contributors, especially those mentioned in the [Contributors list](CONTRIBUTORS.yaml), the Federated EGA community for their support, and our funding partners. - -Please see our [contributing guide](CONTRIBUTING.md) for information on how to contribute to the generation and maintenance of these materials. Thank you in advance for your contributions! - -## License - -The content of the FEGA onboarding materials and website are licensed under the [Creative Commons Attribution Share Alike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/). -