14305 results for ""Pennsylvania+German"+ACS+study+'Socius'+open+access"

in 21.82 milliseconds.

• VIB_VRC Data Access Committee

  Dac EGAC00001000042

• Department of Pediatrics, The University of Tokyo, PPB Data Access Committee

  Dac EGAC00001000163

• Data Access Committee for German Consortium for Translational Cancer Research (DKTK)

  Dac EGAC00001000217

• SA Pathology Data Access Committee

  Dac EGAC00001000220

• The Ingham Institute Gastro-Intestinal Viral Oncology Group Genome Data Access Committee

  Dac EGAC00001000367

• Data Access Committee for COLO829 Somatic reference standard for cancer genome sequencing

  Dac EGAC00001000408

• The Danish Reference Genome - GenomeDenmark data access committee

  Dac EGAC00001000562

• Peter Mac Translational Breast Cancer Genomics and Therapeutics Lab Data Access Committee

  Dac EGAC00001000837

• Data Access Committee for desmoplastic small round cell tumor (DSRCT) RNAseq data.

  Dac EGAC00001000851

• Nagoya University Department of Virology Data Access Committee

  Dac EGAC00001000988

• Stanford Data Access Committee for Multi-Region WES of Metastatic Colorectal Cancer

  Dac EGAC00001001164

• Data Access Commitee of The First Affiliated Hospital of Nanjing Medical University

  Dac EGAC00001001209

• Division of Molecular Oncology, National Cancer Center Research Institute Data Access Committee

  Dac EGAC00001001272

• The Lothian Birth Cohorts Data Access Committee

  Dac EGAC00001001376

• Nicola Murray Centre for Ovarian Cancer Research Data Access Committee

  Dac EGAC00001001588

• The Egyptian Collaborative Cardiac Genomics Project Data Access Committee (ECCO-GEN DAC)

  Dac EGAC00001001594

• The Egyptian Collaborative Cardiac Genomics Project Data Access Committee (ECCO-GEN DAC)

  Dac EGAC00001001680

• VIB CCB Translational Genetics Data Access Commitee

  Dac EGAC00001001808

• Data Access Commitee of the Princess Maxima Center for Pediatric Oncology

  Dac EGAC00001001948

• University of Helsinki Systems Biology and Turku University Hospital Data Access Committee

  Dac EGAC00001001978

• Data access committee for Gut microbiome of BA patients and normal controls

  Dac EGAC00001002146

• Department of Pathology and Tumor Biology, Kyoto University Data Access Committee

  Dac EGAC00001002205

• Division of Molecular Oncology, National Cancer Center Research Institute Data Access Committee

  Dac EGAC00001002331

• NPC genome-wide human SNP array (Hong Kong population) data access commitee

  Dac EGAC00001002581

• Data Access Committee of the Department of Molecular Neurology, UKEr

  Dac EGAC00001002695

• High hyperdiploid ALL single cell whole genome sequencing data Data Access Commitee

  Dac EGAC00001002737

• Tonsil cell atlas Data Access Commitee

  Dac EGAC00001002807

• High hyperdiploid acute lymphoblastic leukemia bulk DNA sequencing data Data Access Committee

  Dac EGAC00001003127

• THL Biobank Data Access Committee

  Dac EGAC00001000660

• British Columbia Cancer Agency (BCCA), PHSAs Technology Development Office, Data Access Committee

  Dac EGAC00001002903

• British Columbia Cancer Agency (BCCA) PHSAs Technology Development Office, Data Access Committee

  Dac EGAC00001002968

• Division of Molecular Oncology, National Cancer Center Research Institute Data Access Committee

  Dac EGAC00001003030

• Singapore Gastric Cancer Consortium Data Access Committee

  Dac EGAC00001003138

• EC IO Data Access Committee UMCG

  Endometrial Cancer Immuno-Oncology DAC UMCG

  Dac EGAC50000000334

• Medulloblastoma Hi-C Data Access Committee

  Contact Information Marco Gallo marco.gallo@bcm.edu

  Dac EGAC50000000357

• Data Access Committee Clinical Genetics at Karolinska Institutet (DAC-CG-KI)

  Dac EGAC00001002960

• Soskiclab data access committee

  Contact Information Blagoje Soskic blagoje.soskic@fht.org

  Dac EGAC50000000830

• Nature and Contribution of Noncoding, Regulatory Mutations in Neurodevelopmental Disorders

  This dbGaP study contains variant call files generated from whole-genome sequencing data of families with autism. The variant callers include FreeBayes, GATK, Platypus, and Strelka2. A family-level VCF file, from each caller, is provided for each family in the study. The families included in this study are from the Simons Simplex Collection (SSC), the Study of Autism Genetics Exploration (SAGE), and The Autism Simplex Collection (TASC); sequencing was performed at the New York Genome Center, as part of the Centers for Common Disease Genomics (CCDG) Consortium. The analysis to generate the variant callsets was supported by a K99 Pathway to Independence grant to Dr. Tychele Turner (1K99MH117165-01). *Access to phenotype data at the individual level for Simons Simplex Collection (SSC) subjects can be requested from SFARI Base: https://www.sfari.org/resource/sfari-base/.

  Study phs001874

• PROGRESS/ELEMENT DNA Methylation Study

  An extension to the Early Life Exposures in Mexico to Environmental Toxicants (ELEMENT) birth cohort of Mexico City, the Programming Research in Obesity, GRowth, Environment and Social Stress (PROGRESS) Cohort is an ongoing longitudinal pre-birth cohort, established in 2006 in Mexico City, partnering Icahn School of Medicine at Mount Sinai with Harvard University and the National Institute of Public Health in Mexico, which was designed to study the effects of prenatal exposure to toxic metals, air pollution, phthalates, and stress on childhood development. Pregnant women of 18 years of age and older, pregnant for less than 20 weeks of gestation, had no documentation of heart or kidney disease, no use of steroids or anti-epilepsy drugs, no daily alcohol consumption, had telephone access, and planned to live in Mexico city for the following 3 years, and receiving care through the Mexican Social Security System were initially enrolled (n=1,054). In addition to clinical, demographic and exposure data collected, cord blood was collected to interrogate DNA methylation across the genome for over 300 mother-child dyads. Clinical assessments and exposures were captured during several life stages, including prenatal, infant (0-1 year), youth (1-18 years), and adulthood (mother). The PROGRESS cohort added well-documented phenotyping of children for obesity, metabolic dysfunction, respiratory outcomes, and cardiovascular outcomes, as well as measures of air pollutant, personal care/consumer product, non-chemical stress, and metal mixture exposures. No clinical trials were conducted in this cohort. The data collected in this study should provide a unique resource to investigate DNA methylation as it relates to several environmental exposures and adverse cardiometabolic and neurocognitive health in mothers and children from a prospective birthing cohort. For access to demographic, clinical, and exposure data please directly contact study principal investigators.

  Study phs002754

• 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

• Berlin Institute for Medical Systems Biology - ccfDNA Methylation Data Access Commitee

  Dac EGAC00001003283

• The data access committee for Detecting Liver Cancer Using Cell-Free DNA Fragmentomes

  Dac EGAC00001003279

• Data Access Policy of the HCEMM - Semmelweis University, Molecular Oncohematology Research Group

  Dac EGAC00001003240

• The University of Hong Kong Gastric Cancer Exome Sequencing Project Data Access Committee

  Dac EGAC00001000032

• Cancer genomics project, the University of Tokyo Data Access Committee

  Dac EGAC00001000087

• GEH Data Access Committee

  Dac EGAC00001000139

• BGI Data Access Committee

  Dac EGAC00001000177

• Data access committee of the Prostate Cancer Research Center, University of Tampere, Finland.

  Dac EGAC00001000423

• The Chinese University of Hong Kong Hereditary Spastic Paraplegia Data Access Committee

  Dac EGAC00001000493

• Data Access Committee for the Centre National de Recherche en Génomique Humaine (CNRGH)

  Dac EGAC00001000723

• UT MD Anderson Cancer Center Department of Genomic Medicine Lipoasarcoma Data Access Committee

  Dac EGAC00001000821

• Peking University "Gene &amp; Cognition" Research Group - Data Access Committee

  Dac EGAC00001000856

• Using iPSC-derived neurons to explore cellular phenotypes associated with schizophrenia Data Access Committee.

  Dac EGAC00001000870

• Immune and Metabolic Features of Brain Metastases Melanoma (Cancer Discovery) Data Access Committee

  Dac EGAC00001001216

• DKFZ Medulloblastoma data access committee

  Dac EGAC00001001844

• ALI-cultured PCD and non-PCD patient nasal epithelium transcriptome data access committee

  Dac EGAC00001002882

• The Data Access Committee for Human Olfactory Mucosa Cells (DAC HOM) at UEF

  Dac EGAC00001003404

• Division of Brain Tumor Translational Research, National Cancer Center Japan Data Access Committee

  Dac EGAC50000000366

• human HYPOMAP

  Data access for HYPOMAP raw sequence data and result data objects

  Dac EGAC50000000410

• English Longitudinal Study of Ageing Genome-wide genotyping using the Illumina HumanOmni2.5-8

  These data are for a Genome Wide Association Study (GWAS) in the English Longitudinal Study of Ageing (ELSA, www.ifs.org.uk/elsa), building on the existing ELSA DNA Repository (EDNAR). This will establish a valuable resource for UK and international scientists, giving them access to GWAS genotyping data. Phenotype data, available on request, includes measures of personality, attitudes, behaviours as well as detailed social and economic outcomes; high quality biomarkers and other intermediate phenotypes; a range of more distal phenotypes, such as direct assessments of health (for example, hypertension, diabetes, muscle strength and cognitive function), and the opportunity to analyse existing biological samples for additional biomarkers, including metabolomic studies. Importantly, this resource would be matched with a near identical resource established in the United States for the Health and Retirement Study (HRS), giving the potential for high quality replication studies and comparative analyses.

  Study EGAS00001001036

• 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

• High-grade serous ovarian carcinoma organoids as models of chromosomal instability Data Access Committee

  Dac EGAC00001003204

• Barts Cancer Institute - Follicular Lymphoma Whole Genome Sequencing Project Data Access Committee

  Dac EGAC00001000086

• Data Access Committee: Whole Genome Sequencing of 18 sequential samples from 3 CLL patients

  Dac EGAC00001000221

• Department of Pathology and Tumor Biology, Kyoto University Data Access Committee

  Dac EGAC00001000273

• Oxford Human Islet Data Access Committee

  Dac EGAC00001000335

• Division of Cancer Genomics, National Cancer Center Research Institute Data Access Committee

  Dac EGAC00001000957

• Expanding the neurodevelopmental phenotypes of individuals with de novo KMT2A variants Data Access Committee

  Dac EGAC00001001147

• AREP(Association pour la Recherche et l’Enseignement en Pathologie) Data Access Commitee

  Dac EGAC00001001196

• Data access committee for RNA-seq as a tool for evaluating human embryo competence

  Dac EGAC00001001215

• Data Access Commitee Polymorphisms in the Mitochondrial Genome associated with Bullous Pemphigoid in Germans

  Dac EGAC00001001341

• International Genetics of Parkinson Disease Progression (IGPP) Consortium GWSS Summary Results Data Access Committee

  Dac EGAC00001002012

• Data Access Committee for the project: Epic arrays from human OB and their mimics

  Dac EGAC00001002482

• The Data Access Committee for Human Olfactory Mucosa Cells (DAC_HOM) at UEF

  Dac EGAC00001002527

• Data Access Committee of the Medical Faculty of the University of Basel (MF-DAC)

  Dac EGAC00001002981

• PELICAN45 and GP21 prostate cancer studies Data Access Committee

  Dac EGAC00001001309

• UAMS - Myeloma Institute Data Access Committee

  Dac EGAC00001000845

• Cyr61-MAC DAC

  DAC for access to dataset on Cyr61-MAC and HUVEC

  Dac EGAC50000000355

• Data access committee for datasets generated by the Tampere University Computational Biology research group

  Dac EGAC50000000177

• LEMA

  This DAC will govern access to WES data associated with the LEMA publication

  Dac EGAC50000000560

• DAC PRECISE Bennstein

  Data access control for datasets submitted by SysMed - PRECISE

  Dac EGAC50000000476

• Volkov Data Access Committee

  Sequencing and analysis data supporting published work of Hadas Volkov

  Dac EGAC50000000907

• Combination pembrolizumab and radiotherapy induces systemic anti-tumor immune responses in immunologically-cold non-small cell lung cancer

  The abscopal effects of radiation may sensitize immunologically “cold” tumors to immune checkpoint inhibition (ICI). We investigated the immunostimulatory effects of radiotherapy leveraging multi-omic analyses of serial tissue and blood biospecimens (n=293) from a phase 2 clinical trial of stereotactic body radiation therapy (SBRT) followed by pembrolizumab in metastatic non-small cell lung cancer (NSCLC; NCT02492568). Patients with immunologically-cold tumors (low tumor mutation burden, null PD-L1 expression, WNT-pathway mutated) in the SBRT arm had significantly longer progression-free survival compared to ICI alone (P<0.05). Induction of interferon-gamma, interferon-alpha, and antigen processing and presentation gene sets was significantly enriched post SBRT in non-irradiated tumor sites (FDR adjusted P<0.01). Significant on-therapy expansions of new and pre-existing TCR clones in both the tumor and blood compartments were noted in the SBRT arm (P<0.05). These findings support the systemic anti-tumor effects of immuno-radiotherapy and may open a therapeutic window of opportunity to overcome resistance to ICI.

  Dataset EGAD50000000404

• dbGaP Collection: NIH Autism -omics Studies

  Autism Spectrum Disorders (ASD) are early onset neurodevelopmental syndromes characterized by impairments in reciprocal social interaction and communication, accompanied by restricted and repetitive behaviors. ASDs afflict ~1% of the human population, and represent a major public health burden. Evidence for the etiology of ASD has consistently pointed to a strong genetic component, though the genetic architecture is indisputably complex. This dbGaP Collection consists of studies that include GWAS, sequencing (targeted, exome, whole genome), transcriptomics, etc, across many different cohorts. Many of the datasets have been curated and harmonized with NDAR prior to submission to dbGaP. Researchers who request and are approved to access this collection will be granted access to all related substudies in dbGaP as well as all NDAR data. Individual level genomics data will only be available for download through dbGaP along with minimal phenotype and pedigree information. Detailed phenotype and available imaging data related to these same research subjects are available for query and download within NDAR. The NDAR GUID will allow individual genomic data to be associated with all NDAR data collected for those subjects.

  Study phs000764

• NHLBI TOPMed - NHGRI CCDG: The Vanderbilt University BioVU Atrial Fibrillation Genetics Study

  Atrial fibrillation (also called AFib or AF) is a quivering or irregular heartbeat (arrhythmia) that can lead to blood clots, stroke, heart failure and other heart-related complications. At least 2.7 million Americans are living with AFib. Individuals with early onset atrial fibrillation (AF) are included in this study of cases from the BioVU sample repository. BioVU is Vanderbilt's biobank of DNA extracted from leftover and otherwise discarded clinical blood specimens. BioVU operates as a consented biorepository; all individuals must sign the BioVU consent form in order to donate future specimens. BioVU subjects are de-identified and linked to the Synthetic Derivative enabling researchers to access genetic data/DNA material as well as dense, longitudinal electronic medical record (EMR) information.

  Study phs001624

• All you need to know about our new DAC Portal v2

  An updated version to boost the management of DACs (Data Access Committees), policies, and data access requests. In September of 2023, we launched new services for all EGA users, including a DAC Portal. Since then, our team has been working to refine it and improve the user experience. The version 2 of our DAC Portal is now ready, with a range of new features aimed at streamlining your workflow and boosting productivity. If you are interested in learning more about the latest version of our DAC Portal, then you are in the right place! In this post, you will find information about the implemented features and more. The full documentation is available on our website. Moreover, we highly recommend exploring the DAC Portal through the Take the Tour. This said, let's get cracking! Customise your data access requests table This table offers the possibility to tailor information about the data access requests by making visible or hiding different columns regarding the Dataset Persistent Identifier, the Organisation or the requestor's name s, among others. You can choose which columns to see, depending on your needs and interests. Additionally, we have implemented two new features columns with two new functionalities, DAC Comment and Expiration Date. You can find more details in the following sections! In this table, all data access requests are displayed by default. With the latest version of the Portal, you can now apply filters, combine them, and save them for future use. Leave internal comments on pending requests and visible to all the DAC Members We understand that many Data Access Committees (DACs) cannot instantly approve or deny data access requests. Often, there's an intermediary phase where discussions and the signing of legal documents are necessary. To facilitate this process, we've introduced the DAC comment feature! When you navigate to the DAC column, you'll find two tabs: "User" and "DAC". Under "User", you'll see the message provided by the requester at the time of requesting access to the data. As a DAC member/admin, you can then add an internal comment in the "DAC" tab. These comments are visible only to DAC members/admins, ensuring confidentiality. Requesters won't have access to DAC comments. By adding a DAC comment to a pending request, we'll know that you've begun reviewing it. This allows you to filter pending requests without DAC comments to focus on genuinely new requests, and it prevents you from receiving email notifications about ongoing data requests. Set expiration dates for permissions and revoke them automatically The latest update to the DAC Portal introduces a new feature allowing you to set expiration dates for new access requests. For instance, if you anticipate approving a data access request but only wish to grant access for a limited time, you can now specify an expiration date for the granted permissions. Once this date is reached, the permissions will automatically be revoked. By default, permissions are granted indefinitely without an expiration date. However, if you ever need to revoke permissions, you can easily do so from the History page. Audit your metadata objects Managing and auditing your metadata objects will be easier from now on as the new DAC Portal enhances and facilitates your role as a Data Controller. This is possible thanks to the tables available in each of the primary tabs visible on the homepage: DACs, Policies and Datasets. Starting with DACs, this section allows to check the policies linked to a specific DAC. In Policies, you can obtain a list of the datasets connected to a particular policy. In the Dataset tab, it is possible to group datasets by either DAC or Policy, as well as the release status. Now you have the option of deprecating metadata objects that you don’t want to use anymore, or that were created by mistake. You will find the deprecate button on the EDIT page of the DAC, as well as for registered policies. You can find more information here. What's neat about this feature is that once a DAC or policy is deprecated, it becomes hidden within the DAC Portal. This ensures that you only see information that is consistently up to date! Define your preferences regarding email notifications For pending requests, you will be able to decide how often you want to get the notifications: daily, weekly or fortnightly. Remember, you will not receive email notifications for pending requests with a DAC comment! Furthermore, you have the flexibility to decide which notifications you wish to receive, such as invitations to join a new DAC or notifications regarding DAC acceptance by the Helpdesk, among other options. Check the User preference to see the complete list of available notification settings! What’s next: incoming DAC Portal API In addition to the new DAC Portal, we are excited to announce the release of the DAC API! This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can consult the DAC API specification. This post was written by Aina Jené and Ana T. Alonso.

  Blog new-dac-portal-v2

• Identification of Long Non-coding RNA Biomarker of Human Lupus Nephritis Disease Activity - Data Access Committee

  Dac EGAC00001003281

• Department of Pathology and Tumor Biology, Kyoto University Data Access Committee

  Dac EGAC00001000150

• Memorial Sloan Kettering Cancer Center - Human Oncology &amp; Pathogenesis Program (HOOP) - Data Access Committee

  Dac EGAC00001000305

• The data access committee for High Grade Serous Ovarian Carcinomas Originate in the Fallopian Tube

  Dac EGAC00001000755

• Data Access Committee for the UCSF Chordoid Glioma of the Third Ventricle Genome Project Dataset

  Dac EGAC00001000776

• The data access committee for genome-wide cell-free DNA fragmentation in patients with cancer

  Dac EGAC00001001180

• Data access policy for PDTX Breast Cancer RNA-seq data from Ros et al (2020)

  Dac EGAC00001001620

• UKR Internal Medicine III data access commitee

  Dac EGAC00001001825

• The genomic landscape of early-stage ovarian high grade serous carcinoma Data Access Commitee

  Dac EGAC00001002547

• DAC for YCC Sarcoma

  Access can be granted by contacting Hyo Song Kim (hyosong77@yuhs.ac).

  Dac EGAC50000000046

• DAC Endoresist

  Data access committee for the Endoresist project of panel sequencing: Professor Johan Hartman

  Dac EGAC50000000174

• DAC for BillionToOne

  This is the Data Access Committee for studies published by BillionToOne.

  Dac EGAC50000000418

• Pan Prostate Cancer Group Data Access Control Committee

  DACC for the PanProstate Cancer Group projects

  Dac EGAC50000000602

• DAC SysMed

  Data access control for datasets submitted by SysMed

  Dac EGAC50000000089