{"id":3078,"date":"2019-02-05T03:08:26","date_gmt":"2019-02-05T03:08:26","guid":{"rendered":"https:\/\/iris.siue.edu\/technology-literature\/?p=3078"},"modified":"2019-02-05T03:08:26","modified_gmt":"2019-02-05T03:08:26","slug":"tools-of-the-trade-voyant-and-annotation-studio","status":"publish","type":"post","link":"https:\/\/iris.siue.edu\/technology-literature\/2019\/02\/05\/tools-of-the-trade-voyant-and-annotation-studio\/","title":{"rendered":"Tools of the trade (Voyant and Annotation Studio)"},"content":{"rendered":"<p>Annotation Studio is a tool much more to my liking than Voyant. It was easy to highlight passages and add comments. I did find that I was being selective in the comments I posted. Normally, I would make any comment that came to mind and add it to my e-book. Having my comments open to the class, there were several that I decided not to post. These were, more often than not, abusive, disgruntled, cuss-filled exclamations about Terry.<\/p>\n<p>I did find that having access to classmates\u2019 comments aided in my close reading of <em>Herland<\/em>. Quite often, I misinterpret a passage or completely miss subtle subtexts. Being able to see what others think about a passage helps reaffirm or realign my understanding of the text. The helpfulness of this is greatly dependent on the quantity and quality of comments added by the participants. Being able to see all the comments in the right pane is useful as we\u2019re reading, although it would be beneficial if each contributor could be easily filtered and each contributor&#8217;s comments displayed with a uniquely colored background. As it is now, it looks like a wall of text that you must pick your way through to find something useful.<\/p>\n<p>Being able to add tag to our comments is great functionality poorly implemented. The only way I\u2019ve found to search for comments by tag is by going through the Tools menu and typing the key word you wish to filter. This is wholly dependent on that word being used as a tag. There needs to be a list of all tags available for the user to select. This would be a great feature if the user was writing a paper on a specific aspect of the book.<\/p>\n<p>I did a little snooping and it seems Annotation Studio may be a forgotten project or at least no longer being enhanced. The most recent copyright I found was 2017 on the main page. This date may be for some background security updates to the code, but the last update to Annotation Studio was back in 2015. The site FAQ states that, \u201cAnnotation Studio is developed as an open source web application, bases on state of the art web design and development technologies.\u201d It\u2019s been awhile since I\u2019ve looked into the open source copyrights, and even then not too deeply, but I would expect that anywhere a copyright is claimed that it must be stated as open source. If this is not being updated by MIT any longer, it would be great if a university took position at the helm that has been vacated.<\/p>\n<p>Voyant and Annotation Studio are tools working in completely different aspects of literature. Voyant only looks at the data of the text. This is great for analyzing diction, finding correlations and viewing trends. The \u201creader\u201d is absent from the text with Voyant. Annotation Studio\u2019s usefulness is reliant on user input. The \u201creader\u201d analyzes the texts and makes comments and markups on a digital copy. The plot, emotion, and subtext are absent from Voyant. If someone asked me to summarize <em>Herland<\/em>, I could do so easily from using Annotation Studio. This only after doing all the legwork that Annotation Studio displays. If I\u2019d only had Voyant as a tool for summarizing <em>Herland<\/em>, I would get puzzled looks. Although I\u2019m pretty sure it won\u2019t come up in any literary conversation, I\u2019m confident in stating that the two terms with the highest correlation to <em>Terry<\/em> are <em>Jeff<\/em> and <em>can\u2019t<\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Annotation Studio is a tool much more to my liking than Voyant. It was easy to highlight passages and add comments. I did find that I was being selective in the comments I posted. Normally, I would make any comment that came to mind and add it to my e-book. Having my comments open to the class, there were several that I decided not to post. These were, more often than not, abusive, disgruntled, cuss-filled exclamations about Terry. I did find that having access to classmates\u2019 comments aided in my close reading of Herland. Quite often, I misinterpret a passage or completely miss subtle subtexts. Being able to see what others think about a passage helps reaffirm or realign my understanding of the text. The helpfulness of this is greatly dependent on the quantity and quality of comments added by the participants. Being able to see all the comments in the right pane is useful as we\u2019re reading, although it would be beneficial if each contributor could be easily filtered and each contributor&#8217;s comments displayed with a uniquely colored background. As it is now, it looks like a wall of text that you must pick your way through to find something useful. Being able to add tag to our comments is great functionality poorly implemented. The only way I\u2019ve found to search for comments by tag is by going through the Tools menu and typing the key word you wish to filter. This is wholly dependent on that word being used as a tag. There needs to be a list of all tags available for the user to select. This would be a great feature if the user was writing a paper on a specific aspect of the book. I did a little snooping and it seems Annotation Studio may be a forgotten project or at least no longer being enhanced. The most recent copyright I found was 2017 on the main page. This date may be for some background security updates to the code, but the last update to Annotation Studio was back in 2015. The site FAQ states that, \u201cAnnotation Studio is developed as an open source web application, bases on state of the art web design and development technologies.\u201d It\u2019s been awhile since I\u2019ve looked into the open source copyrights, and even then not too deeply, but I would expect that anywhere a copyright is claimed that it must be stated as open source. If this is not being updated by MIT any longer, it would be great if a university took position at the helm that has been vacated. Voyant and Annotation Studio are tools working in completely different aspects of literature. Voyant only looks at the data of the text. This is great for analyzing diction, finding correlations and viewing trends. The \u201creader\u201d is absent from the text with Voyant. Annotation Studio\u2019s usefulness is reliant on user input. The \u201creader\u201d analyzes the texts and makes comments and markups on a digital copy. The plot, emotion, and subtext are absent from Voyant. If someone asked me to summarize Herland, I could do so easily from using Annotation Studio. This only after doing all the legwork that Annotation Studio displays. If I\u2019d only had Voyant as a tool for summarizing Herland, I would get puzzled looks. Although I\u2019m pretty sure it won\u2019t come up in any literary conversation, I\u2019m confident in stating that the two terms with the highest correlation to Terry are Jeff and can\u2019t.<\/p>\n","protected":false},"author":38,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sb_is_suggestion_mode":false,"_sb_show_suggestion_boards":false,"_sb_show_comment_boards":false,"_sb_suggestion_history":"","_sb_update_block_changes":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-3078","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/posts\/3078","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/users\/38"}],"replies":[{"embeddable":true,"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/comments?post=3078"}],"version-history":[{"count":1,"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/posts\/3078\/revisions"}],"predecessor-version":[{"id":3079,"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/posts\/3078\/revisions\/3079"}],"wp:attachment":[{"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/media?parent=3078"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/categories?post=3078"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/iris.siue.edu\/technology-literature\/wp-json\/wp\/v2\/tags?post=3078"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}