455 results for "igvault fc 26 Besuche die Website Buyfc26coins.com. Super Service..KWav"

in 11.00 milliseconds.

• How to use EGA Webin?

  EGA Webin EGA Webin serves as a platform for registering metadata for array based submissions, large scale sequence submission as well as for legacy EGA submission accounts (ega-box-XXXX). For large scale submitters of sequence data you have also the option to submit metadata via XMLS programmatic submission, while new submitters are advised to utilise the Submitter Portal for their submissions. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. WEBIN actions: Register metadata for a sequence submission Register study, samples, experiments, runs, DAC, policy and dataset/s after file upload. Register components for your array-based metadata submission Register study, samples, DAC or policy before uploading files. Edit existing submission metadata Change or update previously submitted metadata. Register metadata for a sequence submission Ensure that all sequence files have been encrypted before uploading them to your submission account using the EgaCryptor. Go to the EGA Webin and log in using your submission account name (ega-box-XXX) and password. Register components of your metadata submission Study Samples Data Access Committee (DAC) Data access policy Dataset For array-base submissions: Study, Samples, Data Access Committee (DAC) and Data access policy may all be registered BEFORE file upload and dataset registration through the array-base template. Register your Study Go to the “Studies (Projects)” box Click on “Register Study” and fill in the information related to your study. Click on “Submit”, this will save the information and generate an EGA study ID. To use the study accession number in a publication, the study has to be previously released on the EGA website, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX.Further information about EGA can be found on https://ega-archive.org and “The European Genome-phenome Archive in 202 "(10.1093/nar/gkab1059)" Register your Samples Go to the “Samples” box Click on “Register Samples” Select “Download spreadsheet to register samples” and customise your template, there is a default EGA template (EGA default checklist) but more attributes can be added if required. For the EGA default checklist, there are mandatory,recommended and optional attributes. As well custom fields which can be added if required. Mandatory attributes Field Name Description tax_id Taxonomy ID of the organism as in the NCBI Taxonomy database. Entries in the NCBI Taxonomy database have integer taxon IDs. See our tips for sample taxonomy here scientific_name Scientific name of the organism as in the NCBI Taxonomy database. Scientific names typically follow the binomial nomenclature. For example, the scientific name for humans is Homo sapiens. sample_alias Unique name of the sample. If not selected system will auto generate an unique alias sample_title Title of the sample sample_description Description of the sample phenotype *** Where possible, please use the Experimental Factor Ontology (EFO) to describe your phenotypes. Recommended attributes Field Name Description subject_id Identifier for the subject where the sample has been derived from gender * Sex Optional attributes Field Name Description sex sex of the organism from which the sample was obtained disease_site Affected organ sample type Affected organ donor_id ** Identifier of the donor where the sample has been derived from *Gender should be described as 'male', 'female' or 'unknown'. If 'unknown' due to a known sex chromosome aneuploidy, please create a user defined attribute called 'Sex chromosome karyotype' and add the appropriate value, for example, 'XXY'. **Donor id (Subject id) should be a de-identified subject handle. If unknown, please add 'unknown' to the field. ***Phenotypes should, where possible, be an Experimental Factor Ontology accession. If a term cannot be found to describe your phenotype please use free text. All sample phenotypes considered important for further analysis of the data should be provided (for example, tumour type), additional phenotype attributes can be created by defining your own attributes; use the notion 'phenotype2', 'phenotype3', etc. After you have customised the fields for the sample submission, download the template and fill in the information. Example of the sample template: Finally upload the sample template to get the EGA accession IDs for the samples. Register your Data Access Committee (DAC) Further information on the role of your DAC Go to the “Data Access” box Click on “Register Dacs” Input the information about the DAC and register at least one main DAC contact. Register your Data Access Policy Your Data Access Policy provides the terms and conditions of data use, this is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAC). Go to the “Data Access” box Click on “Register Policies” Select the DAC to which this policy will be linked to and fill in the policy information. Submitting your Runs and Analyses This section is only for sequence data submission, for array-based submission it can be skipped. Please refer to our Submitting array based metadata Runs Registration Go to the “Raw Reads (Experiments and Runs)” box Click on “Submit Reads” Select “Download spreadsheet template for Read submission” Select the template corresponding to your submission type For the templates you have the option to customise the optional fields. To check their description click on “Show Description “ Download the template and fill in the required information. Example of the runs template: We recommend that Fastq, BAM, and CRAM read files are submitted using Webin-CLI When using this interface instead of Webin-CLI, raw sequences must be uploaded in one of the supported data formats before they can be submitted. The files can be uploaded using FTP or Aspera. The study and the sequenced samples must be pre-registered before the raw reads are submitted. Please note that each individual study and sample should be registered only once. You will be asked to provide information about the sequencing libraries and instruments. Submitting your Dataset This section is only for sequence data submissions, for array based submissions it can be skipped. Please refer to our Submitting array based metadata The dataset describes the data files, defined by the run (EGARXXXXXXXXXXX) and analysis (EGAZXXXXXXXXXXX) accessions that make up the dataset and links the collection of data files to a specified Data Access Committee and Data Access Policy. As a result, you must have registered your Reads and experiments, Data Access Committee (DAC) and Data access policy before submitting your Dataset. 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. Please contact EGA Helpdesk for further assistance. Go to the “Data Access” box Click on “Register Dataset” Select the Data Access Committee (DAC) and Data access policy Register your dataset After submitting your dataset you should contact the EGA Helpdesk to provide a release date for your dataset. Datasets are automatically held (i.e. not released) unless they are affiliated to a study that has already been released. Edit/update existing submission metadata Go to the “Report” section of the object you would like to edit. Locate the object and click on the arrow under action. An option menu will be displayed. Objects can be edited through their XML or with the WEBIN menu. After an object has been edited, changes would be available on the website until the submission is released again. Please contact the EGA Helpdesk if you require further assistance.

  Documentation submission/metadata/submission/EGA_webin

• Molecularly matched targeted therapies plus radiotherapy in patients with newly diagnosed glioblastoma without MGMT promoter hypermethylation (N2M2/NOA-20 phase I/IIa umbrella trial)

  Background: Patients with glioblastoma without MGMT promoter hypermethylation are unlikely to benefit from temozolomide (TMZ). Trials aiming at replacing TMZ with targeted agents in not molecularly selected patient populations have failed. Methods: This phase I/IIa umbrella trial aimed at showing safety, feasibility, and preliminary efficacy of targeted compounds in addition to standard radiotherapy initiated within 42 days postoperatively. Molecular diagnostics and bioinformatic evaluation are performed within 28 days after surgery. Stratification for treatment takes place in five subtrials, including alectinib, idasanutlin, palbociclib, vismogedib and temsirolimus, according to the best matching molecular alteration. Patients without matching alterations are randomized between subtrials without strong biomarkers using atezolizumab and asunercept and TMZ as standard of care. Primary objective of the phase I parts of the trial was dose finding or dose validation. In the phase IIa trials, centrally determined progression-free survival at six months (PFS-6) is used as endpoint for efficacy with interim analyses for futility (H0: p=0.231). Results: From May 2018 through July 2022, 301 patients were enrolled and 228 treated in 13 German NOA sites. The alectinib and vismodegib subtrials were closed since no molecularly matching patients were accrued; the idasanutlin subtrial was closed prior to the optimal dose at nine patients at discretion of the company providing the drug. The TMZ subtrial showed a PFS-6 of 18.52% (10/54 patients) (p=0.831) and a median overall survival (OS) of 12.1 months. Asunercept: PFS-6 of 15.4% (4/26) (p=0.8825) and OS of 12.8 months. Atezolizumab: PFS-6 of 21.4% (9/42) (p=0.660) and OS of 11.7 months. Palbociclib with patients demonstrating CDK4 amplification or CDKN2A/B codeletion: PFS-6 of 24.4% (10/41) (p=0.4823) and OS of 12.6 months. Temsirolimus with patients demonstrating mTOR activation: PFS-6 of 39.1% (18/46) (p=0.0109) and OS of 15.4 months. The regimen-limiting toxicity (RLT)-rate is 34.8%, which is insignificantly above the predefined unacceptable rate for RLTs of 30%. Most RLTs had severity grade 3, one RLT had severity grade 4. No RLTs resulted in death. Conclusions: N2M2 allows for elaborate molecular testing being integrated into the treatment decision and efficient determination of treatment activity for patients with newly diagnosed glioblastoma. There is clinical activity of temsirolimus in patients with tumors harboring an activated mTOR pathway although this is not positively prognostic without mTOR inhibition; there is no clinical activity for asunercept and atezolizumab in not molecularly selected patients and also palbociclib in molecularly selected patients.

  Study EGAS00001008033

• Single cell RNAseq of stenotic, inflamed and non-inflamed transmural lesions from patients with Crohn's disease

  This dataset contains a gene-cell matrix derived from single-cell RNA sequencing (scRNA-seq) data of ileal tissue from Crohn's disease (CD) patients and colorectal cancer (CRC) patients. It includes: Crohn's Disease Patients: A trio of transmural lesions (stenotic, inflamed, and non-inflamed) from each patient. Colorectal Cancer Patients: Unaffected ileal tissue used as external non-inflamed control. Cell Level Metadata: The dataset includes relevant cell-level metadata such as cell type annotations used in the study. Experimental Details: Platform: 10x Genomics Chromium Single Cell 3' GEX Sequencing: Illumina NovaSeq Processing: Data processed with Cell Ranger software. Resulting count matrices were merged for downstream analysis, including integration and dimensionality reduction. Dataset Composition: Crohn's Disease Patients: 10 patients with 3 samples each (non-inflamed, inflamed, stenotic), totaling 30 samples. Colorectal Cancer Patients: 5 patients with 1 sample each of unaffected tissue, totaling 5 samples. Data Provided: Merged Raw Count Matrix: The final merged raw count matrix used for downstream analysis. Cell Metadata File: Contains details of sample, tissue, and patient for each cell in the count matrix. Barcodes File: Indicate each cell barcode which also encodes the sample, tissue, and patient details for each cell. CD.S_Inf: Stenotic Corhn's disease inflamed samples CD.S_Sten: Stenotic CD patient stenosis sample CD.S_Prox: Stenotic CD Patient - proximal non-inflamed sample CC.C_Prox: CRC Patient proximal unaffected sample eg: A barcode 'CC.C_1_Prox_AAGTCGTAGACCCTTA' indicates CRC Patient unaffected proximal sampe from CRC Patient no.1 and the nucleic acid sequence indicate a unique cell from this sample. Total Samples: Crohn's Disease (CD) Patients: 30 samples Colorectal Cancer (CRC) Patients: 5 samples Patient_no Sample Sample_type 1 CC.C_1 CC.C_1_Prox CC.C_Prox 2 CD.S_1 CD.S_1_Prox CD.S_Prox 3 CD.S_1 CD.S_1_Infl CD.S_Infl 4 CD.S_1 CD.S_1_Sten CD.S_Sten 5 CC.C_2 CC.C_2_Prox CC.C_Prox 6 CD.S_2 CD.S_2_Prox CD.S_Prox 7 CD.S_2 CD.S_2_Infl CD.S_Infl 8 CD.S_2 CD.S_2_Sten CD.S_Sten 9 CC.C_3 CC.C_3_Prox CC.C_Prox 10 CC.C_4 CC.C_4_Prox CC.C_Prox 11 CD.S_3 CD.S_3_Prox CD.S_Prox 12 CD.S_3 CD.S_3_Infl CD.S_Infl 13 CD.S_3 CD.S_3_Sten CD.S_Sten 14 CD.S_4 CD.S_4_Prox CD.S_Prox 15 CD.S_4 CD.S_4_Infl CD.S_Infl 16 CD.S_4 CD.S_4_Sten CD.S_Sten 17 CC.C_5 CC.C_5_Prox CC.C_Prox 18 CD.S_5 CD.S_5_Prox CD.S_Prox 19 CD.S_5 CD.S_5_Infl CD.S_Infl 20 CD.S_5 CD.S_5_Sten CD.S_Sten 21 CD.S_6 CD.S_6_Prox CD.S_Prox 22 CD.S_6 CD.S_6_Infl CD.S_Infl 23 CD.S_6 CD.S_6_Sten CD.S_Sten 24 CD.S_7 CD.S_7_Prox CD.S_Prox 25 CD.S_7 CD.S_7_Infl CD.S_Infl 26 CD.S_7 CD.S_7_Sten CD.S_Sten 27 CD.S_8 CD.S_8_Prox CD.S_Prox 28 CD.S_8 CD.S_8_Infl CD.S_Infl 29 CD.S_8 CD.S_8_Sten CD.S_Sten 30 CD.S_9 CD.S_9_Prox CD.S_Prox 31 CD.S_9 CD.S_9_Infl CD.S_Infl 32 CD.S_9 CD.S_9_Sten CD.S_Sten 33 CD.S_10 CD.S_10_Prox CD.S_Prox 34 CD.S_10 CD.S_10_Infl CD.S_Infl 35 CD.S_10 CD.S_10_Sten CD.S_Sten

  Dataset EGAD50000000559

• Best Practices for DACs

  Best Practices Data access committees (DACs) are institutional safeguards responsible for ensuring a balance between data protection and accessibility. However, there are no procedural standards that apply across DACs, which can lead to inconsistencies in their reviews and compromise their quality and effectiveness. Standardising DAC processes can foster trust and mutual recognition, paving the way for greater coordination, collaboration, and delegation between DACs and other oversight bodies to improve the efficiency of data access without sacrificing protection. To provide guidance, the following are suggestions for actions a DAC might take upon receiving a data access request: Aim to respond to all initial requests in less than 2 weeks. Failure to do so may result in follow-up emails from the EGA, journals, and ultimately dataset withdrawal. First, check that the data/EGAD number is consistent with your data submission. In other words, ensure that the requester has contacted the correct DAC. Verify that the user will be using the data within the terms of consent by asking them to sign up to the terms within the DAA. Ensure that data users who are granted access to the data comply with the terms of a Data Access Agreement (DAA) and to use the data only in approved ways. Look for an institutional email address for the requester. Search for evidence that the requester is "appropriately qualified/bona fide" for using the data, for example on PubMed, Research Gate, LinkedIn, etc. Confirm that the affiliated organisation is real and that the requester still works there. Inquire with the requester about who should have accounts created at the EGA under the terms of the agreement. If a negative decision is made, promptly communicate it to the requester and support it with the terms of the Data Access Policy that the requester has not met or cannot meet. Keep the information in the DAC up to date. If you leave your institution and are unable to manage data access requests on their behalf, you should add your replacement as a new contact in the DAC. Assist with data access requests for any further questions related to your data. The EGA can only check information that has been deposited in the repository. If the user has a specific question that the EGA cannot answer, we will redirect the user to the DAC. All the EGA studies and datasets referenced in a publication under your DAC must be publicly searchable on the EGA website before the paper is released. If possible, describe the permitted purposes for subsequent research projects, including associated limits and conditions, for all resources hosted in a repository using a common ontology, such as the GA4GH Data Use Ontology (DUO). It is considered best practice to try and release data only to those with an institutional email address. This gives reassurance to the EGA, research participants, and the general public that an appropriate individual is accessing and using the data. 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.

  Documentation access/data-access-committee/best-practices

• How to upload Crypt4GH files

  Uploading files Users who hold 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. To manage the available resources, we enforce a limit of 10TB per submission account at any one time. If you exceed this limit, a “permission denied” message will be displayed. This will prevent you from uploading more files, but connecting to your inbox.For submissions larger than 10TB, please perform uploads in 10TB batches: register all the metadata and then finalise the submission. Upload the next batch of files and repeat the same metadata registration and finalisation process until you have completed the file upload. Further information can be found in the SP documentation. INBOX FTP The INBOX is only compatible with files encrypted using the Crypt4gh tool Before uploading If you are not a registered EGA user, you will first need an EGA user account. Please note that it may take a few days for your account to be activated, as it needs to be vouched for by the EGA Helpdesk. Once your account is validated, you will be able to request a submitter role. [Optional] Meanwhile, you can create and add your public key to your EGA account profile. This option is not available for old submission accounts (e.g., ega-box-NNN). As soon as you have been granted a submitter role, you will be able to connect with your username and password to the EGA inbox using the SFTP protocol. If you have also registered a public key in your profile, you can also connect using this key. To upload files to your account, you can use the graphical user interface (GUI) or the command line. Graphical User Interface (GUI)We recommend using FileZilla, a free, open-source FTP client. However, you can use any other GUI that allows connecting over the SFTP protocol. For FileZilla as your GUI, follow these steps to upload files: Create a new connection in Site Manager (File > Site Manager) and select the following options (Figure 1): Protocol: SFTP - SSH File Transfer ProtocolHost: __EGA_INBOX_DOMAIN__Logon Type: Key fileUser: your EGA usernameKey file: Path/to/your/private_keyFigure 1: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers.Click Connect, and you will log in remotely to your home directory. You can think of this folder as a storage "in the EGA cloud" in which you will add your files for the EGA. The uploading area has three folders:To-encrypt: Files uploaded in this folder will be encrypted automatically on the fly.Encrypted: Files uploaded in this folder must already be encrypted with Crypt4gh. Upload your files here if your connection is unstable or you have problems completing the upload into-encrypt.Etc: This folder contains two files that allow the server to show you your username and group instead of some internal numbers. Please do not upload files here; otherwise, you will obtain a permission denied error. Find the files you want to upload by browsing your local storage (left side of your screen in FileZilla). Select all the files you want to upload, then right-click on them and select Upload (Figure 2). Figure 2: Step-by-step process of manually uploading files to __EGA_INBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can transfer data from their local storage to the "EGA cloud" by following the depicted steps Please note that regardless of which folder you upload your files in, both folders (to-encrypt, encrypted) will point to the same path (/) (Figure 3). Therefore, you will see your files in both folders. Figure 3: Both folders, to-encrypt and encrypted, point to the same path (/)" If your connection is unstable, please encrypt your files first using Crypt4gh. Then upload them to the ‘encrypted’ folder. The example above shows how to connect to __EGA_INBOX_DOMAIN__ using the private key. However, if you prefer to log in using your credentials, you can do so. Please go to the Frequently Asked Questions (FAQs)  for more information. SFTP command line To upload files securely to your private area of the EGA, you can use SFTP(Secure File Transfer Protocol) with your favorite FTP client. Here's what you need to know to get started: Connect to the target host __EGA_INBOX_DOMAIN__. This is the new hostname for the EGA SFTP service. Log in with your EGA username and key files (or password). Upload files to your private EGA inbox to ensure that only you can access the files. By following these steps, you can securely upload your files to the EGA for safe storage and sharing. Using the SFTP command line client in Linux/Unix Open a terminal and type sftp username@hostnameEnter your EGA passwordTo see a list of available SFTP commands, type helpsftp> put – Upload filesftp> get – Download filesftp> cd path – Change remote directory to ‘path’sftp> pwd – Display remote working directorysftp> lcd path – Change the local directory to ‘path’sftp> lpwd – Display local working directorysftp> ls – Display the contents of the remote working directorysftp> lls – Display the contents of the local working directoryType the "put" command to upload files. For example: put *.bamUse the bye command to close the connection (SFTP session). After uploading- Once you have uploaded files to the inbox, please bear in mind that the checksum needs to be calculated, which can take up to two days. You will only be able to link your files to a run/analysis once the encrypted checksum has been calculated.- When linking your files to the 'Run' or 'Analysis', ensure that the file name matches the file path '/name' in the INBOX folder.- Please delete the files from your SFTP INBOX after all the runs/analyses have been registered and files are ingested (SP > Files > Files ingested). This will clear your inbox space an allow you to upload more files. This will also prevent the files from reappearing in your Submitter Portal inbox. Frequently Asked Questions Specific to the inbox What username should I use to log in to my inbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username.  If you have forgotten your registered username, please contact our Helpdesk team for assistance. How are checksums calculated in your inbox? If you encrypt the file beforehand and upload it to the "encrypted" folder, the unencrypted checksum will not be calculated until the file is ingested (i.e., until it is used in a run/analysis). If the file is uploaded to the "to-encrypt" folder, then both checksums are calculated.Please bear in mind that after files have been uploaded to the inbox, the checksum must be calculated, which can take from a few hours to two days.  Specific to using keys to authenticate Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_INBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

  Documentation submission/data/uploading-files/inbox

• 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

• National Cancer Institute Cancer Genome Characterization Initiative (CGCI)

  The Office of Cancer Genomics at the National Cancer Institute sponsored a series of studies as part of the Cancer Genome Characterization Initiative (CGCI) to assess novel emerging sequencing technologies in cancer. The CGCI program included comprehensive characterization of the genetic aberrations found in different pediatric and/or adult tumors. CGCI characterized a number of B-cell non-Hodgkin lymphomas (including diffuse large B-cell lymphoma (DLBCL) from patients with and without HIV+ infection, follicular lymphoma (FL), as well as adult and pediatric Burkitt lymphomas), and additional HIV-associated tumors (including DLBCL, lung, and cervical cancers). All data from these projects is available at the NCI Genomic Data Commons. Individual project descriptions are available by disease on the substudy pages (links are included at the top of this page). Brief summaries are as follows: Non-Hodgkin Lymphoma (NHL) - CGCI investigators probed genomic alterations more deeply than had previously been possible by using state-of-the-art RNA sequencing (mRNA-seq) and whole genome shotgun sequencing (WGS) coupled with leading edge bioinformatics, data management and analysis approaches. The project sequenced tumor DNA and/or RNA from 117 NHL tumor samples and 10 cell lines. This included the genomes or exomes of 1 Follicular Lymphoma (FL) and 13 diffuse large B-cell lymphoma (DLBCL) cases, all with matched constitutional DNA sequenced to comparable depths, RNA-sequencing (mRNA-seq) of 92 DLBCL, 12 FL and 8 B-cell NHL cases with other histologies and 10 DLBCL-derived cell lines. The DLBCL cases and cell-lines are from the two major subtypes of DLBCL: germinal center B-cell (GCB) and activated B-cell (ABC). HIV+ Tumor Molecular Characterization Project (HTMCP) - This project was a joint effort of the Office of Cancer Genomics (OCG) and the Office of HIV and AIDS Malignancy (OHAM). Its goals were to characterize HIV-associated cancers (obtained from HIV-infected patients) and compare them to the same types of cancers from patients without HIV infection. Investigators performed 30X genome sequencing of 100 cases of paired tumor and germline DNA, along with transcriptome sequencing in each of 3 types of HIV+ tumors (DLBCL, lung and cervical cancers). These platforms allow discovery of mutations both in coding and non-coding genomic regions, gene expression and genomic alterations (including translocations, insertions and deletions). Comparing tumors of cancer patients both with and without HIV-infection provides insight into the potential function of this virus in certain cancers. Burkitt Lymphoma Genome Sequencing Project (BLGSP) - This project was a collaborative effort between the National Cancer Institute and the Foundation for Burkitt Lymphoma Research to develop a databank of the many alterations found in Burkitt lymphoma (BL), an uncommon type of Non-Hodgkin lymphoma that occurs most often in children and young adults. The goal of the BLGSP was to explore potential genetic changes in patients with BL that could lead to better prevention, detection and treatment of the cancer. The project characterized the alterations of the tumors' genomes (with matched normal as control) and transcriptomes by sequencing the DNA and RNA of each case. Using the data generated, the ultimate goals of the project was to discover the molecular changes that are present in BL patients and then determine how those changes correlate with treatment regimen and outcome. CGCI data is accessible at the NCI's Genomic Data Commons (GDC) via the GDC's Data Portal and from each of the CGCI Publication Pages at the GDC (Please see the "Supplemental Links" section of any CGCI publication's "Publication Information and Associated Data Files page" at the GDC.). Available datasets include raw sequencing data, datasets generated by the original CGCI research teams (fully annotated clinical information and higher-level/analyzed molecular characterization data), as well as higher level data generated by the GDC. Please see the CGCI Use and Publication Guidelines for updated details on the sharing of any CGCI substudy data, including how to cite CGCI.To learn more about the CGCI studies, please visit the CGCI Program website.

  Study phs000235

• FIGHT-207: Anonymized Genomic Alterations and Clinical Responses

  Background: FIGHT-207 was a phase 2 study of the FGFR1-FGFR3 inhibitor pemigatinib in patients with previously treated, locally advanced/metastatic or unresectable solid tumor malignancies harboring activating fibroblast growth factor receptor (FGFR) gene alterations. Population information: 107 patients were divided into 3 cohorts: FGFR1&#8211;FGFR3 fusions/rearrangements; n=49 Activating FGFR1&#8211;FGFR3 non-kinase domain single nucleotide variants (SNVs); n=32 FGFR1&#8211;FGFR3 kinase domain mutations or variants of unknown significance (VUS) with potential pathogenicity; n=26 Participants on study had tumors that were grouped into the following histologies based on &#8805; 5 patients: Cholangiocarcinoma, gynecologic cancers (cervical, endometrial, uterine), central nervous system (glioblastoma, low-grade pediatric glioma, astrocytoma), pancreatic cancer, breast cancer, urothelial tract/bladder cancer, non-small cell lung cancer, and other (adrenal cancer, anal cancer, cancer of unknown primary origin, colorectal cancer, gastric/gastroesophageal cancer, gallbladder cancer, giant cell bone tumor, head and neck cancer, lung neuroendocrine cancer, nasopharyngeal cancer, ovarian cancer, prostate cancer, renal cell cancer, sarcoma, solitary fibrous tumor). Among the efficacy-evaluable participants, 99 had both independent review committee (IRC) central best overall response (BOR) and tissue NGS- data; 2 additional patients had Not Evaluable (NE) as central BOR Baseline tissue targeted NGS data (F1CDx, Foundation Medicine Inc.) of genomic alterations are reported for N=101 participants Baseline plasma targeted NGS analysis (PredicineCare, Predicine Inc.) of genomic data are reported for N=83 participants; data at disease-progression are reported for N=78 participants. Principal Findings: The FIGHT-207 study provided evidence of clinical benefit of pemigatinib in multiple histologies, explored the clinical actionability of various FGFR1-FGFR3 gene alterations, and leveraged the depth of translational data from targeted NGS analysis of baseline samples and plasma samples obtained at baseline and end of treatment to provide key insights into the biology of FGFR inhibition and the clinical utility of FGFR inhibitors. The FIGHT-207 article (pending in Nat.Med. NMED-A128973B) reports evidence suggesting clinical acquired resistance to FGFR inhibition via secondary FGFR mutations as well as emerging co-mutations in other oncogenic and tumor suppressor pathways. This study also provides evidence of acquired resistance to FGFR inhibition in multiple histologies beyond cholangiocarcinoma and urothelial cancers in a systemic correlative analysis of post-progression ctDNA in a trial. Data available through dbGaP: Anonymized information for 101 participants with both IRC central BOR evaluation (including 2 patients with NE as BOR) and tissue NGS data, including tumor histology, enrollable FGFR alteration, and outcome. Genomic alterations determined by baseline tissue NGS (F1CDx, Foundation Medicine Inc.) Genomic alterations determined by plasma NGS analysis (PredicineCare, Predicine Inc.) of ctDNA analysis at baseline (n=83) and at end of treatment/ disease progression (n=78) including genomic alterations that were not assessed to be Germline SNPs.

  Study phs003590

• Heart Failure Network: Entresto(TM) in Advanced Heart Failure (HFN-LIFE-BioLINCC)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To compare treatment with sacubitril/valsartan versus valsartan alone in patients with advanced heart failure with a reduced ejection fraction and recent New York Heart Association class IV symptoms.Background: Treatment with evidence-based medical therapies improves survival, reduces heart failure hospitalizations, and improves quality of life in patients with chronic heart failure with a reduced ejection fraction. However, evidence supporting the use of medical therapies among patients with advanced heart failure is limited. Patients with New York Heart Association (NYHA) class IV heart failure are not often enrolled in clinical trials.A previous trial reported that, compared with the angiotensin-converting enzyme inhibitor enalapril, sacubitril/valsartan, an angiotensin receptor-neprilysin inhibitor, reduced the relative risk of cardiovascular mortality and heart failure hospitalizations by 20% in ambulatory patients with heart failure with a reduced ejection fraction. Although patients with NYHA class IV heart failure were eligible to enroll, this population was underrepresented. The HFN-LIFE trial was initiated to provide additional information about the tolerability, safety, and potential efficacy of sacubitril/valsartan in patients with advanced heart failure.Participants: Of the eligible patients that enrolled, a total of 335 patients tolerated the run-in phase and were randomized to a treatment group. 167 patients were randomly assigned to receive sacubitril/valsartan and 168 patients were randomly assigned to receive valsartan alone.Design: The HFN-LIFE trial was a prospective, multicenter, randomized, double-blind phase 4 clinical trial. Trial enrollment was suspended early, due to the high risk for adverse outcomes associated with COVID-19 infection.Eligible patients were enrolled and began an unblinded run-in period of 3 to 7 days with sacubitril/valsartan, 24/26 mg (50-mg fixed dose), administered orally twice daily. Participants tolerating the run-in phase were randomized in a 1:1 fashion to receive sacubitril/valsartan (target dose, 200 mg twice daily) or valsartan (target dose, 160 mg twice daily). The initial doses were selected based on guidelines with dose adjustments being made every 2 weeks.The primary efficacy outcome was the area under the curve of NT-proBNP levels at 2, 4, 8, 12, and 24 weeks compared with the level of NT-proBNP at randomization. The secondary efficacy end point was the number of days the patient was alive, out of the hospital, and free from any of the following outcomes: listing for cardiac transplant, cardiac transplant, implantation of a left ventricular assist device, receipt of continuous inotropic therapy for 7 or more days, or hospitalization for heart failure on 2 or more occasions other than the index admission.Conclusions: In patients with chronic advanced heart failure with a reduced ejection fraction, there was no statistically significant difference between sacubitril/valsartan and valsartan alone with respect to reducing NT-proBNP levels.

  Study phs004171

• After the completion of CINECA, EUCANCan, and euCanSHare. What's next?

  CINECA, EUCANCan, and euCanSHare were part of the EUCAN Cluster, made up of six projects that received funding under the same Horizon 2020 call. All EUCAN projects (CINECA, EUCANCan, EUCAN-Connect, euCanSHare, Receptor Plus, and ReCoDID) were aimed at facilitating data reuse and knowledge discovery by enhancing data exchange and long-term collaboration in the health field. Here are some highlights about EGA’s contribution to these projects. CINECA: advances in Federated discovery and infrastructure for cohorts CINECA (Common Infrastructure for National Cohorts in Europe, Canada, and Africa) developed a federated cloud-based infrastructure for making genomic and biomolecular data accessible. The project has assembled a virtual cohort of 1.4 million individuals from sources such as the EGA, CanDIG and H3Africa. The EGA–CRG co-leaded a work package Work Package 1 on Federated Data Discovery and Querying. Beacon v2, championed by Jordi Rambla and Lauren Fromont, has been one of the central elements for the discovery of human genetic and phenotypic data. The EGA-CRG contributed to the development of a model for cohort discovery inside the Beacon v2 model. The team also delivered a Discovery Portal was implemented to explore cohorts and individuals of synthetic data. It is a UI that gathers a network of Beacons, a service for query expansion, and a visualisation tool. Have a look at the Discovery Portal UI, gathering a network of Beacons. You will find entities such as the Barcelona Supercomputing Center (BSC), BioData.pt and the European Genomic Data Infrastructure (GDI), among others. euCanSHare: facilitation of data access management This joint EU-Canada project aimed to build a European and Canadian FAIR platform for cardiovascular data sharing and analysis. The EGA’s tasks contributed to the development of the data management plan and data flows, main web-portal and interoperability protocols. An important part of the EuCanShare platform is the data access manager, a tool for the data owners to control the access to their sensitive datasets. We built a user-friendly interface for data access committees (data owners) to easily manage their data requests and access credentials. The data access portal facilitates the creation and internal organization of the data access committees as well as the linkage of data usage conditions to specific datasets. The interface includes filters for browsing requests and page to visualize the request history helping with the handling of data access requests. EUCANCan: toward a federation of clinical institutions in oncology The EUropean-CAnadian CANcer Network worked towards building a federated network to advance personalized medicine in oncology, by promoting the standard analysis, management and sharing of harmonized genomic and phenotypic data. The EGA led tasks on defining data flows and preparing an adapted infrastructure for long-term data storage and sharing. One of the key contributions was the conception of the EGA communities, offering standard and interoperable solutions for data discovery, processing, and sharing to projects and institutions that would like to manage and share data in the context of the EGA ecosystem. What's Next? The participation in projects such as CINECA, EUCANCan, and euCanSHare provide us with experience for future projects. We are happy to enhance data sharing and reuse, vital for advancing clinical and genomic research. The Discovery Portal is a wonderful proof of concept for the Beacon network. Next, we will finalise both the network and the user interface, and make sure it can be applied to more clinically-centred settings like hospitals. Most data hosted at the EGA are about cancer research. Currently, we contribute to building tools and infrastructure to empower oncology research in several European projects such as EUCAIM, EUCANIMAGE and EOSC4Cancer. We also do not lose sight of initiatives in the field such as the International Cancer Genome Consortium (ICGC) with the project ARGO, whose data model was adopted in EUCanCan.

  Blog cineca-eucancan-and-eucanshare-were-concluded-in-june