{"id":701,"date":"2006-06-09T11:07:07","date_gmt":"2006-06-09T19:07:07","guid":{"rendered":"http:\/\/www.edtechpost.ca\/wordpress\/2006\/06\/09\/dynamically-wikipedia-fying-text-drawdoc-and-wikiproxy-greasemonkey-script\/"},"modified":"2006-06-09T11:07:07","modified_gmt":"2006-06-09T19:07:07","slug":"dynamically-wikipedia-fying-text-drawdoc-and-wikiproxy-greasemonkey-script","status":"publish","type":"post","link":"https:\/\/scottleslie.ca\/edtechpost\/wordpress\/2006\/06\/09\/dynamically-wikipedia-fying-text-drawdoc-and-wikiproxy-greasemonkey-script\/","title":{"rendered":"Dynamically Wikipedia-fying Text: Drawdoc and Wikiproxy Greasemonkey script"},"content":{"rendered":"

http:\/\/nagle.u1i.net\/drawdoc\/autolinker.php<\/a> and http:\/\/wikiproxy.whitelabel.org\/greasemonkey.html<\/a><\/p>\n

Both of these accomplish pretty similar things – take an existing web page, and turn proper nouns\/key terms into links to wikipedia<\/a> automatically.<\/p>\n

Drawdoc<\/a> is currently a web-based app (but not hard to see how it could be a service instead) that employs Yahoo’s term extraction service<\/a> to identify the salient terms in a document, and then offers possible image matches from Yahoo images, and annotates those terms with links to either Wikipedia, Google or Yahoo to the selected terms.<\/p>\n

The Wikiproxy Greasemonkey script<\/a> works slightly differently, as a Greasemonkey<\/a> script<\/a> that appears to just look for ‘Proper Nouns’ on a page and then annotate them as the page is rendered with links to wikipedia. So works on the client side, but the effect is similar, a text automatically annotated with key words to wikipedia.<\/p>\n

In both cases what seems lacking is a connection to wikipedia that actually confirms there is something to link to before creating the link. Not surprising. That’s not how they are intended to work, they are lightweight mashups. But the IDEA<\/strong> here is important – start thinking about collections you have on your campus that are pedagogically significant to your students – how tough would it be to code a greasemonkey script<\/a> that then rendered key terms in your online course as a link to that collection.. of anatomical images? of learning objects? …you get the idea. Why do this? Well, in the case of an approach like drawdoc, it could become an automated annotator for your CMS-based courses, saving time and effort. With a greasemonkey-type approach, it could potentially become a tool that augmented the students experience of materials you didn’t create<\/em> and don’t control with links to content in collections you trust.<\/p>\n

Mashups are here. They’re even commonplace<\/a>, almost. But just wait until they start invading<\/a> the academy<\/a>. You can already get a list of the available ‘web 2.0 APIs’<\/a> (that is almost inevitably incomplete) – do you know what’s available inside your own institution<\/a>? …you’re either on the bus, or it’s running over you… exciting times indeed. – SWL<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

http:\/\/nagle.u1i.net\/drawdoc\/autolinker.php and http:\/\/wikiproxy.whitelabel.org\/greasemonkey.html Both of these accomplish pretty similar things – take an existing web page, and turn proper nouns\/key terms into links to wikipedia automatically. Drawdoc is currently a web-based app (but not hard to see how it could be a service instead) that employs Yahoo’s term extraction service to identify the salient terms … Continue reading “Dynamically Wikipedia-fying Text: Drawdoc and Wikiproxy Greasemonkey script”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[226,448,453],"class_list":["post-701","post","type-post","status-publish","format-standard","hentry","category-the-rest","tag-mashups","tag-web2-0","tag-wiki"],"_links":{"self":[{"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/posts\/701","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/comments?post=701"}],"version-history":[{"count":0,"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/posts\/701\/revisions"}],"wp:attachment":[{"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/media?parent=701"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/categories?post=701"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scottleslie.ca\/edtechpost\/wp-json\/wp\/v2\/tags?post=701"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}