> 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/connected-analytics/project-web-ui/p-data.md). # Data The Data inventory provides access to the files and folders stored in the project or linked to the project. Here, you can perform searches and data management operations such as moving, copying, deleting and (un)archiving. {% hint style="info" %} See also [Non-indexed folders ](/connected-analytics/project-web-ui/p-data/non-indexed-folders.md)which are a special form of data storage optimised for fast processing. {% endhint %} ### Recommended Practices #### File/Folder Naming Platform Core supports UTF-8 characters in file and folder names for data. Please follow the guidelines detailed below. (For more information about recommended approaches to file naming that can be applicable across platforms, please refer to the [AWS S3 documentation](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html).) {% hint style="info" %} **Folders and files cannot be renamed** after they have been created. **To rename a folder**, you will need to create a new folder with the desired name, move the contents from the original folder into the new one, and then delete the original folder. Please see the [Moving Data](#moving-data) section for more information. {% endhint %}

Characters generally considered "safe"

* Alphanumeric characters * 0-9 * a-z * A-Z * Special characters * Exclamation point `!` * Hyphen `-` * Underscore `_` * Period `.` * Asterisk `*` * Single quote `'` * Open parenthesis `(` * Closed parenthesis `)`

#### Data Formats See the list of supported [Data Formats](/connected-analytics/reference/r-resources/r-dataformats.md) #### Data Privacy When adding data to Platform Core, prioritize data privacy. Whether you're using storage configurations like AWS S3 or performing Platform Core data uploads, careful management of data access needs to be considered. When setting up cloud storage, confirm that configuration settings prevent unauthorized access. Always verify that uploads are free of unintended data to avoid privacy breaches. For more detailed information, refer to the Platform Core [Security and Compliance ](/connected-analytics/reference/r-resources/r-securityandcompliance.md)section. #### Data Integrity See [Data Integrity](/connected-analytics/project-web-ui/p-data/data-integrity.md) *** ## Viewing Data On the **Projects > your\_project > Data** page, you can view file information and preview files. ### Folder view (structured) vs flat view (list) You can switch between **folder** view and **flat** view with the icons at the left. * **Folder view** shows the navigation structure and only the **files and folders in the** **current folder**.\ **Searches in folder view** will be performed on **the** **current folder and all subfolders of the current folder.** * **Flat view** shows a list of **all files and folders** within the current project.\ When you perform **searches** in flat view, **all data of your project** will be considered. **Tree view** shows the navigation structure and only the **files and folders in the** **current folder**.\ **Searches in tree view** will be performed on **the** **current folder and all subfolders of the current folder.**

**List view** shows **all files and folders** within the current project.\ When you perform **searches** in list view, **all data of your project** will be considered.

{% hint style="info" %} You **cannot switch between folder and flat view when you are viewing search results**. Clear the search with the clear search button, or the x in the search dialog first. {% endhint %} ### Files To view **file details** click on the filename to see the file details. * **Run input tags** identifies the last 100 pipelines which used this file as input. * **Run output tags** identifies the pipeline which created the file. * **Connector tags** show if the file was added via browser upload or connector. * Clicking on a **folder** will open the folder itself, to see the folder details, use the **folder details** link at the top right of the screen. To view **file contents,** select the checkbox at the beginning of the line and then select **View** from the top menu. Alternatively, you can first click on the filename to see the details and then click the view tab to preview the file. If your data is the **result of an analysis**, you can find the analysis which created it at **Projects > your\_project > Data > your\_data > view > Data details tab > Source analysis**. Clicking the link here will open the analysis.


Filtering	To add filters, select the funnel/filter symbol at the top right, next to the search field.	Filters are reset when you exit the current screen.
Sorting	To sort data, select the three vertical dots in the column header on which you want to sort and chose ascending or descending.	Sorting is retained when you exit the current screen.
Displaying Columns	To change which columns are displayed, select the three columns symbol and select which columns should be shown.	In externally-managed projects, you can see which files are externally controlled and which are ICA-managed by means of the “managed by” column.	In flat view, you can jump to the folder in which files are located with the "Path" column.	The displayed columns are retained when you exit the current screen.

{% hint style="info" %} When you share the data view by sharing the link from your browser, filters and sorting is retained in links, so the recipient will see the same data and order. {% endhint %} To see the **ongoing actions** (copying and moving) on data in the data overview (**Projects > your\_project > Data**), add the **ongoing actions** column from the column list if it is not present yet.\ You can also consult the data detail view for ongoing actions by clicking on the data in the overview. When clicking on an ongoing action itself, the data job details of the most recent created data job are shown. The **Pipeline** and **Pipeline version** columns (which can be added from the column selector) show which pipeline and version produced these files. Files that predate version 2.49 will show blank cells. ### Folders If you open a folder by clicking it, you can see the **folder details** link at the top right. This will open the details screen where you can consult the **folder size** and number of files in that folder, the owning project, **ongoing actions** and **folder id**. You can also download the folder and all contents here with the **download** button. To help navigate between folders in flat view, you can use the "**path**' column in the data view which will open the folder containing the selected file in tree view. If you want to go further up the folder path, you can use the **folder structure above the file** **view**. If the path is not visible, you can add it with the three-columns symbol next to the filter symbol.

### Searching for Data To quickly find data, use the search dialog at the top right. Search is performed with automatic wildcards before and after the search text. You can use \* as additional wildcard, for example `b*n` will match `bunny` as it is interpreted as `*b*n*`. The search string length is limited to 250 characters. You can search on the file name, the path (/folder/subfolder) and tags.

### Secondary Data When Secondary Data is added to a data record, those secondary data records are mounted in the same parent folder path as the primary data file when the primary data file is provided as an input to a pipeline. Secondary data is intended to work with the CWL [secondaryFiles](https://www.commonwl.org/v1.2/CommandLineTool.html#File) feature. This is commonly used with genomic data such as BAM files with companion BAM index files.

*** ## Hyperlinking to Data You can create hyperlinks to data to quickly share it with the following syntax: ``` https:///ica/link/project//data/ ``` ``` https:///ica/link/project//analysis/ ```

Variable	Location
ServerURL	See browser address bar.
projectID	At YourProject > Details > URN > urn:ilmn:ica:project:ProjectID#MyProject
FolderID	At YourProject > Data > folder > folder details > ID
AnalysisID	At YourProject > Flow > Analyses > YourAnalysis > ID

{% hint style="info" %} Normal permission checks still apply with these links. If you try to follow a link to data to which you do not have access, you will be returned to the main project screen or login screen, depending on your permissions. {% endhint %} *** ## Exporting the Data List You can export the list of data which you see in the overview as a CSV, JSON, or excel file. 1. Select one or more files to export at **Projects > your\_project > Data**. 2. Select **Export** at the bottom of the screen. 3. Choose between the following export options: * To export only the list of selected files, select the **Selected rows** as the Rows to export option. To export the list of all files on the page, select **Current page**. * To export only the columns which are currently shown in your view, select **Visible columns** as the Columns to export option, otherwise, choose **All columns**. 4. Select the export format. (CSV/JSON/Excel) *** --- # 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/connected-analytics/project-web-ui/p-data.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.