Open akc472 opened 3 years ago
I think its a really smart move that you've constrained your descriptors so that you're dealing with moods and tone in a general way. It will certainly keep your code concise. Just in case though, you may want to add an "ambiguous" attribute to give yourselves some flexibility if you encounter a mood that could be interpreted as a combination of moods.
I agree with what Victoria said. I like all of the attributes that you guys have decided to include, but I feel like you might run into some instances where it is difficult to tag a line with only one mood (or any of them at all). Like Victoria said, an "ambiguous" tag would take care of any of those. My group ran into this issue in our project and we added an ambiguous tag to our mark-up.
I'm really excited to see the final analysis of this project. With every update, it is clear that you guys are narrowing down what needs to be found in your xml. The mood attributes are awesome, although I do agree with Shane and Victoria about the overlap. I wonder if even the ambiguous tag would be enough, because it may end up being necessary to use that attribute more than originally thought, which would screw up your analysis, I would think. Unless the fact that the emotion is generally ambiguous is enough to prove the question being made. Just a thought!
This week we looked at what we could add to the schema. One of the things that were added were the metadata which included year, title, artist, featured artists (if there are any), and the album. We also narrowed down which tones and moods we would use to describe the verses. For tones we would use negative, neutral, and positive. For moods we narrowed it down to mad, sad, happy, angry, cynical, hopeful, apathetic, empathetic, determined, anxious, and confident. We also added an attribute for certain lines called type, which we'll use to label the topics of certain verses.