 Welcome to the PressBooks product webinar. I just wanted to start with a couple of general reminders. And they are that there are lots of different ways that people can get involved with or support the project. So those are listed at pressbooks.org support pressbooks. I'll drop a link here, making sure everybody knows about that if they're interested or curious. A second thing is that there is a, there's a community forum for open source users. So many of you that come from the open source host self hosting world already know about this forum and probably heard about this on the forum. So if you go to pressbooks.community, you'll find the open source forum. And on that open source forum, there's also a private group for our educational clients that we call it a community of practice for network managers. The third thing I wanted to mention is there are a number of guides that we maintain for pressbooks. You may already know about them, but if not, I'm dropping those in the chat. There's a end user guide that's huge. There's a network manager guide for people that might be in that kind of super admin or network manager role. And then we also have a YouTube channel with a bunch of tutorials and videos. So those may be helpful depending on where you're at and what your needs are. And the last thing I wanted to mention is no matter who you are or what your needs are for pressbooks, we're always interested in open to new ideas. So if you want, or if your users want, anyone can contribute new ideas. We have a repository that's set up in GitHub where new ideas can be shared. GitHub may be new for lots of people. It was certainly new for me a few years ago. So I'm gonna share my screen now and show you what that looks like and how a person might want to use that. So here is the ideas repository for pressbooks. And we say here, do you have an idea for pressbooks you wanna suggest to our team? Please open an issue. So one thing that you would need to do if you haven't already done is create a GitHub account. They're free and you can do that. I have a GitHub account, but if you didn't have one, it would look like this. You'd say sign up to GitHub and you would sign up to GitHub. Once you're signed up or signed in, okay, then you come back to this ideas repository. So let's say you're in the, and you'd come to this little tab that says issues and you can see there's a whole bunch of issues that people have suggested for us and they have all these colorful labels that I have replied and we put them into our backlog. Many of them, like you can see, we have 212 open ideas and 73 that we've already implemented and built. So you could add a new issue or new idea here. You'd enter a title, my great idea. And then we have a little prompt that says like, there's a template basically and we ask you to use the template to fill in your issue. Once it's done, you would just click submit new issue and then I would see that as the product manager and we'd take it to our team and we'd put it in our backlog priority and figure out how we can build it. We may have a back and forth or we may have a conversation. If you're curious to know what people have suggested in Pressbooks, you're always welcome to come look at this public list of ideas and add a comment or add an upload or just let us know what you think about some of these ideas and that often helps us in deciding what are people really interested in and what should we focus on building next. Of course, there's other mechanisms for you to tell us that and we try to listen to however you do it but that's one way that you can share with us something that you want us to do or an idea you have for how to make Pressbooks better. So this is just general reminder. Some of you have already seen that. Many of you may not have so hopefully that's helpful. The next part of the meeting I wanted to just highlight and show you some recent features or new features that we've added in the last several months that you may have missed. So I'm gonna go back to share my screen and I'll talk about them in order. So in the agenda, this is that new features part. So many of you have been using H5P. So H5P, if you want to install it with Pressbooks it's a WordPress plugin. You install, you activate it in a book and then you can create H5P content. So for example, here's a book that I have and you can see I've made 35 different H5P activities in this book. I can embed those anywhere I want in the book. People have already been doing that and if I were to clone this book the H5P activities would come along, which is very cool. But up till now there hasn't been a way for a user to visit a single page and see all of the H5P activities that exist for a given book. And so what we've done is we've made what's called the H5P listing page. So if you were to simply append the H5P dash listing to the URL of any Pressbooks book running a recent version of Pressbooks you would see a page that looks like this. So here for example is the H5P activities list for this particular test book. And I'll drop in the URL. Hopefully we won't cause problems if you all visit this at the same time. So here I can see, here are all the activities that is describing the ID, the title. And if I wanted to see the actual activity I could see it. Oh, that's interesting. I could also grab the reuse. I could copy the content or download the source file. So it's a nice one page listing of all of the H5P activities in a given book. For very large books with lots of H5P activities this page may be a little bit unwieldy which is why we hide them all initially. It might cause your browser to kind of take a while to load this all because it's a pretty heavy task. Or I could also show them all and you'd see now they're all visible and I could scroll down through them. It's a cool new feature. We'll be improving and refining it but it's new. Many people don't know about it and that's hopefully helpful for some of these cases that you have. Another new feature that we added not too long ago was the ability to add many users to a book at once. This was particularly helpful for, let's say you're a network manager and a whole class wants to write a press book together or you're an instructor and you wanna add 20 of your students and you have a list of emails. If you're in a book dashboard and you are a book admin or a network manager you should see this bulk add button under the users interface. So there's the old way to see your users and you can also add users one by one. You can add an existing user or a new user but you should also now be able to do bulk add if you have the right permissions. You would just add a list of people by their emails. So I'll say steelpressbooks.com, Carlos at pressbooks.com, Taylor at pressbooks.com, Amy at pressbooks.com. These are all people I know won't mind. So then I'd say, what role do I wanna give them initially? I wanna make them all authors in this book and I'm gonna say add users. So what pressbooks is gonna do is it's gonna say, these four people we already found in the network so we added them. Amy's brand new at pressbooks. She didn't have an account so we invited her and now if you look at my list of users you'll see Carlos and I can sort by, let's say by authors. Here are the four new authors I just added and I'd be like, you know what? Let's actually upgrade them, let's make them editors. But the book add tools a nice helpful way to add multiple users to a book very quickly. Another thing that you can do now are in limited ways you can do something called a short code within a short code and we're gonna be working to expand this in the future. But here's an example. In pressbooks, when you make a footnote it's constructed as a short code. When you enter LaTeX, one of the ways that you can do that are LaTeX is to do it with the short code. So in my editor you'll see I have this footnote short code and I've also added a math expression using the LaTeX or LaTeX short codes. So if I were to preview this or actually use a saw published we now have a tool or process by which we will run the short code for certain short codes inside of other short codes and it will work across all formats. So this was a new feature and now you can see all of my math is being rendered with the math jacks tool and it happens to live inside of a short code. So that's a new feature. We'll be expanding that and making other short codes possible inside of other short codes. And another thing that we did, it's pretty minor change but it was annoying to lots of people. So you'll notice when you're entering book info this field is huge, right? And this save book information used to just live up here. So let's say you came all the way down and you'd entered all your information and then you said, okay, great, I'm done. I go to another page and you've forgotten to save it. Now the save button you can notice it just isn't a fixed position wherever you scroll on the page, there the save book information is. So hopefully people will forget to save metadata and changes less frequently because this button is now fixed for you in that particular view. Okay, another thing that we added was something that we added to the editor. Many people or some people are working in languages that display the text right to left rather than left to right. I studied Hebrew when I was in college, for example. So let's say I wanted to do that in a book. Let me go to the test book. I'm in the editor, let's just go to this chapter. I don't have my keyboard set up to type in Hebrew but what I would do is I would say, let's say I want this paragraph or this text to be in Hebrew. From the formats choice, there's now an option that says right, right to left. And you'll see, like if I had my keyboard set up it would be right to left text and the punctuation you notice went here at the end. And so this will automatically help you, those of you who are entering language and right to left text, you just select this text style, I'm sorry, from the formats option and you can switch, oh now it's left to right. Actually this is supposed to be displayed right to left and you can do it that way. So that's a new feature that we've added to make it a little bit easier to use right to left languages from that format editor. And then the last thing that I'll mention, I can't show you all of them but we had a really positive recent work with the University of Washington. So we did a big accessibility audit and filled out a big VPAT, which is a accessibility template. We worked really closely with people from OCAD University. There's a group called WebSavvy that works on accessible web stuff there. We hired them to help us with the VPAT and do a full accessibility audit of our platform. And we did that initially. And then people at University of Washington went through and did an even deeper dive into accessibility for the platform. And they noticed a bunch of bugs or issues for us to fix. And we worked through and fixed the majority of them. And a lot of them have to do with keyboard accessible fixes for the admin interface. One example that you'll see is this top nav bar. We've improved the keyboard accessibility and I'll show you right now by navigating this with my keyboard. So I've just tabbed into it. I've clicked enter to open it. I can tab through into the next field. I can open and close with enter, open and close with enter. You'll notice now everything has an unique link. And also here, if you had a lot of books, you probably noticed that it went off the end of the page and it was annoying. We've added an overflow bar so that it scrolls. So now if I'm scrolling through, I have way too many books here, but you can see I've been able to scroll through the books. These bottom books are still visible to me and can be accessed with the keyboard and maybe visible there. Yes, Amy, I'm sure you will as I will. And you can notice that everything in this is now keyboard navigable. And there was a few places that we were falling down on that before. Another thing that we've done is we've made sure that the, if you enable book downloads on your homepage, so let me find a book that does this. I think this one does, but I'm not sure. Okay, great. So this tool right here is a book download bar. This is also keyboard navigable. So if you enter, you open it up and you can tab through your choices and you can tab back and you can close it with the keyboard. So that wasn't fully keyboard navigable and in an obvious intuitive way, and now it is. So there's a handful of those kinds of issues. A lot of them feel probably minor and when you read the bug notes, but for users of assistive technology, we think they'll make a big difference. And there's been at least a dozen or so of them in the last few months that we've done. We're aware of a few more that we're working to fix and we hope to be able to give you more positive updates in the future. If you become aware of something that causes accessibility issues, please report it to us. File a bug or make an idea in the press books repo and we'll fix them as quickly as we're able. So those are some of the new features that we might have missed. And I want to pause there and maybe take any questions or people want to ask us anything about any of the things that I've just demoed or shown. Great question. So Amy in the chat asked, is there a way to get the H5P activity list from the book or should people add the characters to the URL? Right now, Amy, it's kind of like an Easter egg. We haven't added it to the interface anywhere. You have to know the URL. We do expect that we'll, as we build and extend the feature in the future, we'll probably make it, we'll figure out some plan to make it visible or some way to surface that more easily. Right now it's sort of, if you know about this URL, you can go there otherwise. No. Okay. Now I think we're going to get to the part of the meaning that everybody probably came for. This is the big exciting projects that we're working on now that we hope to be able to unveil and release in the near future. So there's two and the first of them is something that's been in the works for a long time. I think probably the seed for this idea came from a conversation I had with Christy Jensen, maybe like three years ago at a UNISN summit. But the idea is we want to make, maybe others of you had the idea independently, but the idea is we want to make a single press books meta directory, which would be, it'll be a refertory essentially. But the idea is every press books network that has, every known press books network does have an API. And from that API, we can make calls on that API and find out metadata and information about all of the public books on that network. And so what we're building is both a database or a repository or backend that will store the metadata and update it regularly for all of the known press books networks. And then we'll be building a front end on top of that, which will allow you to search to filter and find quickly by whatever, by a number of criteria, any press books book in the world that you might want to find. You'll be able to filter by copyright license so that will help you identify and clone things very quickly. One of the problems in the press books universe right now is discoverability. And we think this will go a long way towards helping solve that problem. And I want to show you, I can show you a little bit of like in progress work that we're doing on this. And hopefully we'll have an even better update with a cooler front end at next month's meeting. So what I'm gonna share with you now is my screen here. And this is a tool that's called Algolia. We have an open source license for this. And Algolia is the technology stack that's powering this. But what we're looking at here is we have an index. And in this index right now, we pulled in 512 records. So these are JSON blobs that we pulled in from the API. And for example, let's look at books authored by Steel. So this is a book that I wrote. It's called Steel Test Book New Title. Written in the language English, the author is Steel. The ISBN, I entered a fake ISBN, so I wrote fake. And we've grabbed all of the metadata for this book. And you can see there's lots and lots of attributes available. So there are tons of metadata that we're pulling in and storing in this big database here. And we're gonna pretty soon, we'll have the public metadata for every public book on all known press books networks. And then the next thing we'll do is we'll do something like this. So I will, this is a very rough hacky demo. There'll be something much better at the next meeting. But the idea would be any one of you would go to a website. We're thinking it will probably be pressbooks.directory. And you would see a website that looks like this. It says, hi, welcome to the pressbooks directory. Here is a searchable, filterable directory of public books published across several pressbooks networks. And you'll see a card. It will look much different, but it will be a card that would have the title, the cover, metadata, and a bunch of different fields of interest that help you know whether you're interested in this book or not. And you would see instead of 512 results, we expect you'll see several thousand results. And you'd have a bunch of, these are some examples, but there'd be some faceted search things where you could search by author. You could say, I wanna see all of the books that are clones of this one parent book. Oh, cool. So I can see my book has been cloned five times. And here are some clones that it wasn't aware of. And these are the interesting derivatives. I may wanna look at those and see if there's something based there. I could also say I wanna see everything that has a CCBY NCSA license or whatever. But that's the basic premise of the basic idea. We plan to make it beautiful, we plan to make it useful, and we plan to make it quickly. So we've built much of the backend and the Fetcher technology. And the task that remains for us in the next month will be to build the front end and to make this publicly useful for you in the near future. So that's what we're planning. And there's a lot of things coming for that. We have a spec. If you wanna follow along with our progress, we'll be posting some of these updates in our GitHub places. And we'll also have a meeting like this at the end of next month in which we hope to show you a prototype or a version one that's ready for public use. I'll pause there and say questions, comments, things you wanna ask about or talk about or that you might want to know more about. I had a question, Steele. Sure, Jeremy. Jeremy. So will that inform and forgive me if I don't phrase this question correctly, but will that information be shareable with others, other aggregators or databases so that they can filter by press books books? Yes, so that information already is shareable and this is why I guess the API is a beautiful thing. But yes, so right now we have a public API, a rest endpoint, and anybody can query and use this metadata and information in interesting ways. Lillian may not be prepared to talk about it, but eCampus Ontario, for example, already does, NBC campus, already do really powerful things with the Pressbooks API and this metadata. And this catalog is just one example of one of the many uses you could make of. Metadata provided via the API from public press books books. And Jonathan, there's a comment in there. Why did you make the expression of string rather an express? Yeah, so the prototype that I'm showing you is very dissimilar to what it will actually look like. That was just a very rough proof of concept, but we plan to make different choices when we build the actual thing. So don't judge what you saw, don't judge the actual product by what you saw in that very brief demo. So for faculty looking to document influence on the field for RPT. Okay, so I think this is a pretty complicated one. There's a couple of things that you can do in Pressbooks right now that help you know how widely a book is used. So I think many of you are already aware that you can connect your network to Google Analytics, for example. And again, eCampus Ontario, BC campus have done some really cool things that are Google Analytics plus. We should probably have a webinar where Lillian and Josie just show off these provincial systems and what cool stuff they built on that. But the idea is, and let me just show that to you. It's a bit of a sidebar, but it's probably still helpful. Okay, so in Pressbooks, as a network manager or as a super admin, you'll have the ability here under, if you're hosting with us, you'll just see it here, Google Analytics ID. If you're not, you'll see it under this Google Analytics piece. But in any case, you enter the tracking ID or the dashboard ID for Google Analytics dashboard. And then Pressbooks will send Google Analytics statements. So this will include things like page hits, page views, number of times an individual file was downloaded, which book and what format. So those are all that kind of information as a network manager. You can collect and you can share with faculty upon request or you can, that's a third-party service. You can do whatever you want with it. There's a chapter in our guide that talks more about this, how to use Google Analytics, if that's something that's of interest to you. And it sounds like that's probably a top order of my app. Can't do two things at once. Okay, so here's our guide chapter. This is how to do that. How to start with things in Google Analytics. I am not a Google Analytics pro, but I guess I'll need to become one to do a webinar in it. And I'll probably ask for other experts. So please, if you wanna be a guest expert on that webinar, let us know. So that's one way that you can track impact is by looking at how frequently this resource being viewed, how often are these files being downloaded, et cetera. The second thing though is, how often has this book been cloned or how many adoptions have been made? And it's difficult to know that exactly, but we do think that through the directory, you would be able to, you would at least be able to see how many other public books are based on Source A. So you could certainly, it'd be an easier way to find out, is this book a parent? And yes, these are its children and how many children does a parent have? Now that's probably not super high quality information without more context, but at least it's a start. Right now, for example, it's difficult to know how many children your book has, but you certainly would go to a child and see, oh, it's based on whatever, so you could track it back to the source that way, but you'd have to know the child exists in the first place and the director should make that problem easier to solve. Yeah, and Josie mentions there are other kinds of ways to track page views other than Google Analytics, for example, Metomo used to be called Pwik, it's an open source tool, and we're looking into some other open source, less invasive analytics tracking things that we might make in the future, but nothing on the immediate horizon. So thanks, there's some really interesting conversation in the chat for this. So if you wanna follow more of an analytics, check out the chat, I would say. And I've made a note that we'll have a future webinar on the topic. So I'm wondering, Steele, some of our public books maybe aren't really meant to be entirely public. And we also now have an unmediated version of press books, and so people may be putting stuff in there and making them public that wouldn't necessarily be what you would be expecting to find in a directory like this. Yes, so there's a couple of things that this is something that I will know. The quality of the information in the directory will only be as good as the quality of the metadata entered at point of creation. So as network managers or as super admins, one thing that you can do to help improve the quality of the directory is to use some of the tools available to look at which books on my network are public. If you make a book private, it will vanish from the directory. If you make a book public, it will appear in the directory. If a book has bad metadata in your point of creation, it'll have bad metadata in the directory, but as soon as you update it, it will be updated in the directory. We're gonna run a cron job every, I don't know how frequently, but multiple times an hour we expect. So that directory will be pretty fresh and we will respect whatever decisions you and your network users make. If they make a book private, it will then abandon it and we'll remove it from the directory. So that's the first step of kind of filtering and quality. We may decide that we need to do other kinds of curation once we get it up, but we'll have to see that. I think once we see what comes in, we haven't pulled everything in the directory yet and we'll kind of assess the kind of signal-to-noise ratio at that point, I expect, speaking frankly. What if people don't, what if people want to make their book, whatever it is, public, but don't want to be included in the directory? We'll probably need to add that as a feature like an opt-out at some point. Yeah, so certainly we could, we could choose to display only public books in a catalog. We haven't made that choice yet. So those are really feature ideas or discussions we want to talk about in the future. These are great ideas and we'd love to have them under consideration. But our plan for now is we're going to grab and display the metadata for all public books. Okay, then the next kind of update is going to be more of a textual description and less of a screen share, but we'll probably have something to screen share for you next month. And it's one that many of you have been waiting for for a long time or have been asking about for a long time. As many of you know right now, PressBooks has an LTI provider plugin. It's an open source tool, but it's also a feature that's comment on some of our hosted networks. What the LTI provider does is it transforms PressBooks into an LTI provider, which means that it can create key secret pairs in the old version and connect to a learning management system so that you can bring secure content from PressBooks and display it in the LMS natively within a secure LTI launch. That's what we do right now and we use a standard called LTI 1.1, which was the most recent standard until fairly recently. IMS Global maintains the standards and they released a new version of their LTI specification. It's LTI 1.3 and it introduces a pretty substantial change in its security model and some other things. So we have been working very hard on upgrading our current LTI provider from 1.1 to 1.3, which will use a different authorization process and flow and et cetera. If you'd like to see that, I can show you, I guess, this will not be that interesting, but you can at least see on the back end, instead of the old LTI consumer thing, you'll see a new configuration screen that looks like this. This is all the kind of information that your LMS will provide on the 1.3 security model. The LTI 1.1 was significantly different and so there's a bunch of back end changes and we're feeling really good about our conformance with the 1.3 spec for replacing existing functionality. So fairly soon, we will be able to replace all of the LTI 1.1 providers with an LTI 1.3 spec and I think people will be happy about that generally as long as your LMS supports it and most LMSs do. The second thing that we're doing though that we'll be working on that we're just beginning work on is many of you have wanted to also exchange information with the LMS like grade values or student performance on H5P activities for a chapter or a piece of content and press books with the LMS. The previous LTI specification supported a very primitive thing which was basically a single value as a percentage and you could do that through an outcome service. The LTI 1.3 spec has something called LTI Advantage and it supports assignment and grade services which lets you do a little bit more granular communication information. Our plan is to add support for grade passback and for H5P activities to press books in the very near future. And the idea would be this would be for hosted customers, this would be a paid add-on. It would be priced much lower than the homework courseware platforms that you get commercially and it'll probably, the initial thing would be we'd price it on a per student connection that the institution would pay for and it would be discounted based on volume. I don't, this is not a sales call so I don't wanna go into the sales details but many people have been looking for this feature and been excited about it for a long time. We're excited about it, we're excited about developing it and we'd likely have something more to show you in terms of a demo or a prototype at our next one of these product meetings. I know there was a lot of talking so I'll pause there and ask, take a lot of acronyms as well. Take questions or comments or feedback here. See there's a question in the chat from Jonathan. He asks, are there non-LMS Floss LTI consumers? Good question, I don't know the answer to that question. There are two LMSs which are openly licensed or most of the three LMSs which are openly licensed. Those are the, usually when I'm thinking of LTI consumers I'm thinking of learning management systems so the open source ones would be Moodle, Sakai and Instructure's Canvas. So in the LTI world, there is an LTI provider and an LTI consumer and LTI is an acronym so I'm probably explaining things that many of you know but I saw a question in the chat. So an LTI provider and LTI consumer. LTI stands for learning tools interoperability and it's a way to take a third party tool and make it work, plug and play with a tool consumer. In the ed tech world that we work in, if you're working in higher education you probably have a virtual learning environment or a learning management system depending on how you call it which is the place where students take their courses and blend it around my courses. So it might be Desire to Learn or Blackboard or Moodle or Canvas or Sakai. The LMS is gonna be the tool consumer and there's a number of ed tech tools that are say hey we made this really cool tool we want you to use it and we may want you to buy it or we may want you to pay for it or we may want you to do whatever. We made our tool and it's now standard compliance so you can plug and play with any LMS. The plug and play piece is LTI. So the third party tool will be the LTI provider and the LMS will typically be the LTI consumer. Jonathan's question was are there free and open source tools that are LTI consumers that are not LMS's learning management systems? The answer is probably the best way you'd figure that out I would say would be you can go to IMS Global's website and they have a list of certified LTI tools that conform with the LTI specification that have been certified. And you could look through that to see whether there looks like something that's an LTI consumer that's not a learning management system. So that's my long-winded answer to that question. It just seems like it seems like it would be for like individual personalized learning or LMS is the things that large your educational institutions run and for a really lightweight solution that nevertheless collected all of the scoring on some HIP and a press book instance it'd be nice to have something that would conserve those scores. Anyway, it was just an idle question. Thank you, Steve. Yeah, yeah, okay. Thanks, Jonathan, yeah. So my short answers, I don't really know the answer but I explained a lot of things. Anyway, typical, huh? Okay, any other questions about LTI or what we're planning for the LTI upgrades? If not come and see the next month's product update we'll probably have more substantial things to show you on both of those two big projects. They're underway and so far it's been kind of the unsexy back-end work and there should be some front-end fun things to show in the near future. All right, the last part of the meeting and we only have about five or six minutes but it's a community roundtable and this really is a chance for if any of you have projects that you are working on related to press books that you'd like to tell others about or if any of you have questions or things that you wanna bring up either to talk about with one another or to talk about with us, it's an open forum. If you'd like me to stop recording, I can do that or I can just chop this out of the recording at the end if you prefer. Time is yours. I don't have a specific project but I was curious if anyone, I'm contemplating a project. So I was curious if anyone has done any experiments with text that was originally encoded in TEI and then having the output be published in press books. So the test that I was doing was using the, I think the XSLT through oxygen to produce an HTML and I was just curious if anyone else was hanging around with that type of thing. Alison, would you be willing to give a quick primer on some of the acronyms you use in case people aren't familiar with TEI or XML? Yeah, so TEI is the text encoding initiative. So it's a coding language that has been developed over the last, I guess, couple of decades for digital humanities. So it's a way of encoding text, show the meaning of then the structure of a document along with like further than just heading. So for example, we're looking at a play right now. So the coding would be able to say, this is the speaker of a line. This is the stage directions. This is what kind of stage direction it is. So just a lot more information embedded in the coding itself. And then I actually don't know what XSLT stands for. It's XML style sheet transformation. So we have transformed the XML to make it look different, kind of like what you do with HTML, I think. Yeah, so then taking the TEI and basically turning it into, in this case, HTML with some styling attached to it. Okay, that's a great question. Does anyone have experience with this? I'll jump in and offer a little bit of it. So this is actually something I was actually just working on this last week, Allison. So I'll share, I'll screen share here. So there is a really cool book that was published. It's had several editions. It's called The Discipline of Organizing and it's a real important book in the library information studies field. It's all about how information gets organized and it's gone through all of these different editions. They had a very complicated XML, HTML schema that had been built and had been kind of clunky to build and maintain and they wanted to bring it into press books. And so it now exists in press books, but if you look at the actual book itself, you'll notice if I would inspect the page source, this is probably a little on the weeds, but you'll appreciate it, I think. And you'll see there's a lot still of these extra class extra class elements that have been applied and they have these extra ID elements. This is all legacy from their initial XML or their, I don't know if it was TEI exactly, but it was TEISC in that a number of these elements have additional classes and tags attached to add extra metadata inside of the text itself. So for example, this chapter here, this is a text box and this is a site, they have a class called sidebar title that they're targeting and they're styling and it's sort of a hybrid project, but it's now all in press books and there was some pretty gnarly transformation work that was done and I could connect you with the people at Berkeley that did that transformation before bringing into press books. But yeah, I think it was a couple of a couple, maybe dozens of hours figuring out how to get their source into something that was malleable in HTML-esque and if they could share that information with others to save people time, it'd be great. Yeah, thank you. So email me separately and I'll try to connect you, Alison. All right, awesome, thanks. Anybody else have anything they wanted to bring up in the open roundtable forum in our last minute? I'll just quickly mention, this is Jeremy, one of our physics professors who cloned a couple of the open stacks books into a press book and added some other things was working with Ed Finney for the testing. Ed Finney is a NSF, National Science Foundation test platform that works closely with open stacks and when he put this together this winter, pretty much to have a login that you could have the students log in and take the test. It was just a link in press books and they would go out or whatever. And apparently, and I can't say too much about this only because I haven't been involved directly in these discussions, but the professor is talking with Ed Finney to come up with some solution that will more fully integrate the Ed Finney testing into press books. I don't know how they're doing that and there may be even a way to do that already, but that's sort of happening. Awesome, Jeremy. I'd love to know more about that and see if there's some way we could help. I think that'd be really useful. So thank you for bringing that up and that's something for us to discuss further too. Sounds good. We're at time everyone. Thank you for joining us for this first meeting. Hopefully the format felt good and appropriate to everybody. We'll try to do this every month and feel free to join us and bring a friend next time. Appreciate your time and attention. We'll post, we'll put transcripts on the recording and we'll try to post that within the next week or so. Good to see everyone. Spaces stay healthy, stay safe.