12450 results for ""non-traditional+communal+storytelling+approach"+novel+segment+noted+in+critical+commentary"

in 30.41 milliseconds.

• Comparison of WGBS, EPIC array, EM-seq, and Nanopore sequencing in assessing DNA methylation marks

  Bisulfite sequencing has long been the default method for analyzing methylation marks due to its single base resolution. However, the associated DNA degradation poses a concern for fragmented samples. Although several methods have been proposed to circumvent this issue, there has yet to be a clear consensus on which method is best suited for detecting methylation. We present an overview of the two mostly used and two alternative approaches: whole-genome bisulfite sequencing (WGBS), Illumina methylation microarray (EPIC), Enzymatic Methyl-sequencing (EM-seq) and third-generation sequencing by Oxford Nanopore Technologies (ONT). We evaluated DNA methylation levels in three human genomes derived from tissue, cell line, and whole blood.

  Study EGAS00001008014

• A Cultured Leukemia Stem Cell Model Enables Validation of CDK6 as a Stemness Target Against Acute Myeloid Leukemia

  Acute myeloid leukemia (AML) represents a group of aggressive hematological malignancies, the clinical management of which is made challenging due to the persistence of rare and therapy resistant leukemia stem cells (LSCs) which serve as a source of disease relapse and poor outcomes. There are currently a paucity of methods to reliably enrich and study LSCs, hindering the development of therapies that specifically target LSCs. In this study, we deeply characterize the OCI-AML8227 culture model, which maintains a functional stemness hierarchy originating from its highly primitive CD34⁺CD38⁻ cells, to elucidate LSC biology and uncover LSC-specific therapeutic vulnerabilities. We analyzed both bulk and single-cell proteomics, transcriptomics, and epigenomics to generate a LSC protein-protein interaction network, which was then integrated with an LSC-focused small molecule screen using this model. From these findings, CDK6 was discovered as a therapeutic vulnerability specific to LSCs, which was validated in findings from the BEAT-AML cohort and a patient-derived xenograft (PDX) panel of AML samples through palbociclib treatment. Taken together, our studies validate CDK6 as a druggable vulnerability in LSCs, and authenticate OCI-AML8227 cells as a LSC target discovery engine.

  Dataset EGAD50000001156

• Ultra-deep Error-corrected Sequencing of Peripheral Blood for Clonal Hematopoiesis in Patients Undergoing AAA Surgery

  Patients undergoing elective abdominal aortic aneurysm (AAA) surgery were enrolled to investigate the prevalence and characteristics of clonal hematopoiesis. Peripheral blood was collected at the time of surgical admission using PAXgene DNA tubes. Genomic DNA was extracted and subjected to ultra-deep error-corrected targeted sequencing using a custom gene panel covering recurrent clonal hematopoiesis-associated genes. Sequencing libraries were prepared following established protocols and sequenced on an Illumina NovaSeq X system. The resulting dataset includes paired-end FASTQ files for each participant, enabling high-sensitivity detection of somatic variants down to low variant allele frequencies. This study provides a comprehensive sequencing resource for evaluating clonal hematopoiesis in AAA patients.

  Study JGAS000864

• EGA FUSE Client

  EGA FUSE Client What is EGA FUSE Client? The EGA FUSE Client is a Java Native Runtime (JNR) based Filesystem in Userspace (FUSE) client that allows users to access authorised EGA files by presenting them in a virtual directory. This means that users can use authorised EGA files like regular files without having to download them first. The EGA FUSE Client is a useful tool for researchers who need to access and work with large amounts of EGA data. Why use EGA FUSE Client? The EGA FUSE Client provides several benefits for researchers working with EGA data: Efficient use of storage space: With the EGA FUSE Client, users can access authorised EGA files without having to download them first. This means that users can save storage space on their local machines. Faster access to data: Since users can access authorised EGA files directly through the EGA FUSE Client, they can work with the data more quickly than if they had to download the files first. Simplified workflow: The EGA FUSE Client presents authorised EGA files in a virtual directory, allowing users to work with the files like regular files. This simplifies the workflow for researchers who need to access and work with large amounts of EGA data. Get started with EGA FUSE Client To get started with EGA FUSE Client visit the EGA FUSE Client GitHub repository for more information and installation instructions.

  Documentation access/download/visualisation/fuse-client

• EGA submission account terms

  Submission account terms Each EGA submission account has a dedicated submission box. To ensure continued service to all submitters EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. Those that are near to or exceeding this value will be monitored on a weekly basis by the helpdesk team and the submitter will be contacted and guidance provided accordingly on completing their metadata registration. You will be able to register your metadata associated with the files in your submission account via EGA Submitter Portal, Webin or the EGA REST API. EGA also requests that metadata is submitted within 60 days of upload data to a submission box. When we detect files that are over 60 days old in a submission box we will notify the submitter requesting that metadata be submitted or the files removed from the submission box. It is important to note that data is not archived at the EGA until the metadata describing the files has been associated and the archival process has completed. It is only when associated metadata has been submitted that the archival process into EGA is fully triggered. EGA removes files from the submission box once they have been successfully archived, so no action is required by a submitter to remove successfully archived files. Files over 90 days old will be deleted from the submission box unless EGA Helpdesk has been contacted and confirmed an exemption with the submitter.

  Documentation submission/terms

• Origins and timing of emerging lesions in advanced renal cell carcinoma

  Renal cell carcinoma (RCC) with venous tumor thrombus (VTT) arising from the primary tumor occurs in ~10% of cases and is thought to represent more advanced disease. RCC with VTT and distant metastasis provides unique opportunities to examine the origins and relative timing of tumor lesion emergence and to identify molecular correlates with disease state. We performed multi-region exome and RNA sequencing analysis of a clinical cohort of 16 RCC patients with VTT, with eight patients also having sequenced metastasis, to examine which genomic alterations, biological pathways, and evolutionary processes contribute to VTT and metastasis, and to ask whether metastasis typically arises directly from VTT or is independent of VTT.

  Study EGAS00001005897

• Time-dependent characterization of CNS response in COVID-19

  Coronavirus disease 2019 (COVID-19) caused by SARS-CoV-2 primarily affects the respiratory system, but the observation of diverse neurological symptoms indicates that other organs, including the brain, may be involved. The pathophysiological mechanisms of COVID-19-associated effects on the central nervous system (CNS) have become clearer during the past two years. Nevertheless, the precise CNS-specific molecular mechanisms are still elusive and raise several questions. To further elucidate the host response at brain tissue level, we profiled single-nucleus transcriptomes and performed proteomics from olfactory mucosa, olfactory bulb, medulla oblongata and cerebellum at different timepoints of the disease in individuals who died of COVID-19 and underwent rapid autopsy.

  Study EGAS00001006442

• Single-cell RNA-seq of peripheral blood mononuclear cells in classic Hodgkin lymphoma

  Classic Hodgkin lymphoma (cHL) is a largely MHC class I-negative tumor with recurrent 9p24.1/ PD-L1/ PD-L2 copy gains and the highest reported response rates to PD-1 blockade. We utilized scRNA sequencing to characterize the peripheral immune response to PD-1 blockade and more broadly define non-CD8+ dependent mechanisms of immune evasion in cHL. Peripheral blood mononuclear cells were obtained from 20 patients with relapsed/refractory (R/R) cHL treated with PD-1 blockade (nivolumab) on the CheckMate 205 clinical trial (paired samples from cycle 1 day 1 [C1D1] and cycle 4 day 1 [C4D1]), 11 patients with newly diagnosed, previously untreated cHL and 13 healthy donors.

  Study EGAS00001007569

• Interplay of somatic alterations and immune infiltration modulates response to PD-1 blockade in advanced clear cell renal cell carcinoma -- CA209-010

  Immune checkpoint inhibitors targeting the PD-1 pathway have transformed the management of many advanced malignancies, including clear cell renal cell carcinoma (ccRCC), but the drivers and resistors of PD-1 response remain incompletely elucidated. Here, we analyzed 592 tumors collected from advanced ccRCC patients enrolled in prospective clinical trials of treatment with PD-1 blockade (or mTOR inhibition as control arm) by whole-exome and RNA-sequencing, integrated with immunofluorescence analysis, to define the somatic alteration landscape of late-stage ccRCC and to uncover the immunogenomic determinants of therapeutic response. While conventional genomic markers (tumor mutation burden, neoantigen load) and degree of CD8+ T cell infiltration were not associated with clinical response, we discovered numerous chromosomal alterations in advanced ccRCC associated with response or resistance to PD-1 blockade. These advanced tumors were highly CD8+ T cell infiltrated, with only 22% and 5% with an immune desert and immune excluded phenotype, respectively. Our analysis revealed that CD8+ infiltrated tumors are depleted of favorable PBRM1 mutations and are enriched for unfavorable chromosomal losses of 9p21.3 when compared to non-infiltrated tumors. These data demonstrate how the interplay of somatic alterations and immunophenotypes impacts therapeutic efficacy.

  Dataset EGAD00001006026

• Interplay of somatic alterations and immune infiltration modulates response to PD-1 blockade in advanced clear cell renal cell carcinoma -- CA209-025

  Immune checkpoint inhibitors targeting the PD-1 pathway have transformed the management of many advanced malignancies, including clear cell renal cell carcinoma (ccRCC), but the drivers and resistors of PD-1 response remain incompletely elucidated. Here, we analyzed 592 tumors collected from advanced ccRCC patients enrolled in prospective clinical trials of treatment with PD-1 blockade (or mTOR inhibition as control arm) by whole-exome and RNA-sequencing, integrated with immunofluorescence analysis, to define the somatic alteration landscape of late-stage ccRCC and to uncover the immunogenomic determinants of therapeutic response. While conventional genomic markers (tumor mutation burden, neoantigen load) and degree of CD8+ T cell infiltration were not associated with clinical response, we discovered numerous chromosomal alterations in advanced ccRCC associated with response or resistance to PD-1 blockade. These advanced tumors were highly CD8+ T cell infiltrated, with only 22% and 5% with an immune desert and immune excluded phenotype, respectively. Our analysis revealed that CD8+ infiltrated tumors are depleted of favorable PBRM1 mutations and are enriched for unfavorable chromosomal losses of 9p21.3 when compared to non-infiltrated tumors. These data demonstrate how the interplay of somatic alterations and immunophenotypes impacts therapeutic efficacy.

  Dataset EGAD00001006029

• scRNA-seq of HSPC treated with gemcitabine and carboplatin

  4 samples of 2000000 HSPCs in 2 ml media each were then prepared and treated for 24 hours: carboplatin-high: 150 µg/ml carboplatin carboplatin-low: 18.75 µg/ml carboplatin gemcitabine: 25 ng/ml gemcitabine control: no drug Single-cells were subsequently extracted using the ddSEQ™ Single-Cell Isolator (Bio-Rad) and later sequenced using the SureCell™ Whole Transcriptome Analysis 3' Library Prep Kit (Illumina) on the NextSeq 500 System (Illumina) using the NextSeq 500/550 High Output Kit v2.5 150 Cycles (Illumina) all following the manufacturer's instructions. The raw FASTQ-files are available as read 1 and read 2 files from 4 lanes for each sample giving a total of 16 FASTQ-files. The FASTQ-files were also processed following the ddSeeker (Romagnoli, D., et al., BMC Genomics 2018, doi:10.1186/s12864-018-5249-x) and Drop-seq (Macosko, E.Z., et al., Cell 2015, doi:10.1016/j.cell.2015.05.002) protocols for processing scRNA-seq data to yield the final digital gene expression (dge) for each cell of each sample. This has resulted in one dge text file and one dge summary text file per sample. These 8 text-files with dge data are found in the zip-compressed analysis data-file.

  Dataset EGAD00001006080

• Deep amplicon sequencing to infer malignant clonal populations for The interface of malignant and immunologic clonal dynamics in high-grade serous ovarian cancer

  A total of 192 positions per patient were deeply sequenced in each corresponding tumor sample (including 4 experimental controls and SNVs predicted to originate at each node of the sample phylogeny, see Zhang et al. for details). Genomic DNA templates were used as starting material to generate PCR products. PCR was set up using Phusion DNA polymerase according to the manufacturer’s specifications. The standard PCR conditions used were an initial denaturation at 98C for 30 seconds, followed by 35 cycles of 98C for 10 seconds, 60C for 15 seconds and 72C for 8 seconds, and a final extension at 72C for 10 minutes. PCR products were cleaned up using PCRClean DX beads. Amplicons were pooled by template for sequencing sample preparation. Sample preparation involved a second round of amplification using Phusion DNA polymerase with 6 PCR cycles, with primers specified in Zhang et al. DNA quality was assessed using the Caliper LabChip GX HighSensitivity Assay and DNA quantity was measured using a Qubit dsDNA HS assay kit on a Qubit fluorometer. The indexed libraries were pooled together and sequenced on the Illumina NextSeq500 platform with paired-end 150bp reads using v2 chemistry reagents.

  Dataset EGAD00001003986

• Interplay of somatic alterations and immune infiltration modulates response to PD-1 blockade in advanced clear cell renal cell carcinoma -- CA209-009

  Immune checkpoint inhibitors targeting the PD-1 pathway have transformed the management of many advanced malignancies, including clear cell renal cell carcinoma (ccRCC), but the drivers and resistors of PD-1 response remain incompletely elucidated. Here, we analyzed 592 tumors collected from advanced ccRCC patients enrolled in prospective clinical trials of treatment with PD-1 blockade (or mTOR inhibition as control arm) by whole-exome and RNA-sequencing, integrated with immunofluorescence analysis, to define the somatic alteration landscape of late-stage ccRCC and to uncover the immunogenomic determinants of therapeutic response. While conventional genomic markers (tumor mutation burden, neoantigen load) and degree of CD8+ T cell infiltration were not associated with clinical response, we discovered numerous chromosomal alterations in advanced ccRCC associated with response or resistance to PD-1 blockade. These advanced tumors were highly CD8+ T cell infiltrated, with only 22% and 5% with an immune desert and immune excluded phenotype, respectively. Our analysis revealed that CD8+ infiltrated tumors are depleted of favorable PBRM1 mutations and are enriched for unfavorable chromosomal losses of 9p21.3 when compared to non-infiltrated tumors. These data demonstrate how the interplay of somatic alterations and immunophenotypes impacts therapeutic efficacy.

  Dataset EGAD00001006027

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! The EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• Distribution of data using Live Distribution

  Live Distribution Welcome to the documentation for using the Live Distribution feature for distributing data files securely through the EGA platform. This guide will walk you through the process of downloading encrypted files and decrypting them using Crypt4GH. Please follow the steps below to ensure a smooth experience. Before Downloading Create an EGA user. Make sure that you have the permissions to download the dataset of interest. In case you don’t have access, request access to the dataset. Add your Crypt4GH-compatible public key to your EGA account. Please allow a few hours for your public key to be synced with your profile. Afterwards, you will be able to connect to your EGA outbox using the SFTP protocol. Download Graphical User Interface (GUI) You can use any GUI that supports SFTP connections, such as FileZilla, an open-source FTP client. For Filezilla as your GUI, follow these steps to download files: Open FileZilla and access Site Manager (File > Site Manager). Create a new connection with the following settings (Figure 1): Protocol: SFTP - SSH File Transfer Protocol Host: __EGA_OUTBOX_DOMAIN__ Logon Type: Key file User: your EGA username Key file: path/to/your/private_key Figure 1: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the EGA outbox, ensuring seamless data transfers. Click Connect to access your Outbox. This folder serves as your storage space within the EGA cloud, containing files accessible for download in a secure way. Browse the remote directory on the right side of the FileZilla screen. Select the files you wish to download, right-click, and choose Download (Figure 2). Figure 2: Step-by-step process of manually downñoad files from __EGA_OUTBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can downñoad data from the EGA outbox to their local storage by following the depicted steps SFTP command line You can also use the SFTP command line to securely download files from the EGA Outbox. Using SFTP command line client in Linux/Unix Open a terminal window Enter the following command to connect: sftp username@hostname Enter your EGA password To see a list of available sftp commands type help sftp> put – Upload file sftp> get – Download file sftp> cd path – Change remote directory to ‘path’ sftp> pwd – Display remote working directory sftp> lcd path – Change the local directory to ‘path’ sftp> lpwd – Display local working directory sftp> ls – Display the contents of the remote working directory sftp> lls – Display the contents of the local working directory Type get command to download files. For example: get encrypted_file.c4gh Use the bye command to close the connection (SFTP session). Convenient SSH settings Include the following settings in your SSH config file, located in ~/.ssh/config Host __EGA_OUTBOX_DOMAIN__ EGA-outbox hostname __EGA_OUTBOX_DOMAIN__ User username IdentityFile path/to/the/private/key Replace username and path/to/the/private/key with the appropriate settings, and you will be able to connect to the __EGA_OUTBOX_DOMAIN__ simply using sftp EGA-outbox. How to decrypt Files archived at the EGA are encrypted based on Crypt4GH. Hence, to decrypt the files you need to install Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git After installing Crypt4GH, decrypt files using the following command: crypt4gh decrypt --sk /path/private/key < encrypted_file.c4gh > decrypted_filename The command reads the encrypted file from stdin (with <) and output the decrypted version to stdout (with >). Replace encrypted_file.c4gh and decrypted_filename with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write. Frequently Asked Questions What username should I use to log in to my outbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username, not your email address. Therefore, if you registered a username different from your email address when creating your EGA account, you must use that username to log in. If you have forgotten your registered username, please, contact our Helpdesk team for assistance. I see that some files in my dataset have 'unavailable' as extension. What should I do? Within your Outbox, you'll find a list of all the datasets available for download. Occasionally, certain files may be marked as "unavailable". These unavailable files can be identified by the "unavailable" extension added to their filenames (e.g. filename.fastq.gz.unavailable.c4gh). If you encounter an unavailable file that you need, please reach out to our Helpdesk. We'll promptly work on making the file accessible for download as soon as possible. Specific to using keys Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

  Documentation access/download/files/live-outbox

• The MLPA result of LAM disease

  Tumor biopsies from LAM disease were analyzed by MLPA to characterize the alterations in patients ,to elucidate the landscape of genetic/genomic alterations. The dataset include 44 samples.

  Dataset EGAD00010001757

• Association of DNA-methylation profiles with immune responses in breast cancer patients

  Genome-wide DNA methylation profiling of genomic DNA isolated from blood PBMCs of breat cancer patients before the start of therapy.

  Dataset EGAD00010001854

• SNPArray_TW

  The compressed file contains plink format file for the Affymetrix Human Origins SNP array data of 55 individuals generated and analyzed in Liu et al 2023 study of Taiwanese groups.

  Dataset EGAD00010002424

• CRC cell line Micro-C

  Ultra high-resolution chromatin capture data in CACO2, CL11, HT29, SW403, SW480, SW948 MSS CRC cell lines

  Dataset EGAD50000000294

• DAC Whole Exome Sequences from Eivissan and Menorcan Individuals

  30 and 21 whole exome sequences for Eivissan and Menorcan healthy unrelated volunteers, respectively. The exomes were captured with the Agilent SureSelect Human All Exon V6 capture kit and sequences in Illumina platforms.

  Dac EGAC50000000249

• RNA-seq data for genomic determinants of response and resistance to inotuzumab in B-ALL

  RNA-seq data for 101 samples with B-cell acute lymphoblastic leukemia

  Dataset EGAD50000000095

• Variants Derived From Heart Centre Biobank CHD Probands (Canada)

  Short variants identified in 731 CHD probands enrolled through the Heart Centre Biobank Registry (Canada).

  Dataset EGAD50000000838

• Variants Derived From Kids Heart BioBank TOF Probands (Australia)

  Short variants identified in 245 TOF probands enrolled through the Kids Heart BioBank (Australia).

  Dataset EGAD50000000839

• T Cell Signatures (Cityscape)

  T cell signatures from tumor RNAseq in CITYSCAPE with overall survival data. T cell signatures can be associated with the other clinical CITYSCAPE data .

  Dataset EGAD50000000932

• Human Heredity and Health in Africa Data Access Committee

  Dac EGAC00001000648