> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/basespace/releases/previous-releases/2019/5.36.0.md). # 5.36.0 ### July 9, 2019 - 5.36 - New Ways to Access Datasets * Features * Added FASTQ Datasets and Other Datasets tabs to the projects page. Other Datasets includes uploaded files, and app files that are not part of a biosample. * Added Run and Flow Cell ID data to the biosample dataset tooltips. * Added banner notifications for expiring or expired subscriptions. * Updated the share link deactivation confirmation to include information about managing user access after the link is deactivated. * Adjusted the display of base pair numbers. When the number of base pairs exceeds 1000 Gbp, the scale is adjusted to display in Tbp. * Bug Fixes * Fixed an issue where FASTQ validation continued after a file upload was cancelled. * Fixed an issue that allowed setting a library's prep kit to a deleted kit * Fixed an issue where uploading runs from both sides of a HiSeq flow cell could cause duplication of the project name. * Security Fixes ### Release 5.36.1 - July 22, 2019 * Features * Updated docker.illumina.com to support Enterprise apps (staged release complete 2019-08-06). * Performance improvements. * Bugs Fixed * None. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.bioinsight.illumina.com/basespace/releases/previous-releases/2019/5.36.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.