14312 results for ""Pennsylvania+German"+ACS+study+'Socius'+open+access"

in 10.96 milliseconds.

• Data Access Committee of the Medical Faculty of the University of Basel (MF-DAC)

  Dac EGAC00001002981

• PELICAN45 and GP21 prostate cancer studies Data Access Committee

  Dac EGAC00001001309

• UAMS - Myeloma Institute Data Access Committee

  Dac EGAC00001000845

• Cyr61-MAC DAC

  DAC for access to dataset on Cyr61-MAC and HUVEC

  Dac EGAC50000000355

• Data access committee for datasets generated by the Tampere University Computational Biology research group

  Dac EGAC50000000177

• LEMA

  This DAC will govern access to WES data associated with the LEMA publication

  Dac EGAC50000000560

• DAC PRECISE Bennstein

  Data access control for datasets submitted by SysMed - PRECISE

  Dac EGAC50000000476

• Volkov Data Access Committee

  Sequencing and analysis data supporting published work of Hadas Volkov

  Dac EGAC50000000907

• Submitter Portal API

  Submitter Portal API The metadata submission process can be difficult and time-consuming. For this reason, the EGA has developed the Submitter Portal, a tool that was created to offer a simplified and user-friendly method of registering metadata. Our portal provides features that are intended to make the input of metadata easier, ensuring that your data is registered correctly and effectively. Our page is divided into logical sections and includes a helpful video instruction to further assist you as you complete the submission process. With the Submitter Portal, you can rest assured that the submission of your data is in good hands. For those that want a more flexible and automated approach, we also provide a programmatic approach using the Submitter Portal AP in addition to the user interface of the Submitter Portal. With the help of our API, you can quickly include the submission of metadata into your own workflow for a more effective and individualised experience. Previous steps Create your EGA account To submit data you first need to create your EGA user. Then, once your account has been verified, you will have to request a submitter role and sign the EGA Data Processing Agreement (DPA). When the DPA is signed, you must send it to EGA Helpdesk for further validation. Please, note that if you already have an EGA account, or you have an ega-box (submission account), you can skip this step.  Upload your files Please note that all your files must be encrypted using the Crypt4GH tool before upload them.As soon as you are assigned with a submitter role, you will be able to connect to the EGA inbox and upload your files. Understand the EGA metadata schema It's crucial to comprehend the EGA metadata schema, a set of rules that specify how data is organised, described, and shared inside the EGA, in order to get the most out of this resource. Learn all about EGA metadata schema! Register your DAC and policy There are two objects in the EGA metadata schema that are registered in a separate portal. All DACs and policy objects are registered using the DAC Portal, a tool developed by EGA to help data controllers manage their data stored at the EGA. You can find the relevant information in the DAC Portal Guide. Programmatic submission All the calls to the API need to be Authenticated. We use the OpenID Connect protocol. API Usage Flow: Click here to check the API usage flow schema Obtain Access and Refresh Token: The first step to using the API is to obtain an access and refresh token. These tokens are required for authentication and authorisation of API requests. To obtain these tokens, you need to log in using your EGA credentials. Example: curl "https://idp.ega-archive.org/realms/EGA/protocol/openid-connect/token" \ -d "grant_type=password" \ -d "client_id=sp-api" \ -d "username=your-username" \ --data-urlencode "password=your-password" Use Access Token in API Calls: Once you have obtained the access token, you must use it in all the calls to the API. The access token is valid for a limited time period. When it expires, you will need to use the refresh token to obtain a new access token. Create Submission Object: After authentication, you can start creating a submission object. This object will be used to store all the metadata objects and files related to the submission. Example: curl "https://submission.ega-archive.org/api/submissions" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My submission title\", \"description\":\"My submission description\" }" Create EGA Metadata Objects: Within the submission object, you can create other metadata objects required for the submission. These objects may include information about the submitter, study, sample, experiment, and run. Example of study creation: curl "https://submission.ega-archive.org/api/submissions/{submisison-id}/studies" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" \ -d "{ \"title\":\"My study title\", \"description\":\"My study description\", \"study_type\":\"Metagenomics\" }" If you would like to reuse already registered objects in new submissions, bear in mind that they must have an accession which you must use to reference them. You cannot reuse objects that have not been finalised and accepted yet.For example, when creating a new run which is reusing a previously submitted experiment, instead of using experiment_provisional_id, you must use experiment_accession_id. Enums There are some fields that only accept specific values, i.e. study_type. The API provides several enumerations to list these values. You can list all the enumerations, or a specific one, for example, study_types. Obtain IDs of files You can list the files available in your inbox and filter by a prefix by adding the prefix param, i.e. &prefix=/my_folder/abc Example: curl "https://submission.ega-archive.org/api/files?status=inbox&prefix=/my_folder/abc" \ -H "Authorization: Bearer your-access-token" \ -H "Content-Type: application/json" To improve performance and manageability, we have limited the number of files that the Submitter Portal API can return in a response. If a given call exceeds this limit, user will be asked to narrow down the search by using the query parameters already available in this endpoint. Finalise Submission: Once all the metadata objects are created and linked to the submission, you can finalise the submission. Finalising the submission sends it to the Helpdesk team for review. Please, note that all files linked to the submission must be ingested, and all objects created in a submission must be linked before you can finalise the submission. API Reference: For a full API reference, please check our specification documentation.

  Documentation submission/metadata/submission/sequencing-phenotype/submitter-portal-api

• Study of Clinical Efficacy of Antimicrobial Therapy Strategy Using Pragmatic Design in Idiopathic Pulmonary Fibrosis (CleanUP IPF-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 investigate whether the addition of antimicrobial treatments improves outcomes compared to usual care alone among patients with idiopathic pulmonary fibrosis. Background Idiopathic pulmonary fibrosis (IPF) is a chronic progressive lung disease. Lung dysbiosis, characterized by increased bacterial load and/or loss of diversity, has been reported in patients with IPF and may contribute to hospitalization and death. Clinical trials investigating other chronic disorders suggest that antimicrobial therapy favorably alters the lung microbial community. The CleanUP IPF study was initiated to determine if an antimicrobial treatment reduces respiratory hospitalization or death among patients with IPF. Participants A total of 513 participants were enrolled. 254 participants were randomized to receive antimicrobials, of those 128 were randomized to receive co-trimoxazole and 126 were randomized to receive doxycycline. 259 participants were randomized to receive usual care alone. Design CleanUP IPF was a randomized, unblinded, multicenter study. Patients were randomized to receive antimicrobials in addition to usual care or usual care alone. Antimicrobials included co-trimoxazole (trimethoprim 160 mg/sulfamethoxazole 800 mg twice daily plus folic acid 5 mg daily) or doxycycline (100 mg once daily if body weight Data collected included diffusion capacity of lungs for carbon monoxide (DLCO), forced vital capacity (FVC), and occurrence of severe adverse events. Several questionnaires were administered to assess quality of life, including the impacts of shortness of breath, fatigue, and chronic cough on participants. The primary end point was time to first nonelective respiratory hospitalization or all-cause mortality. The study was terminated early due to futility. Conclusions Among adults with idiopathic pulmonary fibrosis, the addition of co-trimoxazole or doxycycline to usual care, compared with usual care alone, did not significantly improve time to nonelective respiratory hospitalization or death. Martinez FJ, Yow E, Flaherty KR, et al. Effect of Antimicrobial Therapy on Respiratory Hospitalization or Death in Adults With Idiopathic Pulmonary Fibrosis: The CleanUP-IPF Randomized Clinical Trial. JAMA. 2021;325(18):1841-1851. doi:10.1001/jama.2021.4956

  Study phs004314