6170 results for "ps4 fc 26 coins Buyfc26coins.com is FC 26 coins official site..zexT"

in 14.59 milliseconds.

• Atherosclerosis Risk in Communities Study (ARIC-BioLINCC)

  Data Access NOTE:Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. At present, the ARIC sIRB has determined that ARIC data cannot be shared with for-profit entities.Related Studies Other ARIC data available include: Imaging studies (ARIC-Imaging), Genetics and genomics (ARIC, phs000280.v8.p2), Collaborative Cohort of Cohorts for COVID-19 Research (C4R): ARIC (phs002988.v1.p1), and as a component of the Sleep Heart Health Study (SHHS-BioLINCC, phs003637.v1.p1). Available Data Data available for request include ARIC v1-v8 examination cycles, collated annual follow-up communication data for contact years 2-32, and follow-up for mortality, heart disease, and stroke events through 2019. Also included are data from ancillary studies. Objectives The objectives of ARIC are to: 1) investigate associations of factors, including those not previously measured in cohort studies, with prevalence of atherosclerosis and incidence of CHD, clinical stroke and other cardiovascular diseases; and 2) measure cardiovascular disease occurrence and trends and relate these to community levels of, and changes in, risk factors, medical care and atherosclerosis. Background At the time of project initiation, the NHLBI had long recognized the need for longitudinal studies to identify the biochemical and physiological markers and specific environmental factors which place individuals at high risk for the major atherosclerosis diseases. The development of reliable ultrasound examination of peripheral arteries enhanced the expected benefit of such studies. Community surveillance planning began for ARIC in response to recommendations of the 1978 NHLBI Workshop on the Decline in CHD Mortality and has been extended in its purpose to evaluate the large geographic differences in U.S. mortality. Participants Black and white men and women, age 45-64 at entry; sample size: 15,792. Design ARIC is a large-scale, long-term prospective study that measures associations of established and suspected coronary heart disease risk factors with both atherosclerosis and new CHD events in men and women from four geographically diverse communities. The project has two components: community surveillance of morbidity and mortality; and repeated examinations of a representative cohort of men and women in each community. The community surveillance involves abstracting hospital records and death certificates and investigating out-of-hospital deaths. The representative cohorts include approximately 4,000 persons from each community. Community surveillance data includes detailed hospital record abstraction, ECG tracings, and event adjudication. Data from out-of-hospital events in the community include physician, informant, and coroner questionnaires as well as death certificate data and event adjudication. Community surveillance ended in 2014.Cohort participants were examined four times at three year intervals between 1987 and 1998, and have been continuously contacted annually to update their medical histories. Atherosclerosis was measured by carotid ultrasonography. Risk factors studied include: blood lipids, lipoprotein cholesterols, and apolipoproteins; plasma hemostatic factors; blood chemistries and hematology; sitting, supine and standing blood pressures; anthropometry; fasting blood glucose and insulin levels; ECG findings; cigarette and alcohol use; physical activity levels; dietary aspects; and family history. Clinic visits were restarted in 2011 with ARIC visit 5.

  Study phs003738

• Resuscitation Outcomes Consortium Trial of Continuous Compressions Versus Standard CPR in Patients With out-of-Hospital Cardiac Arrest (ROC CCC-BioLINCC)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions.Objectives: To compare the rate of survival to hospital discharge after continuous chest compressions versus standard American Heart Association recommended cardiopulmonary resuscitation with interrupted chest compressions in patients with out-of-hospital cardiac arrest.Background: Standard cardiopulmonary resuscitation (CPR) consists of manual chest compressions to maintain blood flow and positive-pressure ventilation to maintain oxygenation until spontaneous circulation is restored. Chest compressions during standard CPR are interrupted frequently by ventilations. These interruptions reduce blood flow and potentially reduce the effectiveness of CPR. In animals with cardiac arrest, the interruption of chest compressions has been associated with decreased survival. Observational studies involving humans with out-of-hospital cardiac arrest of presumed cardiac cause have suggested that continuous compressions are associated with higher rates of survival than interrupted compressions.Participants: Of 35,904 patients with out-of-hospital cardiac arrest who were screened, 26,148 were eligible for participation in the trial and were enrolled in the trial during either the run-in phase or the active-enrollment phase. The active-enrollment phase included 23,711 patients, of whom 12,653 were assigned to the intervention group and 11,058 to the control group.Design: There were 114 participating EMS agencies across the eight participating Resuscitation Outcomes Consortium (ROC) sites, which were grouped into 47 clusters. Clusters of agencies were randomly assigned, in a 1:1 ratio, to perform continuous chest compressions or interrupted chest compressions during all the out-of-hospital cardiac arrests to which they responded. Each cluster was required to begin enrolling patients in a run-in phase to demonstrate adherence to the protocol before entering the active-enrollment phase of the trial. Twice per year, each cluster was crossed over to the other resuscitation strategy.Patients assigned to the group that received continuous chest compressions (intervention group) were to receive continuous chest compressions at a rate of 100 compressions per minute, with asynchronous positive-pressure ventilations delivered at a rate of 10 ventilations per minute. Patients assigned to the group that received interrupted chest compressions (control group) were to receive compressions that were interrupted for ventilations at a ratio of 30 compressions to two ventilations; ventilations were to be given with positive pressure during a pause in compressions of less than 5 seconds in duration. The primary outcome was the rate of survival to hospital discharge. Secondary outcomes included neurologic function at discharge, which was measured with the use of the modified Rankin scale, and adverse events. Conclusions: During the active-enrollment phase, 1129 of 12,613 patients in the continuous chest compression group and 1072 of 11,035 patients in the interrupted chest compressions group survived to hospital discharge.In patients with out-of-hospital cardiac arrest, continuous chest compressions during CPR performed by EMS providers did not result in significantly higher rates of survival or favorable neurologic function than did interrupted chest compressions.

  Study phs003901

• Inorganic Nitrite Delivery to Improve Exercise Capacity in Heart Failure with Preserved Ejection Fraction (INDIE-HFpEF): Heart Failure Network (HFN INDIE-Imaging)

  Data Access NOTE: Please refer to the "Authorized Access" section below for information about how access to the data from this accession differs from many other dbGaP accessions. Objective: To determine the effect of inhaled, nebulized inorganic nitrite on exercise capacity in patients with heart failure with preserved ejection fraction.Background: Approximately half of patients with heart failure have a preserved ejection fraction (HFpEF). However, there are no proven effective medical treatments for this syndrome. Evidence suggests that impairments in nitric oxide availability have a potentially important role in the pathophysiology of HFpEF.Unlike organic nitrates, inorganic nitrite is converted to nitric oxide in the presence of hypoxia and acidosis, conditions that develop during exercise. Because the cardiac, vascular, and skeletal muscle abnormalities that limit physical capacity and contribute to symptoms in patients with HFpEF characteristically develop during exercise, inorganic nitrite may provide the best way to target nitric oxide delivery precisely at the time of greatest need. The HFN-INDIE trial was initiated to test the hypothesis that compared to placebo, longer-term use of inhaled, nebulized inorganic nitrite would enhance peak exercise capacity in patients with HFpEF. Participants: A total of 105 participants were randomized. 53 were randomized to receive nitrite first and 52 were randomized to receive placebo first.Design: HFN-INDIE was a multicenter, randomized, double-blind, placebo-controlled, crossover study. After enrollment, patients underwent baseline studies to determine eligibility. All patients were required to display objective exercise limitation, evidenced by reduced peak oxygen consumption (V̇o2) on cardiopulmonary exercise testing of less than 75% predicted, with a respiratory exchange ratio indicative of maximal effort (≥1.0). Following qualifying exercise testing, eligible participants received an open-label, single-dose run-in of inhaled, nebulized sodium nitrite (80 mg) to assess tolerability, symptoms, and orthostatic vital signs. Patients developing hypotension (systolic blood pressure The prespecified primary end point was peak V̇o2, measured as the highest 30-second average during upright cycle ergometry, during the 4-week period in which patients were receiving inorganic nitrite as compared with placebo. Accelerometry, health-related quality-of-life scores on the self-administered Kansas City Cardiomyopathy Questionnaire (score range, 0-100, with higher scores indicating better quality of life), echocardiographic indicators of cardiac filling pressures measured at trough drug levels (E/e′ ratio, estimated pulmonary artery systolic pressure, and left atrial volume index; lower scores indicate better health for all), ventilatory efficiency (VE/V̇co2, lower indicating better health), exercise time (higher indicating better health), and NT-proBNP levels (lower indicating better health) were also collected.Data Availability: Data available from this study includes transthoracic echocardiogram images from multiple timepoints. There are 199 echocardiographic exams available, totaling over 13,100 individual echocardiogram images. Conclusions: Among patients with HFpEF, administration of inhaled inorganic nitrite for 4 weeks, compared with placebo, did not result in significant improvement in exercise capacity.Reference: Borlaug et al., 2018, PMID: 30398602.

  Study phs003804

• Lipid Research Clinics - Prevalence Study (LRC-PS-BioLINCC)

  Data Access NOTE: Please refer to the “Authorized Access” section below for information about how access to the data from this accession differs from many other dbGaP accessions. Objectives: The LRC Program began in 1971 under the sponsorship of the National Heart, Lung, and Blood Institute, National Institutes of Health. Part of this program was the Lipid Research Clinics Prevalence Study, a standardized series of cross-sectional surveys of various North American populations designed to determine the prevalence of dyslipidemias and to describe the distributions of lipids and lipoproteins in major ethnic and social groups. In addition to contributing to the aggregate analysis, each independent population-based study was designed with capabilities for separate analyses of lipid and lipoprotein distributions. The participating populations were not selected to be a probability sample representative of the North American population per se, but by virtue of their size and economic and geographical diversity, they provide a useful cross-sectional group. The Family Study was the third phase of the Lipids Research Clinics North American Population Studies. The Family Study was designed to obtain knowledge of the distribution of lipids and lipoproteins among family members and of the association of familial and genetic attributes to dyslipoproteinemias. Background: An association between serum cholesterol and coronary heart disease is well established. A system was developed for classifying hyperlipoproteinemias into six types of patterns, as a basis for characterizing lipoprotein disorders. The Lipid Research Clinics was thus created to improve the detection of and clinical management of hyperlipoproteinemias. The three primary objectives were: 1) to acquire data on the prevalence of different types of hyperlipoproteinemia in various age and ethnic groups, with special emphasis on the nature and frequency of genetic forms; 2) to collect reliable data on the prevalence and incidence of atherosclerosis in different types of hyperlipoproteinemia; and 3) to conduct an intervention trial to determine if lowering plasma lipid levels would reduce the risk of CHD. Participants: There were 60,495 participants. Conclusions: Data from this study confirm findings from earlier studies in developed countries, showing age-related differences in plasma lipid levels. However, for overall distributions, the LRC data showed slightly lower cholesterol and markedly higher trigylceride values than those previously reported for North America. Some variation in plasma lipid values was evident among the clinic populations. The large number of participants within most subgroups permitted a variety of analytic and comparative studies. For example, data from the large pediatric population revealed a drop in plasma cholesterol levels in adolescent males and females. Males aged 20-50 years had higher cholesterol levels than females in the same age group, and higher trigylceride levels between ages 20-70 years. Numbers were also significient for meaningful comparisons between lipid distributions of females who were taking sex hormones and those who were not; in females taking sex hormones, cholesterol and triglyceride levels were higher for subjects younger than 45 years, but slightly lower after age 45, than lipid levels in females not taking hormones (Circulation 1979; 60(2):427-439).

  Study phs003995

• Studying Glioblastoma in a Human Organoid Tumor Transplantation Model

  This study comprises two complementary investigations that leverage innovative human model systems and cutting-edge molecular profiling to dissect glioblastoma (GBM) heterogeneity and tumor-microenvironment interactions. The first study uses a novel Human Organoid Tumor Transplantation (HOTT) model, in which freshly dissociated GBM tumor cells from five patients were transplanted into human embryonic stem cell-derived cortical organoids. This system enables the interrogation of tumor and microenvironment interactions in a human-specific, developmentally relevant context. Using single-cell RNA sequencing (scRNA-seq) and single-nucleus RNA-seq (snRNA-seq), the authors profiled over 216,000 cells, analyzing tumor heterogeneity across multiple media conditions. Ligand-receptor analysis (CellChat), immunofluorescence, and RNAScope were used to validate findings. The study revealed that the HOTT model faithfully recapitulates primary GBM cell types and microenvironmental components, and uncovered a novel bidirectional signaling axis mediated by PTPRZ1 that influences both tumor migration and cell fate in a context-dependent manner. PTPRZ1 is identified to be important for intercellular communication between tumor and microenvironmental cells, while PDGFRB, NOTCH3, HOPX, FAM107A, CLDN5, RGS5, FOXC1, SOX18 are key markers of the neurovascular progenitor that we identify to be a multipotent, restricted progenitor in GBM. Related datasets include the inclusion of immune cells in the HOTT system, termed “iHOTT”. The second study focuses on identifying and characterizing a rare but functionally potent neurovascular progenitor (NVP) population within GBM tumors. By generating a meta-atlas from seven publicly available GBM scRNA-seq datasets, the authors identified a unique tumor-derived cell population co-expressing neural progenitor and vascular markers. This population was validated in situ and in vivo through immunostaining and lineage tracing via DNA barcoding in the HOTT system. Functional knockdown of NVPs in a murine GBM model resulted in reduced cycling cells, altered tumor composition, and increased survival. Clonal analysis showed NVPs have dual potency to give rise to both neuronal and vascular-like tumor cells, contributing significantly to tumor cell diversity. Molecular technologies used across the studies include: Single-cell and single-nucleus RNA sequencing DNA barcoding and clonal lineage tracing (CellTag) Population information: Tumor samples were obtained directly from multiple GBM patients (all IDH1 wild-type, adult), including core and peripheral tumor regions. Human cortical organoids derived from human embryonic stem cells (hESCs) served as the microenvironment in the HOTT model. Principal findings include: HOTT recapitulates the heterogeneity and cell type fidelity of GBM, while enabling the study of tumor–microenvironment signaling. PTPRZ1 has opposing roles in tumor and microenvironment, influencing GBM cell migration and fate via non-catalytic mechanisms. A novel GBM neurovascular progenitor population (NVP) was identified, validated, and shown to contribute clonally to distinct tumor cell types. Elimination of NVPs in vivo reduces tumor aggressiveness and improves survival. Data to be available through dbGaP: Raw and processed single-cell and single-nucleus RNA-seq data (HOTT model and NVP studies) CellTag barcode-labeled scRNA-seq clonal lineage data Associated metadata including patient of origin, experimental condition, and sample annotations.

  Study phs003936

• Transcriptomic analysis of liver CD8+ T cells

  Sorted single CD8+T cells expressing CD14 from human liver for SMARTSeq2. Livers processed: Kucykowicz et al STAR Prot 2022:pubmed.ncbi.nlm.nih.gov/35516846/ Published: Pallett et al Nature 2022 Tissue CD14+CD8+T-cells are reprogrammed by myeloid cells and modulated by LPS The liver is bathed in bacterial products including LPS transported from the intestinal portal vasculature, but maintains a state of tolerance exploited by persistent pathogens and tumours1,2,3,4. The cellular basis mediating this tolerance, yet allowing a switch to immunity or immunopathology, needs to be better understood for successful immunotherapy of liver diseases. Here we show that a variable proportion of CD8+T-cells compartmentalised in the human liver co-stain for CD14 and other prototypic myeloid membrane proteins; CD14+CD8+T-cells preferentially accumulate within the donor pool in liver allografts, amongst hepatic virus-specific and tumour-infiltrating responses, and in cirrhotic ascites. CD14+CD8+T-cells exhibit increased turnover, activation and constitutive immunomodulatory features with high homeostatic IL-10/IL-2 production directly ex vivo, and an enhanced capacity to rapidly produce antiviral/anti-tumour cytokines upon TCR engagement. This CD14+CD8+T-cell profile can be recapitulated by acquisition of membrane proteins, including the LPS receptor complex, from mononuclear phagocytes, resulting in augmented tumour killing by TCR-redirected T-cells in vitro. CD14+CD8+T-cells express integrins and chemokine receptors favouring interactions with the local stroma, which can promote their induction through CXCL12. LPS can also increase the frequency of CD14+CD8+T-cells in vitro and in vivo, and skew their function towards the production of chemotactic and regenerative cytokines. Thus, bacterial products in the gut-liver axis and tissue stromal factors can tune liver immunity by driving myeloid instruction of CD8+T-cells with immunomodulatory capacity. For the analysis of the single cell transcriptome two intrahepatic perfusate samples were isolated and frozen at -80 'C for storage prior to transportation to Newcastle, UK. Once thawed in pre-warmed HBSS containing 0.001% DNaseI, intrahepatic leukocytes were sorted by FACS to index classical mononuclear phagocytes (MNP) defined as Singlets, CD3-CD56-CD19-CD14hiHLA-DR+ or CD14± CD8+T-cells as follows: Singlets, CD3+CD56-CD19-CD4-CD8+V7.2- and split in to CD14± based on an isotype control. Single cells were sorted into 96-well skirted LoBind plates (Eppendorf) containing 5 µL lysis buffer (TCL buffer [Qiagen], supplemented with 1% b-mercaptoethanol [Sigma Aldrich; Merck]) on a BD Bioscience FACSFusion. The sorted plates were subsequently immediately sealed, centrifuged, and placed on dry ice to flash-freeze the cell lysate and stored at -80 'C. A modified SMART-seq2 protocol57 was performed on the single flow cytometry sorted-cells as previously described58. After cDNA generation, libraries were prepared (384 cells per library) using the Illumina Nextera XT kit (Illumina). Each library was sequenced to achieve a minimum depth of 1-2 million raw reads per cell using an Illumina HiSeq 4000 using v. 4 SBS chemistry to generate 75-bp paired-end reads.

  Study EGAS00001006885

• Diagnostic Genomic Analysis is Prognostic in AYA ALL Patients Treated on a MRD-Stratified Paediatric Protocol

  Background: Over the last decade, next generation sequencing has enabled classification of multiple new recurrent genomic drivers of acute lymphoblastic leukemia (ALL). We provide a comprehensive genomic survey of adolescent and young adult (AYA) patients treated on the Australasian Leukaemia and Lymphoma Group (ALLG) ALL06 study. ALL06 clinical trial described the efficacy and tolerability of AYA ALL patients aged 15-39 years treated on a single minimal residual disease (MRD)-stratified platform. In this study we have taken the ALL06 cohort and retrospectively performed comprehensive genomic analyses assessing response of AYA patients with various genomic subtypes treated with a paediatric approach. Methods: Genomic risk classification of B- and T-ALL patients (n=57) enrolled to the study was based on mRNA-Sequencing, MLPA, immunophenotyping and cytogenetics. Results: Using this approach, 36/40 (90%) B- and 13/17 (76.5%) T-ALL patients were classified according to genomic risk. We have linked outcome data with each patient’s genomic risk and found a strong correlation between adverse genomic risk and MRD at the end of consolidation, translating to inferior overall and relapse free survival. Patients with adverse risk genomics who achieved negative MRD status had improved responses compared to those with persistent MRD. Patients with standard risk genomics had excellent responses regardless of their MRD status. Conclusion: Our data argue strongly for incorporation of a genomic risk classification into future ALL treatment paradigms at the time of diagnosis.

  Study EGAS50000000752

• Genetic variability in exon 1 of the glucocorticoid receptor gene NR3C1 is associated with postoperative complications

  Patients having major surgery experience inflammation post-operatively, which may contribute to post-operative morbidity. Endogenous glucocorticoids (GCs) are an essential part of the stress response, but this response varies between individuals, which may in turn affect clinical outcome in general, and post-operative inflammation, specifically. Exon 1 of the NR3C1 gene, encoding the glucocorticoid receptor, contains an established region of differential regulation. DNA methylation patterns in this region have been found to differ between individuals. We investigated the methylation status and genotype in the Cytosine-phosphate-Guanine (CpG) island in exon 1 of NR3C1 in 24 patients who underwent major abdominal surgery and correlated it with post-operative complications. DNA was extracted from peripheral blood leukocytes and underwent targeted bisulfite sequencing of the CpG island. Complications were graded according to the Clavien-Dindo classification and 14 out of 24 had post-operative complications. Multifactorial and partial least square methods were used to analyse the data. A homogenous demethylated pattern was observed in all patients and no single CpG methylation was associated with post-operative complications. Four single nucleotide polymorphisms (SNPs) were significantly correlated with higher Clavien-Dindo scores. Genetic variability in the chr5:143,402,505-143,405,805 region of exon 1 of the glucocorticoid receptor gene NR3C1, but not DNA methylation, was associated with more severe post-operative complications in patients having major abdominal surgery. This indicates that the response to GCs may be of clinical importance for inflammatory conditions.

  Study EGAS00001005737

• NIPT samples for systematic evaluation of BinDel, a software tool for detecting clinically significant microdeletions in low-coverage WGS-based NIPT samples

  This dataset contains three sets of samples. The first sample set contains euploid fetus pregnancies reported by NIPTIFY screening test and postnatal evaluation. Dataset was processed similarly to previously published guidelines from KU Leuven, with modifications [1]. Briefly, peripheral blood samples were collected in cell-free DNA BCT tubes (Streck, USA), and plasma was separated with standard dual centrifugation. Cell-free DNA was extracted from 3 ml plasma using MagMAX Cell-Free DNA Isolation Kit (ThermoFisher Scientific). Whole-genome libraries were prepared using the FOCUS (Fragmented DNA Compact Sequencing Assay, Competence Centre on Health Technologies, Estonia) NIPT method protocol with 12 cycles for the final PCR enrichment step. In the following quantification, equal amounts of 36 samples were pooled, and the quality and quantity of the pool were assessed on Agilent 2200 TapeStation (Agilent Technologies, USA). Whole genome sequencing was performed on the NextSeq 550 instrument (Illumina Inc.) with an average coverage of 0.32× (minimum 0.08 and maximum 0.42) and producing 85 bp single-end reads. The second sample set contains a single NIPT sample postnatally diagnosed with Prader-Willi syndrome. The sample was sequenced with Illumina NextSeq 500 platform, producing 85 bp single-end reads with an average per-sample coverage of 0.32× at the University of Tartu, Institute of Genomics Core Facility, according to the manufacturer’s standard protocols, as described previously [2]. The third sample set contains samples SC005 (SeraCare Life Sciences Inc lot #10446565), SC0042 (#10571706), and SC016 (#10560229). These are SeraCare Life Sciences Inc circulating cell-free DNA (ccfDNA) like mixture of human genomic DNA that consists of matched maternal and fetus. SC005 and SC0042 consist of matched DNA of maternal and fetus with DiGeorge Syndrome. SC016 is a custom-ordered DNA Mix with fetus DNA having a pathogenic loss of the terminal region of 20p13 and a pathogenic 3q29 duplication. SC016 was processed as the first sample set was processed, and SC0042 was processed as the second sample set was processed. Sample SC005 was processed once as was sample set 1 and once as was sample set 2 processed. This study was performed with the approval of the Research Ethics Committee of the University of Tartu (#352/M-12). 1. Bayindir B, Dehaspe L, Brison N, Brady P, Ardui S, Kammoun M, et al. Noninvasive prenatal testing using a novel analysis pipeline to screen for all autosomal fetal aneuploidies improves pregnancy management. Eur J Hum Genet. 2015;23: 1286– 1293. doi:10.1038/ejhg.2014.282 2. Žilina O, Rekker K, Kaplinski L, Sauk M, Paluoja P, Teder H, et al. Creating basis for introducing noninvasive prenatal testing in the Estonian public health setting. Prenat Diagn. 2019;39: 1262–1268. doi:10.1002/pd.5578

  Dataset EGAD00001009512

• 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