#hypothes.is

[chrisaldrich]

Creating a commonplace book or zettelkasten index from Hypothes.is tags

I thought it might be useful to have a relatively complete list of cross linked topical headings in my digital notebook (currently Obsidian) which is a mélange of wiki, zettelkasten, journal, project management tool, notebook, and productivity tool. First, let’s be honest that mélange is too poetic based on what I see of how others use Obsidian and similar tools. My version is structured to have very clear delineations between these forms even though I’m using the same tool for various functions.

I find that indexed subject headings can be useful for creating links between my wiki-like pages as well as links between atomic ideas in my digital zettelkasten. Gradually as one’s zettelkasten becomes larger and one works with it more, it becomes easier to recall individual ideas and cross link them. Until this happens or for smaller zettelkasten it can be useful to cross reference subject headings from one zettel to see what those link to and use those as a way to potential create links to other zettels. This method can also be used as a search/discovery aide for connecting edge ideas in new areas to pre-existing portions of one’s zettelkasten as well. Of course at massive scale with decades of work, I suspect this index will have increased value as well.

I don’t hear people talking about these types of indices for their zettelkasten in any of the influencer spaces or on social media. Are people simply skipping this valuable tool? For those enamored of Niklas Luhmann, we should mention that having and maintaining a subject index was a powerful portion of his system, even if the digitized version of his zettelkasten hasn’t yet been fully digitized. I haven’t seen the whole collection myself, but based on the condition of some of the cards in his index, Luhmann heavily used his subject index. (Note to self: I wonder what his whole system would look like in Obsidian?) Having a general key word/subject heading/topic heading index of all the material in one’s system can be very useful for general search and discovery as well. This is one of the reasons that John Locke wrote about a system for indexing one’s commonplace book in 1685. His work here is likely the distal reason Luhmann had one in his system.

Systems that have graphical knowledge graphs may make this process easier as one can look from one zettel out one or two levels to see where those link to.

Since such a large swath of my note taking practice starts by using Hypothes.is as my tool of choice, I’m able to leverage several years of using it to my benefit. Within it I’ve got 9,314 annotations, highlights, and bookmarks tagged with over 3,326 subject headings as of this writing.

To get all my subject heading tags, I used Jon Udell’s excellent facet tool to go to the tag editing interface. There I entered a “max” number larger than my total number of annotations and left the “tag” field empty to have it return the entire list of my tags. I was then able to edit a few of them to concatenate duplicates, fix misspellings, and remove some spurious tags.

An alternate way of doing this is to use a method described in this GitHub issue which shows how to get the tags out of local storage in your web browser. Your mileage may vary though if you use Hypothes.is in multiple browsers, which I do.

I moved this list from the tag editor into a spreadsheet software to massage the list a bit, clean up any character encodings, and then spit out a list of [[wikilinked]] index keywords. I then cut and pasted it into my notebook and threw in some alphabetical headings so that I could more easily jump around the list.

Now I’ve got an excellent tool and interface for more easily searching and browsing the various areas of my multi-purpose digital notebook.

I’m sure there are other methods within various tools of doing this, including searching all files and cutting and pasting those into a page, though in my case this doesn’t capture non-existing files. One might also try a search for a regex phrase like: /(?:(?:(?:<([^ ]+)(?:.*)>)\[\[(?:<\/\1>))|(?:\[\[))(?:(?:(?:<([^ ]+)(?:.*)>)(.+?)(?:<\/\2>))|(.+?))(?:(?:(?:<([^ ]+)(?:.*)>)\]\](?:<\/\5>))|(?:\]\]))/ (found here) or something as simple as /\[\[.*\]\]/ though in my case they don’t quite return what I really want or need.

I’ll likely keep using more local search and discovery, but perhaps having a centralized store of subject headings will offer some more interesting affordances for search and browsing?

Have you created an index for your system? How did you do it?

[chrisaldrich]

An Outline for Using Hypothesis for Owning your Annotations and Highlights

I was taken with Ian O’Byrne’s righteous excitement in his video the other day over the realization that he could potentially own his online annotations using Hypothesis, that I thought I’d take a moment to outline a few methods I’ve used.

There are certainly variations of ways for attempting to own one’s own annotations using Hypothesis and syndicating them to one’s website (via a PESOS workflow), but I thought I’d outline the quickest version I’m aware of that requires little to no programming or code, but also allows some relatively pretty results. While some of the portions below are WordPress specific, there’s certainly no reason they couldn’t be implemented for other systems.

Saving individual annotations one at a time

Here’s an easy method for taking each individual annotation you create on Hypothesis and quickly porting it to your site:

Create an IFTTT.com recipe to port your Hypothesis RSS feed into WordPress posts. Generally chose an “If RSS, then WordPress” setup and use the following data to build the recipe:

Input feed: https://hypothes.is/stream.atom?user=username (change username to your user name)

Optional title: 📑 EntryTitle

Body: EntryContent from EntryUrl <br />EntryPublished

Categories: Highlight (use whatever categories you prefer, but be aware they’ll apply to all your future posts from this feed)

Tags: hypothes.is

Post status (optional): I set mine to “Draft” so I have the option to keep it privately or to publish it publicly at a later date.

Modify any of the above fields as necessary for your needs. IFTTT.com usually polls your feed every 10-15 minutes. You can usually pretty quickly take this data and turn it into your post kind of preference–suggestions include read, bookmark, like, favorite, or even reply. Add additional categories, tags, or other metadata as necessary for easier searching at a later time.

Here’s an example of one on my website that uses this method. I’ve obviously created a custom highlight post kind of my own for more specific presentation as well as microformats markup.

A highlight from Hypothesis posted on my own website using some customized code to create a “Highlight post” using the Post Kinds Plugin.

Aggregating lots of annotations on a single page

If you do a lot of annotations on Hypothesis and prefer to create a bookmark or read post that aggregates all of your annotations on a given post, the quickest way I’ve seen on WordPress to export your data is to use the Hypothesis Aggregator plugin [GitHub].

Create a tag “key” for a particular article by creating an acronym from the article title followed by the date and then the author’s initials. This will allow you to quickly conglomerate all the annotations for a particular article or web page. As an example for this article I’d use: OUHOAH062218CA. In addition to any other necessary tags, I’ll tag each of my annotations on the particular article with this somewhat random, yet specific key for which there are unlikely to be any other similar tags in my account.

Create a bookmark, read, reply or other post kind to which you’ll attach your annotations. I often use a bookmarklet for speed here.

Use the Hypothesis Aggregator’s short code for your tag and username to pull your annotations for the particular tag. It will look like this:

[hypothesis user = 'username' tags = 'tagname']

If you’re clever, you could include this shortcode in the body of your IFTTT recipe (if you’re using drafts) and simply change the tag name to the appropriate one to save half a step or need to remember the shortcode format each time.

If you’re worried that Hypothes.is may eventually shut down, the plugin quits working (leaving you with ugly short codes in your post) or all of the above, you can add the following steps as a quick work-around.

Input the shortcode as above, click on the “Preview” button in WordPress’s Publish meta box which will open a new window and let you view your post.

Copy the preview of the annotations you’d like to keep in your post and paste them over your shortcode in the Visual editor tab on your draft post. (This will maintain the simple HTML formatting tags, which you can also edit or supplement if you like.)

I also strip out the additional unnecessary data from Hypothesis Aggregator about the article it’s from as well as the line about who created the annotation which isn’t necessary as my post will implicitly have that data. Depending on how you make your post (i.e. not using the Post Kinds Plugin), you may want to keep it.

As Greg McVerry kindly points out, Jon Udell has created a simple web-tool for inputting a few bits of data about a set of annotations to export them variously in HTML, CSV, or JSON format. If you’re not a developer and don’t want to fuss with Hypothesis’ API, this is also a reasonably solid method of quickly exporting subsections of your annotations and cutting and pasting them onto your website. It does export a lot more data that one might want for their site and could require some additional clean up, particularly in HTML format.

Perhaps with some elbow grease and coding skill, sometime in the future, we’ll have a simple way to implement a POSSE workflow that will allow you to post your annotations to your own website and syndicate them to services like Hypothesis. In the erstwhile, hopefully this will help close a little of the data gap for those using their websites as their commonplace books or digital notebooks.

Editor's note:This post was originally published on BoffoSocko.com

[seecantrill]

Annotation and Connecting Our Learning

This is my third year of teaching ED677 at Arcadia University, a course titled “Seeking Equity in Connected Learning and Teaching.” There always so much to record, document and share along the way. Always true in the dynamics of teaching; always challenging to accurately capture.

Let me start with some thoughts about the power of annotation so far this semester.

Over the years, I have been learning from educators I work with about the power of annotation and new tools that support online annotation/social reading. These tools have included Google, Vialogues, Now Comment, Soundcloud, Genius and Hypothes.is. I have dabbled here and there, jumping into conversations that have been organized or creating a new thread in one of the various tools or forums myself. I’ve also been fascinated by the power of annotation historically and across disciplines, worked with Hypothes.is on projects like Letters to the Next President 2.0, and am interested in the power of projects like Climate Feedback to support scientific accuracy and reporting.

It wasn’t until this semester though that I focused on the ways that participants in ED677 were encouraged to annotate -- and the results, so far, have been noticeable and encouraging.

I started this process really during the first week when I asked the participants in my course, who are both inservice and pre-service teachers, to use the commenting feature of Google docs to highlight things they noticed and that raised questions for them on the ED677 Spring 2017 syllabus. Publicly visible, the comments show me where the group’s interests and questions are within the framework that I have created for the semester. I have also found that reviewing the syllabus carefully like this created a shared understanding of ED677 that, previously, has required many individual conversations to support as the semester got started. The structure of ED677 is fairly different than other courses and requires the individual participants to set their own timing and priorities and therefore it is important that everyone reads and understands the goals and resources of the course right at the beginning.

The next step we took with annotation came during our second week together. After we get oriented to the course and introduce ourselves to each other, I encourage us in week 2 to move into thinking about the larger context of this course, ie. the rapidly changing technological landscape in which we are thinking about learning together. In the past I asked everyone to engage in recent work by John Seely Brown and the authors of the Connected Learning Design and Research Agenda while also reading the first chapter of School and Society by John Dewey, a publication of lectures he gave at the turn of the 20th century.

In the past, the Dewey piece has got short shrift from participants in my class and I kept wondering about it -- maybe it was less interesting or relevant than I think it is when I read it. So I read it again. No, I decided -- this article, despite a few archaic words and gendered descriptions, is still interesting and relevant today, 100+ years later. And JSB, in his 2012 keynote, directly challenges us to tackle Dewey’s ideas in the context of flowing on the tides of change today. So I decided to try something new this time around, and I turned to my colleagues Joe Dillon and Remi Kalir who were working on a fascinating project called Marginal Syllabus and asked them if we, as ED677, could join in.

Why “marginal”? The creators explain:

our conversations will engage authors and their texts, topics, and perspectives that may be considered marginal to dominant conventions of schooling and education.

conversations associated with The Marginal Syllabus will occur in the margins of online texts through practices of open web annotation.

They then write that “The Marginal Syllabus is collaborative and emergent attempt to create a new sociotechnical genre of educator professional development in which authors and readers, the practices of amplified marginalia, and learning technologies begin (re)marking on equity and education.”

Perfect, I thought. Here at ED677, we are all about new sociotechnical genres to support equity in learning and teaching, so I decided to barge my way in. And not only were Joe and Remi welcoming, they seemed excited and promptly made a space for Dewey’s 1907 text and created an annotation “flash mob” event to support us during that week. Amazing. Going back to ED677 then, my only job then was to invite the class. I did so by introducing them to the project, adding related scaffolding between the texts and supportive approaches (for those who might be new to this or nervous about doing the work publicly), and an opening annotation of my own, which read:

In 2012 I heard John Seely Brown give a keynote at the DML Conference where he said that "perhaps John Dewey (and Marie Montessori) were 75 years ahead of their time" when driving models of education that brought the learner into the flow of what they were learning. Maybe, he posits, "their intuition was right but their toolset was wrong." See: http://dmlcentral.net/the-global-one-room-schoolhouse-john-seely-brown/

I was so excited by this thought and have been wondering it ever since. So how might we do what JSB does in his speech and recast some of John Dewey's work here from 1907 in today's networked age?

The results of this experiences, and the differences in the ways we engaged with this older text, were significant. Not only did almost all of ED677 participate and contribute their significant knowledge as teachers and learners into the mix, but their reflections that week posted to their own blogs were filled with connections they made between Dewey’s work, John Seely Brown’s, and the research report/agenda for Connected Learning. They also quickly made important connections between to their own work and with their classmates through their shared blog posts. Eric, a graduate student in education aspiring to teach math, wrote “I feel like a conspiracy theorist… I’m finding connections everywhere!”

I should mention that ED677 is an entirely online course taught in the open, meaning that all of the activities and readings we engage in, and our writing and reflections about this work, are posted to our own blogs which are then aggregated together at our shared blog (Domain of One’s Own inspired). While we meet via video every other week, I have found that it always takes time to develop a sense of ourselves as a community and that this sense develops as our comfort with being a community of educational bloggers begins to grow. What I think I am noticing this time around, however, is that this kind of online social reading activity seems to have been a significant jump-start to that sense of belonging to a community, both within the course and beyond it. And since the goal of this course is to be connected learners ourselves, as educators, in order to support equitable access to connected learning and teaching with the youth we work with, this jump-start could have significant implications.

This week we are diving back into annotation as a way to explore the idea of “wobble” as in Pose/Wobble/Flow, and thinking about that idea within communities of other connected educators. I look forward to seeing where this all brings us.

[chrisaldrich]

Hypothes.is and the IndieWeb

Last night I saw two great little articles about Hypothes.is, a web-based annotation engine, written by a proponent of the IndieWeb:

Hypothes.is as a public research notebook

Hypothes.is Aggregator ― a WordPress plugin

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:

Hypothes.is as a public research notebook

No highlighted text in this annotation.

From an indieweb perspective, it's probably far easier, more productive, and better interface if hypothes.is both accepted the webmention protocol as well as sending webmentions. This way one could post their comments (highlights may be slightly tougher) directly to their Known (or other site) and the webmention protocol could handle the posting to hypothes.is. Similarly when one annotates a page, hypothes.is could webmention the page, so the post author/site admin would be aware that the page was marked up. As an "example": http://stream.boffosocko.com/2016/from-an-indieweb-perspective-its-probably-far-easier-more-productive Curated by chrisaldrich.

Preventing abuse – Hypothesis

appreciate your help

I think that a major part of improving the issue of abuse and providing consent is building in notifications so that website owners will at least be aware that their site is being marked up, highlighted, annotated, and commented on in other locations or by other platforms. Then the site owner at least has the knowledge of what's happening and can then be potentially provided with information and tools to allow/disallow such interactions, particularly if they can block individual bad actors, but still support positive additions, thought, and communication. Ideally this blocking wouldn't occur site wide, which many may be tempted to do now as a knee-jerk reaction to recent events, but would be fine grained enough to filter out the worst offenders. Toward the end of notifications to site owners, it would be great if any annotating activity would trigger trackbacks, pingbacks, or the relatively newer and better webmention protocol of the WW3C out of the http://IndieWebCamp.com movement. Then site owners would at least have notifications about what is happening on their site that might otherwise be invisible to them. Perhaps there's a way to further implement filters or tools (a la Akismet on platforms like WordPress) that allow site users to mark materials as spam, abusive, or other so that they are then potentially moved from "public" facing to "private" so that the original highlighter can still see their notes, but that the platform isn't allowing the person's own website to act as a platform to give reach to bad actors. Further some site owners might appreciate graded filters (G, PG, PG-13, R, X) so that users or even parents can filter what they're willing to see. Consider also annotations on narrative forms that might be posted as spoilers--how can these be guarded against? (Possibly with CSS and a spoiler tag?) Options can be built into the platform itself as well as allowing server-side options for truly hard cases. My coding skills are rustier than I wish they were, but I'm available to help/consult if needed. Curated by chrisaldrich.

[borismann]

Jon Udell experiments with cross posting between Medium and his own blog, and using Hypothes.is for portable annotations.

It looks like domain mapping is coming to Medium (see 500ish.com), which will make me happier about using it.

[kubikbudapest]

Hypothes.is x KUBIK

For English version please scroll down

Az amerikai Hypothes.is csapatnak az elmúlt pár napban a KUBIK volt a főhadiszállása!

Ez a fiatal és kiváló non-profit szervezet két magyar taggal is büszkélkedhet.

Nagyon izgalmas fejlesztésen dolgoznak: Böngésző kiegészítőjükkel új szintre emelték a netezést, amivel a jegyzetelés, kommentelés és hivatkozások hozzáadása válik elérhetővé bármelyik weboldalon. Csekkoljátok a honlapjukat: https://hypothes.is/

***

In the last couple of days KUBIK had the pleasure to welcome the American Hypothes.is team.

This young and exceptional non-profit organization has two Hungarian members.

They working on a really exciting web innovation:

With their browser extension they created a whole new level community peer-review on the web which enables us to annotate, comment, reference on any webpage for ourselves or for the public good.

Check out their page: https://hypothes.is/

[gov]

Dan Whaley, speaking now at #PDF13, is the founder of Hypothes.is, a non-profit platform for organizing and peer-reviewing the world's knowledge.

Hypothes.is will be a distributed, open-source platform for the collaborative evaluation of information. It will enable sentence-level critique of written words combined with a sophisticated yet easy-to-use model of community peer-review. It will work as an overlay on top of any stable content, including news, blogs, scientific articles, books, terms of service, ballot initiatives, legislation and regulations, software code and more-without requiring participation of the underlying site.

Pretty cool!

[things-from-places]

One of my favorite teachers from high school once said that "the best decision is an informed one." Dan Whaley and his team at Hypothes.is, along with countless experts and other valuable contributors from different countries and educational/informational institutions, are hoping to take us to the next level of information sourcing via an open-source, not-for-profit platform that allows anyone to annote anything, anywhere (on the web) for at minimum, a more organized, more easily digestible commenting system for information hunters (journalists, researchers, redditors, etc.) and at maximum a whole new way to consume, process, analyze and make something GREAT out of that highest of all super powers: information.