431 results for "fc points ps4 Besuche die Website Buyfc26coins.com. Alles easy, top..XkV1"

in 7.70 milliseconds.

• Selective targeting of TBXT with DARPins identifies regulatory networks and therapeutic vulnerabilities in chordoma

  The embryonic transcription factor TBXT (brachyury) drives chordoma, a spinal neoplasm without effective drug therapies. TBXT’s regulatory network is poorly understood, and strategies to disrupt its activity for therapeutic purposes are lacking. We developed designed ankyrin repeat proteins that block TBXT-DNA binding (T-DARPins). In chordoma cells, T-DARPins reduced cell cycle progression, spheroid formation, and tumor growth in mice and induced signs of senescence and differentiation. Transcriptomic and proteomic analyses identified gene networks involved in cell cycle regulation, embryonic cell identity, and interferon response and revealed features of regulome components, such as druggability for future translational studies and the fine-tuning of TBXT downstream effectors through IGFBP3. Finally, we found high interferon signaling in chordoma cell lines and patient tumors, which was promoted by TBXT and associated with sensitivity to JAK2 inhibitors. These findings demonstrate the potential of DARPins for probing nuclear proteins to understand the regulatory networks of transcription factor-driven cancers, including entry points for therapies that warrant testing in patients.

  Study EGAS00001008140

• 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

• 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

• Longitudinal snRNAseq and DNAseq of IDHmutant glioma

  We collected longitudinal glioma samples from 35 patients with an IDH-mutant oligodendroglioma (n = 13) or IDH-mutant astrocytoma (n = 22) diagnosis based on 2021 WHO glioma classification at two or three time points (n = 75 samples). For each patient, we designated the two earliest samples as the initial and recurrence for longitudinal analyses. In 17 of 35 longitudinal pairs, the initial sample was obtained at primary diagnosis, whereas the remaining 18 cases the initial samples were collected at a subsequent surgery. Between the initial and recurrence samples, 26 of 35 patients received radiotherapy and/or alkylating chemotherapy, whereas no adjuvant treatment was reported for the remaining patients. To comprehensively investigate IDH-mutant glioma evolution, we used snRNAseq and bulk DNA/RNA sequencing from the same resected glioma samples. A subset of these samples was profiled with simultaneous snRNA-ATAC sequencing (48 out of 75), including 21 matched longitudinal pairs,

  Dac EGAC50000000973

• SCANDARE HNSCC 3' Tag RNA-seq

  SCANDARE (NCT03017573) is a multicentric biobanking study, enrolling adult patients with newly diagnosed head and neck squamous cell carcinoma (HNSCC), triple negative breast cancer (TNBC), ovarian and cervical cancer. Tumor tissue and blood samples are collected at several time points during patient's journey, including at diagnosis, post-neoadjuvant chemotherapy in case of neoadjuvant treatment, at surgery, at recurrence and at disease progression following treatment initiated at recurrence. Since its launch in 2017 at Institut Curie, SCANDARE has enabled the longitudinal collection and preservation of samples for in-depth analyses. Here, we describe molecular alterations in 264 FFPE samples at baseline from 90 HNSCC patients using 3'-tag RNA-seq technology, with FASTQ files deposited in the dataset.

  Dataset EGAD50000001655

• SCANDARE TNBC WES data

  SCANDARE (NCT03017573) is a multicentric biobanking study, enrolling adult patients with newly diagnosed head and neck squamous cell carcinoma (HNSCC), triple negative breast cancer (TNBC), ovarian and cervical cancer. Tumor tissue and blood samples are collected at several time points during patient's journey, including at diagnosis, post-neoadjuvant chemotherapy in case of neoadjuvant treatment, at surgery, at recurrence and at disease progression following treatment initiated at recurrence. Since its launch in 2017 at Institut Curie, SCANDARE has enabled the longitudinal collection and preservation of samples for in-depth analyses. Here, we describe molecular alterations in 247 frozen samples at baseline and 138 germline DNA from 139 TNBC patients using WES technology, with FASTQ files deposited in the dataset.

  Dataset EGAD50000001661

• SCANDARE TNBC WGS data

  SCANDARE (NCT03017573) is a multicentric biobanking study, enrolling adult patients with newly diagnosed head and neck squamous cell carcinoma (HNSCC), triple negative breast cancer (TNBC), ovarian and cervical cancer. Tumor tissue and blood samples are collected at several time points during patient's journey, including at diagnosis, post-neoadjuvant chemotherapy in case of neoadjuvant treatment, at surgery, at recurrence and at disease progression following treatment initiated at recurrence. Since its launch in 2017 at Institut Curie, SCANDARE has enabled the longitudinal collection and preservation of samples for in-depth analyses. Here, we describe molecular alterations in 108 FFPE samples at baseline and 108 germline DNA from 108 TNBC patients using WGS technology, with FASTQ files deposited in the dataset.

  Dataset EGAD50000001662

• Variant calling analysis of cfDNA whole exome sequencing in neuroblastoma

  This dataset contains VCF files from a variant calling analysis of 19 neuroblastoma patients. WES or WGS data of the primary tumor were compared to WES cfDNA analysis at the time of diagnosis and at a 2nd timepoint (complete remission, partial remission, disease progression or relapse). For 4 patients, WGS of germline, tumor at diagnosis and tumor at relapse DNA was performed on Illumina HiSeq2500, with 100-bp paired-end reads. For the other patients, WES was performed using either an AgilentSureSelect Human All Exon v5 or a Roche Nimblegen SeqCap EZ Exome V3 kit on Illumina HiSeq2000, with 100-bp paired-end reads. SNVs observed in any of the primary tumors or cfDNA samples studied by WES were targeted using a capture sequencing panel at all intermediate time points.

  Dataset EGAD00001003803

• Security Overview

  Security Overview The European Genome-phenome Archive (EGA) houses consented human data under controlled access. Access decisions are handled by the relevant Data Access Committee (DAC), which autonomously manages requests through the DAC Portal. This document provides an overview of EGA’s practices in ensuring the security of data stored at EGA. As security is a prime concern of the EGA, the EGA is a member of the Global Alliance for Genomics and Health (GA4GH) Data Security work stream. The EGA contributes and helps develop the recommendations outlined the GA4GH Security Technology Infrastructure document, which defines guidelines, best practices, and standards for building and operating an infrastructure that promotes responsible data sharing in accordance with the GA4GH Privacy and Security Policy. Explore the EGA dataflow to gain deeper insights! Accessing data in the EGA involves several steps. First, users need to create an EGA account. Once logged in, they can request access to data controlled by a DAC through the EGA website (see documentation). The DAC oversees these requests through the DAC Portal, and if approved, grants the necessary permissions to the user's EGA account, allowing them to access and download all relevant data and metadata for the requested dataset(s). The key points of EGA security strategy are: 1 Regular Risk Assessment The EGA regularly identifies and assesses risk related to the following: Breach of confidentiality,Breach of privacy or autonomy,Malicious or accidental corruption or destruction of data archived at EGA,Disruption of services provided by the EGA. 2 Risk mitigation The EGA implements and maintains safeguards to minimise the risks identified above in accordance with the 6 control objectives listed in Appendix 1 and outlined in the GA4GH Security and Infrastructure document.If a breach is discovered, the EGA applies a defined protocol to minimise damage. 3 Identity and authorisation management The EGA authenticates the identity of individuals or software accessing controlled access data held at the EGA.The EGA ensures an appropriate level of assurance (LoA) is applied to the identity consistent with the risk associated with that individual, such as multi-factor authentication for DACs.The EGA provides the minimum access rights and privileges consistent with the user’s identity, allowing access consistent with the GA4GH Privacy and Security Policy, as determined by the appropriate DAC. 4 Audit Logs The EGA maintains a set of logs recording: Changes to user access rights,Data access requests,Resource usage. 5 Cryptography, communication security, and data integrity The EGA ensures data transmission integrity using a hash function.All data transmitted to or from the EGA is end-to-end encrypted.All data at EGA is stored using strong encryption.Encryption keys are not stored in the same system as the encrypted data.All data archived at EGA must be accompanied by a signed submission statement ensuring appropriate consent or ethical approval has been obtained, and is in accordance with all applicable laws and regulations. The EGA has a defined protocol defining the response in the event of a security breach, and is continuing to work with the GA4GH Data Security Work Stream to help define best practice and associated standards for breach responses. Appendix 1 GA4GH Control Objectives Control Objective 1: Implement technology safeguards to minimise the risk of unauthorised access, use, or disclosure of confidential and private data.Control Objective 2: Implement technology safeguards to minimise the risk of discovery, access, and use of individuals’ clinical and genomic data, and individual identities, other than as authorised by applicable jurisdictional law, institutional policy, and individual consents.Control Objective 3: Implement technology safeguards to minimise the risk of accidental or malicious corruption or destruction of data.Control Objective 4: Implement technology safeguards to minimise the risk of disruption, degradation, and interruption of services enabling access to data.Control Objective 5: Implement technology safeguards to minimise the risk of potential security attacks and misuse of authorised accesses and privileges.Control Objective 6: Implement technology safeguards to promptly detect the failure to attain the above control objectives and to respond with proper countermeasures.Appendix 2Refer to the document below to learn more about EGA long-term data preservation policy and procedures at EMBL-EBI.Long-term data preservation

  Documentation about/security

• Privacy Notice for the Account User

  Privacy Notice for EGA User Account This Privacy Notice explains what personal data is collected by the specific service you are requesting, for what purposes, how it is processed, and how we keep it secure. Note that this service collects personal data directly provided by the user, and also collects personal data from users that is provided by other organisations. 1. Who controls your personal data and how to contact us? European Genome- Phenome Archive - EGA offers a service for permanent archiving and sharing of all types of personally identifiable genetic and phenotypic data resulting from biomedical research projects, jointly managed by European Molecular Biology Laboratory – European Bioinformatics Institute (EMBL-EBI) and Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG). EMBL-EBI and CRG represent joint Data Controllers’ of processing of your personal data. They and their Data protection officers may be contacted for data protection queries and for exercising your rights under Section 8. You may contact EMBL-EBI, represented by dr. Thomas Keane, by: email at: tk2@ebi.ac.uk or post at EMBL-EBI, Wellcome Genome Campus, CB10 1SD Hinxton, Cambridgeshire, UK. EMBL’s Data Protection Officer may be contacted by: telephone at +49 6221 387-8590, email at dpo@embl.org, or post at EMBL Heidelberg, Data protection officer, Meyerhofstraße 1, 69117 Heidelberg, Germany. You may contact CRG, whose EGA team is represented by dr. Jordi Rambla de Argila, by: email at jordi.rambla@crg.eu, or post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), Dr.Aiguader 88, PRBB Building, 08003 Barcelona, Spain. CRG Data protection officer may be contacted by: email at dpo@crg.eu post at Fundació Centre de Regulació Genòmica - Centre for Genomic Regulation (CRG), C/ Dr. Aiguader, 88, PRBB Building, 08003 Barcelona, Spain. 2. Which is the lawful basis for processing personal data? We process your personal data on the grounds of important public interest. For monitoring your activities on the website, we process your personal data on the grounds of important public interest. Such legal basis is found in Article 5(1)(a) of EMBL Internal Policy No 68 on General Data Protection (hereinafter IP 68), which is equivalent to Article 6 (1)(e) of the EU General Data Protection Regulation (hereinafter GDPR) and upon which personal data are processed for the achievement of the aims laid down in 1973 agreement establishing EMBL, such as the promotion of the cooperation in the fundamental research, in the development of advanced instrumentation and in advanced teaching in molecular biology and dissemination of information. 3. What personal data is collected from users of the service? How do we use this personal data? We collect the following personal data from you: Name Email address Title/Position Organisation Organisational affiliation Username and password (to authenticate access to the system) IP Address (for anonymous usage statistics) We process your personal data: to provide you with the authenticated access to the EGA service (opening and managing submission and distribution account), to publicly publish some aggregate data to facilitate scientific research (e.g. number of accounts, geographic distribution), to better understand the needs of the users and to guide future improvements of the service, to create anonymous usage statistics. If you do not provide us with your personal data we will not be able to open the user account and offer you our services or we will only provide you a subset of functionalities available within the service. 4. Who will have access to your personal data? The personal data will be disclosed to: Authorised staff in the data controller’s institutions acting on data controller`s behalf and instructions (for all user account data), Requested dataset Data access committee – DAC will have access to the name, email, organization, affiliation, title/position of the distribution user account, using it for their own purpose of granting access to their datasets. 5. Will your personal data be transferred to third countries (i.e. countries not part of EU/EEA) and/or international organisations? Distribution user account data are in the process of granting access disclosed to dataset(s) DAC, which might be a recipient in countries outside of the European Economic Area. Insofar as the second joint controller may be subject to GDPR, data transfer to and from the first joint controller (EMBL-EBI) is necessary for important reasons of public interest embedded in the aims of the EMBL and justified in the Article 9(4) of IP 68 (equivalent to Article 49(1)(d) of GDPR) read in conjunction with EMBL`s 1973 establishing agreement and Article 179(2) of the Treaty on the Functioning of the European Union. 6. How long do we keep your personal data? All data are stored for as long as you have the account open. Thereafter the storage is prolonged for as long as our service is live, even if you stop using our services. This prolongation is necessary for further scientific research, to ensure legal compliance and security and to facilitate internal and external audits it they arise. By contrast, the log files for the data categories related to anonymous usage statistics (raw web service logs) are processed only for 30 days and thereafter erased. 7. The joint Data Controllers provide these rights regarding your personal data You have the right to: Not be subject to decisions based solely on an automated processing of data (i.e. without human intervention) without you having your views taken into consideration. Request at reasonable intervals and without excessive delay or expense, information about the personal data processed about you. Under your request we will inform you in writing about, for example, the origin of the personal data or the preservation period. Request information to understand data processing activities when the results of these activities are applied to you. It must be clarified that rights under points 4 and 5 are only available whenever you need support whilst using our website. For other processing based on the grounds of important public interest you cannot exercise your rights to object, rectify or erase your personal data according to the Article 13(2)(a)(b) of IP 68 (equivalent to Article 17(3)(b)(d) and Article 21(6) of the GDPR). 8. Supervisory authority If you wish to complain against the processing of your personal data, you may do so by post at: EMBL Heidelberg, Data Protection Committee, Meyerhofstraße 1, 69117 Heidelberg, Germany, or Autoritat Catalana de Protecció de Dades (Catalan Data Protection Authority), C/Rosselló 214, Esc A, 1r 1a, Barcelona 08008, Spain. Published at: February 6, 2019

  Documentation data-protection/privacy-notice/ega-user-account