We tweeted the Traversal on three accounts: 1) Dene Grigar's account that had over 2,800 followers, 2) Nicholas Schiller's account, with 2,200 followers and 3) ELL Team Member Veronica Whitney's site, with over 175 members. Whitney was in charge of posting and reposting on Twitter during the event. The hashtag we used was #elitpathfinders, the same hashtag developed for the original Pathfinders project.
The first posts announce the event ahead of time using the hashtag #elitpathfinders.
Grigar posts a photo of Kolb rehearsing for the Traversal the day of the event.
These next few posts contain information about the work for the audience who do not have prior knowledge of Socrates in the Labyrinth.
These next four posts are from students in the audience.
This post is from Nicholas Schiller who provides a link to access more detail on Kolb's work.
This is post shows the original copy of Socrates in the Labyrinth
which Grigar purchased from Eastgate.
This post from Grigar thanks David Kolb for participating in the live Traversal of his work, Socrates in the Labyrinth. YouTube ChatAs we were relying heavily on YouTube for distribution of video for our live streamed Traversal, with this Traversal we began to capture the discussion that took place in YouTube's chat feature.
Here is the chat for David Kolb's reading of his Socrates in the Labyrinth. The linear nature of text chat presented challenges for including in this book, we'll explore other techniques for capturing this conversation in future chapters.
We found Storify useful as a tool for pulling together all of the Facebook and Twitter posts into one interface. While our story could have been exported as a .pdf or made into a screen capture, the output is not an accurate representation of the original format and presents other display issues. Instead, Nicholas opted to export the story to HTML, save the content locally, and then host it on our web server. Weeks into our project, the developers of Storify announced that the site would not be continued after May 2018, which means we will not have access to this tool in future stages of our project.