Week Three: The Community Historian and Beginnings of an Initiative

The Community Historian

    This week, I began conceptualizing the beginnings and foundation of the History Harvest concept using the draft I discussed last week. As I navigate through the process of helping to coordinate a History Harvest with the City of Debary, I figured it would be beneficial to write and document my own thoughts towards community initiative as I work with my own community partner. My goal in creating this guide is not to just give instructions, but rather to inform with advice based on real experience that I gain in planning the concept. This past semester, I defined the "Community Historian" as "An individual dedicated to the enduement and prolonging of a collective history based on memory with the intention of empowering a communal historical authority." 

    Through drafting and conceptualizing, I realized this week the volume that the Community Historian contributes to the project is the very foundation itself; Without a knowledgeable partner, the project has no foothold no ground to gain traction, resulting in a spree to find whomever possible with no real mission. Every community partner has had a heart for the stories that are captured, giving light and voicing the importance to their own community as we tell their story. I would argue that the Community Historian is a vital asset to the project and without them, the initiative could no exist in it's greatest form. From Eatonville, Greenwood Cemetery, and now Debary, the Community Historian is vital to the success of the project.

The Beginning of the Initiative: Planning and Strategy

    Having understood the beginnings of the History Harvest and the level of involvement the Community Historian plays, it continues to grow even more complicated. From the beginning of conversations with Community Historians, responsibilities are handed out left and right to everyone involved to ensure that the project and it's goals are successfully met. The brochure will go into detail on materials and the collection of paperwork from participants, but here, I would like to dive into the pre=determined responsibilities.

    The History Harvest model cannot be sustained by one person, student, community member, or staff person. Rather, it require the conjoined effort of a team to ensure each goal is met throughout the day. A big part of this is the designation of roles, jobs, and responsibilities to those within your team. Specifically, it is important to known what is the student's job, the staff person's job, and the Community Historian's job. A student is responsible to organize their participants to ensure they are set up for success, pointing them in the right direction and carrying the weight of a team leader when preparing "day of" materials. The staff person may assist, but their primary job is as a support role, managing paperwork and instructing the student as they prepare University owned materials (scanners, printers, datasheets, participation forms, camera, etc.). The Community Historian carries one of the larger roles, working to coordinate with the community to secure a location for the event itself whilst spreading awareness to fellow residents. While these delegations might seem specific, each team member can assist the other in support as they fulfill their own task. It must also be said that a History Harvest is not a "week of planning" ordeal, but rather it must be planned over a month in advance. As the semester goes on, I hope to showcase more of the creation of the brochure, engaging in the visual aspects of the education process.