 So welcome this morning or afternoon based on where you are. This is part of a series that we do here at the Center for Open Science that, in effect, is sponsored by one of our project's OSF institutions, which is a product, a suite of features on the OSF for research institutions of all kinds. And today we're going to highlight a diverse set of collaborations across open science that really involve a lot of different parties. And so let's take a look at some of these that we're going to have sharing today. Whoops, too far. So the PressQT infrastructure project is going to share Natalie, Noel, Rick, and Sandra. We'll hear a little bit about each of these individuals and projects here in just a couple of minutes. The Open Scholarship Knowledge Base, Marcy Reedy, will share a little bit about that. The Center for Information Technology and Architecture, Adrienne Rigabello is our guest from the Center. And then the Center for Open Science ourselves, as the host, I will wrap up, with a little bit of OSF institutions information. And one of the really exciting things about working here at the Center with OSF institutions in particular is that while these technology, the products that we work on is obviously a big part of what we do. Another really huge component of our work is working and speaking and sharing with really neat projects and individuals like these. So really appreciate having the opportunity to have them there, them come and join us today, but also just generally being able to host activities like these is really a pleasure. I'm going to give you the 90-second version of what the Center is for some of you who may not be as familiar with the Center and some of the things we do. Generally, our mission is to increase the openness integrity and reproducibility of research. And obviously that's a big, huge, broad goal with lots and lots of culture behavior change involved. And so we're structured to really take on that mission from three directions. We have a policy team that works with publishers and funders and many other bodies to create or encourage incentives for change. We have a research team who studies things like the current incentives or new incentives or new projects to see if those are actually encouraging the work that we are hoping, the changes we're hoping to see, and then infrastructure projects that I myself worked with that builds technology to enable those things that we're really asking folks to embrace as culture change. So with that, part of what I'm tasked with is not just sharing what OSF and what COS is doing, but really great practices across open science with our partners globally. So really, really thrilled to have some of our participants here today, just a few of the very, very many that I would love to highlight at some point. So to start with the PressQT project, I'm just going to share a little bit about their project, which itself is a technical and cultural collaboration. So Sandra, you want to take it away? So do you see my screen? Yeah, we sure can. Great. So I can start. So yeah, thank you very much for the invitation. I'm Sandra Gazing. I'm one of the co-PIs of the PressQT project. And I hope you still see me because I get messages that I cannot access the microphone. You're still here and see me? Yep. Error messages during a talk. Great. We are seeing your presentation mode. OK. Swap here. You know what? Let me, instead of trying. No, I didn't say in. Oh, OK. I know I have another slideshow in the back. I maybe just keep it as a full, so let's say, a presenter view. No, I didn't want that. Give me one more five seconds. Let me slideshow. If you could do the play from the press. I got it. I got it. So yeah, and Rick is also on the call. He's one of the co-PIs of PressQT. And Eric mentioned Natalie and John are co-PIs, Noel and Justin developers for the PressQT project are both on the call. And Brad is also a developer who couldn't join today. So what is PressQT about? If you look at the research data management and with the preservation landscape and the science gate base and workflow-enabled user interfaces, we have these really beautiful solutions. But sometimes they're not connecting to each other, like also apps and PressQT is there to build bridges between systems. So the idea is really we got first a planning grant and then an implementation grant to collaboratively design, develop, and connect repositories and data and software preservation quality to increase the quality of software preservation and data preservation. So if we look at the timeline, so the concept is that we look first at the community we asked and so the big survey, we had workshops to get feedback, how the tool design should look like. And then we looked at the different tools and services we would like to develop and co-develop this partners. And really on the stakeholder side, we looked at the main researchers, data curators, repository managers, librarians, software developers, workflow to develop. Yeah, you can see the list. And I hope one of these expressions or more you feel also targeted by, that this could be interesting for you. And you're one of our partners with OSF and the concept is that these are not standalone solutions that we are developing, but that really partner systems and services can be easily integrated. So if you look at the nice little circle, so we have a core team, we have partners and we have extended community being able to really use this and the, yeah, user centered open design and collaborative development is really important to us. So we have the stage that we have a couple of services. So additional partner system can be configured via JSON and Python functions. We transfer data in bagged format and all the metadata is added in JSON. We do already fixity checks, keyword enhancement we started this testing for fair and fair is especially also interesting, not only because it's a big topic at the moment, the community, but it's also, what does fair really mean? How can you test it? That something is really findable and, yeah, interoperable. So, and we have this pluggable configurable architecture. It's Vestful web services. We are going to APIs and a consideration of diverse structures and why are we doing this this way? Because of feedback and also the idea is that nobody has to leave their working computational environment that has additional features. So, and to see, for example, we look at different things. So we have the current target integrations include OSF, create and D as a federa derivate. We are using it, not add M, GitHub, Synodo, GitLab, fixed share. And we can search there. We can download, upload, transfer the upload and transfers and work at the moment at current and D. And we support also either services like easy or keyword enhancement. So I'm happy to go into more detail if you have questions about easy. But for the moment, I would say, I give it to Justin to make a short demo. And I start, I stop sharing the screen. Just don't, you probably can take over. Sounds good. You guys can see the Presquiti interface here. Yes. Okay, great. So let's do a transfer from OSF to Synodo. For Presquiti, we use API tokens from each target as validation or authentication. So we can see here the OSF resources I have for this particular user is just the three there. For the demo, let's transfer this one. You can also click through and see what's inside every project. You can download individual files, just folders, upload to folders or different projects, create new projects. For this demo, we're gonna transfer this COVID-19 project to Synodo. We'll use our Synodo token there. In Synodo, I just have this one project, which you can see over here. I could transfer into that project by selecting the folder. For this demo, we're just gonna create a new project. It'll ask what you wanna do with duplicate resources, not really relevant for a new upload, but if you were going in somewhere where it found a file with the same checksum, it would ask whether you wanna update a file or just ignore it. And then we have our keyword enhancement feature built into the transfer process. So what this will do is it will gather keywords over here in OSF. You can see in this project, we have animals and water as some keywords. We run that through a SciGraph API, which offers us enhancements and we can go through and select ones we wanna add to our project. So we'll select those. And then before we transfer, we just give you a few details about what is gonna take place. So we're gonna transfer the resource to Zanotto as a new project. It'll create a metadata file at the top level. And since we're also doing keyword enhancements, it will write a metadata file to OSF as well, just to let you know how those keywords were added to the project. It says where the keywords will be stored in each target. OSF only provides checksums for OSF storage files. This particular project just has files in OSF storage. So that's good. And COVID-19 will be written in bagged format as a zip file. Now this is specific to Zanotto as it's a finite target. If we were going to say GitHub or GitLab or transferring something to OSF, they have infinite structure capabilities. But since Zanotto is one top level project that contains files, we have to zip up everything we're bringing over. Just to make sure that that hierarchy is consistent with what it was at the source. So this will download. It'll create a zip to be passed over to Zanotto. Once it's successful, you can see we updated over here. We've got our new Zanotto resource, the keywords that were added. So if we refresh our OSF project, we can see that those keywords have been added. We've added this metadata file that has information about the idea of the action that took place when it took place and the keywords that were added based on the CyGraph enhancer and over here in Zanotto. We've got the COVID-19 project. You can go through and add all the information that Zanotto needs before you were to publish. This metadata file is based on the zip that was created on the PressQT server. And if we open the zip that we've uploaded, let me just move my zoom stuff there. This metadata file has information about each individual file that came from OSF and then all the files are inside OSF storage. And we can see that all the files pass the fixity checks and the transfer was successful. And that is all. Thanks, Justin. So the idea with PressQT is that we have shown the user interface which we have for demo projects but the idea is really that it's integrated in your Science Gateway, in OSF, in different solutions that people can really say, oh, I can use it directly to transfer files securely and with fixity checks to another system but also add keywords. And the next, what I said was what we are working at the moment on is really to do fair tests that you can get an idea like, oh, how fair is my data I have already in OSF or in Q-Rate and DR in another Science Gateway like Hive Zero and then you get a hint what could be maybe improved or what do you gain if you put it in the preservation system but you might lose on the fair scale of data. So that's the idea behind it. So, yeah, it helps with transferring data that people don't have to first download in one system and upload in a preservation system but couldn't do it seamlessly and also between different working environments. Any questions for me there? We're gonna go ahead and just go through all of our speakers, Sandra, and then we'll come back and do some questions. So thank you. Thank you, Sandra. And we're gonna now just go right over to our next speaker and that's gonna be Marcie to talk about the Open Scholarship Knowledge Base. Hello and welcome everyone. Thank you for joining us. Justin and Sandra, that was fascinating. Really appreciate you sharing with us. Let me share my screen. So yes, thank you so much for joining everyone. I'm going to put in a link actually. Excuse me, let me get back to the Zoom link here to put in a link to the Knowledge Base. I can do that for you, Marcie. Gotcha. Okay, sorry, as I put the link in, it removes my PowerPoint. So thank you so much. Appreciate your time, everyone. The exciting thing about the Open Scholarship Knowledge Base or OSKV that we're calling it for short. So this is hot off the presses. We're just releasing it now. We're really excited about it. It's a really exciting important time to have this discussion with you on this webinar with really, really recent information. I have put in the link to the Knowledge Base itself. So I invite you to click on that as I'm speaking, maybe click around, browse around, see what you think. I'm just going to go on a high level description to answer some of the most common questions, but the Open Scholarship Knowledge Base was built around the knowledge and understanding that Open Scholarship can be challenging, especially for people that don't have the tools or the background knowledge to really understand. They may want to enter into it, but not necessarily know how to start. So the concept was, let's create a platform that can ease that transition for them. Let's make this as easy as possible, building in an interface where resources were searchable, they were accessible, it was easy to upload and to have a discussion about them and very, very searchable for the people that were working on it. So that's what it is. It is a platform knowledge base that allows anyone that is searching for educational resources to access them very efficiently and easily. This is a list of the resources gathered in collections, as you can see here, to help organize and correlate them into ways that will make it easier for the user, as I was saying, that's coming in to search for these resources. So if we use the analogy of a library, this is an online library collection, the collections are the bookshelves that are there, organized by various topics that someone may go into the library and look for different resources they're needing, analysis, data, education, policy, publishing, reproducibility, research methods to help ease that search. This is an example of a resource that is included in one of these collections. So for instance, if someone was looking for a statistics curriculum and syllabus that they could use to help teach, they could go there. This is learning statistics with R and they could find something to support them. We realized the need for a searchable database like this, you know, years ago, of course, but never did we really anticipate the flood and the demand that we have right now, considering everyone is looking for online resources and everyone is looking for educational materials to support online instruction. So this is again coming at a critical time. Another resource just to share as an example of what you might find available. I'm a Harry Potter fan, so this is an article that's looking at the Harry Potter methods of reproducibility, you know, kind of fun and interesting. So if someone was looking to introduce the concept of reproducibility to their class, they could go online and find this article to share. So I've talked about how the OSKB is an online platform that makes resources easily searchable and it is. But what differentiates it is that it is a lot more than that. It is a very community-based tool. So this isn't just a technological tool that is remote and removed online. Like this is grounded in the community. There's discussions, there's interchange among scholars. It was conceived of and designed by the community and it's based in the community. So we really wanted and we really wanted to serve the community needs. So that is a underlying and non-negotiable principle underpinning the OSKB. These are some of the groups that also are created within the OSKB that enable that interchange and dialogue among the community members. So if we return to the library analogy, these groups of users would be the tables that are assembled around the library, study tables of users and people that were discussing and talking and learning together about a topic. So this is another way to help facilitate the organization of the platform into user groups that have similar needs and are looking for similar resources, have similar questions that they can exchange with each other. And these educators and researchers and librarians and everyone can help monitor their group and make the group usable and the most effective for them. So they can help edit content, they can help suggest content, they can look for content gaps to say, hey, we need more here. And really leave good feedback and input for their other colleagues all around the world. The why. You know, have talked a little bit about this and you know, with the recent demand for online curriculum, of course the why is even more in demand, but we recognize how quickly resources go out of date and they can be hard to find and there are barriers to entry. And talk about this. So we wanted to find a platform that eliminated or minimize those barriers and to really ease that usability for the widest, largest number of groups. Again, this talks about how the interface is designed to make it as easy as possible, the collections. We also have some detailed contributor guides. If you go to the OSKB that really has a detailed list of how you can submit resources. So the options are there submit resources from the web and existing resource or you can author an original resource. And it goes detailed step by step with that. Here part of authoring a resource you can see. And previously the presentation talked about the metadata that went through and keywords searchable. A lot of that is included here. I just included this as a general depiction to kind of get the type of information that we're searching for or that we're looking for when content is uploaded. So of importance is choosing a license. How is this? Is it open access? Is it creative comments? Putting author attributions widely within the work. Again, adding the metadata so people can easily find the resources, tagging the audience members and the groups so that it can be matched to those that were best needed. And all of this is part of what the community will help to monitor and regulate and make sure that that information is accurate and meeting the needs. Here is a flow chart that describes the process of beginning to end. If you're, I won't go into much detail. But interested in submitting a resource of how a user would enter there. They would upload from the portal. It walks you through step by step. But there is a checklist of materials that are acceptable. It's hosted on OER Commons. So following their guidelines, then you check the license, make sure it is open access. You find a group that it belongs to and contributed it. Then it goes to an admin review that looks and makes sure that the material is appropriate for that group. That it is an open license and is properly categorized. And after that is completed, it will finally be published and made available. So with that broad overview, we wanted to give different points for how people can be involved. We really, really encourage you to join this community and be active. Of course you can submit resources. Please join in. If you have your own resources, or if you know of others that you might be able to upload and share with other authors, the broader, the most diverse community we can get, the stronger it will be. Help us promote, though, as could be among your networks. If you hear someone that's looking for educational resources, looking for something to supplement the instruction, please let them know. And critically, consider being a hub or group administrator. That flow chart that I showed where it's a group and admin approving the resources that were submitted is a critical component of the hub. So if you have a couple of hours a week and are interested, we would love you to join our team. So in addition, we are having some training sessions that are going to go into the details of what I did broad-level. The intro to open educational resources and practices and contributing high-quality OER. We invite you to join these trainings and learn more about how the value of OER and open educational resources are and how you might be able to utilize them and how you can contribute those to a larger community. So we hope you will join us in doing that. And with that, I will turn it back to Eric and say, thank you so much for your time. Thanks so much, Marcy. So our last speaker today, Adrian, can tell us a little bit about CEDA. So if you can stop sharing that, he can start. Hi, everyone. Thank you, Eric. Thank you, everyone. I'm really looking forward to see you to participate actually in the OSKB project. It seems really useful and nice. So I will quickly introduce our activity here in the center for the OER. Down in the Royal Academy of Fine Arts in Copenhagen. So basically the project that we are starting to work with with OSF is called Fungal Architecture. I'm going to very quickly introduce it. Oops. But prior to the project, basically I just wanted to show some of the things that I'm going to talk about. The project basically I just wanted to show some context. So basically the goal of the project is to research and provide insights on building a Fungal Automaton at the architectural scale. So it's a European project with four partners of which one industrial, Mogu, and so we have CETA, which I'm part of, Utrecht and Bristol also. So obviously we are based in Europe and just far enough for the COVID to separate us as it's transnational. Just to introduce quickly to have a feeling of what CETA is doing. So basically we are doing what is commonly called in our domain, computational design, which means that looking through material properties, structural, thermal engineering, or different types of explicit datasets that we can get, we are looking at the way how to creatively use them in order to enhance architectural experiences. So for example, such a project involving mathematics, there is obviously a notion that very much architectural, to say, form finding of, I want to add you also, lots of projects in computational design can refer to optimization of resources, for example. This one here that you see involves computational design as computational geometry. For example here, a research on how to actually build those artifacts and then the bottom images, all the way, once we've built it, all the way analyze it, all the way compare the model to the realizations. And just as an example, another project here is looking at the creative formation of aluminum panels, I think it was aluminum, in order to optimize material usage, for example in this case, obviously at the bridge. So talking a bit more about fungal architecture, basically fungal involves mycelium, it's kind of the root system of mushrooms. And it has been explored for example here by the agency, the studio at the living, with 12 meters tower made of bricks. And now what we are looking at is basically making something a bit more monolithic and alive actually. And that's also why we are working with several partners because it's a fairly complex topic. And basically we are also, part of the project is that we are working with nature. So eventually we've non-protectable knowledge in a way. So obviously open source is at the core of the project. So in terms of structuration as I guess most trance organization of a research project, we have different levels of dissemination opportunities. For example, there is obviously a rather big bio design community, biohacking community that already exists. And that is at the time kind of a strategic partner, informal strategic partner to the project and also beneficiary to the outcomes of the project. Obviously among the members also there are collaborations happening even if different partners work on different sides of the project, trainings also that are shared between the different partners. And the framework of the funding that we have, which is always in 2020, the funding is also implying the production of open... I can't see part of the screen, but basically it's open hardware, open software and open data. So it's not somehow mandatory to produce it or to disseminate it within the project, but it should be, to some extent, part of the larger dissemination of the project. So it's a very important both naturally and funding related to the very important side of the project to us. And that's the most relevant image I found in order to explain my feeling about OSF is that we've all these different practices ranging from amateurs doing bio-designing their garages up to the mycology department in Lucrette. We have a very different set of tools and methodologies to walk through. And I find that OSF so far, I'm sorry about the blur, but I guess that you all know this kind of page, that eventually what's interesting is that we're in the same project. So here you can barely see, but I guess that you also have this experience, maybe that with the different components we can segregate the different partnerships that we have with different institutions or even individuals or different communities, which is a very critical point for us in terms of dissemination. And so again, if you started to use OSF, you know that there are quite a long list of add-ons and interfaces that you can activate, enable, both for storage and citation, which are to us very important, obviously, because some members of our communities we use, like GitHub, for example, also from the early description of the activities of our lab at CETA, you could probably understand that we are managing both, I don't know, datasets in front of CSB sites, for example, and also 3D scans and also protocols for making mycelium components, for example. So we have a large nature of the data and we say that we are managing and this is quite critical and something that we find very useful in OSF and the fact that it's allowing us to have this one interface for different communities. Okay, so I'm sorry, it's not a voluntary blur, but here basically if we look at one component, for example, we are using the wiki as a basic to-do list, which is useful for us because then we have also the files that are up to date below, obviously, people within our organization are also access to the different cloud services. And beyond this quite basic feature, something that is also determining for us is the citation. And yeah, I mean, when we are talking about bio design communities, for example, and people that are in places, it can be that people are not always constantly producing academic publications. So this is also a way for us, both in for our activities and also to, I mean, if a non-academic partner would say uses OSF, the person can be cited also in further walks, not only by academic peers. So this is also a very nice integration for us. And I would just like to talk a bit about that very quickly. So basically now we are just into the process of starting teaching activities that are related to our research project, finger architecture project. So for example, I mean, we haven't tested the way of interfacing with the students. Is it view only links? Do they need to create accounts in order to document the projects on the platform? That's something that we need to make sure a bit and hopefully share our insights in months or two. Actually, today with some fellows in the lab, we were talking also about the fact that they're just an optic paper pile for citation management for bibliographic management. So that's another one that could be interesting. We've been talking a bit also very about dissemination metrics that might be also useful for researchers to highlight. And so yeah, I would just like, I mean, it's not really in the order, but the time management of tasks could be interesting because for example, we are using a very simple trade of all, you know, to track our experiments in the lab. Obviously, it comes nicely with the text manager, the reminders that they are there. The fact that we can assign labels and so on becomes a bit visual. So that's something that's in use here and that could be interesting. And the fact that, I mean, you've quite understood that we are doing also something that is both with explicit data sets and with eventually more qualitative or passive data sets in a way, I may say so. So for example, we do have a use for mood ball, for example, like more visual sorting and intuitive sorting of information. So that could be eventually another thing to add in order to have another kind of typology of tools to be interface with. And that's about it. If you have any questions, I would be glad to answer. Thank you. Great. Thank you so much, Adrian. And I just take the opportunity as he just mentioned this. He and I had, excuse me, it talks a few weeks ago about some of these elements that he just called out there. And that's what I'm here for. So anybody, you want to come and chat with me about the things, the practices that you have, the tools that you use, and you could see value and whether they interact with OSF already or not, or maybe they interact by way of press QT or similar tools. Let's talk about it. Cause the only way I can, can improve in those directions is I know what you need and what you use. So please, please do come and talk to me about that. And my contact info will be in these materials that you'll, you'll get later today or tomorrow. Sandra, I see you posted a question for Adrian. You want to go ahead and articulate that one. Hey, cool. Yeah. Thank you both. Matthew and Adrian for great talks. So one question I would have. I mean, this looks fantastic. Interesting. So, so when you said, oh, open hardware, and I only know that we have the situation that people, yeah, like their tools and they want to try it. And therefore, for example, a partnership with hotel, which is a big extension of OSF framework to also be able to start tools. So it's this something you would be maybe interested in that would be dockerized because sometimes the problem is just I come from the EU, you hear my accent. Originally from Germany. So I know how it goes normally with the EU project in that regard. So can you collaborate on, let's say, putting tools and jobs from outside the EU on hardware? That's a good question. I think so because it's not, I mean, there is nothing specified about that. I think it's, I mean, there is no up to my knowledge, at least there is no notion of competitiveness or closeness, closeness, exclusiveness to European partners. And actually it's from our perspective, the community that we are engaged with are located also in the US. I wouldn't say unfortunately worldwide for now, but also in the US for sure. Okay, cool. So that, yeah, so maybe you could stay in contact and talk about a couple of things there that would be great. Great. Love to see things come together right here. That's fantastic. So I do, I have a question for both Sandra and Marcy and I'll start with Sandra here, but you guys are in two phases, two different phases of a similar quest where there is a technology of some variety, but you determined early much to our excitement that it's not technology that you build and hope that people come to it. It's community driven and determined. So what did that look like at the beginning for each of you in sort of shaping what the direction of the product or the initiative was going to be? Yeah. For Preskiti we really wanted to see what the community wants. So we did the workshops, we had in total two big workshops gathering from different stakeholders feedback and really asking questions like what kind of preservation systems do you use? What kind of gaps do you have? What kind of, you know, what do you really need? And it was often very clear that people were like, okay, yes, I know there are preservation systems, but how do I get my files there in a convenient way, for example? How can I increase the data which is available? The other thing was our big survey. So we got 1,400 answers which gave us a lot of insights, what to do. So therefore we selected the features and it was also very clear that people have their own environments and to add another environment means another hurdle. So that was then the idea to say, okay, we are the bridge behind the scenes. But the bridge behind the scenes is hard to show without a demo user interface. So therefore we showed the demo user interface and we are also happy if someone says, you know what, I have the system and I work with it, but I'm fine with working with the demo user interface because it would mean more work on my side to integrate Prescuti. So there's no problem to use a user interface. It's just, yeah, it depends what people want. So that was, we had the surveys and the workshops and went from there and the other thing is an open process, development process, all the partners, everyone who's interested can contribute. So for example, they have every two weeks a community card who wants to join, who wants to give us feedback or say what everyone can contribute. We are, before we are integrating features, we're making suggestions to the partners that we plan it like this, open partners can come back with their feedback or say, oh, they would prefer other features or yeah. So it's a very open process involving all the partners and the community from the beginning. Yeah, that's such a critical question, Eric. Thank you for pointing that out and to echo what Sandra was saying, just really, we had a similar approach and was instrumental in launching the OSKB. We, as you pointed out, it wasn't so much that we had this idea for a tool and then we wanted to convince the community that it was worth their time and their effort, wanted to start with the community first, discover what they needed and then build the tool to meet those needs. So at the very beginning, we, or the development team outlined reasons why we may fail with the OSKB and one of the reasons was a lack of diversity among the community. We wanted to, above all, make it a very, very warm and welcoming space for everyone. So we wanted this platform and this interchange to have diversity all across it with the ideology and the disciplines that we didn't want it to be pigeonholed or where some disciplines were overrepresented among others and we wanted to have a diverse group of administrators with their backgrounds and their ethnicity to make sure that all viewpoints were heard and represented among that community and it really was at the heart of it because we wanted that open resource to be open for all and if it really was reaching segments of the community and educators that were really kind of already served or were already working within the open access space or already felt welcome in the open access space, then it wasn't really meeting a need because that community had what they needed. So we wanted to expand that and push those boundaries and bring in new people. So that's the continuing search is expanding the community Yeah, that's outstanding for both answers are really exciting because that's really a foundational belief for us here at the center. The community really is coming first. So for anything that you've heard today, I think all of us would love to hear your feedback and want to talk to you about how, whether you want to contribute or just have something you want to share that may be relevant, please do come and talk to us. So that just the last few minutes here, I'm going to share a feature that is part of the OSF institutions suite of tools that I mentioned earlier. So this is on our staging environment of the OSF, which, you know, looks and works the same as the OSF here. And for some of you who already have dabbled or been part of OSF institutions for some time, then you recognize the ability to affiliate projects with your institutions, your labs, your universities or your researchers, which is a really neat feature and what the data that's been building up around all of your researchers participating and affiliating their data. What we can do is build a dashboard for each of those members now, and this is in production. I'm going to show you a staging one today just so I'm not revealing anybody's real data. But what the dashboard does is gather all of those users that are participating and if enabled those affiliations. So you see everyone on campus who's taking part is on OSF. You can see what kind of public project work they're doing. You can even see just a raw count of their private projects. You can't see their private projects obviously. A total count of users so you can track and see how progress is going on campus with your outreach and advocacy for these tools. This updates every single night so you can see it on a micro level if you really need to. We can also, based on how your identity management works, determine each user's department. This isn't self-reported. It's something that the university has metadata for that they may or may not release the third parties. But if they do release that then we can also associate users with their departments and you can sort and narrow down by those department levels. So you can see where you have clusters of activity and we'll visualize that too. So if you have an area of campus, so in a case like Adrian's when it is partners university of Bristol, their architecture program does a big push to get their work onto OSF. You can actually find your architecture program on here and see how that grows over a month or a couple of months. And then a total project count for determining or distinguishing between public work and private work. So this is available now in production. So I'm happy to chat with anybody that has an interest in learning more about institutions, OSF institutions generally or just the OSF and how it enables some really cool information for institutions to learn a little bit more about the kind of activities that researchers are doing that are kind of hard to distinguish without some tools that support that data gathering. So I'm just going to quickly check to see if we had any questions pop up in the meantime. I don't think so. But to keep a lookout for a follow-up with all of this material that we went over today and you'll have my contact information and please do feel free to reach out to us and we'll see one more question. Go ahead, Sandra. OK, great. Thank you. Marty, one question. Do you see maybe also the possibility that people when they're using your knowledge base are like, oh, I would like to have this in another system. This article, for example, in my instance of a preservation system or my instance of, you know, transferring data somewhere else. Because that would be, yeah. Yeah. We certainly, sure, would love to be able to form those interchanges. We haven't created that capability just yet or some of the technological connections to do that. But the degree to which in the metadata and all of the information created, the authors and the users can upload and then put attributions and links and sources and referencing back is strongly, strongly encouraged so that those network of connections and, you know, lines between everyone engaging in this work can be clearly drawn. Great. Yeah, maybe we also should follow up because you could talk about that. You could use Prescotti for getting, for example, into Synodo or in other systems. Just saying, yeah. Great. Thank you. That would be wonderful. Another example of collaboration in real time. Yeah, that's outstanding. Really, that's great. Thank you. Thank you all of you. The speakers, all of you that came and joined us to listen and really looking forward to conversations and conversations that this can inspire. So keep looking out for more material. And thanks again for joining.