16517 results for "sec+and+unspecified+malignant+neoplasm"

in 56.44 milliseconds.

• Spatio-temporal analysis of prostate tumors in situ suggests pre-existence of treatment-resistant clones

  The molecular mechanisms underlying lethal castration-resistant prostate cancer remain poorly understood, with intratumoral heterogeneity a likely contributing factor. To examine the temporal aspects of resistance, we analyzed tumor heterogeneity in needle biopsies collected before and after treatment with androgen deprivation therapy. By doing so, we were able to couple clinical responsiveness and morphological information such as Gleason score to transcriptome-wide data. Our data-driven analysis of transcriptomes identified several distinct intratumoral cell populations, characterized by their unique gene expression profiles. Strikingly, certain cell populations present before treatment exhibited gene expression profiles that matched those of resistant tumor cell clusters, present after treatment. We confirmed that these clusters were resistant by the localization of active androgen receptors to the nuclei in cancer cells post-treatment. Our data also demonstrated that most stromal cells adjacent to resistant clusters do not express the androgen receptor, and we identified differentially expressed genes for these cells. Altogether, this study shows the potential to increase the power in predicting resistant tumors.

  Study EGAS00001006113

• An Isogenic Cell Line Panel for Sequence-based Screening of Targeted Anti-cancer Drugs

  We describe the creation and characterization of an isogenic cell line panel representing common cancer pathways, with multiple features optimized for high-throughput screening. More than 1,800 cell lines from three normal human cells were generated using CRISPR-technologies. Surprisingly, we discovered most of these lines did not result in complete gene inactivation, despite integration of sgRNA at the desired genomic site. However, a subset of the lines harbored true, biallelic disruptions of the targeted tumor suppressor gene, yielding a final panel of 100 well-characterize lines covering 19 pathways frequently subject to loss of function in cancers. This panel included genetic markers optimized for sequence-based ratiometric assays for drug-based screening assays. To illustrate the potential utility of this panel, we developed a multiplexed high-throughput screen that identified Wee1 inhibitor MK-1775 as a selective growth inhibitor of cells with inactivation of TP53. These cell lines and screening approach should prove useful for researchers studying a variety of cellular and biochemical phenomena

  Study EGAS00001005974

• Human NXPE1 mediates variation in sialic acid O-acetylation in Colon Tissue

  Sialylation, and its modifications, have important consequences for development, differentiation and immune system regulation in nearly all human tissues. An accounting of all the genes responsible for modifying sialic acids is incomplete, with only one pathway for O-acetylation being well-defined in humans. Using whole genome sequencing of normal human colorectal tissue we identify a haplotype on chromosome 11 that is associated with differences in mild periodic acid Schiff staining (mPAS), a marker of acetylation of sialic acids. Of the genes in this region, only SNPs from NXPE1 correlate perfectly in a validation data set. NXPE1 protein expression by IHC also correlates with mPAS staining patterns in homozygous, as well as heterozygous colon crypts that have undergone spontaneous gain of the mPAS phenotype. Manipulation of NXPE1 expression with CRISPR-Cas9 causes changes to modified sialic acid levels in both 2D cell line and 3D normal colon organoid models. These findings suggest NXPE1 may cause O-acetylation of sialic acids in colorectal tissue, potentially defining NXPE as a new family of sialic acid-modifying genes.

  Study EGAS00001007704

• MutWP5: CRUK Mutographs of Cancer: Cancer Mastectomy (WG)(Novaseq)

  Sequencing of LCM-derived microbiopsies from 40 women who underwent mastecomies due to breast cancer. LCM and sequencing will be conducted on both normal, unaffected breast, and, where possible, tumour tissue. Goal to assess the mutational burden, spectrum, and clonal dynamics within the tissue, and compare findings between the normal and associated cancer tissues. Whole-genome sequencing will be conducted on samples identified as promising from the initial targeted data. Results from this poriton of the study will be compared to women who had cosmetic breast reduction surgeries and those who are BRCA carriers. . This dataset contains all the data available for this study on 2023-03-08.

  Dataset EGAD00001010114

• Genomic Advances in Sepsis (GAinS): RNA-seq

  Sepsis is defined as life-threatening organ dysfunction caused by a dysregulated host response to infection. This cohort comprises a subset of patients enrolled in the Genomic Advances in Sepsis (GAinS) study, an established biobank of adult sepsis patients. Patients with sepsis due to community acquired pneumonia or faecal peritonitis were recruited from 34 hospitals across the UK from 2005-2018, with samples for functional genomics and detailed clinical information collected on the first, third and/or fifth day following ICU admission. RNA was extracted from leukocytes isolated at the bedside using LeukoLOCK kits. We have previously identified sepsis response signatures (SRSs), transcriptomic endotypes that are associated with differential early mortality (Davenport et al, Lancet Respir Med, 2016; Burnham et al, AJRCCM, 2017) and response to treatment in a clinical trial (Antcliffe et al, AJRCCM, 2018). We generated RNA sequencing data on 903 samples, including 134 samples repeated from our previously released microarray data. Libraries were prepared using NEB Ultra II Library Prep kits (Illumina) and sequenced on a NovaSeq 6000. Reads were aligned to the reference genome (GRCh38) using STAR and gene counts quantified using featureCounts (annotation Ensembl v99). Counts were TMM-normalised and log-transformed. Following QC, processed data were available on 864 samples from 667 unique patients.

  Dataset EGAD00001008730

• Whole exome sequencing data from non-small-cell lung cancer patients receiving immunotherapy prognosis

  The plasma samples and white blood cell samples were collected from 30 non-small-cell lung cancer patients and 3 healthy individuals. The solid tumor biopsy samples from 14 patients (a subset of the 30 patients) were collected. The cfDNA was extracted from their plasma samples using the QIAamp circulating nucleic acid kit from QIAGEN (Germantown, MD). The cfDNA WES library was constructed with the SureSelect XT HS kit from Agilent Technologies (Santa Clara, CA) according to the manufacturer’s protocol. In brief, 10ng of cfDNA was used as input material. After end repair/dA-tailing of cfDNA, the adaptor was ligated. The ligation product was purified with Ampure XP beads (Beckman-Coulter, Atlanta, GA) and the adaptor-ligated library was amplified with index primer in 10-cycle PCR. The amplified library was purified again with Ampure XP beads, and the amount of amplified DNA was measured using the Qubit 1xdsDNA HS assay kit (ThermoFisher, Waltham, MA). 700-1000 ng of DNA sample was hybridized to the Agilent SureSelect Human All Exon V6 (Agilent) capture library and pulled down by streptavidin-coated beads. After washing the beads, the DNA library captured on the beads was re-amplified with 10-cycle PCR. The final libraries were purified by Ampure XP beads. The library concentration was measured by Qubit, and the quality was further examined with Agilent Bioanalyzer before the final step of 2x150bp paired-end sequencing on the Illumina HiSeq X10 platform (Illumina) at an average coverage of 200. Whole-exome capture libraries of genomic DNA of the 30 non-small cell lung cancer patients were constructed via Roche SeqCap EZ Exome V3 (Roche); whole-exome capture libraries of genomic DNA of the 3 healthy individuals were constructed via Agilent SureSelect Human All Exon V6 (Agilent). Enriched exome libraries were sequenced on the Illumina HiSeq 3000 platform (Illumina) to generate 2x100bp paired-end reads at an average coverage of 200.

  Dataset EGAD00001006096

• TGF-β attenuates tumour response to PD-L1 blockade by contributing to exclusion of T cells.

  We examined tumours from a large cohort of patients with metastatic urothelial bladder cancer (mUC) treated with an anti–PD-L1 agent (atezolizumab) and identified major determinants of clinical response and immune escape. Whole transcriptome profiles were generated for 368 patients using TruSeq RNA Access technology (Illumina). Somatic mutations were determined via whole exome sequencing for a subset of these patients. - Response was associated with CD8+ T effector cell phenotype and, to an even greater extent, high neoantigen or tumour mutation burden (TMB). On the other hand, lack of response was associated with a transforming growth factor β (TGF-β) signature, particularly in patients with CD8+ T cells preferentially residing in collagen-rich matrix surrounding tumours. Integration of these three independent biological features provided the best basis for understanding outcome in this setting. -

  Study EGAS00001002556

• How to encrypt files with Crypt4gh

  File preparation Due to the processes used at the EGA for file archival the use of non-alphanumeric characters in a filename will cause issues in archival. By convention whitespaces in filenames are to be avoided and should be replaced with the underscore character (_). Before encrypting your files please make sure that any files that will be uploaded to EGA do not use special characters such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | & Crypt4gh EGACryptor Files encrypted with Crypt4gh must be uploaded via INBOX 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. 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. Encrypting your files Please note that you can also encrypt your files by uploading them directly to the "to-encrypt" folder in your upload area If your connection is unstable, please encrypt them using Crypt4gh The EGA encryption of this inbox is based on Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git Save now the following Crypt4GH public key, into a file, say ingestion.pubkey. __EGA_INGESTION_PUBKEY__ Encrypt a given file with the following command: crypt4gh encrypt --recipient_pk ingestion.pubkey < file_to_encrypt > encrypted_file.c4gh The command reads the file from stdin (with < ) and output the encrypted version to stdout (with > ). Replace file_to_encrypt and encrypted_file.c4gh with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write.

  Documentation submission/data/file-preparation/crypt4gh

• DAC Portal documentation

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

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

• 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