Open MJB288 opened 5 years ago
I think this project is really interesting as a means of understanding Poe's values and metaphors in a way a textual analysis might miss. My questions, then, which I haven't seen answered in your other updates are:
1) How do you qualify these language formations? Like, what makes some specific section of language "catch and release"? Obviously that's subjective, but I'd like to hear you elaborate some on what your rationale/process is.
2) What does this research MEAN to how we understand Poe? Again, subjective and I understand you can't necessarily until you're done, but I'm curious about your thoughts now.
Again, really cool way to approach Poe. I read him in high school like everyone else but I have never really thought about him and I never picked up this imagery being a focus of his. Obvious in retrospect and really cool.
Your group is doing a great job at pacing your project. It seems your group has started working on a bit of everything or at least discussed goals. Using project boards might aid in achieving those goals, as well as providing a sense of accomplishment! It's great that your group was able to come to agree on the markdown style for this project, including general markdown styles as well as catering it specifically to your project needs.
Sounds like you guys are making steady progress on all fronts, and it's nice that you have the workload split between yourselves according to strengths. Settling on a cohesive marking style is something our group is also working towards, and its definitely a major part of moving forward in your analysis. Have you guys found more clarity in your research inquiry as you've begun to establish the analytical side of things? All around, it seems like your project is really starting to take exciting shape-looking forward to what comes next!
Today's meeting was rather informative. We went over how to use the git command line in relevance to our project. After overcoming some initial technical issues concerning Git, we drew up a quick pre-planning of our website, nothing much, just a title and our obdurodon single word (surprisingly, "Poe" by itself was not taken). The most important act of the meeting was settling upon a markdown style. As a test run, we each had marked down one different poem and compared styles. After comparing and contrasting our styles, we have settled upon tagging the parts of speech as the element names, and putting the values we need (openess/closeness, capture/release) in a value attribute tag. Since we are doing poetry, we agreed that we should preserve the line structure as well via tagging. For next week, Ethan will be tagging 10-15 poems since he is going to be doing most of the markup/document analysis, while we will each do 5-7. Another task we have is coming up with a schema for our agreed upon markup style. Finally, we also have to come up with a preliminary homepage as a placeholder for our project site. For right now, we are still feeling pretty good about this project.