> For the complete documentation index, see [llms.txt](https://librarydata.gitbook.io/voyage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://librarydata.gitbook.io/voyage/human-data.md).

# Human data

## Requirements

* Pens
* Access to title/items in catalogue data
* Paper clips
* Human data data sheet printed

## Objectives

* Icebreaker
* Participants will begin to understand the fundamentals of data analysis: Sort, Filter, Group by, Roll up, Count, and Unique     Key

## Task

We will be separating into groups of 8-10.

### Part A: Becoming data 5 minutes

Using the titles/items in catalogue data provided, choose one row and fill in the printed data sheet paying attention to how the data is formatted Each person will represent one title in the library catalogue

### B: Human data 15 minutes

Pin the sheet to your shirt and stand up! Through an interactive exercise, where each of us embodies a row of data, we’ll answer a few questions.

## Key points

* It helps to share what you know and don’t know about analysing data.

## Source Material

Adapted from [BetaNYC 2017](http://bit.ly/opendata_offline) Creative Commons 4.0 - Attribution - Share-alike


---

# 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://librarydata.gitbook.io/voyage/human-data.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.