# Dataset Versions {% hint style="info" %} An Apollo license is required to use Apollo Datasets on the DNAnexus Platform. Org approval may also be required. [Contact DNAnexus Sales](mailto:sales@dnanexus.com) for more information. {% endhint %} Because the dataset is a series of JSON objects, fundamental changes to the structure are versioned to help simplify support for functionality and communication. The intent is that the current version (v3.0) continues to support the evolution of user needs and any updates are incremental vs major. ## V3.0 Dataset The v3.0 dataset framework was built to provide a flexible infrastructure to support data from the following 4 groups: ### Phenotypical/Clinical Data With v3.0, wider support was built for phenotypical / clinical data to be split across many entities with one-to-many relationships and that contain wider longitudinal data attributes. This data is most commonly ingested via Data Model Loader or other standardized pipelines such as the UK Biobank loading pipeline. The v3.0 data model supports linking data across multiple databases. ### Assay Data The v3.0 data model expands the relationship between the phenotypic data and omic data to allow for multiple assay types to be linked to a singular core phenotypic dataset. The linkages can be directly to the core main entity such as Patient, or each assay can link to different entities. For instance, an RNAseq assay might be linked to a specific Encounter. This data is most commonly ingested via a specialized loader like the VCF ETL Orchestrator and then merged with a core phenotypic dataset to generate the novel pheno-geno dataset. ### Default Dashboards With the v3.0 framework, dashboards can be directly explored, so defaults are no longer needed and dashboards can be shared with most users directly. If you want a default dashboard, set it on the properties of the dataset object as follows: For every dashboard you want to appear in the dropdown, add a property entry as follows: `dashboard- : ` where the display name can be any alphanumeric name, including spaces. Up to 10 entries can be added. To choose which record should be the default one loaded, add one additional property of `defaultDashboard : ` where the display name matches one of the entries. The user must have viewer access to all records. A sample configuration with three dashboards: ``` dashboard-group 1 dash: record-G39384knk39ksdnf32 dashboard-group 2 dash: record-G393d9e949mgyJel42 dashboard-group 3 dash: record-G84nheiIKjenmlk84j defaultDashboard: group 1 dash ``` ## V1.1 Dataset ### Default Dashboards Most datasets ingested before Q4 2020 were in v1.1 format. The default dashboards for each v1.1 dataset are embedded in the dataset proper. Because of this, to set or update the defaults, the dataset must be recreated using [Data Model Loader](/developer/ingesting-data/data-model-loader.md), using the "skip ingestion" setting. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://documentation.dnanexus.com/developer/datasets/dataset-versions.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.