As a researcher, I fully appreciate the pro-commonplace book conceptualization of the first post, and the second takes things amazingly further with a plugin that allows one to easily display one’s hypothes.is annotations on one’s own WordPress-based site in a dead-simple fashion.
This functionality is a great first step, though honestly, in keeping with IndieWeb principles of owning one’s own data, I think it would be easier/better if Hypothes.is both accepted and sent webmentions. This would potentially allow me to physically own the data on my own site while still participating in the larger annotation community as well as give me notifications when someone either comments or augments on one of my annotations or even annotates one of my own pages (bits of which I’ve written about before.)
Either way, kudos to Kris Shaffer for moving the ball forward!
Examples
My Hypothes.is Notebook
The plugin mentioned in the second article allows me to keep a running online “notebook” of all of my Hypothes.is annotations on my own site.
My IndieWeb annotations
I can also easily embed my recent annotations about the IndieWeb below:
[ hypothesis user = 'chrisaldrich' tags = 'indieweb']
Hypothes.is annotations and the #IndieWeb boffosocko.com/2016/06/17/hyp… ht @krisshaffer
Cool thing is. Udell and the gang are pretty open to suggestions, it sounds like. At the same time, it’s quite possible that webmentions wouldn’t fit in their overall vision of the tool.
#meta-annotation #Hypothesis
Syndicated copies:
This Article was mentioned on kimberlyhirsh.com
I’m making a few notes to myself here to document my process for keeping a public research notebook. They might be of interest to you, too.
First, I’m talking here mostly about keeping up with the literature. There are (in my opinion obvious) ethical implications of actually sharing your data on your website. I’ll explore them as I write my proposal, but right now, all I’ve got is other people’s research that I’m reading and writing about, and then I’ll probably have some memos on my own process of preparing for comps and selecting my dissertation topic. Nothing wild.
So, what am I doing? Well, inspired by some writing by Kris Shaffer and Chris Aldrich, and by the fact that I gave a keynote last weekend on Connected Learning and the IndieWeb, I want to share my reading notes on some of the readings I’m doing for comps. It will help me keep track of my most important notes, and maybe it’ll be useful for other people researching similar topics. I tend to pick fairly under-researched areas, and I know it can be frustrating to have to dig up the literature on those, so this is one way I can maybe make it easier for colleagues.
Raul Pacheco-Vega is another inspiration, as he both shares reading notes and has heavily influenced my literature review workflow.
What’s the workflow?
I find the source, as described through one of the various techniques in my literature review workflow, and pull it into Paperpile. If Paperpile can’t find a PDF on its own, then I track a PDF down or, if it’s only available physically, track down a physical copy.
If it’s a PDF, I read it on my Android tablet with Xodo, making highlights and annotations using my Musemee Notier stylus. If it’s a physical text, I take notes on a dedicated COMPS spread in my Bullet Journal (I use a Moleskine large dotted black notebook and a Pilot G2 07).
I create a new Google Doc.
From Paperpile, I copy the citation and paste it into the Google Doc. I name the Google Doc Author Year Article Title. (These are all in a folder called “Synthetic Notes,” nested in a folder named after the literature area.)
I type up a quick synthetic note based on my highlights and annotations.
I use Paperpile to find a link to the source of the original.
Then, I use a bookmarklet with the WordPress Post Kinds plugin to create a new bookmark on my website. (I use the bookmark post kind instead of a read, because I’m only doing an Abstract-Introduction-Conclusion extraction, not a full read of the piece.)
I paste the abstract into the Summary box in the Response Properties box.
I paste the contents of my Google Doc into the WordPress editor and use the “Clear formatting” button to clean up messy GDocs code.
I give the post a tag related to the literature area (e.g., connected-learning) and select the category “Research Notebook,” then publish!
You may have noticed that this workflow leaves out Hypothes.is entirely. This is for a few reasons, but mostly just that right now, Hypothes.is would add several extra steps as I read on my tablet rather than on my laptop. I’d have to open up the PDF on my laptop, re-highlight and annotate using Hypothes.is tools, then use the Hypothes.is aggregator plugin to bring over those to my website. So for now, I’m doing it all manually on my site and not sharing anything there.
Replied to a tweet by Hungry Bread Elevator (Twitter)
Some of the off-label uses of Hypothes.is have been enumerated lately, including some I’ve mentioned.
I’ve tinkered a bit with CROWDLAAERS, but it’s always seemed to me geared toward a very niche audience including teachers potentially using it for grading? Perhaps I’m missing some more of its flexibility? Remi Kalir might be able to help elucidate it or indicate if he’s noticed anyone using it for off-label usage.
I might see it being more useful if one could analyze site-wide annotations on a domain with a wild-card search of this sort: https://tomcritchlow.com/*.
I have to imagine that it would be cool to see all the annotations and conversations across something like the New York Times with a data visualization tool like this.
Jon Udell and gang are aware of Webmention, but haven’t pulled the trigger (yet) on making the decision to build them in. I’ve outlined some methods for making their platform a bit more IndieWeb friendly by adding markup and some additional HTML to allow people to force the system to be able to send webmentions. I do frequently use Jon’s facet tool to check highlighting and annotation activity on my website.
I have found Crowdlaaers useful several times in that I’m aware that some pages are annotated, but they’re either not public or are part of other groups for which I’m not a member. An example of this is this page on my website which has one annotation which I can’t see, but by using Crowdlaaers, I can. Another example is viewing annotations on sites that have subsequently blocked Hypothes.is like this example. Of course, sometimes you’ll do this and find odd bugs floating around in the system.
Syndicated copies to: Twitter icon