> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/microarray/general/microarray-general-reference_material-list/000003030.md).
# What is the Content Descriptor file in GenomeStudio 2011.1 Methylation Module?
In GenomeStudio 2011.1, a Content Descriptor file is required to create a project. It refers to the \*.bpm version of the manifest and is not to be confused with the similarly named LIMS Product Descriptor file (\*.xml).
* The Bead Pool Manifest (\*.bpm) file provides information about probe content on the array.
* The Product Descriptor or Product Definition file (\*.xml) contains fields describing the specific product format.
In the final window of the Project Wizard during Methylation Project creation in GenomeStudio 2011.1, the user is required to select the Content Descriptor file.
**Figure 1.** Content Descriptor selection window in the GenomeStudio Project Wizard.
Selecting "Browse" prompts the user to navigate to a Bead Pool Manifest (\*.bpm) file saved on the computer:
**Figure 2.** Navigating to the Content Descriptor/Bead Pool Manifest.
Once the\*.bpm file is selected in the Project Wizard window, it will appear in the dropdown menu.
**Figure 3.** Content Descriptor field populated with the Bead Pool Manifest file.
Click "Finish" button, which is no longer grayed out, and the project will load.
**References:**
* [Infinium MethylationEPIC BeadChip Product Files](https://support.illumina.com/array/array_kits/infinium-methylationepic-beadchip-kit/downloads.html)
* [Infinium Mouse Methylation BeadChip Product Files](https://support.illumina.com/array/array_kits/infinium-mouse-methylation-beadchip-kit/downloads.html)
* [Methylation Screening Array Product Files](https://support.illumina.com/array/array_kits/infinium-methylation-screening-array/product-files.html)
* Custom Array manifests can be downloaded from [MyIllumina Custom Products](https://customproducts.my.illumina.com/) following instruction on Illumina Knowledge [How to access custom array product files (manifests and product definition files) in MyIllumina](/microarray/iselect-custom-genotyping/microarray-iselect-custom-genotyping-reference_material-list/000001531.md)
\
\
\
| |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3030), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003030%20-%20Microarray%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |
---
# 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://knowledge.illumina.com/microarray/general/microarray-general-reference_material-list/000003030.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.