19229 results for "Buy fc coins Buyfc26coins.com is EA Sports official for FC 26 coins They are the best FC seller..nEoY"

in 36.70 milliseconds.

• Drug Perturbation of Primary Lymphoma Patient Samples and RNA Sequencing

  This submission contains 3'-end-based shallow-depth RNA sequencing data from 108 patients with chronic lymphocytic leukemia and 8 patients with lymphoma. Each primary patient sample was treated in vitro with DMSO as a control and with up to ten small-molecule drugs (ibrutinib, duvelisib, everolimus, trametinib, nutlin-3a, I-BET762, MK2206, selinexor, compound 26, and a combination of ibrutinib and compound 26). The samples were sequenced after 48 hours. The total data set consists of 1476 RNA sequencing samples from 6 batches (pilot, batch 1, batch 1 replicate, batch 2, batch 3, batch 4).

  Study EGAS50000001500

• Virtual Growing Child 5-Dimensional Functional Models for Treating Respiratory Anomalies (dMRI-VGC)

  Objectives We are sharing a database of dynamic magnetic resonance imaging (dMRI) scans of normal children, which can serve as a reference standard to quantify regional respiratory abnormalities in young patients with various respiratory conditions and facilitate treatment planning and response assessment. The database can also be useful to advance future AI-based research on image-based object segmentation and analysis. Background In pediatric patients with respiratory abnormalities, it is important to understand the alterations in regional dynamics of the lungs and other thoracoabdominal components, which in turn requires a quantitative understanding of what is considered as normal in healthy children. Currently, such a normative database of regional respiratory structure and function in healthy children does not exist. Participants 200 normal children (ages 6-18 years) participated in our research study related to this dataset. DesignThe shared open-source normative database is from our ongoing virtual growing child (VGC) project, which includes 4D dMRI images representing one breathing cycle for each normal child and also segmentations of 10 objects at end expiration (EE) and end inspiration (EI) phases of the respiratory cycle in the 4D image. The lung volumes at EE and EI as well as the excursion volumes of chest wall and diaphragm from EE to EI, left and right sides separately, are also reported. The database has thus 4,000 3D segmentations from 200 normal children in total. The database is unique and provides dMRI images, object segmentations, and quantitative regional respiratory measurement parameters of volumes for normal children. All dMRI scans are acquired from normal children during free-breathing. The dMRI acquisition protocol was as follows: 3T MRI scanner (Verio, Siemens, Erlangen, Germany), true-FISP bright-blood sequence, TR=3.82 ms, TE=1.91 ms, voxel size ~1×1×6 mm3, 320×320 matrix, bandwidth 258 Hz, and flip angle 76o. With recent advances, for each sagittal location across the thorax and abdomen, we acquired 40 2D slices over several tidal breathing cycles at ~480 ms/slice. On average, 35 sagittal locations are imaged, yielding a total of ~1400 2D MRI slices, with a resulting total scan time of 11-13 minutes for any particular study participant.The collected dMRI scan data then went through the procedure of 4D image construction, image processing, object segmentation, and volumetric measurements from segmentations. 4D image construction: For the acquired dMRI scans, we utilized an automated 4D image construction approach to form one 4D image over one breathing cycle (consisting of typically 5-8 respiratory phases) from each acquired dMRI scan to represent the whole dynamic thoraco-abdominal body region. The algorithm selects 175-280 slices (35 sagittal locations × 5-8 respiratory phases) from the 1400 acquired slices in an optimal manner using an optical flux method. Image processing: Intensity standardization is performed on every time point/3D volume of the 4D image so that image values have the same tissue-specific meaning across all subjects. Object segmentation: For each subject, there are 10 objects segmented at both EE and EI time points in this database. They include the thoracoabdominal skin outer boundary, left and right lungs, liver, spleen, left and right kidneys, diaphragm, and left and right hemi-diaphragms. All dMRI scans utilize large field of view images, which include the full thorax and abdomen to the inferior aspect of the kidneys in the sagittal plane. We used a pretrained U-Net based deep learning network to first segment all objects, and then all auto-segmentation results were visually checked and manually refined as needed, under the supervision of a radiologist with over 25 years of expertise in MRI and thoracoabdominal radiology. Manual segmentations have been performed for all objects in all datasets. Volumetric measurements based on object segmentations for lung volumes (left and right separately) at EE and EI, as well as for chest wall and diaphragm excursion volumes (left and right separately) are reported. ConclusionsThe provided database is unique and provides dMRI images, object segmentations, and quantitative regional respiratory measurement parameters of volumes for normal children. The database has 4,000 3D segmentations from 200 normal children, which to our knowledge is the largest and only such dMRI dataset to date. All images and object segmentations are saved in DICOM. All DICOM files (176,574 in total) have been anonymized, and PHI has been removed. The database can be used as a reference standard to quantify regional respiratory abnormalities in young patients with various respiratory conditions and facilitate treatment planning and response assessment. The large amount of object segmentations can potentially benefit AI-based research on image-based object segmentation and analysis.

  Study phs004002

• Phase II trial of targeted immune-depleting chemotherapy and reduced-intensity allogeneic hematopoietic stem cell transplantation using 8/8 and 7/8 HLA-matched unrelated donors and utilizing two graft-versus-host disease prophylaxis regimens for the treatment of leukemias, lymphomas, and pre-malignant blood disorders

  Background: Major problems with stem cell transplantation (SCT) for cancer treatment are a lack of suitable donors for patients without an HLA tissue-matched sibling and graft-versus-host disease (GVHD), a serious side effects of immune-suppressing chemotherapy that is given to bring the cancer under control before SCT. In GVHD, the patient's immune system attacks the transplanted donor cells. This study will try to improve the results of SCT from unrelated HLA-matched donors using targeted immune-depleting chemotherapy to bring the cancer under control before transplantation and to lower the chance of graft rejection, followed by reduced-intensity transplant chemotherapy to make the procedure less toxic. Objectives: To evaluate the safety and effectiveness of targeted immune-depleting chemotherapy followed by reduced-intensity transplant chemotherapy in patients with advanced cancers of the blood and immune system. To evaluate the safety and effectiveness of two different drug combinations to prevent GVHD. Both regimens have been successful in preventing GVHD, but they work by different mechanisms and affect the rebuilding of the immune system after the transplant. Eligibility: People 18 to 74 years of age with advanced or high-risk cancers of the blood and immune system who do not have a suitable HLA-matched sibling. Design: All patients receive chemotherapy before transplant to treat the cancer and suppress immune function. All patients receive a conditioning regimen of cyclophosphamide for 4 days and fludarabine for 4 days before SCT to prepare for the transplant. Patients are randomly assigned to one of two combination drug treatments to prevent GHVD as follows: Group 1: Tacrolimus starting 3 days before SCT and continuing for 6 months, plus methotrexate on days 1, 3, 6, and 11 post-SCT, plus sirolimus starting 3 days before the SCT and continuing through day 14 following SCT. Group 2: Alemtuzumab for 4 days starting 8 days before SCT, plus cyclosporine starting 1 day before SCT and continuing for 6 months. Patients receive the donor's stem cells and immune cells 2 days after the conditioning regimen. Patients are followed at the clinic regularly for the first 6 months after SCT, and then less often for at least 5 years. Some visits may include bone marrow aspirates and biopsies, blood draws, and other tests to monitor disease status. A skin biopsy, oral mucosa biopsy, and saliva collection are done to study chronic GVHD.

  Study phs002021

• 'IL-17A-Producing ILC3s and Duodenal Adenoma in FAP'

  Familial Adenomatous Polyposis (FAP) is a hereditary tumor syndrome that significantly enhances the risk of duodenal adenomas, with variations observed even among carriers of the same genetic variant. In this study, intestinal ILCs were isolated from 82 FAP and 26 non-FAP patients and analyzed through flow cytometry, qRT-PCR, and bulkRNA-sequencing. The data revealed a heightened frequency of ILC3s in FAP patients, and increased IL-17A production of duodenal NKp44(-)ILC3s was associated with FAP. Significant elevations in IL1B, IL23A, and DLL4 mRNA expression levels were found in FAP duodenal adenoma tissue, along with enhanced expression of DUOX2 and DUOXA2. The results suggest the involvement of IL-17A-producing NKp44(-)ILC3s in duodenal adenoma formation in FAP.

  Study EGAS00001007347

• Gut microbiome dynamics unravelled with metagenomics sequencing

  It has been already several years since we discovered that microbial therapeutics like Faecal Microbiota Transplantation can be used to treat Clostridium difficile infection (CDI) and Inflammatory bowel disease (IBD) with great success. The concept has challenged us to test the limits of our knowledge with the perspective to improve health in the most diverse conditions like Parkinson disease, depression, autism and obesity, just to mention a few. Note: the figure belongs to the original paper and is owned by the authors. Allyson L.Bird and colleagues from Genentech Inc. (San Francisco) recently published an interesting study building up on the key concept that “As microbial therapeutics are increasingly being tested in diverse patient populations, it is essential to understand the host and environmental factors influencing the microbiome.” The authors of this work analysed 1359 gut microbiome samples using shotgun metagenomics sequencing.  The results of the comparison done between microbiota composition across the different groups showed that biological sex is the strongest driver of diversity, while aging (age range studied: 20–69) appears to be the second factor. As smartly outlined in the authors’ own graphical abstract (figure to the left), Bacteroidota species consistently increased with donors' age while Actinobacteriota species, including Bifidobacterium, decreased. This study also integrated data from oncological patients to draw cancer-related evidences. After correcting the biases for technical and geographic differences, they found that cancer patients show significantly altered gut bacterial communities compared with their healthy counterparts. Eg. E.coli was found to be increased in cancer patients together with Bacteroidota/Firmicutes ratios. By comparing sequential samples taken from the same donors (413) within short-distance time points, the authors found that in the short term, intra-individual differences were less than the inter-individual ones, indicating a certain community stability being the norm. One of the pivotal points from this interesting study is that the data proceeds from extremely well-defined and selected donors. Specifically, the data for 949 selected healthy donors came from the Milieu Intérieur (MI) Consortium and extensive metadata, including demographic variables, serological measures, dietary information, and systemic immune profiles, are available. This precise stratification allowed for the robust detection of smaller changes, compared to former works. All sequencing data has been deposited in the EGA archive under the accession number EGAS00001004437. Enjoy this amazing open access paper published in the Experimental Journal of Medicine on January 2021.

  Blog gut-microbiome-dynamics-unravelled

• National Human Genome Research Institute (NHGRI) GENEVA Genome-Wide Association Study of Venous Thrombosis (GWAS of VTE)

  Overview: Our overall long-term goal is to determine risk factors for the complex (multifactorial) disease, venous thromboembolism (VTE), that will allow physicians to stratify individual patient risk and target VTE prophylaxis to those who would benefit most. In this genome-wide association case-control study (1300 cases and 1300 controls) we hope to identify susceptibility variants for VTE. Mutations within genes encoding for important components of the anticoagulant, procoagulant, fibrinolytic, and innate immunity pathways are risk factors for VTE. We hypothesize that other genes within these four pathways or within other pathways also are VTE disease-susceptibility genes. Therefore, we performed a genome wide association (GWA) screen and analysis using the Illumina 660W platform to identify SNPs within 1,300 clinic-based, non-cancer VTE cases primarily from Minnesota and the upper Midwest USA, and 1300 clinic-based, unrelated controls frequency-matched on patient age, gender, myocardial infarction/stroke status and state of residence. This is a subset of a slightly larger candidate gene study using 1500 case-control pairs to identify haplotype-tagging SNPs (ht-SNPs) in a large set of candidate genes (n~750) within the anticoagulant, procoagulant, fibrinolytic, and innate immunity pathways. Study Populations. Cases. VTE cases were consecutive Mayo Clinic outpatients with objectively-diagnosed deep vein thrombosis (DVT) and/or pulmonary embolism (PE) residing in the upper Midwest and referred by Mayo Clinic physician to the Mayo Clinic Special Coagulation Laboratory for clinical diagnostic testing to evaluate for an acquired or inherited thrombophilia, or to the Mayo Clinic Thrombophilia Center. Any person contacted to be a control but discovered to have had a VTE was evaluated for inclusion as a case. Cases were primarily residents from Minnesota, Wisconsin, Iowa, Michigan, Illinois, North or South Dakota, Nebraska, Kansas, Missouri and Indiana. A DVT or PE was categorized as objectively diagnosed when (a) confirmed by venography or pulmonary angiography, or pathology examination of thrombus removed at surgery, or (b) if at least one non-invasive test (compression duplex ultrasonography, lung scan, computed tomography scan, magnetic resonance imaging) was positive. A VTE was defined as: Proximal leg deep vein thrombosis (DVT), which includes the common iliac, internal iliac, external iliac, common femoral, superficial [now termed "femoral"] femoral, deep femoral [sometimes referred to as "profunda" femoral] and/or popliteal veins. (Note: greater and lesser saphenous veins, or other superficial or perforator veins, were not included as proximal or distal leg DVT). Distal leg DVT (or "isolated calf DVT"), which includes the anterior tibial, posterior tibial and/or peroneal veins. (Note: gastrocnemius, soleal and/or sural [e.g., "deep muscular veins" of the calf] vein thrombosis was not included as distal leg DVT). Arm DVT, which includes the axillary, subclavian and/or innominate (brachiocephalic) veins. (Note: jugular [internal or external], cephalic and brachial vein thrombosis was not included in "arm DVT"). Hepatic, portal, splenic, superior or inferior mesenteric, and/or renal vein thrombosis. (Note: ovarian, testicular, peri-prostatic and/or pelvic vein thrombosis was not included). Cerebral vein thrombosis (includes cerebral or dural sinus or vein, saggital sinus or vein, and/or transverse sinus or vein thrombosis). Inferior vena cava (IVC) thrombosis Superior vena cava (SVC) thrombosis Pulmonary embolism Patients with VTE related to active cancer, antiphospholipid syndrome, inflammatory bowel disease, vasculitis, a rheumatoid or other autoimmune disorder, a vascular anomaly (e.g., Klippel-Trénaunay syndrome, etc.), heparin-induced thrombocytopenia, or a mechanical cause for DVT (e.g., arm DVT or SVC thrombosis related to a central venous catheter or transvenous pacemaker, portal and/or splenic vein thrombosis related to liver cirrhosis, IVC thrombosis related to retroperitoneal fibrosis, etc.), with hemodialysis arteriovenous fistula thrombosis, or with prior liver or bone marrow transplantation were excluded. Controls. A Mayo Clinic outpatient control group was prospectively recruited for this study. Controls were frequency-matched on the age group (18-29, 30-39, 40-49, 50-59, 60-69, 70-79, and 80+ years), sex, myocardial infarction/stroke status, and state of residence distribution of the cases. We selected clinic-based controls using a controls' database of persons undergoing general medical examinations in the Mayo Clinic Departments of General Internal Medicine or Primary Care Internal Medicine. Additionally persons undergoing evaluation at the Mayo Clinic Sports Medicine Center, and the Department of Family Medicine were screened for inclusion as controls. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to venous thrombosis through large-scale genome-wide association studies of 1,300 clinic-based, VTE cases and 1300 clinic-based, unrelated controls. Genotyping was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR). Data cleaning and harmonization were done at the GEI-funded GENEVA Coordinating Center at the University of Washington.

  Study phs000289

• Ovarian Cancer Organoid Biobank - RNASeq data

  Ovarian cancer (OC) is a heterogeneous disease usually diagnosed at a late stage. Experimental in vitro models that faithfully capture the hallmarks and tumor heterogeneity of OC are limited and hard to establish. We present a novel protocol that enables efficient derivation and long-term expansion of OC organoids. Utilizing this protocol, we have established 56 organoid lines from 32 patients, representing the spectrum of ovarian neoplasms, including non-malignant borderline tumors, as well as mucinous, clear-cell, endometrioid, low- and high-grade serous carcinomas. OC organoids recapitulate histological and genomic features of the pertinent lesion from which they were derived, illustrating intra- and inter-patient heterogeneity, and can be genetically modified. We show that OC organoids can be used for drug screening assays and capture different tumor subtype responses to the gold standard platinum-based chemotherapy, including acquisition of chemoresistance in recurrent disease. Finally, OC organoids can be xenografted, enabling in vivo drug sensitivity assays. Taken together, this demonstrates their potential application for research and personalized medicine.

  Dataset EGAD00001004509

• Comparison of 3 protocols for deriving pancreatic progenitors from hPSC with RNA-seq and ATAC-seq

  Several distinct differentiation protocols for deriving pancreatic progenitors (PP) from human pluripotent stem cells have been described but it remains to be shown how similar the PP are across protocols, and how well they resemble their in vivo counterparts. Here we evaluated three differentiation protocols; performed RNA and ATAC-seq on isolated PP derived with these, and compared them to fetal human pancreas populations. This enabled us to define a shared transcriptional and epigenomic signature of the PP, including several genes not previously implicated in pancreas development. Furthermore, we identified a significant and previously unappreciated cross-protocol variation of the PP through multi-omics analysis and demonstrate how such information can be applied to refine differentiation protocols for derivation of insulin-producing beta-like cells. Together, our study highlights the importance of a detailed characterization of defined cell populations derived from distinct differentiation protocols, and provides a valuable resource for exploring human pancreatic development.

  Study EGAS00001003513

• Incentives and Case Management to Improve Cardiac Care: Healthy Lifestyle Program (HeLP)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this study.Objectives: The HeLP study assessed how early case management, financial incentives contingent on cardiac-rehabilitation attendance, or both impacted adherence to cardiac rehabilitation among patients with lower socioeconomic status (SES) who had a cardiac-rehabilitation-qualifying diagnosis. Background:Cardiovascular disease (CVD) is the leading cause of death in the United States. Regular attendance at cardiac rehabilitation (CR) is the number one recommendation for patients who have experienced a recent cardiac event. CR is a secondary prevention outpatient program involving an individually tailored structured exercise program along with counseling and encouragement regarding lifestyle changes to reduce the recurrence of major cardiac events.Despite the benefits of CR attendance, enrollment and adherence to the program are low. This is particularly true of individuals of lower socioeconomic status (SES), who also generally suffer a higher burden from CVD on account of higher-risk cardiac profiles. As these profiles are the result of modifiable behavior targeted by CR (i.e., smoking, obesity, lack of physical activity), methods of increasing CR attendance among this population are necessary.Case management and financial incentives contingent on CR attendance are two potential strategies for addressing this issue. Previous studies have shown how trained case managers can support and assist patients with attending CR and improving their cardiac health, and how financial incentives can promote various types of health-related behavior. The purpose of the present study was to evaluate how these two interventions, individually and in tandem, fared at improving CR adherence among individuals of lower SES specifically. Participants:A total of 314 participants were screened, and 209 were randomized. All consented to have their data shared for research purposes. Design:Eligible patients were approached either while still in the hospital or during initial visits to CR. After obtaining informed consent, clinical and demographic characteristics (i.e., age, sex, education, race and ethnicity, smoking status, and CR-qualifying diagnosis) and depressive symptoms were collected. Participants then were randomized 2:3:3:3 to usual care (UC), case management starting in hospital (CM), financial incentives for attending CR (FI), or financial incentives plus case management (FICM). For all participants regardless of condition, an appropriate referral for CR was confirmed after randomization. Over the course of the study participants completed three assessments – one at intake, one after four months, and one after one year. Clinical (i.e., cardiorespiratory fitness, body composition, and cardiac-related quality of life) and sociocognitive (i.e., Beck Depression Inventory, Achenbach System of Empirically Based Assessment, and Behavior Rating Inventory of Executive Function) measures were obtained at each assessment. Participants randomized to the UC condition were contacted weekly by study staff for adverse event checks, but received no additional intervention. Participants randomized to the CM condition were immediately assigned a case manager. Case managers met with their participants, usually within 24 hours of consent while they were still in the hospital, to introduce themselves during an initial check-in. Within the first week of consent they completed a longer, more thorough initial needs assessment with their participant and established behavioral goals. For the next 16 weeks, case managers met with their participants at least once a week, typically over the phone, to discuss progress on these goals and address any problems or barriers that had arisen. Case managers also were available via phone outside of these regular meetings during normal working hours and Saturday mornings. Participants randomized to the FI condition could earn money for completing an initial CR orientation and attending CR sessions. Twenty dollars could be earned for completing the CR orientation session. CR attendance was reinforced on an escalating schedule starting at $10. Payments increased by $2 for each successive session attended, and capped out at a maximum of $40 per session. Unexcused absences resulted in the incentives for that session not being earned, and the potential earnings for the next scheduled session being reset to $10. Successful participation of two consecutive sessions following the reset resulted in the incentives being returned to the amount prior to the reset. In total, participants could earn $1220 for attending the initial orientation and all 36 sessions of CR. The primary outcome of interest was the percentage of participants who completed at least 30 sessions of CR. Secondary outcomes included the number of sessions completed, cardiorespiratory fitness (peak VO2 and estimated metabolic equivalents (METs)), body composition (waist circumference and BMI), depression scores, and both general and cardiac-related qualify of life. Conclusions:The two interventions involving financial incentives (i.e., financial incentives alone and financial incentives plus case management) significantly improved CR adherence compared to usual care. Subsequent analyses revealed that the combination of financial incentives and case management led to greater improvements in CR attendance than financial incentives alone.

  Study phs003737

• Novel mutational mechanisms and drivers in Pancreatic Neuroendocrine Tumours

  Pancreatic neuroendocrine tumours (PanNETs) are increasing in prevalence due to earlier detection, consequently creating challenges in clinical care, as current classification permits unsatisfactory therapeutic stratification. We performed whole genome sequencing of 102 primary PanNETs and defined the genomic events underlying their pathogenesis. We describe the mutational signatures they harbour, including a novel G:C>T:A Base-Excision-Repair-deficiency signature due to MUTYH inactivation. We uncover a larger than expected proportion of germline mutations in clinically sporadic PanNETs. These include previously unreported mutations in DNA repair genes MUTYH, CHEK2, BRCA2, and PALB2, which together with MEN1 and VHL occur in 16% of patients. Somatic mutations (point mutations and structural rearrangements) commonly occurred in genes involved in 4 main pathways: chromatin remodelling, DNA damage repair, activation of mTOR signalling (including novel EWSR1 gene fusions) and telomere maintenance. Aberrations in these mechanisms are associated with subtypes of PanNET with potential clinical application for prognostic and therapeutic stratification.

  Study EGAS00001001732

• Spatiotemporal evolution and inter-patient heterogeneity in primary and recurrent/metastatic head and neck squamous cell carcinoma

  Head and neck cancer squamous cell carcinomas (HNSCCs) are heterogeneous in terms of origin and aetiology. In addition, there is uncertainty about the spatiotemporal genetic evolution from initial diagnosis to recurrence/metastasis (R/M) after primary treatments and further disease progression following systemic treatment. Changes in the genetic profile have implications on the selection of appropriate treatments for patients, especially in the era of targeted therapies and immunotherapies. Here, we analysed a cohort of 11 HNSCC patients with metachronous R/M, among whom nine had paired primary and R/M samples suitable for next-generation sequencing (multiple R/M samples collected at different time points were available for some of the patients). At the genomic level, the R/M samples shared a fraction of the somatic single nucleotide variants (SNVs) with the index primary tumours, but they also acquired many additional mutations, while losing only a few others. A similar behaviour was also observed when examining the changes of mutational signatures between primary and R/M samples. Overall, R/M appeared thus more genetically diverse than the respective primary tumours. The transcriptomic analysis showed that R/M samples had lower immune cell infiltration and several genes related to immune response were significantly downregulated compared to the primary samples. Our results underline the importance of analysing multiple samples per patient to obtain a more complete picture of the patient’s tumour and advocates a re-biopsy in the event of R/M and treatment failure, in order to select the most appropriate therapeutic strategy.

  Study EGAS00001007464

• Bleomycin Induced Pneumonitis WGS dataset

  This is whole genome sequencing data from a cohort of 18 patients with germ cell tumours or Hodgkin Lymphoma, who developed clinically significant bleomycin-induced pneumonitis despite low clinical risk. DNA was extracted from whole blood, and 150-base paired-end reads were generated on an Illumina NovaSeq 6000 instrument to a minimum 30x depth. Sequence reads were aligned to the GRCh38 reference with BWA MEM, and germline variants were called following GATK best practice procedures. The dataset comprises per-sample read alignment files in BAM format, and a joint-called germline variant file in VCF format.

  Dataset EGAD50000002221

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• Pediatric Whole Genome Sequencing Diagnostic Utility

  The standard of care for first-tier clinical investigation of the etiology of congenital malformations and neurodevelopmental disorders is chromosome microarray analysis (CMA) for copy number variations (CNVs), often followed by gene(s)-specific sequencing searching for smaller insertion-deletions (indels) and single nucleotide variant (SNV) mutations. We compared diagnostic rate of WGS to CMA and targeted gene testing of 100 patients referred to The Hospital for Sick Children Genetics clinic in 2014. WGS identified genetic variants meeting clinical diagnostic criteria in 34% of cases, representing a 4-fold increase in diagnostic rate over CMA (8%) (p-value = 1.42e-05) alone and >2-fold increase in CMA plus targeted gene sequencing (13%) (p-value = 0.0009). WGS identified all rare clinically significant CNVs that were detected by CMA. In an additional 26 patients, WGS revealed indel and missense mutations presenting in a dominant (63%) or a recessive (37%) manner. We found four subjects with mutations in at least two genes associated with distinct genetic disorders, including two cases harboring a pathogenic CNV and SNV. When considering medically actionable secondary findings in addition to primary WGS findings, 38% of patients would benefit from genetic counselling.

  Study EGAS00001001623

• Lymphoma_primary_patient_drug_perturbed_RNASeq_samples

  3'-end low-depth RNA sequencing data from 108 patients with chronic lymphocytic leukemia and 8 patients with lymphoma. Each primary patient sample was treated in vitro with DMSO as a control and with up to ten small-molecule inhibitors (ibrutinib, duvelisib, everolimus, trametinib, nutlin-3a, I-BET-762, MK2206, selinexor, compound 26, and a combination of ibrutinib and compound 26). Sequencing was performed on the Illumina HiSeq4000. The dataset contains FASTQ files.

  Dac EGAC50000000578

• Establishment of Human Trophoblast Stem Cells from Term Smooth Chorion

  Human trophoblast stem (TS) cells, which were established from blastocysts and first-trimester placental villi, can differentiate into the all trophoblastic subtypes, extravillous trophoblast (EVT) cells and syncytiotrophoblast (ST) cells. We newly generated human TS cells from the term smooth chorion (Ch-TS cells). They has the potential to differentiate into both ST and EVT cells as same as human TS cells derived from early placental villi. The transcriptomic profile of Ch-TS cells is also similar to conventional human TS cells.

  Study JGAS000777

• DNA methylation database for gynecological cancer detection, classification and assay development

  MeD-seq data (fastq files) from gynecological cancers and associated healthy tissues. In total 292 fastq files generated by MeD-seq are deposited consisting of: healthy tissues (vulva n=11, cervix n=15, endometrium n=13, fallopian tube n=18 and ovary n=13), precursor lesions of cancer (vulva n=23 and cervix n=46) and cancer (vulva n=21, cervix n=45, endometrium n=26, fallopian tube n=8 and ovary n=33)

  Dataset EGAD50000000611

• MGMT genomic rearrangements contribute to chemotherapy resistance in gliomas

  Temozolomide (TMZ) is an oral alkylating agent used for the treatment of glioblastoma and is now becoming a chemotherapeutic option in patients diagnosed with high-risk low-grade gliomas. The O-6-methylguanine-DNA methyltransferase (MGMT) is responsible for the direct repair of the main TMZ-induced toxic DNA adduct, the O6-Methylguanine lesion. MGMT promoter hypermethylation is currently the only known biomarker for TMZ response in glioblastoma patients. Here we show that a subset of recurrent gliomas carry MGMT genomic rearrangements that lead to MGMT overexpression, independently from changes in its promoter methylation. By leveraging the CRISPR/Cas9 technology we generated some of these MGMT rearrangements in glioma cells and demonstrated that they lead to TMZ resistance both in vitro and in vivo. Lastly we showed that such fusions can be detected in tumor-derived exosomes and could potentially represent an early detection marker of tumor recurrence in a subset of patients treated with TMZ.

  Dataset EGAD00001006281

• Single cell targeted DNA-sequencing (and antibody sequencing) of high hyperdiploid B-ALL

  This dataset contains all sequencing data of the publication "Single-cell DNA and Surface Protein Characterization of High Hyperdiploid Acute Lymphoblastic Leukemia at Diagnosis and During Treatment". We provide both the raw fastq-files as well as the processed data in the form of .h5 files. There are 13 patients: XJ176, XH135, XJ180, XI145, XI148, XI167, XI150, XJ175, XJ178, XI162, XF98, XG111 and XG115. Of 9 patients, also follow-up samples during/after treatment were sequenced: XJ180, XI145, XI148, XI167, XI150, XJ175, XJ178, XI162 and XG111. To identify the cell types and distinguish between normal and leukemic cells, cell surface proteins were also captured for 6 samples: XF98, XG111 (at diagnosis and during treatment), XG115, XI162 (after treatment) and XJ175 (after treatment). All samples were processed on the MissionBio platform with a custom amplicon panel, and DaB-seq for the combined targeted DNA and protein sequencing.

  Dataset EGAD50000000829

• JMML targeted sequencing (2013)

  Juvenile myelomonocytic leukemia (JMML) is a rare myelodysplastic myeloproliferative neoplasm of early childhood initiated by germline or somatic RAS-activating mutations (Chang, Dvorak et al. 2014). Clinical evolution is heterogeneous, with acute myeloid leukemia (AML) transformation in 1/3 of cases and frequent relapses after hematopoietic-stem-cell transplantation (HSCT), although some patients experience spontaneous remission (Locatelli, Nollke et al. 2005; Matsuda, Shimada et al. 2007; Takagi, Piao et al. 2013; Locatelli and Niemeyer 2015). The initiating lesion incompletely predicts outcome, suggesting the involvement of additional mutations. Genetic profiling of a large JMML cohort (n=118), including whole-exome sequencing (WES) in 30 cases, uncovered additional genetic abnormalities in 56 cases (47%). Somatic events were rare (0.38/case/Mb) and restricted to sporadic (47/78; 60%) or NF1-associated (8/8; 100%) JMML. Multiple concomitant genetic hits were identified targeting the RAS pathway in 13/78 (17%), RAC2D63V, which activates the PI3K/PDK1/AKT and the mTORC2 pathways, and a novel pathway for JMML, the polycomb repressive complex 2 (PRC2), in 26/78 (33%) of the sporadic JMML cases. Interestingly, PRC2 imbalance was recently shown to synergize with RAS activation (De Raedt, Beert et al. 2014). JMML outcome was associated to the mutational profile, suggesting a dose-dependent effect for RAS-pathway activation, distinguishing very aggressive JMML rapidly progressing to AML.

  Study EGAS00001001324

• Programmatic submission based on XML

  Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

  Documentation submission/metadata/submission/programmatic-submission-xml

• Characterization of a human iPSC-derived islet differentiation model

  To explore the contribution of islet development to T2D pathogenesis, we characterised the transcriptomes of 3 human iPSC lines (from independent donors) differentiated along the islet development lineage. Whole transcriptome RNA-seq was performed at 7 developmental stages: definitive endoderm, primitive gut tube, posterior foregut (PF), pancreatic endoderm, endocrine progenitors, endocrine-like cells, and beta-like cells (BLC). Differentially-expressed (ΔExp) genes were assigned to the stage in which they were most upregulated (versus baseline iPSC profile), and used to assess the enrichment of T2D GWAS genes, as well as to predict the upstream transcription factors at each developmental stage.We found 9409 ΔExp genes across all stages, including known markers of islet development (NEUROG3, INS). Genes ΔExp in the most-differentiated (BLC) stage were significantly enriched for genes within the 99% credible sets of T2D GWAS loci. Despite this enrichment in BLC only, over 70% of genes mapping within the credible sets were ΔExp before this stage, highlighting the relevance of key T2D GWAS genes in islet development: e.g. expression of TCF7L2 peaked during the PF stage (log2FC=1.2; q=8.5×10-10). REST and LMNA are also highlighted by the analyses as having a potential function in islet development, considering their pattern of expression and those of the genes they regulate. Transcriptomic signatures derived from this iPSC differentiation model highlight T2D-associated GWAS loci, monogenic diabetes genes and potential master regulators of gene networks with plausible function in islet development. All these provide clues for developmental mechanisms contributing to T2D diabetes pathology.

  Study EGAS00001002721

• Intraductal transplantation models of human pancreatic ductal adenocarcinoma reveal progressive transition of molecular subtypes

  Pancreatic ductal adenocarcinoma (PDAC) is the most lethal common malignancy, with little improvement in patient outcomes over the past few decades. Recently, subtypes of pancreatic cancer with different prognoses have been elaborated. However, the inability to model these subtypes has precluded mechanistic investigation of their origins. Here, we present an orthotopic xenotransplantation model of human patient-derived PDAC organoids in which organoids are grafted via direct injection into the pancreatic duct of immunocompromised (NSG) mice. Tumors that arise from these intraductally grafted organoids (IGOs) enable the distinction of the two main PDAC subtypes: intraepithelial neoplasms from this model progress in an indolent or invasive manner representing the classical or basal-like subtypes of PDAC, respectively, depending on which organoid they originate from. RNA-sequencing was used to characterize the tumors that resulted from IGO xenografts, and to compare the fast- and slow-progressing IGO tumors. Tumors generated using a traditional orthotopic xenograft model, in which organoids are injected into the parenchyma of the pancreas (i.e. orthotopically grafted organoids, or OGOs), were also sequenced for comparison with the IGO tumors. To further characterize the model, laser-capture microdissection followed by RNA-sequencing was used to compare intraductal to invasive lesions resulting from IGOs. To better understand the connection between KRAS signaling and the fast-progressing phenotype, RNA-sequencing was used to compare cultured organoids in which oncogenic KRAS (GeneID: 3845) was hyperactivated to control organoids, and to compare laser-capture microdissected lesions derived from IGOs of KRAS-hyperactivated organoids to lesions derived from control organoids. To ascertain copy number, low-coverage, whole genome DNA-sequencing was performed on organoids cultured in vitro, and on laser-capture microdissected lesions derived from IGO tumors.

  Study phs002045

• Non-coding mutations reveal cancer driver cistromes in luminal breast cancer

  A dataset of ER+PR+ breast tumor samples that were analyzed in order to identify mutation enrichment in cis-regulatory elements and cistrome. The repository includes sequencing data from 88 patients. 26/88 were sequenced using ATAC-seq

  Dataset EGAD00001007650

• Kids First: Whole Genome Sequencing Studies of Multiplex Nonsyndromic Cleft Lip/Palate Families

  Nonsyndromic cleft lip with or without cleft palate (NSCLP) is a common birth defect that affects approximately 135,000 newborns worldwide, and imposes significant medical, psychosocial and financial burdens to affected individuals and their families. Genetic variation in numerous genes has been associated with NSCLP, however the exact mechanisms by which they contribute to the condition remain largely unknown. Here, we will use whole genome sequencing and robust analytical approaches to systematically evaluate the causes of NSCLP in 923 individuals from large multigenerational families.

  Study phs002626