445 results for "fc 26 coins sale Besök Buyfc26coins.com Perfekt för att uppgradera mitt Ultimate Team..nc1F"

in 9.63 milliseconds.

• Single-cell RNA-seq of celiac disease-specific plasma cells

  Disease-specific plasma cells (PCs) reactive with transglutaminase 2 (TG2) or deamidated gluten peptides (DGP) are abundant in celiac disease (CeD) gut lesions. Their contribution toward CeD pathogenesis is unclear. We assessed expression of markers associated with PC longevity in 15 untreated and 26 treated CeD patients in addition to 13 non-CeD controls, and performed RNA-sequencing with clonal inference and transcriptomic analysis of 3251 single PCs. We observed antigen-dependent V-gene selection and stereotypic antibodies. Generation of recombinant DGP-specific antibodies revealed a key role of a heavy-chain residue that displays polymorphism, suggesting that immunoglobulin gene polymorphisms may influence CeD-specific antibody responses. We identified transcriptional differences between CeD-specific vs non-disease-specific PCs and between short-lived vs long-lived PCs. The short-lived CD19+CD45+ phenotype dominated in untreated and short-term-treated CeD, in particular among disease-specific PCs but also in the general PC population. Thus, the disease lesion of untreated CeD is characterized by massive accumulation of short-lived PCs that are not only directed against disease-specific antigens.

  Study EGAS00001004623

• All you need to know about our new DAC Portal

  With the DAC Portal, it is possible to streamline the process of managing access to sensitive data, ensuring that researchers have the necessary resources to advance scientific discovery while maintaining the highest standards of data protection and privacy. We know that, as a new tool, its first use can be complex. For this reason, in this article we will try to show all the elements of interest. Enjoy! Credentials: who needs to create a new user to access the DAC Portal and who doesn't? Only new users (since September the 12th) need to create an EGA account to access the DAC Portal. The EGA team went one step ahead by creating EGA accounts for former DAC members to login to the DAC Portal. These accounts are linked to the personal email used in the DAC structure: To check the linked email, DAC members can paste the DAC ID right after this link: https://metadata.ega-archive.org/dacs/ (e.g. https://metadata.ega-archive.org/dacs/EGAC00001002543) In case of password oblivion, it is possible to set a new one. All the process is channelled through the personal email. Some DAC members may be interested in updating the DAC email. This action can be done contacting our Helpdesk team. For the correct functioning of the DAC Portal, users must add the missing information of the DAC Profile. For a deeper dive, check out our documentation. The first step: knowing your workspace on the Portal Once logged in to the platform using the EGA User credentials, note the sections available: DACs and Policies. In the first one it is possible to check all user's registered DACs by default. It provides a comprehensive overview of each DAC, including its EGA accessions (EGAC), title, status, and the number of data access requests associated with each DAC. Whereas the Policies section is where users can manage and view all their registered policies, along with their associated EGA accessions, links, and titles. A drop-down menu is available with shortcuts to the most useful pages in the top right corner. It is possible to check DACs and policies, as well as creating new ones. In this menu, users can also contact the Helpdesk team using the “Need Help?” section to make inquiries about DACs and policies. Comprehending the DACs list & making the most of all the features Colours are crucial in the DAC's section as they will indicate the user role and the status in every committee, namely: Yellow: you are the administrator of the DAC and have full control to add other contacts, modify the content, and manage data access requests. Orange: you are a member of the DAC and have the authority to manage data access requests but cannot make any changes to the content. Blue: you have been invited to join the DAC and need to either accept or decline the invitation. Grey: the DAC is currently pending validation by the EGA Helpdesk team. Red: the DAC has been declined by the EGA Helpdesk team. Discover more information on how to view the message from Helpdesk containing the declination reason or how to validate or reject a DAC invitation by taking the tour of the DAC Portal. How to create, register and edit a DAC Creating a DAC is an easy process that only requires users to complete the necessary information. After that, the EGA Helpdesk team will review the proposal and validate the proposal. Once the DAC is validated it is possible for authorised users with admin role to edit it at any time, ensuring that all information and contacts associated with the committee is accurate and up to date. Membership management is controlled by searching for the EGA user looking for their username, email, or organisation. Please, note that for a person's details to appear in this search engine, they must have registered as a EGA user. Data Access Committee administrators manage two types of permissions that apply to contacts: Main contact and Role. Both can be modified at any time: Main contact refers to the primary person we firstly contact for any inquiry about the DAC (please, note that we can contact all DAC members, and this refers to the person we will contact first). Role defines the actions that can be taken by each contact. There are two possible status, admin and member, details of which can be found in the Take the Tour. Keep in mind that, to save the modifications, it is always necessary to click on “Update”. Moreover, it is also possible to delete any contact in a DAC whenever it is needed. The data request process: how to manage access requests The data request process is now channelled through the EGA website. Once a user sends a request access, the petition will go directly to the DAC Portal profile of the DAC members liked to the requested dataset. Whenever a request is received, a sand clock symbol will be displayed next to the DAC responsible for the dataset involved. By clicking on the DAC, it is possible to discover more information about requester(s). In this section, DAC Portal users will also be able to modify the display of the data access requests. It is possible to group requests by dataset accession or username, depending on the user preferences. Additionally, it is possible to isolate specific requests by user or dataset. To accept a request, users must slide the button to the right. Once the button turns green, it signifies that the request is accepted; the requester will be granted access to the requested dataset. To make lives easier, we have implemented a “Select all” button to easily accept or revoke multiple requests at once. To decline requests, it is necessary to slide the button to the left. A red button means the requester will not be granted access to the dataset. The DAC Portal will always ask to submit the reason why the data access was denied. Please, note that any decision, grant or denial, must be confirmed clicking the "Apply" button. This will update the status of the request and notify the requester accordingly. Taking control of the activity in the DAC Portal: checking the requests history The History button is a useful feature that allows users to access a list of all the requests that have been granted. This is especially useful for auditing purposes, as it enables to keep track of who has been granted access to the data and when. To facilitate control for those users with several requests we have included a filtering option. It allows to filter requests by user, mail, dataset, EGA ID, and date (these are combinable to boost the search). Don't forget about policies: creation, management, and update Similarly to the DACs section, in the Policies one users can manage and view all their registered policies. By clicking on any policy, it is possible to view its details as well as making any necessary updates or modifications. The sheets symbol and its adjacent number indicate the quantity of objects using a policy. By clicking in the location symbol users will go directly to the DAC page on the DAC Portal to see more information about that DAC. DAC Portal users can create new policies. The first step requires to link the policy to a registered DAC. After defining the title, users can either add a link to an external URL containing terms & conditions or write the policy content directly on the DAC Portal. Keep in mind that both options can be included. Data Use Ontology (DUO) codes can be added to new policies. These codes are used to specify the permitted and prohibited uses of the data. Please, note that some of them require a modifier to provide additional specificity. Find out more by checking out this specific content on the DAC Portal Tour. Policies can be modified at any given time by clicking on one registered policy, which will display the current information.

  Blog new-dac-portal

• PanCuRx Translational Research Initiative

  The goal of the PanCuRx TRI is to seek solutions to the high fatality rate of pancreatic adenocarcinoma (PDAC), the most common type of pancreatic cancer, by generating new knowledge about the genetics and biology of the disease, mechanisms of how tumours grow and tailored treatment options. PDAC is the fourth leading cause of cancer death in Canada and is expected to become the second-leading cause of cancer death within the next decade. The current five-year survival rate of eight per cent is the lowest of all epithelial cancers. There are major clinical challenges to treating the disease, including the fact that PDAC spreads to other parts of the body early so surgical removal of the tumour benefits few patients, that PDAC has proven relatively resistant to systemic therapies such as chemotherapy and that there has been limited benefit from the use of newer molecular targeted agents. The PanCuRx team has created the world’s first resource of tumour-purified PDAC whole genomes; more than 500 PDAC samples, with combined clinical annotation, have been successfully sequenced and analyzed at the Ontario Institute for Cancer research in Toronto. The resulting clinical genomic resource created from this data has led to multiple new findings that have established a framework to better understand PDAC biology and lays the foundation for new genomic approaches to better understanding the disease. The team also launched a clinical trial called COMPASS (Comprehensive Molecular Characterization of Advanced Ductal Pancreas Adenocarcinoma for Better Treatment Selection: A Prospective Study), which is recruiting patients with advanced PDAC (both locally advanced and metastatic) at The Princess Margaret Cancer Centre (PM) in Toronto. The study uses the molecular results from individual patient tumours to guide selection of better second line treatment on a case-by-case basis. The primary objective of the initial study was to assess the feasibility of collecting tumour materials from patients with advanced PDAC and delivering results within 56 days of biopsy. Having achieved this objective, the trial has expanded to other cancer centres across Canada. Pancreatic cancer is one of the most deadly forms of cancer and outcomes have not improved in four decades. The PanCuRx initiative is providing a better understanding of the disease and actively applying new knowledge to cancer patients through clinical trials. This knowledge will help to improve quality of life and prolong survival for pancreatic cancer patients worldwide.

  Study EGAS00001002543

• MicroRNAs, Hypertension and End Organ Damage in Humans

  Study 1) Profiling of microRNAs in plasma of patients with hypertension complicated or not by metabolic syndrome or chronic kidney disease Hypertension (HTN) or high blood pressure is associated with subclinical target organ damage such as cardiac, vascular and kidney injury, which may lead to complications and death. In this study, we investigated circulating microRNAs as biomarkers of target organ damage in HTN patients. We profiled circulating microRNAs by RNA sequencing in platelet-poor plasma of normotensive subjects and patients with HTN complicated or not by metabolic syndrome (MetS) or chronic kidney disease (CKD) (n=15 each group). Differentially expressed microRNAs were identified with a threshold of false discovery rate <0.1. Differentially expressed microRNAs were identified uniquely to associate with HTN (8), MetS (1) or CKD (13), and 8 were similarly differentially expressed in different groups. This study identified the association of differentially expressed circulating microRNAs with target organ damage in HTN patients, which could have some pathophysiological and therapeutic implications. Study 2) Profiling of microRNAs in gluteal subcutaneous small arteries of patients with hypertension complicated or not by chronic kidney disease Hypertension (HTN) is associated with vascular damage characterized by endothelial dysfunction and vascular remodeling and stiffening, which contributes to kidney injury leading to chronic kidney disease (CKD). MicroRNAs are short non-coding RNAs which repress/degrade target mRNAs. The microRNA role in vascular injury in HTN remains unclear. In this study, we aimed to identify differentially expressed microRNAs in small arteries of patients with HTN associated or not with CKD, in order to shed light on the pathophysiological molecular mechanisms. Normotensive subjects and HTN patients associated or not with CKD grades 3-4 were studied (n=15-16). Small arteries were isolated from subcutaneous gluteal biopsies, RNAs were extracted, and small and total RNA sequencing was performed by Illumina HiSeq-2500. Differentially expressed genes were identified with a P<0.05 and fold change (FC) >1.3. Differentially expressed microRNAs and mRNAs were identified uniquely to associate with HTN (microRNAs: 10, mRNAs: 68), CKD (microRNAs: 68, mRNAs: 395), and both groups (microRNAs: 2, mRNAs: 32). This study identified differentially expressed microRNAs and mRNAs in small arteries with target organ damage in HTN, which could have some pathophysiological and therapeutic implications.

  Study phs002389

• Integrated Personal omics Processing (iPoP) Longitudinal multi-omics profiling of prediabetes

  Type 2 diabetes mellitus (T2D) is a significant health problem. Close to 20 million individuals in the United States have T2D, and 79 million aged 20 years or older are clinically pre-diabetic, with a 5-year conversion rate of 10% to 23% from prediabetes to T2D. In a collaborative effort to systematically understand diabetes and its etiology, the team is comprised of leading experts in research on both the human host as well as the microbiome, as properties of both are likely relevant in T2D development. For a better elucidation of mechanisms of onset and progression of T2D disease, the group is performing a detailed analysis of the biological processes that occur in the microbiome and human host by longitudinal profiling of patients at risk for T2D. Both microbiome and host profiles are being analyzed by state-of-the-art omics platforms, and these large-scale and diverse data sets will be integrated to determine the dynamic pathways that change during the onset and progression of T2D, especially during viral infections and other stresses. This longitudinal study is expected to reveal changes in the microbiome and host at an unprecedented level of detail, and identify molecules and pathways that play important roles in diabetes onset and progression.

  Study phs001719

• Gene Expression and Biomarker Utility in Post-Mortem Samples

  The FAA Functional Genomics Team examined the feasibility of analyzing gene expression profiles using post-mortem brain, lung, muscle, and blood samples collected from aviation accident fatalities, with the goal of validating post-mortem extracted RNA for use in RNA sequencing. We compared the RNA sequencing results obtained from THC-positive and THC-negative samples to determine whether RNA sequencing on samples collected from aviation accident fatalities was possible and if any differences in gene expression associated with THC consumption were detectable post-mortem. The study population included 57 males of indeterminant age who perished in general aviation accidents and for whom post-mortem toxicological testing identified delta-9-THC or its primary or secondary metabolites, as well as negative controls. We determined that RNA sequencing on post-mortem aviation accident fatality samples is possible, and further identified genes showing differential expression in lung and muscle between THC-positive and THC-negative samples. We conclude that post-mortem tissue samples collected from aviation accident fatalities are suitable for gene expression profiling, but caution researchers that such samples have low RNA integrity numbers and some degree of microbial contamination is both probable and to be expected. Raw sequencing files (.fastq) from this study are available in dbGaP.

  Study phs003546

• Stratifying and Targeting Pediatric Medulloblastoma through Genomics

  In this project, genomic analyses of pediatric medulloblastoma samples, obtained through the international medulloblastoma consortium, will be performed. RNA and miRNA expression profiles of 1000 samples, representing all four subgroups (Wnt, Shh, Group C, and D), will be studied to identify novel subtypes within each subgroup. The resulting subtype-specific expression profiles will support the development of reliable and robust biomarkers to more accurately and reliably classify medulloblastomas for treatment in clinical trials. For that purpose, two assays will be developed: an antibody-based immunohistochemical assay and an orthogonal nucleic acid-based hybridization assay. Additional genomic DNA analysis of the 300 high risk subgroup cases will support the discovery of subgroup specific somatic mutations in order to inform current clinical trials of targeted therapies, and to identify genes and pathways already targeted in other diseases. Such therapies could be rapidly transitioned to Phase II trials in medulloblastoma. Furthermore, the discovery of somatic mutations could be used for developing as well as validating specific biomarkers. The project team will also try to identify risk factors that predispose children to this type of cancer.

  Study EGAS00001000273

• IMCISION DNAseq

  Whole-exome sequencing of 32 primary head and neck squamous cell carcinoma samples prior to treatment with neoadjuvant anti-PD-1 (n=6) or anti-PD-1 + anti-CTLA-4 (n=26) immunotherapy. DNA quantity used: 50ng. Library Preparation Kit: Twist Human Core Exome Plus (Twist Bioscience). Sequencing parameters: NovaSeq 6000, 2x 100 bp. File type: fastQ.

  Dataset EGAD00001008139

• Paired Biopsy Project: West Coast Dream Team

  This project aims to analyze the paired metastatic biopsy samples from patients with metastatic castration-resistant prostate cancer (mCRPC), collected before the initiation of the first-line androgen receptor signaling inhibitor (ARSI) for mCRPC and after radiographic disease progression on that ARSI, to understand the resistance mechanisms. We generated both whole genome sequencing (WGS) and RNA-seq data on these samples. A majority of these samples have been deposited in the public domain along with prior publications, and this project contains the 16 WGS samples that have not yet been deposited.

  Study EGAS50000000327

• 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