> For the complete documentation index, see [llms.txt](https://annarbor.worldiaday.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annarbor.worldiaday.org/people/jenna-hartel.md).
# Jenna Hartel
Jenna Hartel received a Doctorate of Philosophy in Information Studies from the Department of Information Studies at the University of California, Los Angeles (2007). As a child, she had an uncommon enjoyment of information, realized in a love of reading, keeping diaries, and writing letters. Today, her research is organized around the question: What is the nature of information in the pleasures of life? She is investigating this matter through the concatenated study of information phenomena in serious leisure -- cherished, information-rich pursuits such as hobbies.
Her empirical research explores the content, structure, and use of leisure information on personal and social levels, and her theoretical work aims to characterize the nature of information in leisure realms. She has published on these topics in JASIS\&T, Journal of Documentation, Knowledge Organization, and Information Research; and she is the author of the article “Leisure and Hobby Information and its User” for the recent edition of the Encyclopedia of Library and Information Science (2010).
* :link:
---
# 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://annarbor.worldiaday.org/people/jenna-hartel.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.