> For the complete documentation index, see [llms.txt](https://govex.gitbook.io/open-data-dataset-starter-kit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://govex.gitbook.io/open-data-dataset-starter-kit/readme.md).
# Introduction to Dataset Inventory Guidelines
NOTE: This guide has been deprecated and replaced with a newer one at
## Introduction to Dataset Inventory Guidelines
Conducting a data inventory can lay the foundation for a performance management program and releasing data to an open portal, but developing and maintaining a dataset inventory should also be considered a data governance best practice. Identifying datasets that are available within departments is helpful for leadership and staff in all city agencies, and integrating public comments into the data release prioritization schedule ensures that stakeholders voices are heard.
The Center for Government Excellence recomends the following steps.
* **Step 1.** [Identify Datasets](/open-data-dataset-starter-kit/identify-datasets.md)
* **Step 2.** [Post Inventory](/open-data-dataset-starter-kit/post.md)
* **Step 3.** [Determine Release Schedule](/open-data-dataset-starter-kit/release.md)
To assist cities in creating a dataset inventory, the [Center for Government Excellence at Johns Hopkins University](http://govex.jhu.edu/), a partner in the [What Works Cities initiative](http://www.whatworkscities.org/), has created these guidelines. By learning from the experiences of other cities and following best practices developed by the Center, cities will be able to identify and release high quality datasets that are valuable to city residents and other stakeholders.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://govex.gitbook.io/open-data-dataset-starter-kit/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.