> For the complete documentation index, see [llms.txt](https://fdilab.gitbook.io/open-data-commons/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fdilab.gitbook.io/open-data-commons/tutorials/upload-to-odc/upload-a-methodology-file.md). # Upload a Methodology file Methodology files are great to attach narrative and protocol descriptions associated to a dataset. You can upload a methodology file in either **.doc** or **.pdf** form following the same process described to [upload a data dictionary](/open-data-commons/tutorials/upload-to-odc/upload-a-dictionary.md) Currently, the ODC do not require methodology documents for you to upload and publish your datasets. However, we encourage you to include them as they improve the interpretability and reusability of your data. Some recommendations for compiling a methodology document: * If the dataset comes from a published paper (and hence has the methodology already published), you can provide the paper citation and link as part of the Methodology doc/pdf. Due to potential copyright issues, do not copy/paste the methods from any published papers. * If you have multiple protocols you wish to upload for the to the same dataset, we recommend combining them all into a single word document or pdf. The ODC only allows a single Methodology file to be attached to each dataset. --- # 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://fdilab.gitbook.io/open-data-commons/tutorials/upload-to-odc/upload-a-methodology-file.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.