19441 results for "Buy fc 26 coins Buyfc26coins.com is EA Sports official for FC 26 coins This is the best service ever..VBsp"

in 72.50 milliseconds.

• Single-nucleus RNA-sequencing data of kidney biopsies from patients with primary FSGS, maladaptive FSGS, proteinuric controls and healthy controls

  This dataset includes FASTQ files of single-nucleus RNA sequencing of cryopreserved kidney biopsy cores from adult patients with diagnosed primary FSGS (n = 9, all nephrotic), maladaptive FSGS (n = 9, not nephrotic), proteinuric controls (PLA2R-positive membranous nephropathy, n = 3), and healthy controls (n = 4). A total of 120,751 high-quality nuclei were identified, including 2,471 podocytes and 1,574 parietal epithelial cells (PECs). In addition to the raw FASTQ files, the dataset includes processed data files from all 25 samples, generated using Seurat in R: barcode files, features, count matrices, and associated metadata. Details regarding the bioinformatics pipeline can be found at https://github.com/lambrechtslab/FSGS_Deleersnijder_et_al

  Dataset EGAD50000001557

• A Multi-Gene Mutation Classification of 468 Colorectal Cancers Reveals a Prognostic Role for APC

  Colorectal cancer (CRC) is a highly heterogeneous disease, for which prognosis has been relegated to clinic-pathologic staging for decades. There is a need to molecularly stratify subpopulations of CRC to better predict outcome and assign therapies. Here we report targeted exome sequencing of 1,321 cancer-related genes on 468 tumor specimens, which identified a subset of 17 genes that best classify CRC, with APC (Gene ID: 324) playing a central role in predicting overall survival. APC may assume 0, 1, or 2 truncating mutations, each with a striking differential impact on survival. Tumors lacking any APC mutation carry a worse prognosis than single APC mutation tumors, but tumors with two APC mutations and KRAS (Gene ID: 3845) and TP53 (Gene ID: 7157) mutations confer the poorest survival among all the subgroups examined. Our study demonstrates a substantial prognostic role for APC and suggests that sequencing of APC may have clinical utility in the routine staging and potential therapeutic assignment for CRC.

  Study phs001111

• Single cell RNAseq FASTQ files of three PDAC organoid lines (P28, P40, P47) using SORT-seq

  This dataset contains raw FASTQ files from single cell RNA sequencing of three patient-derived pancreatic ductal adenocarcinoma (PDAC) organoid lines (P28, P40, P47) cultured under standard conditions. For each line, single cells were FACS sorted into 384-well capture plates, with each well containing a 50nl droplet of barcoded primers. Plates were processed following an adapted SORT-seq protocol, and cDNA libraries were generated using CEL-Seq2 with TruSeq small RNA primers (Illumina). Sequencing was performed on an Illumina NextSeq500 platform using paired-end reads (read 1: 26 cycles, index read: 6 cycles, read 2: 60 cycles). Data are controlled-access and intended for single cell transcriptomic analysis of PDAC organoid heterogeneity and WNT pathway activity.

  Dataset EGAD50000002220

• Whole exome and Transcriptome sequencing of treatment-naïve esophageal adenocarcinoma biopsies and matched peripheral blood mononuclear cells

  Exome sequencing was performed on n=28 treatment-naïve esophageal adenocarcinoma (EACs). Three to four biopsies sampling different areas of each tumor were pooled before nucleic acid extractions to mitigate the elevated heterogeneity described for EAC. WES was performed on EAC biopsies at 120X average coverage, with autologous PBMCs used as germline controls at 80X average coverage. Libraries were prepared from 30 ng of input DNA using the SureSelect QXT Human All Exon V7 kit (Agilent Technologies) and sequenced on the NextSeq 550 (Illumina), 2x150 bp. BCL files were demultiplexed to FastQ files using bcl2fastq2 software (Illumina). Three paired end sequencing batches were analyzed independently (Batch1: samples 8, 10, 11, 12, 15, 17, 18; Batch2: samples 20, 24, 25, 26, 27, 29, 30, 31, 33, 34 ; Batch3: samples 35, 37, 39, 40, 41, 43, 45, 48, 54, 55, 57). RNA sequencing was performed on n=26 treatment-naïve esophageal adenocarcinoma (EACs). Three to four biopsies sampling different areas of each tumor were pooled before nucleic acid extractions to mitigate the elevated heterogeneity described for EAC. RNAseq libraries were prepared on 50 ng of total RNA (with RNA integrity index RIN >=7) with the TruSeq Stranded mRNA library preparation kit (Illumina) in accordance with low-throughput protocol. After PCR enrichment (15 cycles) and purification of adapter-ligated fragments, the concentration and length of DNA fragments were measured using D1000 Screen Tape System (Agilent), obtaining a median insert size of 311 nucleotides. Then, RNAseq libraries were sequenced using the Illumina NovaSeq platform, 1x100 bp, obtaining on average 100 million single reads per sample.

  Dataset EGAD00001010876

• Biopsy-Derived Organoids in Personalised Early Breast Cancer Care: Challenges of Tumour Purity and Normal Cell Overgrowth Cap Their Practical Utility

  The ability to establish organoids composed exclusively of tumour rather than healthy cells is essential for their implementation into clinical practice. Organoids have in recent years emerged as a powerful tool to expand patient material in culture and generate modifiable 3D models derived from humans or animal models. For translational research, they enable the creation of model systems for an ever-increasing number of cell types and diseases. And in personalised medicine, they potentially allow for functional drug testing with high predictive power in certain settings. We found that using biopsy material from untreated, early-stage primary breast cancer patients poses significant challenges for consistently culturing tumour cells as organoids. Specifically, we observed frequent outgrowth of genetically normal, non-cancerous epithelial cells. We analysed >100 biopsy samples from early-stage breast cancer and present our large collection of >70 organoid lines. We also show methods of assessing successful tumour cell culture in a time and cost-efficient manner, proving a high rate (>85%) of normal cell overgrowth in early-stage breast cancer organoids. Finally, we show a number of successful attempts to culture cancer organoids from mastectomy-derived tissue of advanced, metastatic breast cancer. We conclude that the usefulness of organoids from early breast cancer for translational research and personalised medicine, especially guidance of adjuvant or post-surgical maintenance therapy, is strongly limited by the low success rate of culturing cancerous cells under organoid conditions.

  Study EGAS50000000605

• What is a DAC?

  What is a DAC? Given the complexity, scale, and diversity of global submitters and studies, the EGA operates a distributed data access model in which requests are made to the data controller, not to the EGA. The European Commission defines a data controller, in the General Data Protection Regulation (GDPR), as the person that determines the purposes for which and the means by which personal data is processed. A Data Access Committees, commonly referred to as DACs, comprise on or more individuals (or data controllers) that review data access requests and make decisions on who can access personally identifiable genetic, phenotypic, and clinical data deposited at the EGA. Therefore, the members of a DAC should be individuals who have the authority to approve data access requests. The animation describes how you can authorise access to your sensitive data with the help of Data Access Committee and Authorisation tool. Acknowledgement to CSC - IT Center for Finland, Elixir Finland, Elixir Europe. Frequently Asked Questions How can I create a Data Access Committee? How can I create a Data Access Committee? The members of a DAC can come from different areas of expertise, such as data management, data analysis, information technology, legal and compliance, subject matter experts, privacy and security, and representatives from the organisations or individuals that provide data to the DAC. The specific members of a DAC can vary depending on the needs of the organisation and the type of data being managed. The EGA strongly suggests checking with your organisation to align with its regulations How should a DAC be named? The chosen name must be informative to the applicant.  For example, internal identifiers, such as grant numbers, should not be used. Individual PI names should also not be used. DAC's are often named after the organisation or department of the data source.  Browse the full list of DAC names currently in the EGA. How can I become an EGA DAC contact? To register a DAC at the EGA you must create first as an EGA user. Once your EGA user has been approved by the Helpdesk team, you will be able to log in to the DAC Portal. How can I register a DAC? To register a DAC, follow the DAC Portal instructions.  You will be required to provide a DAC name, name of the individual(s) that make up your DAC and contact details for your DAC including your Institutional email(s). Wherever possible, the DAC should make sure that all points of contact are readily available and able to answer any initial data requests/queries in < 2 weeks.  Once your DAC is registered, you will have to wait upon the validation from our Helpdesk team. As soon as all the validations have been completed, your DAC will be activated. Alternatively, you can also establish a DAC at the EGA during a programmatic submission through Webin API. Which are the possible roles of a DAC contact? There are two possible roles for DAC contacts: member and admin. An admin has additional privileges compared to a member: An “admin” can manage data requests, create and edit policies, edit the content of the DAC, add or remove contacts, and decide the role of each contact. A “member” can manage data requests and create policies. However, a member does not have permission to modify DAC details, edit information from policies where they are not admins, or add/remove contacts. There is no limit to the number of admins in a DAC, and each admin is responsible for deciding who should have editing privileges. This allows for a more decentralised and democratic approach to managing the DAC. How can I modify the information of a DAC? To modify a DAC, follow the instructions here. Keep in mind that only DAC contact with an admin role can modify the information of a DAC. If your DAC was registered before the lauch of the DAC Portal, and its ID is EGAC0 (not EGAC5), you must use the programmatic submission to modify it. Please, do not hesitate to contact our Helpdesk team if you need help with this! To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What’s the link between DAC, policy and dataset? A dataset is linked to one single policy. At the same time, one policy has a one to one relationship with a DAC. In this example, you can see that in this dataset page, we are only showing the information of one DAC (1 dataset - 1 DAC). However, the ratio of objects does not work the same in the other direction. One DAC can own multiple policy objects. And each policy object can be reused in several datasets. Thus, one DAC can manage one or more datasets. In this example, you can see that in this DAC page, we are showing all the datasets that are managed by one DAC (1 DAC - >400 datasets). EGA Data Access Committee Best Practices Which are the EGA DAC best practices? Refer to DAC Best Practices What happens if a DAC member changes institutions? EGA is committed to the protection and ownership of the data stored in our systems. We respect the institution's ownership of the data, and as such, if a DAC member changes institutions, the ownership of the data will not be transferred to the new institution. Therefore, before changing institutions, we request that the DAC contact add a new member who will replace them once they no longer work at the institution. This ensures that the data remains protected and is accessible to authorised personnel at the institution. To prevent potential data breaches and ensure adherence to GDPR regulations, it is essential that the European Genome-Phenome Archive (EGA) is informed via the Helpdesk team of any changes to the Data Access Committee (DAC). This should be done in addition to any changes being made on the DAC portal. Data Controllers (as per the definition in the DPA) are also responsible for notifying the previous DAC of any modifications. Without proper notification, changes might not be automatically updated in our system, leading to the risk of incorrect permissions being applied and potential data access issues. Therefore, it is imperative that all Data Controllers follow this protocol to maintain data integrity and security. What happens if EGA detects an unresponsive DAC? EGA defines an unresponsive DAC as a DAC with one or more contacts who do not respond to data access requests. EGA has procedures in place to identify these types of DACs, escalate the issue, and attempt to reassign the DAC to a responsive contact. This is a crucial step in ensuring that data can be accessed and utilised by researchers. If EGA identifies an unresponsive DAC, the organisation will first try to resolve the issue by escalating it to the appropriate parties. This may involve attempting to reassign the DAC to a more responsive contact. Unfortunately, in situations where we cannot reassign the DAC, the dataset will be withdrawn from the public website and the files will be removed from our system. If an EGA ID is referenced in a publication, the EGA will take extra steps to ensure that the public is made aware of the data's unavailability. I don't want to receive an email notification for pending requests. How can I do that? If you are an EGA DAC with pending requests, you will always receive emails for new data access requests. However, 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! How can I manage data access requests? What documentation does the DAC need to provide? Each dataset that is submitted to the EGA must be linked to a policy object. The policy is a Data Access Agreement (DAA), which defines the terms and conditions of using the dataset, such as how the data files should be stored once downloaded or details of publication embargoes that should be observed by the approved user. As part of the Data Access Agreement, information regarding the application can be captured to help inform the DAC when making its decision. For example, requestors could be asked to provide a proposed title for their research and a proposal of how the data will be used. By asking for provision of such information the DAC can be assured that the requestor fully understands any consents associated with the data. It is important that accounts created at the EGA, are created solely for those individuals that will be downloading the data from the EGA. As part of the data access request, we strongly encourage you to identify individuals that will need an account at the EGA in order to prevent sharing of login details, which is strictly prohibited under EGA user account policy. Such information can easily be captured in the DAA. NOTICE The data access agreement template below is provided for guidance only and should be adapted as you see fit to suit your own purpose. In the interest of promoting data sharing, we suggest that if an agreement cannot be met around clause 19 in this example that both parties should agree to remain silent, and that the clause should be removed from the agreement. Example DAA How can the DAC provide the DAA? The DAC should provide their own DAA when registering a policy. Data requestors will download this document and should fill it in and send it back to the DAC. Data access decisions should be based on such documentation. The DAA can be downloaded through the request data webpage. Once it has been filled in, the signed copy of the DAA can be uploaded back to the request data webpage and sent to the DAC for review. How can I grant access to the data? Once you receive a data access request, you can login to the DAC Portal. In this portal you will see all your pending requests and will be able to grant or decline access to the requestors. I am a member of the Data Access Committee. Could I approve somebody else to deal with the requests on my behalf? If you want to delegate data access decisions to someone else, make sure that the individual's account is officially registered as a member of the DAC. Remember that a DAC contact with an "admin" role can always add new members to an existing DAC, remove members, and modify contact details through the DAC Portal. Can I automatise the process of managing data access requests? The answer is yes! You can use a programmatic approach using our DAC API! Check out the DAC API specification! Data Breach What should a DAC do if they suspect a breach? If a DAC suspects a data breach of one or more of their datasets, they should immediately contact the EGA Helpdesk team at this link. The DAC must provide the following information when contacting the EGA Helpdesk team: A list of affected datasets An estimated date of the data breach (or interval of dates) A list of unauthorised users who accessed the data (if available). Otherwise, they can provide a list of authorised users for the affected datasets Any observations they would like to raise to the EGA team Once the DAC has contacted the EGA team, we will respond within 48 hours (please allow some leeway during peak times) and activate our data breach protocol. What can I expect from the EGA if they detect a breach? Once the EGA determines that a security incident has occurred, we will notify all DAC members that a data breach has been detected, and take steps to contain the incident. Containment approaches may include: Revoking a data provider's access to the EGA resources, such as by changing passwords. Removing affected EGA datasets from distribution, such as by withdrawing a dataset. Disabling certain functions or services, such as the EGA ingestion pipeline. Shutting down the system or disconnecting it from the network. After the incident has been contained, the EGA will determine whether it is necessary to eradicate components related to the incident. Finally, the EGA will enable recovery of the service to normal operation and confirm that all services are functioning normally.

  Documentation access/data-access-committee/what-is-dac

• RNA-seq samples

  Raw FASTQ files obtained by RNA sequencing of tumor samples from patients (age 12-29) with newly diagnosed, recurrent intermediate or high-grade sarcoma.

  Dataset EGAD00001008393

• WTCCC case-control study for Hypertension

  WTCCC genome-wide case-control association study for Hypertension (HT) using the 1958 British Birth Cohort and the UK National Blood Service collections as controls.

  Study EGAS00000000009

• Mitochondrial DNA sequencing of human iPSC, parental cells, and iPSC derived cardiomyocytes

  Dataset contains whole mitochondrial DNA sequencing data in fastq format (Illumina MiSeq paired-end) of 62 samples, in total. Those samples include sequencing data of the endothelial cell populations of 10 different donors and of 26 early-passage iPSC clones derived thereof. Moreover, the dataset contains the data of 7 of those iPSC clones sequenced additionally in passage 30 and 50, each. Lastly, 4 iPSC clones were sequenced during directed cardiomyocyte differentiation, each at day 0, 5, and 15 of differentiation.

  Dataset EGAD00001008021

• Cell-free DNA Methylome Analysis Enables Early Preeclampsia Prediction

  This dataset contains in solution target-enrichment bisulfite sequencing of placental tissue, buffy coat and plasma DNA from pregnant women. Blood samples were taken for cell-free DNA (cfDNA) DNA extraction from 64 women at the time of early-onset preeclampsia (PE) diagnosis, or from 38 controls (uncomplicated pregnancies) at a similar gestational age that did not develop preeclampsia subsequently. Among these subjects, plasma samples from 7 PE patients and 6 controls were also subjected to oxidative bisulfite sequencing. Placental tissues from 11 PE and 26 control subjects after delivery, and buffy coat from 16 PE and 16 control subjects at the same time of cfDNA sampling were profiled. A discovery cohort for early PE assessment in the first trimester was collected. In this cohort, cfDNA from 75 pregnancies that went on to develop early-onset PE and from 124 matched controls were collected and methylome sequencing were carried out. An independent validation cohort to validate early PE assessment with methylome profiling was collected as well. This validation cohort includes cfDNA samples from 61 PE and 136 control pregnancies.

  Dataset EGAD00001010159

• How to upload GPG files

  Uploading files Users that holds an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• Longitudinal snRNAseq and DNAseq of IDHmutant glioma

  We collected longitudinal glioma samples from 35 patients with an IDH-mutant oligodendroglioma (n = 13) or IDH-mutant astrocytoma (n = 22) diagnosis based on 2021 WHO glioma classification at two or three time points (n = 75 samples). For each patient, we designated the two earliest samples as the initial and recurrence for longitudinal analyses. In 17 of 35 longitudinal pairs, the initial sample was obtained at primary diagnosis, whereas the remaining 18 cases the initial samples were collected at a subsequent surgery. Between the initial and recurrence samples, 26 of 35 patients received radiotherapy and/or alkylating chemotherapy, whereas no adjuvant treatment was reported for the remaining patients. To comprehensively investigate IDH-mutant glioma evolution, we used snRNAseq and bulk DNA/RNA sequencing from the same resected glioma samples. A subset of these samples was profiled with simultaneous snRNA-ATAC sequencing (48 out of 75), including 21 matched longitudinal pairs,

  Dac EGAC50000000973

• 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

• WTCCC case-control study for Rheumatoid Arthritis

  WTCCC genome-wide case-control association study for Rheumatoid Arthritis (RA) using the 1958 British Birth Cohort and the UK National Blood Service collections as controls.

  Study EGAS00000000011

• WTCCC case-control study for Type 1 Diabetes

  WTCCC genome-wide case-control association study for Type 1 Diabetes (T1D) using the 1958 British Birth Cohort and the UK National Blood Service collections as controls.

  Study EGAS00000000014

• WTCCC case-control study for Type 2 Diabetes

  WTCCC genome-wide case-control association study for Type 2 Diabetes (T2D) using the 1958 British Birth Cohort and the UK National Blood Service collections as controls.

  Study EGAS00000000016

• WTCCC case-control study for Coronary Artery Disease

  WTCCC genome-wide case-control association study for Bipolar disorder (CAD) using the 1958 British Birth Cohort and the UK National Blood Service collections as controls.

  Study EGAS00000000003

• 10x Genomics raw data of intestinal plasma cells

  The dataset contains raw fastq files (fastq.gz) for Chromium Single Cell 5’ gene expression (GEX), human B cell VDJ and feature barcode (CSP) sequencing from transglutaminase 2-specific and other small intestinal plasma cells isolated from four untreated celiac disease patients. Single cell 5’ gene expression, V(D)J-enriched and cell surface protein libraries were generated using Chromium single cell kits, and barcoded cDNA from a total of 5,000-10,000 cells per sample was generated using the 10x Genomics Chromium Controller. The libraries were pooled prior to sequencing on a NovaSeq 6000 instrument (Illumina) using the following configuration: read 1: 26 cycles, read 2: 89 cycles, index read 1: 8 cycles.

  Dataset EGAD50000000342

• WTCCC2 case-control study for Ulcerative Colitis

  WTCCC2 project genome-wide case-control association study for Ulcerative Colitis (UC) using the 1958 British Birth Cohort and the UK National Blood Service collections as controls.

  Study EGAS00000000084

• NHLBI TOPMed: Best ADd-on Therapy Giving Effective Response (BADGER)

  BADGER is a 56-week randomized, double-blind, three-treatment, three-period cross-over trial that will evaluate the differential improvement in control that is achieved following three separate treatment interventions in children whose asthma is not acceptably controlled on a low dose of ICS (per NAEPP guidelines). All participants will enter an 8-week run-in period during which time they will receive a dose of 1x ICS (fluticasone 200 &#956;g/day). During this 8-week time period, running 2-week averages to establish the lack of acceptable asthma control will be calculated. Thus, a child could qualify for randomization at any time during this 8-week run-in period. This approach should maximize both patient safety and successful enrollment. Children will continue to receive 1x ICS during the entire treatment phase. During each period of the treatment phase, they also will receive one add-on therapy in the form of LABA, LTRA or additional 1x ICS. The order of the add-on therapy assignment will be determined by randomization into one of six treatment sequences (order determined randomly). Each treatment period will be 16 weeks in length; the initial 4 weeks of each period will be considered to be the washout period for the previous treatment. The primary outcome measures will be frequency of asthma exacerbations, asthma control days, and FEV1.

  Study phs001728

• From research to data sharing: exploring EGA user's experiences

  The Cell Plasticity and Regeneration Group at the Bellvitge Biomedical Research Institute-IDIBELL focuses on the process of recruitment of macrophages that takes place in the small intestine during injury and healing. They recently published a paper titled “Mucosal Macrophages Govern Intestinal Regeneration in Response to Injury" in Gastroenterology Journal. As part of the research, some experiments were conducted using human intestinal organoid lines. These cells were processed for RNA sequencing, and the sequencing data were deposited at the EGA to be made available to the scientific community. When dealing with human genomic information, repositories must ensure the availability of the datasets while ensuring data protection. In this context, the European Genome-phenome Archive stands as a service for secure archiving and sharing of genetic, phenotypic and clinical data resulting from biomedical research. Following the recent publication of their paper, we took the opportunity to talk to Ilias Moraitis, first author, and Jordi Guiu, group leader, to find out about their experience with data sharing. Could you explain the focus of your research? In the lab, we study intestinal regeneration and how immune cells participate in this process. We use several techniques: engineered mouse models, image tracing, as well as mouse and human cells intestinal organoids. What challenges do you face regarding data management? We didn’t have a lot of problems. Always the informatic part, the data analysis, can give problems. But everything was smooth and working. We think it’s very important to deposit the data in repositories. For the mouse data it is very straightforward, but for us it was the first time depositing human data, which is sensitive because it comes from patients, and this is legally regulated. That’s why we thought about the EGA, and it was our first time. Why do you think it is important to submit data to repositories such as EGA? Because we think data is important for the science. Nowadays, we are sequencing a lot everywhere worldwide and having these resources shared with the scientific community it’s not only good for science, but it is also saving money and reducing costs. And there is so much data in there that can be used for other projects and for other questions. And it saves time! How was the process of submitting the data to the EGA? The communication worked very well but it was slower than we would like. But I think this is something we learn on the way. People usually wait until the last minute to do this before publication but if you know it in advance, you can start the process earlier. If you had to repeat the process, would you do anything differently? It’s like everything, isn’t it? For the first time you don’t know, you aren’t sure, but for the second time you know the steps, you know what to do and it’s faster. Of course, we would to do it earlier. Also, there were some things related to the control access that we didn’t know how to manage, but it was something more internal to us. Who is going to receive the communications and when, is our ethical committee going to evaluate this? All these technicalities that we didn’t know before starting this process, so we had to think about all these things. Next time it will be faster on our side. Do you have any suggestions for us to improve the submission process? Maybe we’ll need to ask our bioinformatician who did it! He was in charge of this part. Besides that, we think if the process were faster, it would be better for everyone. Also, in science a lot of times you have to do a lot of things at the very last minute, because of the nature of the experiments, or the need to accomplish for submitting a paper. Being faster in the process would be a plus. On your side, we went through the process and were able to find some information, but there were aspects we weren't aware of and weren't sure how to handle. I'm not sure if other institutes have different protocols for managing data requests or how they handle these internally. We believe the main issue lies in how the forms are filled out. Do you have any recommendations for other submitters? The main advice is to do this with enough time. Submit the data when you have the sequences, and don’t wait until the last minute. And then it can be under embargo, so you don’t need to make it public at that moment. As soon as you sequence, upload it and then it will be there for whenever you need to publish. How do you think we could encourage other researchers to submit their data? There are different layers here. One is that it is mandatory. You have to do this. The other is that we belong to a research community, to the same community and sharing this is making our research community stronger and more efficient. And then, also because this gives you visibility. The data is there, other people can analyse your data, and this also will bring citations to your papers. It has many advantages.

  Blog from-research-to-data-sharing

• Genomewide Association Study of Inflammatory Bowel Disease

  WTCCC genome-wide case-control association study for Inflammatory Bowel Disease (IBD) using the 1958 British Birth Cohort and the UK National Blood Service collections as controls.

  Study EGAS00000000006

• Germline RUNX1 Variation and Predisposition to Childhood Acute Lymphoblastic

  Somatic mutations of RUNX1, which encodes the myeloid and lymphoid transcriptional factor RUNX1, are common in both B- and T- acute lymphoid leukemia (ALL) and are associated with poor prognosis of T-ALL. However, there has been no comprehensive investigation of the pattern or prevalence of RUNX1 germline mutation in both B- and T-ALL. Here we report germline RUNX1 variants in 1.23% of B-ALL and 2.11% of T-ALL, identifying 31 unique variants in 62 B-ALL and 18 unique variants in 26 T-ALL children. The majority of frameshift and nonsense variants affected RUNX1 function in transcriptional regulation, hematopoiesis, and cellular proliferation. We identified JAK3 as the most frequent somatic mutation in T-ALL with RUNX1 variants. These results not only identify RUNX1 as a leukemia predisposition gene but also further underline the importance of germline genetic variants to the development of ALL

  Study EGAS00001005403

• Genome-Wide Association Studies of Prematurity and Its Complications (African American)

  Preterm delivery resulting in the birth of a premature infant is a complex problem with a devastating impact on individuals, families and society. The prevalence of preterm birth has increased steadily in developed countries over the last 20 years and more than three million children die of preterm birth worldwide each year. Despite the importance of the problem and its disproportionate occurrence in poor and minority populations, the underlying causes have been difficult to identify. Spontaneous preterm labor has as its suspected triggers infection, stress, poor nutrition and inherited factors. The single best predictor for preterm delivery is a previous preterm birth. Studies of twins and of recurrences within families provide evidence that genetic factors underlie a substantive component of the risk for prematurity. One major challenge in studying genetic factors in prematurity is that the risk case is not truly established. The genetic risk could reside either in the mother and her uterus or in the infant/placenta. Identification of genetic factors in the mother and/or infant could provide insights into identifying relevant environmental covariates that may be more amenable to rapid interventions but difficult to find using standard epidemiology alone. A comprehensive genome-wide association study (GWAS) is the ideal way to identify those genes that would not be suspected based on our current understanding of the biology of parturition. We are using 2200 African American samples with term or preterm labor. A subset of these (~800) are infant samples recruited by the Neonatal Research Network as part of a study on cytokines and infection in extremely low birth weight infants (Schelonka RL, et al., 2011. PMID: 21145756). Therefore, this group consists of infants &lt;1,000 grams with clinical outcome data for the infant allowing study of the genetic contributors for not only preterm birth but also the complications that often accompany preterm birth. The result will enable a better understanding of the biology of parturition and suggest environmental modifications that can prolong gestations to improve neonatal and adult outcomes. 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 preterm birth through large-scale genome-wide association studies of African-American cases and controls from multiple sites in the United States. 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 phs000353

• Genome-Wide Association Study of HIV-1 Host Genetics Among Injection Drug Users

  The overarching goal of this project is to identify and characterize genetic determinants of HIV 1 susceptibility and resistance in samples of African American (AA) and European American (EA) injection drug users (IDUs) by conducting (1) a case/control genome-wide association (GWA) study of HIV 1 infection (positive/negative); (2) a case-only GWA study of viral load among HIV+ IDUs. The study uses existing samples and data from Urban Health Study (UHS) (PI: Alex Kral), which was the longest-running study of street-recruited IDUs in North America, from 1986-2005. UHS was a serial, cross-sectional sero-epidemiological study. Data were collected every 6 months in communities with a high prevalence of injection drug use in the San Francisco Bay Area. It used targeted sampling in neighborhoods at easily accessible community field sites, such as churches, single room occupancy hotels, and community centers. Eligibility criteria for initial entry to the study were (1) injection drug use in past 30 days; (2) ability to provide informed consent; and (3) age 18 or older. The UHS cohort includes over 9,000 African American and European American IDUs whose serum samples have been stored and data are available on HIV antibody status, HIV risk behaviors, drug abuse and demographics. The current study includes 985 HIV+ cases and 5,222 HIV- controls. Approximately six HIV- controls per case were frequency matched on: (1) self-reported ancestry; (2) sex; (3) age; (4) year of ascertainment; and (5) HIV risk class. This GWAS (DA026141) was funded by the National Institute on Drug Abuse (NIDA; PI: Eric O. Johnson). Funding support for genotyping, which was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR), was provided by NIDA and the NIH contract "High throughput genotyping for studying the genetic contributions to human disease"(HHSN268200782096C).

  Study phs000454