 Great, well, thank you guys so much for joining us today for a webinar on custom annotation groups for publishers. A little bit of organization about how we're going to present today. First, I'll just say a few words about hypothesis. I'll tell you a little bit about how it works. Some of the details about integrating it. Then we want to show you some publisher use cases in the wild. I want to spend the majority of time actually showing you live sites. So if I speed rather quickly through some things at the beginning and there's questions, don't hesitate to ask. Nate's going to tell you a little bit about what we're doing in the education front and some upcoming events. And then we should have plenty of time at the end for QA. So a little bit about hypothesis. For those of you who don't know us, we are a mission driven nonprofit. We're an open source technology company that is working on enabling annotation overall knowledge on the web. You can see some of our funders at the bottom of the screen there. And we're in the process of working towards transitioning to an earned income model, both with publishers and with education verticals. We are darn close to 4.5 million annotations. I think we'll be close to 4.6. You have to check these things frequently. You can see on the screen here the annotations fall into a couple of different categories. Pretty standardly, about 20% of the annotations are done in the public channel. About 20% are done by users to keep them completely private for their own purposes. And then 60% happens in collaboration groups. So it's that sort of bit of the iceberg underneath the water that we don't see where a lot of exciting things are happening. So we're happy to be able to share information on that. Two years ago, the W3C published annotation as a web standard. So what that means is basically in future versions of browsers, just like you tell your browser what your preferred search engine is, you'll be able to say, and I use a particular annotation client. The goal being that there can be multiple annotation clients. And if they're all based on the standard, annotations that are made will be able to interact with each other, just like we can email back and forth, even though we use different email clients today. So I wanted to start just kind of briefly setting up the situation of, you know, how annotation is different than commenting because I think we've, we've had commenting for some time and some publishers have not had good experiences with it. And, you know, annotation is really, I think quite a different animal. And so just just to kind of briefly touch on that, you know, one thing is actually connection between annotations and between annotators. So comments as previously incorporated into websites were really stranded on their individual pages. And there was no way to really get a 30,000 foot view of what have been done across the website, or what have been done by an individual person. So now through group and individual activity pages, it's really easy to get an idea of activity in space to search and explore annotations there and, you know, pursue those annotations to their original locations. 20% public annotations of the larger cohort, we do send to Crossref for inclusion in their event data project and indexing by Google. So those are discoverable. The second point that I like to focus on is the collaboration factor. So again, you know, we tend to think about public annotation, but there's so much going on kind of underneath the surface. As of yesterday, I had had Nate run some numbers again, there are 32,000 collaboration groups on hypothesis so lots of activity there. And then finally, persistence. So each annotation has a unique persistent web address so you can cite it. And annotations are available for folks to download and utilize their own annotations for organizations who want to connect to our API. You can see the public annotations or if you sponsor a group, you can see your group annotations as well. So a lot of differences there that simply were not possible with comments. One example that I like to mention, again, when thinking about how comments differ from annotations is really, you know, not so much focusing on quantities of activity but really looking at quality. So just a little case study. About a year ago PubMed announced that they were discontinuing PubMed Commons, because of relatively low uptake and comparison to the whole corpus of articles on PubMed. So a number of folks reached out to us via Twitter to see if we could actually rescue these comments before they disappeared. So we worked together with PubMed and Europe PMC to be able to gather these comments to add DOIs to them, to add PubMed IDs in the form of tags to make them more findable, accessible, interoperable and reusable. And now if you look at the tag there at the top PubMed Commons archive, if you go into hypothesis and you actually search for that tag, you'll have the entire corpus of annotations that will come up. Recently we made these annotation layer visible on top of Europe PMC by default. So if you don't want to mess around with browser extensions, you can go and take a look at it live on Europe PMC. And you can also explore via our page and the slides will have a link so you can take a look. So a little bit about how we envision annotation over the version of record on the web. We think about it in terms of layers. So you have the article on the publisher website. The article never moves the book chapter, the document, the blog. But you can have a number of different conversations happening simultaneously on top of it. You can have that public channel that I mentioned where people are adding information that they think will be generally useful to whoever comes to the page. You can have a private group such as a classroom working on that same article with their annotations only visible to folks who are part of the group. And you can have publishers inviting authors, expert communities, and also even the publisher staff, which I'll show you some examples, adding layers of annotation and depending upon what you've come to the page to do. You can toggle back and forth between those different layers, just like you might monitor monitor different channels with a messaging tool that you use internally now. The way that hypothesis works is kind of two parts. There's that bit that pops out over the content. That's the client. So you can use it to annotate any web page, HTML PDF, or EPUB, and then where the annotations are stored, which is on our server. So each time you open up a page, a call will go to the server say, hey, are there any annotations on this page that this user can see. So that would include public annotations, any annotations that you've made yourself, as well as any groups that you're a part of. This keeps readers on top of the version of record, precluding the need for them to, you know, move a copy of the PDF into a scholarly collaboration network, or other site keeps them returning to your content as they review their notes as they follow through collaborative groups with other researchers. We provide analytics, which I'll talk about in a little bit so you can note engagement that's happening in these different contexts. The publisher controls the group on their site and I'll show you a few different options with that. And this breaks down the content silos and maximizes the opportunity for discovery of annotations and their respective content. And the API's enable repurposing of data, for example, if you want to do text and data mining on top of it, or if you want to set up a widget to display recent annotations on another part of your site, you can definitely do that. So, as I mentioned before, we're an open source company, so the code base is available for anyone who wanted to take it and integrate it into the site. You don't even have to tell us you're doing it, we like if you do, because we'd like to help you be successful. But if you want to work with us to enable this branded and moderated layer, which I'll be showing today, we're happy to do that. We do offer document based pricing, and the wider you deploy on your site, the cheaper it is on a per document level. There are a number of documents that you add per year as a proxy for publisher size, but you can deploy back to volume one issue one or earliest copy right here. If we're looking at books, and you can certainly start with a smaller pilot or you can go all in across the entirety of your site. If you already have existing accounts that are widely used. You know, we are able to offer a single sign on which we can talk about more in the in the q amp a folks are interested. The types of groups that I'm going to be showing today are the open group. This is world readable world rightable, as we say, anyone can participate. And then the restricted group when a publisher has a more specific use case in mind, which is still world readable, but the only folks who can create annotations or folks who are part of the approved annotators for that group. The UI customization full customer support from our amazing client services team, open source maintenance to continue to approve the code fixing the bugs anything like that. And what I like to point out is the most important thing is a success program to make sure that you can achieve your goals with annotation, and then we can put together the training and outreach that will help you get there. So a little bit more about integrating hypothesis. These publisher groups I think I've probably covered everything here, but just an example on the side of how different group layers might display depending upon how you've you've set things up. So you can toggle back and forth between those different configurations as I mentioned, and many publishers are selecting to offer, you know, kind of mix and match. There for general discussion, perhaps one for authors, perhaps one for staff updates and in the like I'll show you some of that. And I mentioned before these group activity pages so these function as group dashboards. So when you go, whether you're an individual user, going to your page, you can see annotations there, or going to the group page. You can browse and search there you can click on tags, you can do domain queries across URLs to see if there's annotations already existing on your content, or you can filter by groups. So it's a great way to explore. And again, I'll tell you more about this. If there's a high level of interest. Analytics, we're frequently asked, you know, what kind of reports we do. So you receive full analytics on, of course, annotations that are made that are that are public for anything that is made in either your public group or in the hypothesis public channel. You can see who made it when it was made upon which document, what the selection was and what the user had to say about it. For things that are private and groups that are private, of course, that's information that's not available, but you can still see the number of annotations, the documents where those annotations occurred, and the time that they happened. So even if you can't 100% see the activity, it's still a great indicator that engagement is happening on top of the document. You can look at key annotator segments, for example, in the in the neuroscience and neurobiology space, research resource identifiers are used for reproducibility purposes so there if you fall into that space, more than 125 journals you probably already have some SciBot annotations on your content. We report those as well the number of annotators, the number of new annotators, as well as top annotators and top annotated pages so lots of information that you can get from analytics. And if there's other types of metrics you would like us to capture. We would love to hear from you and try to work out how we can make that happen. So, just a little quick slide, you know, I'm asked all the time, well, you know, who's using hypothesis, you know, how many publishers have done an integration. So, because end users can get accounts for free and hypothesis can be used anywhere on the web, you know, a lot of times I just say, oh, all of them. So, I'm going to jump over in just a second and show you some live examples. To do that I need to quickly make a trip to my other browser. So I'm going to go out of full screen and hand over to Nate to tell you a little bit about our education. Okay, thanks Heather. While you're doing that, maybe I'll share my screen so I can just show the slides. Okay, great. So we noticed amongst the folks registering that there might be some folks who are coming from higher education or a teaching and learning background interested in high policy. And, you know, a lot of what Heather's been talking about has been specific to publishers, of course, which, you know, oftentimes colleges and universities are also publishers right, but for the teaching and learning context we just wanted to let you know that recently, hypothesis launched an integration with all the major learning management systems, including, you know, Blackboard, D2L, Canvas, Moodle and Sakai, and basically any LMS that is LTI compliant learning tools interoperable standard compliant. And so there's more information about this on our site. We're not going to delve into it today. And we have our director of education, Jeremy Dean, heads up this effort working with teaching and learning and would love to connect with anyone who's more interested in that. And so I'll just share and chat here. A link to a blog post that we issued recently that I can't figure out how to get back to chat. So how often I drive while I'm talking. Okay, I will. Yeah, we'll share the link while Heather's talking in a second. There's a lot of really exciting things happening now in the teaching and learning space with this ability for teachers and students to be able to annotate on with single sign on in their own learning management systems. So we just wanted to make sure that you were aware of that in case that's an area of your interest. We have both a pilot program and a partnership program like we have with with publishers working with higher education and even K 12. And then also we just wanted to mention that coming up here in May will be participating in the seventh annual I annotate conference so it's the only conference that's really dedicated to digital annotation. It happens annually this year it's going to be in Washington DC for the first time at the newly refurbished headquarters of the AGU the American Geophysical Union. Which is the first net zero refurbished building in the nation's capital which is really cool so we're excited to go to that. You'll notice the kind of fancy artwork here for I annotate each year I annotate takes up a theme this year. It's annotation unleashed the Web at 30 and actually thanks to Heather's creativity. We the conferences move toward a kind of heavy metal to her motif and so that's that's why it's all looks all red and spidery they're a little scary. But don't be scared it's going to be an awesome conference there will be folks there on both from the publishing world, research scholars, scientists, technologists, journalists fact checkers people from teaching and learning and education and so it really brings together everyone. Who's focused on or thinking about annotation across all the different disciplines. And it's a two day event that will be again in Washington DC area followed by a one day do a fun hack day where people actually pull up their sleeves and dig in and do work on annotation. I will also share the link to the I annotate website. After Heather takes back over here so that you can take a look at the preliminary program. There's actually still time to submit submit proposals if you have actually been working in annotation already and have something that you'd like to share with with the assembled crowd and I annotate and then there's February 17th is the deadline for puzzle submission. So that information is all on the website. So we just wanted to make sure you knew about that. Certainly if you're an East Coast area would be easy to get to. And we would welcome and love to see everyone who's on this webinar come to that and really have a deeper dive in this kind of really collaborative intimate environment where it's usually between 100 and 200 people gathered and really focused on annotation for a couple of days it's a great event. Okay, so Heather, do you want to take it back over. Yep, I think I have. Yes, you have. Okay, just just started to jump the gun there that thing. No problem. We're taking care of that while I did a couple of housekeeping items in this in this window. So as promised, you know, I do want to spend some time showing you some, some publisher groups in different use cases that are that are alive now. And we'll be sharing the slides and I think that there are links that to go visit some of these in context. So, almost exactly a year ago today actually a year ago tomorrow on January 31. We launched the life collaboration. So it was the first publisher that we work with to develop publisher specific features and functionalities. So we're glad to say that as a result of their collaboration with us these are now available through the publisher groups, you know that I've been describing. So, we find ourselves now on an elife article, the way that you launch annotation and elife is to simply start annotating or you can click on this tab here. It's got the nice little number badge you can see the kind of number of annotations on the page. One of the projects that elife has had underway is inviting authors as part of the workflow process to introduce themselves so here we can see on this article that Ben angle has introduced himself and added some update links. He's been interacting with some readers on top of his content. And at the top of the client here to the right, you can see the elife branding indication that this is their layer, as well as the moderation flag here at the lower right so if I were to click the moderation flag that elife moderator would get a notice to go and review that annotation for its appropriateness. And the publishers designate their own moderators for these layers. And some of the customizations can be seen here, you know, matching matching fonts, and the like. So this is an open group. Any of you who want to play around with annotation can go to elife. It does use elife accounts so you would need to make an elife account in order to, to participate have your orchid handy because that's what everything hinges upon. And one of the things that one of the reasons I like to show this article as you can see at the top here. There's a big red banner that this article had a correction. And if we click on the page note which is an article level annotation. You can see details about this particular correction in this case, citation was missing and it was added. So elife staff and staff and other publishers have found annotation cards to be a useful way, not to replace the regular update flow, but to draw a correction of the readers that something has changed in the article. So again, this is an, this is an open group. I want to show you another open group. This is through collaboration with American Psychological Association, which launched last fall. And you can see each publisher kind of integrated things a little bit differently so a PA uses a little button here at the top. And if you click on that, it's going to open the APA publishing open group. And in this case, one of the projects that APA has done is they looked at their top downloaded articles for 2018. And they invited several of the authors who are responsible for them to provide some updates. So in this case, Russell Warren has done an excellent job. He's been adding some, some links, some notes. Here's a little video of an interview that he recorded which you can play. And just did a really amazing job utilizing tags and the like. So that might be a use case which might appeal to too many of you. So open groups, but some publishers have really specific use cases in line when they come to us where they're not quite sure that they want to open things up yet for everyone to annotate. So the first, what we call restricted group, we put together for American Diabetes Association and this actually launched in spring last year. Let me scroll up. So every January, ADA publishes an update to the standards of medical care in diabetes, and they wanted to have a mechanism to add additional information and updates without waiting for the next annual cycle to come around. So we created a group for them that's world readable to anyone who lands on the ADA site, but the only folks who can create annotations into this layer are the ADA staff. So you can see they've got their account is the same name as their group. They really did an amazing job with these updates. If I scroll down here, they treated them like true first class research objects. So you can see the date that the annotation was originally published, the date it was approved by their publications committee, suggested citation and some tags. And I do like to, you know, highlight again that you can cite these annotations because they do have a unique persistent identifier. So if we go to the ADA group activity page I mentioned these dashboards and activity pages before. These are all of the updates that ADA actually included on this issue last year. So you can go in and you can see what these updates consisted of. You can use the little view annotation in context to go to the article and be scrolled down right to the annotation. You can share out annotations. You can search this and they've also included these helpful tags. So if I just want to see updates that are referring to hypoglycemia, I can click on that. It's going to add my filter at the top. And again, these are great ways to find content. They've got internal links, external links. They've added some tables and charts. Really did a nice job. Another example of a restricted group is a project that we did Cambridge University Press together with Syracuse University's qualitative data repository. And this is a project called annotation for a transparent inquiry. And it's designed to bring context to citations in the social sciences in the same way that citations have become more transparent in the hard scientists. So in each case, if I click on an annotation card, you can see that this particular annotation is tied to this sentence. But it gives the author the ability to add a lot of additional information about methodology about sources, additional links, connections to the data, translations that they would not have been able to fit into the article for space annotations on the print side and for maybe some limitations on the electronic side as well. So this is a project that includes about six other publishers in addition to Cambridge. We're in the process now of making these annotations visible on those other publisher sites. Again, like the group page that I mentioned over ADA, you can click on the group activity page to see all of the articles across Cambridge that are part of this project and explore them and share them and the like. A lot of the publishers that we talked to are interested in what annotation can do in regards to peer review. This is an interdisciplinary journal called murmurations. It's hosted on the PKP iteration of OJS. And what they've done here is they've created a restricted group for each article, includes the authors, the journal editor and the reviewers. And they work in a completely open peer review process. If we scroll down a little bit, you can see an interaction here between Linda Vanasupa, who's the editor and the author Shantel Beebe. If the public wants to add annotations, they can't do it in this group, but they can hop over to the hypothesis public channel and do so there. So it's a great example of utilizing peer review, annotation and peer review. Another project around peer review, and I don't have any screenshots of this. I do apologize, some should be coming soon. It's a project that BioMed Central did in collaboration with a company called Research Square. Four of the BMC journals offer this as an option and I'm told that more are coming soon. So when an author submits a manuscript to one of these journals, they are offered the opportunity to opt into what's called in review. So in review is something that is designed to bring more transparency to peer review. So in parallel with the traditional peer review, if I scroll down here, you can see community feedback is welcomed through use of the hypothesis tool. And the interest from authors in opting into this project has been really, really high and we're working together with BioMed Central and Research Square to kind of give kind of jumpstart suggestions and best practices to get going with this tool. So this is in review. And then I want to show you our latest publisher to launch, which is the American Society for Plant Biologists. I'm really, really excited about this collaboration here. And again, in the area of peer review, ASPB had in the plant cell been publishing what they call peer review reports. These peer review reports were being published as supplemental material. They really weren't getting a lot of attention. Folks didn't realize they were there. The click-through rate was relatively low. So they wanted to utilize hypothesis to draw attention to these peer review reports. So here we've had one of the staff members from ASPB who's added an annotation here that this article has a peer review report. It doesn't change the existing workflow. It doesn't require moving. But if I click on that peer review report, you see it will take me to the PDF and there's a lot of information about the peer review. So we're hoping that this will dramatically increase the visibility around these peer review reports that they've done. Just like the other examples that I showed you, they have their activity page. So you can see how many links they've gone ahead and added about peer review reports. So all of the peer review reports can be discovered and explored from here. And because they're using hypothesis for some other purposes, they're using peer review report as one tag. But one of the other projects that they're interested in looking at is drawing attention to activities that happen on their blog. Like so many society publishers, they have a content site and a member site and perhaps you might even have more than that. And how do you bridge these sites together? Well, with one annotation group, you can scope it to multiple websites. So for your members and your readers, you can offer this kind of bridge through annotation. So ASPB had been offering these, what they call first author profiles, but they live in a separate site. So they're kind of hidden here under extras on the side. So we're working with them to grab images of the authors, a couple sentences of the bio and providing a link. And we will be embedding hypothesis on top of the plantae blog so that folks can actually add annotations there as well. So this is just a smattering of the use cases that publishers are looking at now for annotation. And I'm happy to be able to show you. And now we'll open it up for questions. Hey Heather, that was great. So we have one question so far from Allison. And she's asking if annotations are captured in altmetric scores. Yeah, that's a great question. And we're in conversation with altmetrics about this now. There's a couple types of annotations. So it might well be that annotations are captured in a couple of different ways. For public annotations, of course, we can set up a connection with altmetrics that will enable folks to click through and see what the annotator has written. But because there are private annotations on top of content, that's also an indication of engagement. So we may end up with two colors on the donut. So I'm not sure exactly what the timeline will be for that happening. But, you know, I would say, you know, hopefully sooner rather than later. One thing, you know, I kind of add on that I heard a great presentation at the altmetrics 5am meeting back in September. And it was a presenter from Taylor and Francis talking about how when they found a really interesting altmetrics story, they would go back to authors and ask authors to maybe do a little update of the article and then share that update through social media to kind of build on that interesting story. We think the same thing is definitely possible and you know elive is doing a little bit of this now to promote out interesting annotations or conversations that are happening. One of the things I didn't draw attention to but I should have is each one of the annotations can be shared through a variety of different social media or by email. And the folks who get the link don't have to have a hypothesis account or even know what hypothesis is that they click on the link and they can get to the content. They will be taken to the content scrolled down to the annotation and they can see that there. You can also share from the top of the client if you want to share out a fully annotated article. So, in addition to kind of having annotation included as altmetrics, you know, we're talking to publishers of how they can again take these unique stories and build upon them from a promotional standpoint. Heather, we've got a new question from Paul. Can you talk a little bit about the relationship between layers and groups and annotation. Yes. So, let me let me see that's a great question. So there are a lot of different types of groups. I talked about the hypothesis types of different layers and groups I talked about the hypothesis public channel so this is the, the public annotations that anyone can make anywhere on the web. They don't require a publisher to have done an integration or website to have done integration. They are brought through a browser extension or bookmark lit. And once you're good to go with hypothesis account and you have those things, you can discover annotations anywhere. And private groups, as I showed in the, when I talked about in the, in the, in the group slide are as, as you might gather from the name, completely private. So no one would know that those annotations are there unless they're part of the group. They joined the group through a link. So this is the way most of our educational use cases happen, but as, as well in the researcher content, some publishers are doing internal workflow projects, you know, through, through completely private groups. So this is one of these sponsored groups from publishers. So, you know, I think the best way to describe it is that if you, if a publisher supports a group on top of their content that's going to be the group visible by default. So all of these examples that I showed from elive to APA to ADA, for folks who are not, you know, regular annotation users, they're going to see the publisher group by default when they come to the content. And they can switch into other channels if they prefer, you know, to do that, or if they want to go into one of their private groups. But it's a signaling mechanism on the part of the publisher that this is something that they're participating in that they're supporting in comparison to the, to the regular public channel. So the idea if is that you can toggle. So you can see if I dropped on my group's menu. I'm a part of a lot of groups. So depending on what I've come to the page to do. I can move into that channel if I go into the hypothesis channel here. You know, I can, I can take my notes or make public annotations separate from the ASPB channel, which is the plant cell reviews here. So it's kind of a winding answer to your question, Paul. So if you had something a little bit more specific in mind, you know, please refine and I'll try to do a better job. Hey, that's great to be able to see it live to Heather. So next up a question from Sarah. Have we had issues with annotations showing up to other users outside of a private group and if so what can be done about that. I have never heard of that happening. I don't know if you heard about it. Well, I can think of one example so in some of the teaching and learning examples that we had before we had the LMS integration deployed. It's really up to each individual user to make sure that they were annotating in the group or layer that they wanted to or that they were supposed to. So for example, in a lot of like college or university classes, the instructor would ask students to annotate in a private group. But as Heather was just showing, in order to annotate in a private group you actually need to go to that group menu and select it, like she's showing on the screen now to make sure that you're not annotating in the public layer instead annotating in a in a private group. And so most of the cases we've seen where somebody has sort of accidentally annotated in the wrong layer group have come from that just sort of not realizing that you had to switch to that group and make those annotations there. Yeah, maybe I can show just quickly. So this is a group that we use that hypothesis for internal purposes so if I grab some some text here. So this is a private group and and I select here, you know, just say, you know, more than I see post a hypothesis reading or I can still keep it privately. But when you are annotating in a private group, when we've done some work lately, you know, I think it was just about to mention to to ensure that students, you know, are in the right private group, but you do, you know, you every time you make an annotation. It will basically show you kind of your, your group of last activity. So I tend to make most of my annotations only me. So we'll show up. You know, the first thing will show up here will be only me and then if I decide to go public I need to select it, but you do need to select it each time, but if I were accidentally in the public channel, and not an hypothesis reading. You know, I might accidentally make an annotation in the wrong place, but it doesn't mean that the security of the hypothesis reading group is compromised. Right, so we don't have any examples where annotations are made in a private group and then accidentally get exposed. It's more just on, you know, the issue of a user knowing where they're annotating. In the in the LMS integration context, students are automatically enrolled in a private group that has everyone in that course that's in their learning management system enrolled in it as well. And so by default, they're all annotating in a private group. And so there's less room for kind of accidentally annotating in a public player in that LMS integration. So that's particular to the teaching and learning context. So just as a side note there, we don't have a way yet to move an annotation from one layer or group to another. So if one did accidentally make an annotation in a public group one would have to go in, copy it, delete it and then change to the private group contest text and paste it again. So another question then from Emily. So in restricted groups, is there an administrator who can manage the content within that group. So each group has an administrator and for restricted groups that it's this the same case. The administrator right now is also the moderator. So for many of our publishers if they have, you know, more than one person who's going to be taking care of that they might create shared account shared credentials to use. We're in the process of building out more administrative capabilities. And we're doing that in, you know, association with our partners to make sure that we do that in a way that will be really helpful. So for restricted groups where there are a certain number of approved annotators. The plan is that the administrator would be able to add and remove annotators in the group right now we actually assist with that process. And there may well be other things that administrator can change the description of the group can add information, you know, if there is a user guidelines or a disclaimer or anything like that. The group needs to link to, you know, again on the on the group page if I jump back over to here. You can add a it's not filled in here but you can add a description for your group that has layers like that. And again we're looking for feedback from our publishers on what other types of administrative needs we could help to meet with this. I'll ask a kind of follow up question on the question of privacy and groups following up on Sarah. And so, you know, really kind of further exploring this idea of whether a member of a private group can share an annotation out with non non group members and so all the annotations within the private group, even that whole layer, the layer that the private group is attached to so all the annotations that it contains are really only visible to the people inside that group. So someone. So there's no way to share like a single annotation from that private group out to the world, except of course someone in the group could copy it and go paste it, you know they can paste it anywhere right they can paste it on Twitter or they could, you know, put it in the blog post or they could you know send it in an email. But the actual so you know the people in the group of course could violate the privacy of the group, but there's no mechanism inside hypothesis itself to share a single annotation outside of the private context. If that makes sense, Paul. Okay, so related just related to that I mentioned that if you do share an annotation that the person you share it with doesn't have to have hypothesis they do have to have access to the content. So it's not any kind of a back door to get into subscription content when you're not, when you're not allowed in there you would see a indication that you didn't have access. I've also been asked what happens if someone annotates subscription content and then they, their subscription ends. So, you know, similar to what you see here on the group page, you would still have access to your annotations but if you tried to follow through to see them in context and you would come up against the publisher paywall. But this way, you always have access to your notes. One of the upcoming features for end users is going to be an export button, you know, from your user page, so that if you're not a technical person, I'm not a technical person, and you don't know, maybe how to get up and running with an API, you'll be able to just export your your annotations right from your active. Okay, just one more question on this kind of privacy issue and so Sarah I think you might be exploring an issue that you might be having with some annotation that's going on already and so invite you to get in touch with our support folks in order to clarify that. So you can visit our website, I'll put a link in in just a second and click on the help button, or you can email support at hypothesis, and I'll put that email into but just in short the most common reason that we see folks not being able to see annotations inside a private group context like that, when they believe that they should be able to be seen by the other group members is because they have accidentally posted their annotation as only me. And I think Heather was just kind of showing that so even within a private group context, you can make annotations that are private only to yourself. So it's like two layers of privacy deep right. So you're, you're making an annotation in a private group, but then you're also indicating that that annotation is Heather showing here is going to be private only to you. And so if a, if someone in the private group does accidentally make a private annotation in a private group, they can go back later and toggle that annotation to be shared with a group as opposed to private only to them. So there is that ability to kind of toggle between it being fully private and shared with a group with just as Heather demonstrated there on screen. The little lock shows that that's an only me rather than public. So I hope that helps sir that's that really usually the most common reason why an annotation can't be seen when one expects it to be seen is that that only me. So go back and edit it just open it up again, toggle it to the group as as Nate mentioned if you're completely in a different group you need to copy it but if you just need to set it from only me to group visibility, you can do that just in the little drop down. So we don't have any other questions queued up right now that if anyone we're still we're happy to hang around we actually scheduled a full hour in case anybody wanted to have further discussion we can also open your mic if someone wants to actually have a voice conversation about something. Can I can I show one. One thing really quickly Nate. I don't see why not every person who gets a hypothesis account if you just click on your name, you'll be able to see all of the annotations, all of the highlights, everything that you've that you've done. This is my page so I see my my public my private and my groups. So you can see some of the the one that I did here, the two that I did in the on top of the plant cell are visible here. I can also filter on my tags so I do a lot of reading about space. So if I can filter by my space tag. I can see all of my articles about black holes and Chinese moon landings, as well as all my sub tags. I can search my annotations as well. And if I get rid of the filters including my own name. We have access to you have access then to all of the public annotations made anywhere in the world. So you can see what's been happening. It's not uncommon to come in here I don't see today and see annotations in Chinese Japanese Arabic, you know French Russian Spanish. I can search stuff I just want to see things that have to do with education. I can I can pop that in now it's not a full text search it will search the metadata for the article, the selection that somebody highlighted as well as anything they wrote about it. So somebody's doing a project on Marbury versus Madison if I find an interesting annotator, I can click on their name and see what else they may have annotated so just just a couple of things here. But it's a great way, as I mentioned to kind of get an idea of what is happening in the space, and these are the ones that are fed out to Crossref event data. Great yeah and I just as I noted in the chat there on as Heather was indicating the annotation kind of composition panel supports all languages and character sets, as well as equations using latech. So we have another question from Emily, is it possible for two people to work on the same account at the same time. I imagine that you mean the same document at the same time. And then you can clarify Emily on the same hypothesis account or the same document. If you're talking about the same document and annotate together in real time. Definitely, you can do that and you'll see a little refresh indicator to let you know that there are new annotations and she last came to the page. She actually means she's clarified that she means, well both really she's interested in the answer to both. Yeah. So if you have a shared account for example like an admin account. I have my account open at any given time on multiple browsers. I'm not sure because I'm one person I wouldn't be actually making an annotation at the same time so that might potentially muck it up. But we can we can dig into that a little bit further, but you can have, you know, obviously as many accounts as you like from the from the publisher side. It depends on you know what your what your use cases. Excuse me. So if you want to maybe detail what you're trying to do what you hope to do a little bit more we can tell you. There shouldn't be any issue. I mean, I don't know that it would be recommended it would be a very specific use case to use the same hypothesis account, and at the same time in multiple places. But there shouldn't actually be any issue with that because the way that hypothesis works in its kind of client server architecture right is each person each, you know, human who's logged in using an account with a particular document is kind of like kind of in their own little field and so the two humans could be logged in with the same account in different places and and saving annotations to the same account theoretically so that should work if there's a use case for it. So do we have any other questions we're happy to to converse more if anybody has questions. I will say one thing we didn't cover in this webinar but I've mentioned in other webinars before. There's a lot of publishers who are using hypothesis for internal workflow solutions so springer publishing for example, we're launching a new ebook platform, and they wanted to make sure that their XML was well formed so they created a group that had their production team and their proofreaders and they uploaded half of the chapters I think was 4000 chapters, and they made annotations in that group for anything that they thought needed to be changed on top of the HTML they made 10,000 annotations which sounds like a lot but if you think it's 4000 chapters that actually sounds like it's pretty pretty good HTML there. There's a lot of articles of writing up a little white paper about that and American Society for microbiology was moving a number of their journals from one part of their platform hose to another. And they knew that a number of their landing pages would need to change as a result. So, rather than printing out the websites and marking them up with stickies and pen and giving them to some for colleague to follow up on they created a group in editorial. They asked each other questions right on top of the websites noted links that needed to change. And then they were able to, you know, include that colleague in the group, and they could take care of those things and they could get a nice handle on where they were in that process so if you have thought about using Hypothesis for an internal work what project that is the private group functionality so you know you don't need to work with us but if you want our help or our advice in terms of best practices we're happy to to support you. One more follow up with Emily is there is there an update. When when there's an update to the hypothesis extension or plug in our clients, like a technical update does one need to redownload it and insult again and the answer to that is no, it will it will automatically update itself. So that the actual hypothesis sidebar and tool that you used to annotate will update itself and the same is true if a if a publisher has Hypothesis embedded or a website has Hypothesis embedded in in their website. They won't need to, you know, change things on their website in order for users to get any new updates to the actual client functionality that they used to annotate. Great questions Emily, it looks like you're, you're hard at work using it already. That's great. Emily can participate in the next webinar. Yeah, we'll have you present Emily. Well, if that's it. Thank you guys so much for your time and attention today. I'm very excited to be here with you. And shortly the video and slides will be added to the the blog posts that takes care of this webinar. And if you'd love to, we'd love it if you'd share it out with other colleagues and if you have other questions I'm Heather at Hypothesis. So please do reach out. We have an open Slack channel that you can join. You can follow us on Twitter and if you have suggestions or ideas we'd love to hear from you. Thanks everybody and have a fantastic rest of your day.