Multi-omic profiling of human peripheral blood is increasingly utilized to identify biomarkers and pathophysiologic mechanisms of disease. The importance of these platforms in clinical and translational studies led us to investigate the impact of delayed blood processing on the numbers and state of peripheral blood mononuclear cells (PBMC) and on the plasma proteome. Similar to previous studies, we show minimal effects of delayed processing on the numbers and general phenotype of PBMCs up to 18 hours. In contrast, profound changes in the single-cell transcriptome and composition of the plasma proteome become evident as early as 6 hours after blood draw. These reflect patterns of cellular activation across diverse cell types that lead to progressive distancing of the gene expression state and plasma proteome from native in vivo biology. Differences accumulating during an overnight rest (18 hours) could confound relevant biologic variance related to many underlying disease states.
The study aims to quantify the gene expression in blood samples in 20 prostate cancer patients under the Southern African Prostate Cancer Study (SAPCS). The objective is to identify a list of differentially expressed genes.
Treatment with checkpoint inhibitors is effective in multiple cancer types. However, even in cancers with high response rates such as Hodgkin lymphoma, some patients fail to respond or relapse following an initial response to checkpoint inhibitors. In this study, we examined patients enrolled in a clinical trial of ruxolitinib with nivolumab in relapsed or refractory Hodgkin lymphoma (NCT03681561). Patients relapsed or refractory to anti-PD1 therapy received ruxolitinib for 8 days followed by nivolumab every 4 weeks and continued ruxolitinib twice daily. For this transcriptomic study, peripheral blood mononuclear cells (PBMCs) were collected at baseline and 8 days of ruxolitinib therapy and analyzed by single-cell and bulk RNA-sequencing.
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!
The is dataset includes the whole exome sequencing of the tumor from a sinonasal glomangiopericytoma case together with the matching blood. The whole exome sequencing revealed somatic PIK3CA and CTNNB1 mutations.
Nanopore data from 3 medulloblastoma samples of which 2 are tumor-normal pairs sequenced with the MinIon and one is tumor only data sequenced on the PromethIon. The data consists of BAM files aligned using minimap2
Induced pluripotent stem cells (iPSCs) hold great promise for regenerative medicine, but genetic instability is a major concern. Embryonic pluripotent cells also accumulate mutations during early development, but how this relates to the mutation burden in iPSCs remains unknown. Here, we directly compared the mutation burden of cultured iPSCs with their isogenic embryonic cells during human embryogenesis. We generated developmental lineage trees of human fetuses by phylogenetic inference from somatic mutations in the genomes of multiple stem cells, which were derived from different germ layers. Using this approach, we characterized the mutations acquired pre-gastrulation and found a rate of 1.65 mutations per cell division. When cultured in hypoxic conditions, iPSCs generated from fetal stem cells of the assessed fetuses displayed a similar mutation rate and spectrum. Our results show that iPSCs maintain a genomic integrity during culture at a similar degree as their pluripotent counterparts do in vivo.
We would like to dissect human hair follicles and assess the mutations found in diffferent parts of the follicle eg bulge, root etc. We can also compare this with mutations found in the surrounding epidermis of the same patients (this is done under a different study). This may provide insights into the origin of PTCH1 mutants frequently seen in basal cell carcinoma but so far not located in our whole epidermis work as well as defining the clonality of the hair follicle
The first genome-wide association study of fulminant type 1 diabetes mellitus was performed in Japanese individuals. As previously reported using a candidate gene approach, a strong association was observed with multiple SNPs in the HLA region, and the strongest association was seen for rs9268853 in the class II DR region (P=1.56 x 10-23, odds ratio [OR] 3.18). In addition, rs11170445 in CSAD/lnc-ITGB7-1 on chromosome 12q13.13 showed an association at a genome-wide significance level (P=7.58 x 10-9, OR 1.96). Fine mapping of the region revealed that rs3782151 in CSAD/lnc-ITGB7-1 showed the lowest P value (P=4.60 x 10-9, OR 1.97 [95% CI 1.57-2.48]). The risk allele of rs3782151 is a cis-expression quantitative trait locus (eQTL) for ITGB7 that significantly increases the expression of this gene. CSAD/lnc-ITGB7-1 was strongly associated with the susceptibility to fulminant, but not classical autoimmune, type 1 diabetes, implicating this locus in the distinct phenotype of fulminant type 1 diabetes.
Structural variations (SVs) are large genomic rearrangements that can drive many diseases. Conventional short-reads whole genome sequencing (cWGS) allows their identification with base-pair resolution, but suffers from high false discovery rate. cWGS taps in short-range information from short-reads while linked-reads sequencing (10XWGS) utilizes long-range information. 10XWGS allows linkage of short-reads originating from the same large DNA molecule with a unique barcode captured in a gel bead in emulsion. This mitigates alignment-based artefacts from cWGS especially in repetitive regions. However, the false discovery rate of this technology is unclear. In this study, we performed a comprehensive analysis of different type and size of SVs predicted from these two technologies. The SVs common between both technologies were found to be highly specific by PCR and Sanger sequencing while validation rate dropped for uncommon events. Further, we propose a novel enrichment approach for filtering out false positive calls from both the technologies independently. To this end, we trained a machine learning model for respective technologies and used it to characterise SVs from MCF7 cell line and a primary breast cancer tumor with high precision. This approach would be valuable in understanding true mechanisms driven by SVs in various diseases.
