> For the complete documentation index, see [llms.txt](https://docs.data.ca.gov/california-open-data-publishers-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.data.ca.gov/california-open-data-publishers-handbook/6.-update-and-maintain-the-dataset.md).

# 6. Update and Maintain the Dataset

It is important to maintain data updates according to the target frequency indicated in the metadata.

While automated updates are ideal, especially for more frequently updated data, we know that sometimes that's not an option. Below are considerations for making sure you can maintain data updates in line with your target frequency.

## Best practices checklist: automated updates

Automation will most likely be set up by a technical team in your organization. The following are practices to make sure your automation is resilient.

* [ ] Dataset update steps are captured and annotated through an automated process (e.g. scripts or ETL/ELT platform)
* [ ] Standardized and user-friendly alerts for automation success and failure are sent to appropriate points of contact including technical and program contacts
* [ ] Sufficient logs are kept to ease troubleshooting issues and identifying root causes of ongoing problems

## Best practices checklist: manual updates

* [ ] Place update procedure documents ([developed in Step 2](/california-open-data-publishers-handbook/2.-prepare-data-for-publishing.md#checklist)) in a common document repository where other staff can access as needed
* [ ] Identify one or more staff who could manage the dataset and help address issues in your absence or upon leaving your role
* [ ] Cross-train staff on updates to ensure continuity


---

# 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://docs.data.ca.gov/california-open-data-publishers-handbook/6.-update-and-maintain-the-dataset.md?ask=<question>&goal=<endgoal>
```

`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.