 My name is Nate Angel. I'm the director of marketing at Hypothesis. I'm joined here by my colleague Heather Staines and she'll introduce herself in just a second. I just wanted to give you guys a couple of pointers on housekeeping. We're using this Zoom platform to give this webinar and it has two features that allow you to communicate with us. One of them is the chat feature. As you can see probably in a toolbar at the bottom of your screen where it says chat, Heather's already been doing a little bit of chat inside the window there as have some others. We'll be posting some links that we talk about from the webinar into that chat. There's also a Q&A button at the bottom that you can use as you move along. As we move along through the webinar you can enter any questions and answers that you would like to see us address. We should have plenty of time to just talk amongst ourselves after we do a short presentation at the beginning so there will be plenty of time for that. We are recording this and we will post it and send you a link to it to both the slides and the recording after the show. It takes about a couple of hours to get that all put together. Without further ado I'm going to go ahead and start sharing my screen again with the beautiful mountains that Apple's provided for us. And we will get started. Heather, do you want to introduce yourself? Sure. Hi, I'm Heather Steins, the Director of Partnerships for Hypothesis. I'm happy to have so many of you join us for today. Thanks for kicking us off, Nate. First I want to give you a little overview of what we're going to be talking about today. Nate, do you want to advance the slides? Great. First we're going to give you a little intro about hypothesis and how it works. Then we'll go into a little bit more detail from an implementation standpoint on how you can integrate hypothesis on your site yourself. Then for those of you who may not have a big technical team or may not have the time, we'll go ahead and talk about how we can work to do a supported implementation. And then as Nate said, we should have plenty of time for per Q&A at the end. I'm going to hand over to Nate to give the first bit and I'll talk to you in just a bit. Thanks, Heather. One of the things that's a little bit different about hypothesis is how we are as an organization. We're a non-profit organization and we formed on that way on purpose so that we could be an independent entity that was really dedicated to the mission of moving annotation forward across all the different domains, including especially the domain of publishing and scholarly publishing. We've been funded to date by grants from generous sponsors like you see on the slide. And also key to this stature that we have, the status that we have as a non-profit organization, is that we work in an open source model so that all the technology that we write, we publish openly in a repository. And for anyone who leans in a more technical direction, I invite you to visit the developers page, which we will share the link in the chat later. On our website, which contains all the information that you would want to learn about in order to get more heavily involved with the open technology itself. Another key aspect to that open strategy is the degree to which we are integrated with the new W3C web standard for annotation that was published in just about a year ago. Now, coming up, we're coming up in the one-year anniversary, we should have a birthday party for the web standard. Hypothesis was one of the participants in helping to make this web standard happen. And we're very committed to maintaining close alignment with the standard ourselves so that we can all live in a world where any annotation solution that you choose conforms to this standard and then annotations can be fully interoperable across the whole corpus of human knowledge. Hopefully, at least that's the goal and so that people don't get stuck in proprietary silos where information is kind of hidden away. Just a little bit more on hypothesis and where we are these days. So, you know, compiling numbers through November last year, we're up to just about 2.4 million annotations. We may hit 2.5 today. I know that Heather's anxiously watching the numbers tick by so that could happen any minute now. And you can see from this chart that there's kind of a range of different modes now that people are annotating in both public and private. And so the blue and the bottom are people that are just taking notes for themselves in a private mode. The green is in the public where they're annotating fully publicly. And then the capability that we have out in the wild right now is the idea of using private groups where groups of people will come together and collaborate. We'll talk about that more. And so you see people who are both sharing with their private group, the other people in their group, and or privately inside those groups as well. And so you can see the kind of how annotation use with hypothesis has sort of increased over time showing a healthy growth rate. And we also are starting to see annotation now around the world. It's heavily centered in English-speaking countries on the upper left, as you can see here, including the United States and the UK. But we see this pretty concentrated activity in smaller pieces now and countries all over the world. And so this is the same timeframe as that last graph. And it gives you the top 30 countries where there have been annotation sessions making those annotations that we saw in the graph before. So we want to talk now just a little bit to give you an overview of how hypothesis works. And so trying to understand just sort of the basic functionality so that you walk into the idea of how to implement the tool with an understanding of the capabilities. And so one of the first things to understand about the way hypothesis is architected is the idea that it is offering multiple layers of annotation. And so going back to when I was talking about the idea of there being a public layer and then private groups on top of that, that's this idea of layers of annotation, right? And so you can kind of imagine it as almost putting a transparency over some sort of web document, right? Whether that's a web page or a PDF or an EPUB. And that first layer of transparency might be the public groups layer. However, if you'd like to switch to a view of seeing only a private group, you can use hypothesis to switch that view and bring up a layer that just shows the annotations in your group of collaborators that you've organized yourselves. We're rolling out a couple of other kinds of group configurations now that Heather will be talking to you about in a minute. This idea of layers enables hypothesis to bring some kind of order to the different modes in which one might want to annotate. And so that publishers can have more control over the kinds of layers that they want to expose on their sites. And so they might have both that public layer and then there might be private groups annotating in their own layers on top of that information. And then the publisher might also be exposing other public layers that contain notes or authorial interventions so forth. The basic underlying architecture of hypothesis is based on a kind of classic client service server model where the client is the tool that you use or people use to annotate. And so it's based in the browser. And it's the tool that allows you to highlight text once you have it open in the browser and then annotate on it, add tags, save it, you know, log in, log out, reply, share, all the kinds of things that you would do as human being interacting with the actual annotations. When you make an annotation, however, those are saved in the server, in the server environment. And another key part of hypothesis open standard space interoperable philosophy is the idea that there won't necessarily only be one server that might be holding the annotations of the world. So hypothesis maintains and runs like kind of the default reference server infrastructure for hypothesis annotation. But there are other people around the world who are also running their own servers that are based on the same underlying open source technology. So when you're actually engaged in annotation itself, there's a couple different ways that you as a user or your users, if you're a publisher, could get their hands on the client, they would get access to the client. And the one that we're going to be really focused on today is the idea of you as a publisher embedding that client in your website or publishing platform, so that the users come to your publication and the client is already there activated waiting for them to start to use it. They may not have an account and an identity yet, but they would at least be able to read any public annotations that were exposed. And they wouldn't need to take any technical steps in order to access the client and start using it. There's a couple of other ways though that that client can be sort of delivered to users these days. And the other one that most people are using widely now is in the browser plugin mode. So that's the case where the user equips themselves with a client in their browser. And so they might use the Chrome plugin, which is the most mature version of the browser plugins right now. And so that would mean that any website or web page that they visit with their Chrome browser when they have the hypothesis plugin enabled, they would have the annotation capability built in. If they happen to visit a publisher's web page who also has the client embedded hypothesis handles that kind of seamlessly behind networks and understands that there's already a client embedded and delivers that instead of the user's browser plugin. And then finally, there's a way to share links from hypothesis. So if you are annotating in hypothesis, make annotations, and then want to share a link possibly with people who don't yet have haven't enabled themselves with the browser plugin, or maybe you're annotating on a page that doesn't have the embedded client, you can share a link that will redirect every user to a version of that page that has the client injected into it and delivered so that they can start annotating without pretty quick pre equipping themselves as well. We are focused today on the idea of how easy it is to actually embed the client in your website. So we'll focus on that. And so at this point, I'm going to hand the reins back over to Heather, and she's going to talk to you about some of the integration options. Great. Thanks, Nate. So first, we'll talk about integrating the free version of hypothesis. As Nate mentioned, we're open source. So you can embed hypothesis in your site or your platform. You don't even have to tell us. We like it if you do because we'd love to make an announcement and we even love to offer you free training for folks and resource access and the like. The basic implementation passes very straightforward. It includes all the primary annotation capabilities that are listed. You can create all those different types of annotations that Nate mentioned, create deep links, groups, and all the like. Go ahead, Nate. Sorry. Nate's driving the slides for me today. Not very well. There we go. Thanks. It's really straightforward. I am not a technical person, but I have been told by a number of people that it is. It's basically a line of JavaScript that you can put on your site. If you also have a lot of information in PDFs, there's some additional things you can do to wrap those PDFs in hypothesis. I've been told by some folks with some excitement that it took them about 30 minutes to install. And then I've mentioned that number to other people and they started laughing and said that they did it in three. So I'd love if someone wants to actually screen capture implementing hypothesis and we'd love to kind of share out to prove how easy that is. We also have a number of plugins for embedding hypothesis. Before we started working with publishers a little while back, most of our activity was in the researcher and education space. So the Canvas integration is really important to a lot of our users. We're recently launching a pilot with Canvas. And we've got a number of schools that are using within the learning management system hypothesis for collaboration assignments for close readings. And that's pretty exciting to watch that develop. We also integrate quite readily with a lot of the other open source platforms out there like OGS, for example. If you have a blog or some sort of social activity on your site where you have WordPress, for example, it's really easy to install the plug in there. And because we want hypothesis to be available to publishers regardless of their size or or native technical capability, we wanted to ensure that if you're hosted, you can easily get hypothesis as well. So we spent a lot of time last year getting agreements in place and doing a lot of explorations with technical folks. So we're happy to say we've got great coverage with even a few more platform hosts launching soon. And there's a link that will be available in the slides to show you more ways to integrate hypothesis. There's a number of configurations you can do to customize hypothesis to fit your site. This is just an example. Don't let your eyes glaze over for how to turn highlights on and off by default. And we're including a list to all the configuration options as well as part of the documentation. As Nate mentioned, our goal is really to have a universal client that can be used anywhere on the web on any type of content for any type of annotation regardless of your intention to be able to interact with and share notes that are made on content. Nate mentioned the different annotation layers. So we wanted to show you just a little bit of a screen grab of how a publisher may want to display multiple annotation layers. Our first two layer publisher is going to be launching in a bit. That's with Johns Hopkins University Press. And they wanted, for example, a general discussion layer that anyone could join, but also a layer that's restricted to notes from the author and interaction in that layer with invited critiquers. You could also have a layer for review summaries or even open peer review. You can have as many layers as you like. And I'll talk a little bit more about that in just a second. Every user in every group gets what we refer to as an annotation dashboard or an activity page. You can use it to see what other annotations have been made. You can explore things that have been created by other users. You can filter by tags. You can search by a number of different facets. And also, if you take off all your filters, you have access to all the annotations that have been made publicly across hypothesis, and you can search those as well. This is a quick screenshot of my activity page. These activity pages can be set narrowly or broadly. You might have one per book, one per journal title. You could put in a collection of journals with a similar subject area, or you could have them be domain-wide. And it's also important to us that our users who get hypothesis accounts should be able to annotate anywhere on the web. In addition to HTML, PDF, and EPUB, you can also annotate a variety of data that can be displayed in the browser. And one of the things to note, if you are a publisher that has your content in multiple locations, like, for example, on your own platform, but also in PubMed Central, public annotations that are made on your platform would typically be visible in the public PubMed Central version as well to other folks who are bringing the plug in there. Similarly, if you work with aggregators, as many of you do, we're talking with ProQuest and EBSCO and the like to make sure that, in Ovid, to make sure that annotations can be made visible on their sites as well. There's a number of different ways we can do this equivalent between the documents, and we're happy to tell you more about that. Some of them are listed here on the screen. We have a very robust hypothesis API, and you can do quite a number of things with it. You can use it, of course, to read and search for annotations. It can be used to create, update and delete, but interestingly, we have a lot of requests for folks who might want to use it for text and data mining purposes, and also to repurpose on other sites of their website. For example, you could have interesting annotations, display in a widget on your marketing page. You could have annotations that are public feed into your Twitter stream. There's a number of things that you can do there, and again, there will be a list to the full documentation. We feel really strongly that data should be in the hands of the folks who the publishers and the folks who create it. Being able to export your annotations, being able to make your annotations portable, that's really important to us. For some publishers, the free version of hypothesis annotating in the public layer may not be enough, and we recognize that. A lot of publishers view annotations that might be visible by default on top of their content as part of their content. We do offer supported and customized implementation. We've got some questions, and we'll just get to those I think at the end is probably best. If you don't have a technical team or you really don't want to be bothered to implement yourself, we're happy to assist you with that. We have a simple document-based pricing that offers a volume discount for the more documents that you deploy across. We use a number of documents published per year as a proxy for size. You can start with a small amount of content and expand over time. We also have some journal-based pricing that's available for you. We can connect up if you have your own accounts on your platform so that there's no need for your users to create separate hypothesis accounts or log in twice. That's something we're happy to tell you more about. We offer the creation of the publisher-branded and moderated groups that Nate mentioned. There are a number of customizations you can do to your UI to make it look like the annotation client fits readily with your page. We do offer a really robust program to ensure that you have a successful rollout of annotations including training, in-house training, training for folks like editorial board members, and even training for end users. We'll work with you to help promote the fact that annotation capability is available on your site. We provide full customer support and also open source maintenance. Just a little bit more to tell you on publisher groups. These are completely configurable. The publisher gets to decide who can read the annotations and who can create them. You can, for example, have groups that are publicly readable but can only have annotations created by a limited number of folks who the publisher has designated. We're launching soon with American Diabetes Association, for example, who wants to use hypothesis to do updates on their annual standards of care issue. Of course, they only want to make sure that qualified folks are annotating on top of that important medical content. We're working with them on that group. The Johns Hopkins example that I mentioned earlier can be limited just to authors. But we also offer the capability of groups that are publicly visible and anyone can join, either through your account or through hypothesis accounts. It's completely flexible that way. You can deploy over just a certain type of article, over just one issue, as I mentioned, over just one title. Moderation is available via folks that you've designated in-house, and there are a number of default visibility options. You can, for example, have a button that shows that annotation is possible on the platform or a call to action like annotate me, different things like that. I mentioned UI customization. There's a number of things that you can do now. You can change the colors. You can alter the borders. The typefaces are configurable. You can control the width of the sidebar. It's not obscuring important content on your site. You can direct whether highlights are on or off by default. We can employ some pop-ups, if you like, for the first time that users visit when you have annotation that give them a little call to call to action. I'm going to hand it back over to Nate to talk a little bit about more about what we offer. When we work closely with a publisher who's implementing hypothesis on this paid supported version, one of the first things that we want to make sure is that the publisher and hypothesis have a clear idea of what's actually going to constitute success for the publisher. What are they trying to accomplish with annotation? There may be cases like the American Diabetes Association that Heather just mentioned, where they're primarily looking to add additional published information on top of a published work. The annotation experience for their readers is largely going to be a reading experience. They're not primarily looking for their readers to annotate. They're looking for their readers to find ancillary information addenda and so forth to the published text. On the complete other end of the spectrum, there's the idea of engaging your readers in deeper conversation using annotation as a way to bring them more value to visiting the document or publication record. One of the things that we like to do at the beginning is work with the publisher to define what it is that they're looking to accomplish through annotation, to provide more engagement, publish more material, provide an outlet for their authors and editors to communicate. There may be pre-publication workflows that are enabled, different kinds of things like that. By establishing that early on, we can work together to figure out measurements so that we can then evaluate whether annotation is actually delivering on the goals that the publisher might have. Then as Heather mentioned, follow that up with the idea of training so there may be internal folks on the editorial team that need to be highly trained so that they can annotate. There may be groups of authors or invited experts that might have training, so there might be something like a hosted webinar between the publisher where we are invited to provide additional guidance to some of their star annotators, if you will. Another thing that we like to do then is help the publishers think about the best way to organize events and evangelizing activities so that they can foster additional annotation on their site. There's a whole variety of different kinds of ways that that can happen. One of the things that we do is help the publisher think through and orchestrate the best way to get their community involved in the annotation process. We also are very interested in the idea of promoting the publisher's innovations and also promoting the idea that interoperable standards-based annotation is starting to become a key part of the scholarly toolchain. We work closely with publishers to coordinate promotion around their use of annotation on their platform. Heather mentioned the combination of user-based support and open-source maintenance that hypothesis enacts. When we're working with a partner who's contributing to the ongoing sustainability of hypothesis, we are providing that full end user, both tier one and tier two technical support. We have help desk functionality that can answer any question from, you know, I lost my password and I can't log in all the way up to the deeper technical integration questions. Then the open-source maintenance is a concept that people may not be familiar with. Because we're not a commercial entity, hypothesis spends most of its resources, frankly, on developing and stewarding the open-source technologies that make all of this possible. One of the purposes of the partnership is to have entities like publishers like yourselves that are making use of this open standards-based interoperable annotation and making contributions to its ongoing welfare and maintenance. Part of what the fees that we collect from publishers that we work with in this way go to is this idea of open-source maintenance. Not only the development and stewardship of the code base and the reference implementation, often we're also hosting the server for publishers, although with larger customers, sometimes they want to run their own implementation and we are also involved with that whether we're hosting it or just advising them on their hosting. Then there's also the work that we do in the various communities that are sort of surround the ecosystem of annotation. That's the standard space work that continues that W3C, in fact, Heather was just giving a webinar yesterday with Rob Sanderson from the John Paul Getty Trust who was one of the key architects of the W3Web standards and there's still work to be done there. There's other kind of components of the standards that need to be advanced and we're involved in that as well. Then Heather mentioned the annotating all knowledge coalition, which is a group that primarily made up of publishers and platforms and people engaged in scholarship and research tools that are organized around the idea of advancing annotation, not just hypothesis, but all the forms of annotation that might be taking place in the world. Then I can't help but make a plug here for the I Annotate conference. We just locked in the dates for next year, so I Annotate 2018 will be in San Francisco on the 6th and 7th of June in 2018. We'll be opening up both the registration and the call for presentations to that in the not too distant future, but you might want to hold the date now. The 6th and 7th of June 2018 in San Francisco will be the next I Annotate conference and that's a really unique gathering of about 150 folks who come together who are just really primarily focused on annotation and it's the activities that happen around annotation in not only the fields of publishing and scholarly publishing, but also journalism and fact-checking, education, teaching and learning and research and scholarship more generally. It's a very vibrant, interesting, and yet still intimate experience that I highly recommend. We've come to the end of our, we've come to the end of our prepared remarks here and we're right on the nose at 8.30 Pacific time and maybe different for you. And so I'm going to actually take down the slides and we can start addressing questions. So we have one queue doc that we'll get to from Stephen and then anybody else who's interested in asking questions, please, you can put them either in the chat or in the question and answer tool and we'll be happy to address them. Last time we talked with folks for over half an hour about different scenarios for publication use cases and it was a really vibrant and interesting discussion. So Heather, maybe you have an answer to this one. I don't know off the top of my head. I'd have to try it. But Stephen has asked if you can annotate Google Books. Yeah, I've not actually annotated Google Books. Some of the questions that come into my mind. The work we did with New York University Press and Libraries was to enable the capability of annotating on EPUBs and part of that process was to be able to inject hypothesis into a frame. So I do know on the Google Book pages a lot of times the pages that you can preview are in a frame and so I'm not sure if that work that we did for EPUB implementation has carried over there yet. So it's something that I will take back to the team. One of the challenges when you're talking about PDFs like that, some of the older PDFs may be images rather than actually text that's selectable. So for image-based PDFs, if you can view them in your browser, you can make a page-level annotation. For example, if you're not able to go ahead and select a text and we're working with some projects to refine that so that that will be possible. But we will go and check it out and get back to you. If there's not the capability out of the box to implement annotation on Google Books, we can go to our open source community page. There's a number of folks who've created additional extensions and the like and it's quite likely someone has a workaround that enables you to do that. Yeah, I was just actually quickly trying it behind the scenes while Heather was talking and the first book that I came up with was actually one of those cases where it was an image-based PDF scan. We don't have image-based annotation built into the experience yet. And so until there's OCR text to annotate, that would block that kind of annotation. Have to try and experiment with another book that had accessible text that was indeed not just an image. So another question from Brian. How has publishers worked changing as a function of annotation? Are they approaching content creation or updating in a new way? This is probably another good one for Heather to address. Yeah, so in many cases if there are critical additions, annotations by the author or by other invited experts may well be judged as part of the content. So we've actually just this week been talking to publishers about what the best way might be to depict official annotations made as part of the book, even if they don't want to have an entirely separate layer for that. So that's one part of the discussion. Another really interesting thing that's made possible by the technology behind hypothesis linking is the ability for you to use linked data or entity extraction. So for example, 125 journals in the neuroscience space use these things called RRIDs, research resource identifiers. And those are really critical for reproducibility purposes, if you need to know exactly which stem cell line was used or where a reagent was purchased. These RRIDs are typed into the papers and they resolve to external databases. A team at University of California San Diego created an account called Cybot that actually looks for these RRIDs when you open up a HTML or PDF of paper and then displays the information from the external database along the side in the form of annotation cards. So you don't need to navigate away to find out the information that lives behind that. So we're talking to a number of other folks who have different types of identifiers like celestial data in their content that they'd love to put more information. And I've also talked to publishers who are interested in using annotation to give pointers to readers on how to best use their platform. So it doesn't have to necessarily be publishers changing how they view their content. It could be how publishers changing how they view the entire user experience as a result that they now have another communication tool that's possible to use with readers. We've also got a number of publishers who are using annotation in peer review and with the movement towards different types of open peer review. This is a really interesting example. E-Journal Press has integrated hypothesis into their manuscript submission platform and I think it's available now to all publishers who use E-Journal Press and we're in conversations with all the other big producers so we can figure out what the best way would be to introduce them. So really, really interesting developments there on the on the publisher side. And another question from Eric who's noticed that there was a moderation capability and he was wondering if we could talk a little bit more about how the moderation capability works. Do you want to take that one too? Sure. So I should say yeah you mentioned the student example and yeah students and some academics are even notorious for having conversations going to get off track or trolling each other. The way that hypothesis has been made available largely through researchers bringing it themselves to the site. We haven't seen a lot of abuse to date, a handful of cases. Most of the examples where students are involved, these are private groups that are joinable by the students. The instructor whoever has created the group can provide a moderator function. There are flags in the private groups just as there are in the public layer. You can indicate if you find an annotation to be objectionable. We at Hypothesis do monitor those complaints on the public layer and investigate and take care of them. For the publisher groups as I mentioned there are similar flags that can go to a dashboard that the moderator can use to decide whether an annotation needs to be hidden or even some more serious action taken against a person who's in abuse. We're also working on some other types of moderation that folks are interested in. There are some publishers who would like to see every single annotation before it posts so that something will be developing or to require, for example, that anyone have an orchid before they can create annotations. As the service scales we're also looking at things like sentiment analysis and user behavior so we could pre-screen or get some early warning systems in place if someone is undertaking some abusive behavior. Great and I also see that Andrew has asked if readers can annotate on their phones and so I'll take a stab at that and Heather you can chime in too if you want. So we've definitely optimized for browser, you know, larger device browser based annotation at this point and so the best experience you can have is definitely in a full-blown computer. Annotation on tablets is definitely possible and some of it really comes down to the amount of screen space that's available and tablets obviously having more screen space are better equipped to handle that. I have annotated on my iPhone. It's not an entirely seamless experience to be sure and so one of the things that we have on our horizon here and I can't give an exact time frame but is to better optimize the mobile experience because clearly that's important to a lot of different use cases. So right now I would say it's possible but I wouldn't necessarily recommend it and so if mobile access and mobile annotation is one of your primary focuses you might want to think about an implementation that that held off until there was further development there. Yeah and I would just add that I do annotate on my phone and it's really kind of user preference. You know some of us don't like to answer emails on our phone because it's cumbersome to type them out and there's other types of things that we don't like to do on our phone also depends on your phone. I'm not one of the folks who has a giant phone. What I typically do with hypothesis of my phone is I use it to make just a few annotations and then later on I go and a tag and then I go back to my activity page later on to review the article. So I use it a little bit more on the long lines of a bookmarking capability but you know it's pretty straightforward and again it depends on your tolerance for screens. And the other thing there is that of course if we go back to the slide where I was mentioning the different ways someone can get to the client itself if you visit a website or platform that has the client embedded then of course your phone would be capable of delivering it as well. Or if you use one of the links to a site that doesn't have the client embedded but the link injects the client into the experience then that could also work on the phone but there isn't a plug-in for your phone-based browsers that allows you to carry it with you wherever you go on your phone. So that's another another aspect to the phone experience. And then great Andrew let us know if there are some other aspects that you wanted us to answer. And so Jen has asked Heather she says that you mentioned tagging and so she's wondering if you can tag users in a group. You know Jen it might be interesting if you could also provide a little more context for what kind of purpose you would see that serving that I'll let Heather answer. If you're talking about kind of the equivalent of an at mention in an annotation you can't do that at this time. But what you can do from the group dashboard page that I mentioned before is you can see all the members in a group and what they've annotated and you can you know issue or apply to them. Different types of notifications are some of the frequently asked questions and you know in addition to notifications around replies and the like we're developing a whole suite of different notifications and you know a tagging a user at mention of a user is frequently requested. Again you know because it's an open source community effort it may be likely if that's an essential for you that you can take a look at our developer and community Slack channels for example and someone may have created an extension or a custom edition that will do that at this time. And just while Heather was talking there I shared my screen and brought up a view of my user dashboard and so this is the context where I'm looking at my user dashboard while I'm logged in as myself so you can see here that I am logged into hypothesis as myself. And so what that means is I'm looking at this dashboard with it filtered to look at only annotations that I have authored which is what this little faceted search box means up here in the upper left. If I pulled that out then I would be looking at every annotation that I had access to view which would include all the public annotations and any annotations that I had made or made privately or made in private groups that I belong to. So one can use this dashboard functionality to sort of filter by user by tag which again would be annotations that are that are tagged with certain tags by URL or by group. I see Jen's put a little bit more information so Nate if you want to go back to your profile page to the right side there's the tag cloud that was visible so that shows all the tags that Nate has added as he's been reading articles and he can add those to his filter at the top and you can filter by tags that may have been used. Right now you know when you're creating an annotation and you know we'll I think our next webinar will probably be a little bit more from a researcher standpoint and we have a video on our website in five minutes where I show how researchers create annotations and make tags so that may be something you want to take a look at publisher publisher page. We get a lot of questions about whether you can assign a predefined tag set. The peer review implementation that I mentioned that eJournal Pressed did they did want to have certain tags that reviewers could select so there is a capability to connect hypothesis up to existing ontologies. If someone wants to do an experience around our experiment around that we'd be happy to work with you to kind of pull that together so either one is possible and it just provides you know a little bit more information if you're a heavy annotator like I am I think I'm upwards of 26,000 annotations at this point. I can tag them by the different industry groups that I participate in the sessions I'm presenting in or moderating so I can share them with my panelists and select you know just a tag to filter things here. Nate's showing a project that we do together with TripleAS called Science in the Classrooms. You want to talk a little bit about that Nate? Well when you were bringing up the idea of kind of predefined tags I was thinking of this implementation at TripleAS the Science in the Classroom where they've done something this is a really specific and interesting implementation of annotation I think. Their purpose at Science in the Classroom if you don't know it already is to help people who are just entering the scientific field whether they're students or other folks learn how to read real scientific papers and they realize that it's reading scientific papers it's not an easy task certainly as a humanities person not something that I'm very adept at and so what they've done is you see this learning lens box on the left here is they have what is basically a predefined set of tag categories that you can sort of turn on in the interface in in different layers and so you can see that I had turned on the glossary tab tag and so what that did was highlighted with the different color individual terms that have been highlighted and glossed using annotation so this is basically a way that they can kind of flip on and off different tagged annotations on the same work and so they've done a lot of work to kind of customize the user interface of how the annotations display to the end user on their site but the process that they use to kind of collect and submit the annotations if I'm not mistaken is actually done by grad students who use the normal hypothesis client and a controlled tag vocabulary in order to kind of make these annotations to begin with is that right Heather yes that's correct and then we've we've got a new question from our old buddy steel wag staff hey steel thanks for coming and he says that he knows that we're talking about hypothesis for publishers but he's um has a question about hypothesis for readers and reader apps and so he's wondering if in this use of pocket which is a app that he uses to save and read a lot of HTML based articles it would be possible to integrate hypothesis with the reader application rather than a publisher application that's a great question steel do you I have some thoughts on it Heather do you want to say anything about that um so I'm working you know mostly in the publisher and education bases when you're a startup one of the tricky things is you can't run in a million different directions and do everything that's part of why we depend on the community so I'd say first you know check the community channel and see if someone may have been working on this already we are all in favor of doing integrations when that's possible I'm not familiar with pocket to know whether that's a open source or whether they're working with the standard now that we do have the standard you know as as Nate mentioned the fact that annotations should be able to talk to each other regardless of you know what service or app you know has been used to create them is is key so that's something we you know love to look into when we have a little bit more bandwidth yeah actually I think um steel there's there's been a conversation between folks at hypothesis and specifically the folks at pocket which obviously isn't the only application that one might might use in this way um but it's also one that I make use of and so I welcome your question for that reason and so there's kind of been I think some preliminary conversation about you know what it would look like and if that were that were something that should and could happen um and it's certainly I think technically certainly within the realm of technical feasibility um it's really just about um making sure that uh you know that client experience is embedded in pocket and then there's the secondary question of user identity now that hypothesis is using the industry standard oauth authentication protocol that opens the door to integration with other kinds of kind of identity systems like the one that pocket is using right because you certainly wouldn't want to have the experience where you logged into pocket and then in order to annotate had to log into hypothesis the secondary um has a secondary step and so I think really the ideal integration in that case would be one that took advantage of this new state that hypothesis is in where it could use uh kind of integrate the um user identity and authentication with with a tool like pocket then the other question I think goes to the fact that I think pocket is often used in a mobile environment at least that's how I mostly use it and so um I think that some mobile optimization would really need to happen in order for hypothesis to be effective in that environment but I think it's it's definitely an area that we would like to advance um and as Heather mentioned when she was talking about the universal client part of hypothesis's mission is to um try to make interoperable standard space annotation available everywhere if possible and and definitely part of that strategy is to work toward having annotation embedded in common tools that people use like web browsers um so uh you know we have discussions going with some of the major browsers about bringing annotation into the browser experience is sort of a fundamental capability the same way that search is right now in the browser experience so I can't predict whether you know uh an implementation like pocket or an environment like kindle or something might be the first kind of thing that we see or whether you know it might not be in in a browser environment um as a as a kind of standard capability rather than as a plugin we know how amazon supports open and how they love to share um so maybe we can make a prediction that it might not be kindle at least that um yeah we keep referring to you know these different um conversations and I've mentioned a couple times you know the community um you know one of the fantastic things about being an open source project is um that it's not just us um that are thinking about this and working on this it is a community effort um Nate's pulling up the annotating knowledge page um just a few more words on that it's it's free to join if you're interested it's just for folks who want to explore annotation and you know we sort of say uh if you if you do annotation it should be standards-based and hopefully interoperable so that it um benefits the community um if you are interested in joining me whether it hypothesis and I'd be happy to provide um more information about that we do uh get together um sometimes for phone meetings and sometimes in person um most recently prior to the force meeting in October um back in Berlin um which was a really interesting uh day together with the folks um at cocoa and a lot of other open source projects um one more thing I just want to mention this was uh um you know a a web webinar that's focused on how you know if you want to integrate yourself you know it's straightforward so you know we didn't include you know slides specifically on use cases but I'd love to hear from you you can do a lot of experiments if you're thinking about annotation you can use the free version of hypothesis to try a lot of things out um I've heard from publishers who put together a team within their production department and they included their offshore vendors and they're annotating on top of their xml workflow answering each other questions if it's in the browser you can annotate it um so we thought that was pretty cool um another one of our publishers is doing a big um journal migration within their platform host so they knew that a number of their journal landing pages would need to change as a result so they created a private group and they made notes on the landing pages of what they thought they might need to update um and and they said they found that um you know to be really to really helpful um we also have a group that's doing a project between editorial and sales uh so many of you may have sales colleagues who do campus visits and you may have folks on that campus who are authors and editorial board members and important influencers and so what they're doing is you know tagging um authors by campus so that sales colleagues can go in and you know filter and see who they might want to uh visit or at least uh drop a name too um and and so those are you know you know some of the things that you can try out it's basically a workflow solution um I've heard from some folks who annotate um purchase orders um and invoices rather than keep in emailing them endlessly back and forth to each other so we'd love to hear ideas that you have about how hypotheses might fit into your workflow um so that we can find out more about how that goes yeah we seem to have um run out of questions certainly people you're free to leave at any time of course um we're not holding you here but we're happy to stick around and continue any conversation that anybody might want to have I'm putting some of the links from um the webinar into uh into the chat there um and one of the other things that I want to share is um a link to uh the kind of home page for this webinar itself which is where the um we will post the recording and um also has a series of links in it that are helpful and that will be a good link uh to share uh with colleagues or other folks who you want to introduce uh introduce to the conversation that we had here today okay anybody got other questions they wanted to bring up happy to hear from anyone about anything does anyone else um already have hypothesis integrated into their platform or is thinking now about uh doing that in a in a near time frame we seem to have uh believed everybody into into silence has raised her hand and would you like to type in the chat um or in the question and answer box maybe you accidentally raise your hand I know the the hand raising functionality is some maybe not the most useful uh it's like a few years back that was all the rage uh to do some presentations in second life I know nature had a virtual island in second life called second nature um and librarians were keen on having presentations happen there and your avatars could do all kinds of crazy stuff that you weren't intending make a fool of yourself in a in a virtual world um we do have a comment um from steel that they're using it with press books at um University of Wisconsin at Madison pretty cool Nate do you want to say anything about the some of the integrations for the OER resources that you're involved in yeah well actually we should have steel step up to talk about that um steel has done some really great work there at Madison on integrating annotation into um open source textbooks and other kinds of curricular materials using press books which is a word press based we'll call it content management system that's particularly well suited for publishing um book length and book book organized information and is often used in the OER community um one I think one of the most interesting things that I've seen with with annotation in in the OER space is actually the work that steel's done and so he is has been sort of experimenting with the use of annotation as a way to deliver additional ancillary information so in a way it's a little bit like the science in the classroom example that we were showing before but in this instead it's the a case of being able to deliver more interactive capabilities that are linked to granular places inside a larger curricular piece like a textbook and so you might have something like a a formative or summative exercise you know an assessment a kind of quiz a mini quiz that is linked directly into the um the part of the text that addresses that information so a student can immediately start to practice or get feedback on their understanding of what they've been reading and so steel's been experimenting with uh with uh ways of using the hypothesis annotation layer to deliver new kinds of information and interaction in that annotation layer that aren't just you know human notes on the material it's really interesting stuff i'll put a link uh to um oh steel's already done it for me he's put a link to his own his own blog post which is an excellent read really really interesting and so ann has uh has now um got her question up in the q&a if you see it there heather I do um so uh for those of you who don't have the question box open um ann notes that they're interested in adding hypothesis to their app um where they have a database of college curriculum in the U.S. and it's maintained and currently in academic catalogs can hypothesis um be first step to machine learning um so I mentioned the you know the entity extraction and you know link data aspect around the research resource IDs so one of my questions would be you know around identifiers that might be used I know from another startup in a previous life that um naming of courses and and naming of departments even doesn't have a lot of um consistency um across across colleges um maybe even within colleges I know my husband works and and the translate requirements from one department to another and that can be challenging so I'd want to learn a little bit more um about what you've been finding in terms of the data but because hypothesis um linking technology can point a user uh not just to a URL but to creating a persistent um unique identifier for a sentence or a paragraph or a cell in a file um you know that that could be something where you could point people directly into the resources the hypothesis ABI API may be um as I mentioned for you know text and data mining purposes something that you could run through and and and do uh extractions on but we'd probably need to find out a little bit more about your project uh before we could advise you further and I think um I would and I have been able to do an introduction uh with our education director um Jeremy so I hope you're able to conduct uh connect with him and um I'm happy to talk to you further as well yeah and so um I mean one of the basic things that I just hold in my mind is that you know if information is available through a browser and it is in the format of uh HTML um you know uh textual PDF we'll say or EPUB now um thanks to the collaboration with NYU and Redium um and evident point and others um that there is the possibility to integrate it with with open annotation um so uh there's uh there's quite a bit of room for experiment there and a lot of it would depend on the kind of nuances of whatever your application is how it's organized and how it's presenting information yeah so I see we're coming up on the end of the hour thanks to those of you who um who stuck it out um we will uh as Nate mentioned send you a recording so you can share internally um look for um additional webinars we've got some coming up with some publishing partners and platform partners we're working with um and launching with um so that if you have folks who who didn't um today uh and they want to attend a live webinar there'll be plenty of occasion for them to do that um and I can't stress more you know we enjoy um having you interact with us this way we'd love to hear from you and um don't hesitate to reach out and get in touch