APS-1 TCR Sequencing

Single cell TCR sequencing of expanded regulatory T cells (Tregs) in 9 APS-1 patients and 9 ange and gender matched controls. T-cell receptor (TCR) libraries were generated using the Single Cell Human TCR Amplification Kit and the Library Construction Kit from 10x genomics.

22/02/2024
18 samples
DAC: EGAC50000000081
Technology: Illumina NovaSeq 6000

Access Policy1 Study Files

Metadata

Request Access

DUO:0000006
version: 2021-02-23

health or medical or biomedical research

This data use permission indicates that use is allowed for health/medical/biomedical purposes; does not include the study of population origins or ancestry.

DUO:0000021
version: 2021-02-23

ethics approval required

This data use modifier indicates that the requestor must provide documentation of local IRB/ERB approval.

DUO:0000027
version: 2021-02-23

project specific restriction

This data use modifier indicates that use is limited to use within an approved project.

DUO:0000046
version: 2021-02-23

non-commercial use only

This data use modifier indicates that use of the data is limited to not-for-profit use.

University of Bergen Rare Monogenic Autoimmune Syndrome (APS-1) Data Access Policy

Data Access Policy for Genomic APS-1 datasets archived in Federated EGA Norway 1. Data Access Committee Each dataset submitted by University of Bergen (UiB) for archival and controlled access sharing in Federated EGA Norway, has a DAC appointed by UiB to govern controlled access to the dataset according to this Data Access Policy. Multiple datasets may be affiliated to a single DAC. UiB as an institution has the overall data controller responsibility, and will appoint a DAC based on proper internal procedures that ensures involvement of institutional functions such as Data Protection Officer, legal control, etc. 2. Data use conditions To advise any would-be requester on how the data can be used, Data Use Ontology codes (DUO) is associated to each dataset, providing the requester more insights into which terms for sharing and use of the data that applies, and that needs to be addressed as part of the communication with the DAC in a data access request. No access to any UiB dataset deposited in FEGA Norway can be granted to a requester before all applicable conditions and requirements for the use and management of the data have been agreed upon in a signed Data Access Agreement. 3. Data Access Agreement The Data Access Agreement (DAA) will include requirements specific for both the dataset and the management of the data in the hands of the requester applying for access, and will thus be an individual DAA for each case of granted access to a dataset. As a rule, a DAA for an UiB dataset will take the form of a Data Transfer Agreement, where the requester will commit to take on responsibilities and duties as a data controller. 4. Processing of requests for access The overall data access approval process at UiB can be summarised as follows: ● DAC for a UiB dataset is contacted by a potential data requester ● DAC continues communication with requester to understand the purpose of use, i.e. research setting the dataset is envisioned for by requester, to identify if data sharing is possible directly under current conditions for the dataset, or actions such as re-consenting is needed and desirable to accommodate the proposed research setting/data use. ● A Data Access Agreement is jointly formulated and agreed upon, with the DAC following internal UiB to include the Data Protection Officer and Division for research support. ● When a completed DAA has been signed between the parties, and archived at UiB, the DAC will instruct the FEGA Norway node to release the data to the requester,

Studies are experimental investigations of a particular phenomenon, e.g., case-control studies on a particular trait or cancer research projects reporting matching cancer normal genomes from patients.

Study ID	Study Title	Study Type
EGAS50000000181	Single cell transcriptomics in expanded Tregs of APS-1 patients	RNASeq

This table displays only public information pertaining to the files in the dataset. If you wish to access this dataset, please submit a request. If you already have access to these data files, please consult the download documentation.

ID	File Type	Size	Located in i
EGAF50000061914	fastq.gz	1.1 GB	Federated EGA
EGAF50000061915	fastq.gz	2.3 GB	Federated EGA
EGAF50000061916	fastq.gz	838.2 MB	Federated EGA
EGAF50000061917	fastq.gz	1.9 GB	Federated EGA
EGAF50000061918	fastq.gz	1.0 GB	Federated EGA
EGAF50000061919	fastq.gz	2.2 GB	Federated EGA
EGAF50000061920	fastq.gz	1.3 GB	Federated EGA
EGAF50000061921	fastq.gz	2.8 GB	Federated EGA
EGAF50000061922	fastq.gz	2.1 GB	Federated EGA
EGAF50000061923	fastq.gz	813.6 MB	Federated EGA
EGAF50000061924	fastq.gz	1.3 GB	Federated EGA
EGAF50000061925	fastq.gz	973.6 MB	Federated EGA
EGAF50000061926	fastq.gz	1.9 GB	Federated EGA
EGAF50000061927	fastq.gz	1.1 GB	Federated EGA
EGAF50000061928	fastq.gz	1.9 GB	Federated EGA
EGAF50000061929	fastq.gz	1.1 GB	Federated EGA
EGAF50000061930	fastq.gz	2.2 GB	Federated EGA
EGAF50000061931	fastq.gz	1.0 GB	Federated EGA
EGAF50000061932	fastq.gz	2.2 GB	Federated EGA
EGAF50000061933	fastq.gz	1.1 GB	Federated EGA
EGAF50000061934	fastq.gz	2.5 GB	Federated EGA
EGAF50000061935	fastq.gz	938.0 MB	Federated EGA
EGAF50000061936	fastq.gz	2.0 GB	Federated EGA
EGAF50000061937	fastq.gz	1.3 GB	Federated EGA
EGAF50000061938	fastq.gz	2.8 GB	Federated EGA
EGAF50000061939	fastq.gz	492.5 MB	Federated EGA
EGAF50000061940	fastq.gz	953.7 MB	Federated EGA
EGAF50000061941	fastq.gz	1.2 GB	Federated EGA
EGAF50000061942	fastq.gz	2.3 GB	Federated EGA
EGAF50000061943	fastq.gz	1.1 GB	Federated EGA
EGAF50000061944	fastq.gz	2.1 GB	Federated EGA
EGAF50000061945	fastq.gz	774.2 MB	Federated EGA
EGAF50000061946	fastq.gz	1.4 GB	Federated EGA
EGAF50000061947	fastq.gz	972.8 MB	Federated EGA
EGAF50000061948	fastq.gz	2.0 GB	Federated EGA
EGAF50000063639	fastq.gz	1.2 GB	Federated EGA
36 Files (54.9 GB)