> For the complete documentation index, see [llms.txt](https://code-for-philly.gitbook.io/partnerships/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://code-for-philly.gitbook.io/partnerships/building-a-relationship/case-study-relationship.md).

# Case study: RLadies relationship

### Who are RLadies Philly?

RLadies is an organization that "promotes gender diversity in the R community and in data science more broadly" ([website](https://www.rladiesphilly.org/)). In additional to a community Slack, they hold monthly meetups, and collaborations with other organizations.

### How did we get in contact?

Marieke Jackson, who was leading a Code for Philly [project with Prevention Point](https://codeforphilly.org/projects/prevention_point_unified_reporting_system), met Karla Fettich at an RLadies meetup. Karla was an RLadies organizer and volunteer at Philadelphia Animal Welfare Society (PAWS).

### How did the relationship progress?

Eventually, Marieke heard about Karla's work at PAWS and wondered whether it was a good fit for Code for Philly. At this point, she had joined Code for Philly's leadership team. She and Michael Chow--projects co-lead at the time--set up a quick initial meeting, and scheduled PAWS to present at a hacknight!

To learn more about the PAWS project, see their [project page](https://codeforphilly.org/projects/paws_data_pipeline).

(**TODO finish this case study. If you are interested in completing these docs, or telling the story of Code for Philly projects, join the Code for Philly**[ **partnership project**](https://codeforphilly.org/projects/code_for_philly_-_creating_new_projects_and_partnerships) **and / or our** [**leadership team**](https://codeforphilly.org/pages/leadership-support_team_open_positions)**!)**


---

# 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://code-for-philly.gitbook.io/partnerships/building-a-relationship/case-study-relationship.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.