 Great. Just a little bit about what we're going to be covering today. A few slides on how hypothesis works. I know some of you are very familiar with it. A little bit about integrating hypothesis in your platform, what we kind of refer to as supported hypothesis, which includes the group functionality. A quick look at the E-Life integration and a walk through that our designer put together that will show you some of the options when it comes to publisher group. And then as Nate said, we should have some time for Q&A at the end. First, as many of you may already know, hypothesis is a mission driven not for profit. We are open source and we're strong believers in open standards. Some of the names that you see across the bottom of the screen are partners who have generously supported us over the years. We're in the process of a transition, a five year transition to earned income and part of that is working with publishers. We worked for a few years with the W3C to get annotation approved as a web standard, which happened almost exactly a year ago today with an extremely high number of votes. What that will mean is in future versions of web browsers, just like you tell your browser what your default search engine is today, you'll be able to tell your browser which annotation client you're using. And in future, if every annotation client works in accordance with the standard, interaction between annotation clients should be possible in the same way that we can email each other today even though we might use different email clients. We're currently at 2.7 million annotations and counting. We crossed 2.7 million this week. We need to update our graphic there a little bit. You can see here that about a quarter of the annotations have been made that are completely public. Those completely public annotations are contributed to the CrossRough Event Data Project, so they're indexed by Google and Discoverable. A high number of annotations are made as part of collaboration groups, and we're very curious to see as the new groups for publishers rolls out what percentage of annotations might be made in that sort of a forum as well. Just a quick snapshot recently of the different user sessions and where folks are coming in from around the world. Probably not surprisingly, there's a high number of English-language speaking countries represented at the top, the United States, United Kingdom, India, Australia, Canada. But you can see across the board there just with the top 30 that we've got nearly every geographical region in the planet represented and quite a number of languages. So if you go and explore the public-facing annotations and hypothesis, they're quite commonly come across annotations in Chinese, Japanese, Arabic, French, Spanish, Hebrew, and more. Just a few slides on how hypothesis works. We believe in layers of annotation, as I mentioned, built on open standards. What it means is on top of the content and annotations do live in line with the text that the annotator is referring to, you can have multiple conversations going on on that same piece of content. You could have a conversation going on in the public layer. In the private space, Mr. Johnson Science class could be working on a collaboration project together. We have a designated layer that's reserved for experts in the community. For example, the scientists that we work with at Climate Feedback, who fact-checked news articles in regards to climate change. And publishers are also looking at annotation as an additional mechanism to distribute information about content. We'll show a little bit more about that in just a few minutes. The thing that's great about hypothesis is you can annotate anywhere. You can annotate in the major digital formats, HTML, PDF, and EPUB, as well as many kinds of data. And there is equivalent across those formats. So annotations that you make on the HTML would typically appear on the PDF and vice versa. If you are a publisher that has your content on multiple platforms, let's say you work with PubMed Central, for example, or you work with aggregators like ProQuest and EBSCO, annotations made in one place on your content should be connected to annotations on content that's held elsewhere. There's a variety of different ways that we do that. Canonical URLs, looking for tags in the metadata that refer to DOIs as well as PDF fingerprints. Just a bit about integrating hypothesis. The basic implementation is free. As many of you know, if you're a researcher, you can come to our website at Hypothesis and get a free account today. We've got a plugin and browser bookmarklets that cover the major browsers, and that's free, of course, to use. Similarly, if you're a publisher or a platform host, you can do a no-cost integration of the basic hypothesis into your platform. It includes all the primary annotation capabilities. We have a number of plugins that I mentioned. If you want to embed hypothesis in your site, just a few of them mentioned here. There's a complete list available on our site. We've spent a lot of time the last year working with the different platform hosts mentioned here and some others that will be announced soon to enable smaller publishers who are using those platforms to get going with hypothesis. We also have a very robust API that you can get started with today. There's a number of pieces of information and things that you can do with the API. We believe very strongly that users should be able to get their annotations out and that publishers and other entities that want to make use of their annotations should be able to do so readily, whether they want to repurpose on their website, say in a widget for marketing purposes or to use for text and data mining. Nate's going to be including some links to our documentation and if you've got questions about it, we're happy to answer those today as well. What if you want something that's a little bit more custom. As we started to work with publishers a couple of years back publishers let us know that if they would enable by default annotation to be visible on their platform. It seemed that by association those annotations would be connected to their to their content. Enabling branded layer that a publisher could moderate was work that we undertook for elife. We enabled a number of customizations to allow the client to fit more readily with the publisher platform. And we've got some other things that I'll talk to you about in just a second here. When it comes to pricing, we typically use a number of documents that you want to deploy hypothesis across as a proxy for publisher size. You can deploy hypothesis as narrowly or as broadly as you like. You can put it on one journal title, for example, you could put it on even even one book, you could put it across your entire platform. The proxy size when we ask you the number of documents you add per year that does include adding hypothesis back to volume one issue one so it includes back files. It's just the mechanism that we use to proxy publisher size. We can also connect to publisher existing accounts. If that's something that you're interested in. And what we're going to be focusing on today and a little bit more detail is the technology that we call publisher groups. Again, these are branded and they can be precisely configurated to meet publisher needs. They can be restricted where public their publicly readable annotations, but the only folks who can create annotations in those layers are those invited and allowed to buy the publisher. There are also general discussion layer opportunities where annotations are publicly readable and basically anyone in the world can join and create those those annotations. When it comes to UI, we've got a number of things that you can do and some of them I'll show you on the life implementation. You can control the colors of the client and the text, the information about the borders, different typefaces so that it will fit with your content. Some default measurements for the sidebar, whether it will be open or closed, some configurability around highlights, as well as different calls to action so that you can let readers know that annotation is available on your site. We think very much a hypothesis about how annotation can be successful. So we always meet with our publishers ahead of time to talk about what types of goals publishers are trying to achieve in enabling annotation and how that success can be measured. We offer a variety of different types of training internal to the publisher aimed at end users, as well as dedicated training for folks like editorial board members who kind of sit in between. So that, you know, with internal as well as external champions, annotation will be a stronger success on your platform. These programs will working around engaging key annotators. Some things that have been tried successfully in the past by partners include putting together annotation events, annotatathons, you might say, enabling author annotations as part of regular workflow, or inviting expert commentary. We work with you to coordinate our promotion, both when you sign when the publisher groups launch. We'd love to present together with your conferences and even put together case studies and way papers on different types of uses. As an open source and nonprofit support and open source maintenance are critical to our future success. Many of our partners are in this space as well. We need to be able to provide to our partners technical support. We've got a great support engineer who recently started with us. We have an open source code base that's available for a deeper technical dive and a community that's working on annotation capabilities across the board. We're also, as I mentioned before, keenly dedicated to standards and interoperability. So we're working with a number of open tool providers and platforms to enable that. We believe strongly in annotation as a community effort in 2015 we started the annotating all knowledge coalition. It's a group that currently consists of more than 70 publishers platform hosts and technical companies, dedicated to supporting an annotation and trying out new projects together. We also host the I annotate conference, which will be coming up the first week of May this year in San Francisco, or sorry, the first week of June is usually the first week of May. And we'll be putting together a partner event, having two full days of presentations around different types of annotation, as well as a hack day. And we'll be happy to tell you to more about that. We recently posted the registration page, and we'll be doing a formal call for proposals. We'd love to have you participate. Now I'm going to stop sharing my screen here for a second and go over into. Actually, I'm right here in the tab go over and show you a little bit about the life integration. If you want to come back later and explore aspects of the life integration yourself, you can certainly do that. The links that I'm going to be going to now are available as part of the blog post that we did a few weeks ago. And if you go to this blog post on our website and scroll down, there are links to a couple of articles that elive has preceded with annotations. So you can go ahead and check out what's been done so far in the platform. Now we'll pop over, and I can tell you a little bit more about the integration that was done there. So first you may notice that the sidebar looks a little bit different in the elive integration. These are the customizations that I mentioned if I scroll up to the top. Elive wanted to streamline what's visible in the client. And this is in keeping with their minimalist approach on their new website. You can see it looks beautiful here. They also wanted to change the call to action a little bit. So you can see now that I've closed the client. It's not visible here on the left, but you can explore annotations by clicking on an annotation tab here. And you can also, if you go down a little bit further, click on this little conversation bubble. Similarly, if you want to start annotating, you can actually select text and the annotation tools will appear. Elive is an example of using publisher accounts to provide annotation to readers. So that means that anyone who comes to Elive who has an Elive profile can just start annotating. They don't need to create a separate hypothesis account. So if you do want to play around with this on the Elive platform, have your orchid handy and create yourself a nifty Elive profile. And then you'll be able to take part yourself. If I open up the annotations here, you'll see that first time annotators get a little getting started pain. So they can get going. The way that Elive has worked with some of this content is to have the authors do some annotations to kick things off. So you can take a look here and see what Xavier has provided here in regards to his article. Elive editors have also provided some brief information in the form of page notes. So page notes are annotations that are tied to the entire document rather than one piece of text within it. So check those out as well. If we scroll down a little bit, we can see that in addition to Xavier's annotations, we've got some feedback from some folks who are reading the annotation here. We've got another example that I can show you that has got a number of annotations. Whoops, my page is timed out. So let me give that a second to reload. We're really curious to see how things are going with Elive and we're right in the middle of doing an awareness campaign with them that I'm sure Nate would be happy to tell you a little bit more about. So while my page reload should be able to see here again my annotation tab. So here we have another author who's provided annotations Benjamin Engel. He's got some great links to additional resources. There's some other folks who are weighing in here about the discovery and similar to the other article, there's information provided here by Elive about the content. So just an example of what Elive is doing. I've got one more quick thing to show you before we open up to questions and to do that I just need to stop sharing for a second while I swap over to a different application. Let me be right back. Here we go. So I just wanted to show you a couple more things that are possible. So this is a walkthrough that demonstrates the group's functionality that our designer put together for us. I mentioned that I showed you that Elive has their call to action. One of them is a tab that you can click on. It's also very simple to put a button on your platform that will show the number of annotations on a given piece of content or a call to action like annotate PDF or annotate me. It's very customizable how you would like that to appear. Once a user clicks on, oops, let me go into my slide share so it's a little bit more, a little cleaner for you here. Once a user clicks on the button. Then let's hang on here. Sorry having trouble getting this to advance. Okay, maybe we're not going to do it in the slide share book. Once you click on the button, then the client will pop open from the side and you can see that this is the publisher branded layer. It's got the little bio Pope logo there and it's got a general discussion layer. This first piece of the walkthrough indicates the connection to publisher accounts. So what you can see here is that these annotations are world readable just as in the Eli example. But if you want to create annotations, you're directed to either create an account or log in. In this case, it's referencing publisher account. So if you go ahead and log in there, you'll see you got to get started getting started pain similar to what we saw on the Eli platform. So, Eli has one publisher layer that's intended for general discussion, but one of the cool things that I mentioned in the presentation is the publishers can actually have multiple layers atop their content. This is covered as part of the pricing policy that we have so you can have an unlimited number of layers for different purposes on your content. So we've got here a general discussion layer, which I'll show you next, and then a couple of layers that are restricted for specific purposes. For example, authors annotating their own work or peer review summaries or reviewer content. You could also use this if you wanted to add as a publisher information on how your content, you know, might be used new features. If you have any automated entity annotations, you know, you might make that visible in a separate layer as well. So for each one of these layers, you have the opportunity to view activity. So we can go in and see what the activity page looks like. So this is a way that an end user can see what other content on the site has been annotated. They can explore what other annotators are doing, take a look at what tags have been applied, they can see different articles that have been annotated. And this general discussion activity page can be set as narrowly or as broadly as a publisher wants. It could be deployed across one book, it could be deployed across one journal, a collection of journals with a similar subject area, or across the entirety of your site, or even if you have multiple platforms across that as well. And as I mentioned, it's a great way for folks to discover other content that is of interest to annotators on your platform. We'll be sharing this presentation with you afterwards. It's just got a couple of slides here on how you highlight and create annotations. And I want to show you a little bit about restricted layers. So for example, if a user clicks on the layer that's indicated for reviews, they get a message that the group is read only so they can see the annotations that have made here by reviewers. And there'll be an information page which explains the criteria for annotating in the group. We get a lot of questions about using regular hypothesis accounts. And so I should stress that publishers who integrate hypothesis do not have to use their own accounts. Many of our publishers do not even have account systems or profile systems of their own. So they're happy to use regular hypothesis accounts. And you can still have the publisher branded and moderated layer even if it's run in the back end with hypothesis accounts. There's just an additional step when the user wants to create annotations, they just need to create a hypothesis account first. So if you are currently annotating on Eli, for example, using their accounts, and you want to switch to your regular hypothesis account, you can just log out of Eli. But what we want to make it easier for users to do is to actually connect and bridge between the publisher account and the regular hypothesis account. So this flow is intended to demonstrate that so you could actually log into your hypothesis account and be logged into both. This is some work we're going to be completing in the next couple of months. So you can see here that now that I'm logged into both accounts, I can see the publisher authoritative layers by default at the top. But I can also see that there are annotations in the public layer, as well as a private annotation group neuro club that I'm a part of. So I can direct my annotation to whichever layer is appropriate in that case. So this has been just an example of a walkthrough of different possibilities that you can do if you're enabling publisher branded and moderated layer. That's the end of the plan presentation. And we're happy to take any questions now. Hey Heather. It's been a pretty quiet group so far. Suzanne also joined us as we were going along. You know, we have such a small group of folks to we could also turn on audio if you even want to have a voice conversation. August Suzanne get now do you have stuff that you'd like to ask about or do you like to describe how you're thinking about annotation at your institution and we could talk about how hypothesis might fit in. Okay, yet now it says yes let's see if I can allow to talk wow. Okay, yet now I'm promoting you to a panelist so you can talk. So if you have audio yet now you should be able to. Yeah, you're muted. You can just click on the little microphone and the lower left you should be able to unmute yourself. I can do that. In August we see your question and we will we will get to that too. Can you try? Yes. Thank you. So, I'm interested of course in the connection with the learning management system at our institution, which is Sakai. And we're interested in an LTI connection. I noticed you do have something going on with Canvas. I don't know if the processes are the same for the two. If not, what would it take to to affect an LTI connection for a Sakai based learning management system. You want me to take that one Heather. Go ahead. So, as you may remember, I'm an old erstwhile Sakai community member. So the good news is that we took the beta work that we did in Canvas and LTI connection there. And are now working with an outside team of developers actually to extend that LTI integration into any other standards compliance LMS which would include Sakai of course thanks to Dr. Chuck. So that there will at least be basic integration capabilities between hypothesis and an LTI compliant LMS like Sakai. That was hard to say. The first thing of course is to get the hypothesis client embedded into the LMS. And then the second is which most people have earmarked as the most important feature is so that there's single sign on and rostering capabilities that cross between the course or project sites in the LMS like Sakai and hypothesis so people don't have to make new accounts. Be happy to hear about other thoughts you have on the integration. I don't have other thoughts I was a bit surprised when you said you would need to integrate hypothesis into the LMS first the LTI connection would not be enough. In other words, would there be work has to be done on the Sakai LMS structure or is it just strictly the LTI connection that is already built into our system. It should it should all work with just an LTI connection. In fact, I've done some preliminary testing on what we have already and the LTI connection is working. There's a couple of bugs that need to be worked out. But it should the goal is definitely to make it all work with Sakai standard LTI capabilities. And that would be either at the full implementation level or at a particular course or project site level. It would be good to be able to do it at a particular course level. We work with other vendors that use LTI and the biggest weakness is that they just make the simple connection and don't really respond to our course structures. So hopefully we can create something more flexible by courses. So that's our interest. Yeah, and that's where the the single sign on and rostering integration, I think is is crucial so that one of the common practices with hypothesis in this kind of matters in the publisher use case to is that often if you have a course or any group of people like a journal club or or a group of peer reviewers or any kind of editorial function, the publishing side, they often want to annotate together in a group structure. And so we've long had what we call the private groups, which a lot of educators have made use of because the teachers and students can work together privately as Heather mentioned. And so one of the goals of the LTI integration is to make it so that the course roster in an LMS like Sakai is automatically put into a private group structure and hypothesis so they can annotate together, which doesn't mean you couldn't do public annotation to if you wanted to. But the assumption is is that most people will want to be annotating in a in a course environment in a private group structure. That makes perfect sense. Great. Well, so we should. The goal is to have that LTI integration capability ready so that it would be available even before fall 2018. And knowing how academic calendars work, we know that you really need it in the spring sometime in order to think about using it for the fall so Yes, I know you all too well. And so stay tuned. I'm sure you know our colleague Dr. Jeremy Dean. And so he is leading point obviously in all the education work. And, you know, we'll be we'll be doing updates he'll be leading some as soon as we have something juicy to show he'll of course be leading webinars and that as well. But there are people working on it as we speak. So, that's cool. I have one more quick question. Sure. You've been using it with students at this this semester. I've noticed that the interactions the replies are not listed in with the. I'm not sure what the term is that that when you click on somebody's ID you get a list of their annotations but you're only getting the top level you're not getting the interactions. I realize it's a complex thing to to solve but have you guys thought about that or done anything to be able to show the actual discussion rather than just the top level posting. Yeah, so you've you've you've recognized something that's a well known issue of course and that that area we talked about as the user profile area or sometimes they called activity pages where you can browse and search through any any kind of faceted group of annotations including those of a particular user and you're right right now replies are not returned automatically into that into that view. And so we we understand that that's a that's a drawback and it's not even as complicated as you have pointed it out. So we are, we've already done prototypes where it's included and we recognize that as a key thing that you see forward. So you should also see that in this spring time frame. I lost my ability to talk there. Excellent. Thank you. Thank you very much. Sure. Um, and so we have another question from August who had asked, have you thought about the overlap between cross mark and hypothesis for post pub updates that seems like a Heather question. Yeah, actually is it's one of the very first use cases that I thought about for hypothesis I think even before I was officially part of the company and I'm reminded of it. Whenever I see that there's a correction that elife article that I showed had the red banner across the top indicating that there that there had been a correction. I think it would be great. I've had a couple of quick calls, you know with Ed Pence at Crossref to kick things off. It's probably probably do for a check in with any time you want to add additional information doing it through the form of an annotation is one way to do it. Folks who don't know, for example, to click on a cross mark to get an update might never know that something you know has been done. Also, we're doing some work with the American Diabetes Association that they're implementing one of the restricted layers to do updates on their annual standards of care issue. And so it's critical to them that just ADA staff be able to do that. But one of the things that we've also had in discussion is using annotation cards to make updates and corrections more visible. So you could connect an article, your annotation card in line with its update or correction. And similarly, if someone comes across the DOI for the update or correction, connect that back to the original article. In some instances, it's a good way to indicate to readers who might be starting their, their research online, but who may in a hospital setting for example still be looking at a printer and at some point to let them know that something's been corrected in the online edition that they need to take care of when they look at the print. But yeah, any kind of identifier like cross mark is an excellent use case. We seem to have stunned them into silence August and Suzanne. Is there anything else that you'd like to talk about? We don't have to stay the whole time, of course. But we're happy to talk more. I can also promote you so you can use your voice if you'd prefer. Any other questions, thoughts, suggestions, ideas? Is the microphone still on for me? It is, yes. Go ahead. Any thoughts on media annotation besides text, images, video, things like that? Other kind of media? One, sorry Heather, I was just jumping on this. We definitely have earmarked image and video and audio annotation as a future thing to focus on. Right now we're still focused on making sure that text annotation is widely supported across all platforms and formats like EPUB was just added over this last fall. Our colleague John Newdell, who you may know, has been doing some really interesting work in the annotation of the textual transcripts that accompany video and actually audio as well. And I can point you to a couple of blog posts about it. He's published some of it on the hypothesis blog, but he's also done some of it on his personal blog. And so I will dig those up for you and put them in the chat. So it's not quite video annotation, but it comes pretty close because it's a way to annotate the textual transcript, which one would want to have for a variety of reasons anyway, and have it be synced to the timeline of the video audio piece. Wow. You want to add something, Heather? Nope, it's great overview. So I will dig that those up for you, and you will get a list of links in the email kind of synopsis of the webinar as well. Okay, thank you. Oh, it looks like we might have answered that. You muted yourself, Nate. Right, well, I was talking. That's a good idea. I know other people who want to have that power over me as well. I could just shut him up. That would be awesome. Well, thank you guys so much for joining today. As Nate mentioned, the recording will be available for if you have colleagues that we're not able to join, and we'll also make the walkthrough presentation that I just show available. I also should mention, and we can include this as part of the follow up, Nate, that we've launched a little test site on our fictitious publisher here, Biopub, that just gives an initial, you know, snapshot into these open groups, which again is the world readable and world writable groups. And as as the restricted groups become go online in the next few weeks, you know, I think we'll be adding that to the test site as well. So if you want to go take a look at that, you'll be able to play around a little bit. I do encourage you to take a look at the integration that elife has done. And just a reminder that to do so, you need to create an elife account and have your orchid ready. I hope everyone on this call, you know, has an orchid. They're big supporters of hypothesis and we're in turn big supporters for them. So we feel everyone should have that. And if you have any other questions, don't hesitate to get in touch with me or Nate or anyone on the team and look for some announcements in the next couple of weeks and months of new publisher integrations that are going to be coming out.