 Welcome everyone, we're gonna go ahead and get started. Hello, welcome to the last session of the day. I am Paige Pope, I am C&I's communications coordinator. My first one, of course, thank you for being with us today. It's been a great first day and I'm looking forward to seeing familiar faces and meeting some new people after this session at the reception. So we are going to dive into the lightning round. So these will be five minute back to back sessions. Very, very exciting. The heart will be racing. I thank our speakers for joining us here as well. Please hold your applause between each speaker if you can. I know it's hard not to. And then also questions, please hold those until after at the reception. So following these five minute lightning sessions, my colleague Diane's going to come up and explain our breakfast discussion tables, which will take place tomorrow. And then they'll also be brief one minute roundups of those topics from some of the facilitators. So once the five minute lightning rounds are done, I ask that you please wait to also watch that as well. So without further ado, I'm going to hand it over to Christina. Thank you. Hey everyone, I'm Christina Drummond. It's a pleasure to kick us off here with a quick update on a suite of research projects. These are all aimed at strengthening our cyber infrastructure for the scalable trusted exchange of sensitive usage and impact metrics that have to do with the open access and publicly accessible research that's created in our public and commercial organizations that make up our ecosystem of scholarly communications. This update builds from a workshop that we held prior to the spring C&I this year, funded through the National Science Foundation. And at that workshop, we had the objective of coming together to understand what was needed to scaffold our infrastructure here in the US to support that evidence based decision making that's related to open and public access impact. We brought together experts from publishers, platforms, data infrastructures, standards, alongside program officers to explore the topic, develop recommendations, and I only have five minutes, so I can't tell you all of what they did, but that's why we have QR codes here. So you can grab the proceedings, you can check out the videos that we pulled together. We have a wonder collection of expert invited talks on the state of usage and impact data. Suffice to say, there are multiple research action areas that we identified as necessary to inform this question of whether we need to have national cyber infrastructure. If that open infrastructure should be global, should be federated, and what that means. We explored how we need education and advocacy, but what came to the fore is that first of all, we have to have a common vocabulary, we have to understand to collaborate, and from those collaborations, we also need to learn from minimum viable product. So through the support of the National Science Foundation and the Mellon Foundation, we've been able to jumpstart some research to assess the unique aspects of usage and impact exchange for open journals and open data, and how that extends to books, while an infrastructure and MVP is moving forward to look at how best to exchange book usage data. An NSF Eager is supporting team at Stratos to document and crosswalk usage and impact data vocabularies. We commonly refer to as the fruit basket of metrics. So thinking about how we compare apples to apples to oranges to papaya, so on, so on. We need to understand that vocabulary and have those crosswalks in hand. The same award is also supporting some folks over at Clark and Esposito to analyze and document the usage data supply chains. So we understand how that data from the point of creation when folks access these digital research objects and scholarship outputs, all the way to the point where we need it for reporting in analytics and evidence-based decision-making. And we have that for open access books. You see the bitly up there, but we also understand how does that particular supply chain differ for publicly accessible journal outputs and open data. In the meantime, the Global Open Access Book usage data trust effort, I'm the executive director of, it continues to move forward with some research and development. So with the support of the Mellon Foundation, we've started our technical development to complement ongoing governance and policy development. We have a team over at 67 Bricks that are in process of assessing the existing operational open science and open scholarly infrastructure environment because we want to build on what is already out there. We need to identify what meets the requirements to play specific roles in a scholarly communications, usage and impact focus data space. And I'll pause and say, if folks have never heard of data space, there's a whole thing called international data spaces, IDS, you guys can Google it, I only have five minutes. But that said, with this particular project, we're working to understand how this established European reference architecture model applies to our scholarly communications ecosystem and which entities that exist today can play some of the five key service roles that are necessary to run a data space, namely identity access management, metadata brokerage, data exchange, clearing house so you can understand how those transactions occur, vocabularies providers of which of course we have many, and data processing app store so we can all go to the same place. Might be able to tell that's a very complex onion. I'm all about the fruits and vegetables, I think I'm getting hungry, I know we have just a couple more minutes to reception but I'll note here that the intent for the book usage data trust and the IDS pilot or the data space pilot isn't to recreate the wheel but rather to bring together and reinforce our existing infrastructures that we use today in our institutions. And so with that, I'll note we're also wrapping up your work to draft rules for the ethical controlled data exchange and data use for that usage data that's coming both from public and commercial entities to those who are receiving it. And so these principles in general are gonna be put forth in a public rule book, you'll see that shortly. As we hand it over to some legal scholars to come up with model contracts. Just in time for a first set of organizations to pilot the data space next year. So if you work with OA book usage data and you want to support the work we're doing, participate in the pilot, learn about data spaces, you'll get to find me at the reception, thanks. All right, good afternoon everybody. My name's Eric Mitchell, I'm the university librarian at UC San Diego and co-PI on leading an IMLS funded three year effort that seeks to develop data science expertise in doctoral students and early career information professionals. I'm here today speaking with you, representing my co-PI's Jane Greenberg, Rachel Frick and John Wheeler, as well as my colleagues in program planning leads Crystal Goldman and Kevin Popovic. And I'm here today to talk with you about our focus on innovating professional education and to invite you to join us in exploring this idea over the next several months. So over the last five years, leading and its precursor project leads have trained dozens of fellows in data science and we're so proud to have these fellows moving on in their careers and excelling in their various roles. We're also really grateful for the dozens of mentor organizations and mentors who have participated and supported these fellows over the last five years. And this December we're graduating our final round of fellows through the support of IMLS and we really are very appreciative of all the work everybody's put in. As we wrap up leading, we're working to publish our data science curriculum, we're working on publishing best practices and sustaining communities of practice and we're looking past leading and asking questions about the future of professional education. So I know we all share a commitment to supporting the next generation of information professionals and I recognize that leading is just one of many a wide range of these education programs. Earlier today I was chatting with a couple library directors and we were sharing best practices about supporting early career professionals and I know a lot of us have been through programs like this. Within leading, we saw a lot of positive career outcomes come from participation of our fellows and we discovered or rediscovered rather that sustainability is one of the key challenges that all of these programs face in our field. And so as we thought about what sustainability means for leading, we also noticed that there were many different practices in place. And so these two issues, excuse me, these two issues, the realization that sustainability is a key problem and that there's many examples of success prompted us to ask this question, how might we help libraries collaborate to innovate professional education that impacts recruitment, growth and retention? As I said, this question has guided the work of leads and leading over the last five years and we think there's an interesting conversation for us to have as a broad information community in this space. So to explore this question, we're gonna be convening a series of online workshops in January and February, 2024, with the goal of bringing us back together around the CNI in San Diego next March to share what we've learned. And we're gonna use a design focused methodology note as the innovation funnel where we'll first learn more about the problem, something we are all familiar with. We'll work on identifying possible solutions and then develop outcomes that we'll then present. So we would love to have you plug in and engage in this work. If you're interested in learning more, I encourage you to sign up on our listserv using the QR code here so we can share information with you as we conduct our planning. Hit the data list dot design site to learn more about where we currently are and come to the birds of the feather breakfast that I'll be hosting tomorrow morning at 7.30. Thank you. Carnegie Gimellon is pleased to announce a soft launch of InGen, the ecosystem for next generation infrastructure. InGen embraces the idea that infrastructure includes people and technology and that the best infrastructure is built when you embed engineering in a human centered ecosystem. It reflects the realization that open source software and open science are drivers of next generation infrastructure. CMU's capacity for both has grown to the point where we feel we can influence national and even global strategy and programs and policies. Having said that, we recognize that no single institution is going to build next generation infrastructure by itself. So InGen is an umbrella framework through which we hope to identify partners both within and beyond CMU. Some of the initial programs and priorities include working on open science and automated science through the CMU Cloud Lab. Cliff mentioned this during his opening remarks today earlier. CMU Cloud Lab is an offsite remote state-of-the-art research facility for life sciences, materials science and engineering research. Any CMU researcher with a computer and an internet connection will be able to access, experiment with and share data, software, a wide array of instrumentation methods, protocols, AI and ML algorithms. Originally developed by Emeril Cloud Lab for Bay Area startup companies we explicitly do not want to share results with each other. We are re-engineering the platform for the broader more open university environment. As an example, I'm glad to note that the Emeril Cloud Lab has open sourced programming language for the platform. Cliff also mentioned that in October at CMU in Pittsburgh with funding from the National Science Foundation we convened a diverse group of participants to examine whether Cloud Lab could be a model or a platform for a national network of these so-called self-driving laboratories. So anyone with an internet connection and a computer will be able to conduct open automated science. Second program is looking at climate change and de-carbonization through the open energy outlook. This is an initiative from the Scott Institute at CMU. It's a model for looking at the impact on de-carbonization from different policy choices. Open source software, the CMU OSPO is working with the team to build a community around its subsequent development and use. On the national stage, the Department of Energy has already expressed its interest in using this particular model. Cliff also mentioned the importance of cybersecurity. The CMU OSPO has been working with the Software Engineering Institute which is a federally funded research and development center and charged by the Department of Defense to be its software advisory group. One potential point of connection with the broader network is I'm in discussions with Amazon Web Services around building a platform for evaluating AI-assisted and AI-generated code. Building on CMU's strengths in computer science, we've been conducting some educational pilots that bridge theory and practice through using open source software as a laboratory while working with mentors from industry partners. Stephen Wally, an executive at Microsoft has been leading this effort. This past summer, he taught with Michael Hilton of Computer Science. We are in active plans to teach this again next summer at CMU's campus in Doha, Qatar and to build a workshop-style version of this at CMU's campus in Kigali in Rwanda providing some global exposure. The final program I'll talk to you about is the Open Forum for AI. And at the key part of this is what we're calling openness in AI. The idea is to build a technical framework that is rigorous and at fine-grained granular level that accounts for all the artifacts of AI and the workflows and the orchestration that connect them. The goal is to build a human-centered participatory inclusive AI that bends the arc towards augmented intelligence and allows a broader ecosystem of players to build smaller, lightweight, more accessible AI models with direct feedback from underrepresented groups. It builds on CMU's expertise in AI particularly responsible AI. I'm pleased to note that the co-director of the Responsible AI Initiative at CMU Hoda Hadari has agreed to lead the effort working with the CMU Ospo. Initial partners include the Open Source Initiative which manages open source licenses and will provide legal expertise and the Atlantic Council which is a DC-based think tank affecting federal policy development. The funding support for all of these initiatives listed here were always grateful for external support but I want to highlight the support that CMU is putting in to both the Ospo and the engine including through library reserve funds. I will end with my standard slide which has a question Jen Stringer stole my thunder but I'll take that as a point of affirmation. It's a provocative question for you but I'm interested in your provocative questions for me. Thank you. Hello, everybody. I'm Dylan Riediger from Ithka SNR and I'm here today to share a couple of data points from a report that we'll be publishing early in 2024 sharing findings from a national survey of research data support services that we conducted over 2023. I should mention my colleague Ruby McDougal who is not here today but who developed the methodology and conducted much of the research data collection and analysis. We are doing this work in partnership with 29 universities who are participating in our cohort project on coordinating research data support services across campus. And the inventory's purpose is to provide a detailed map about the availability and the distribution of research data services, excuse me, data services and it's intended to support decision making about how best to coordinate those offerings going forward and to align them with researchers' needs. The inventory's based on a sample of 40 R1 universities, 40 R2 universities, 40 small liberal arts colleges and a sample of the Canadian Association of Research Library members. And our data collection involved hand searching websites of universities that were included in the sample to identify formal research data services that were being offered by any unit on campus. As you can see from the slide, we collected information on where the service was being offered, what subjects and topics were being covered and some information about the delivery format of those services. I'll say before I move on to share a couple of data points that we defined research data services for the purposes of this project as concrete programmatic offerings that were designed primarily to support researchers in their capacity as researchers. So I'll share two things. First, what services we found and then I'll talk a little bit about which units were offering those services. The first thing I'll point out is that there are quite a few research data support services being offered by campuses these days. We found that on average there were over 12 at a typical R1 and five at R2s. And I should note that this average can be quite misleading because even within Carnegie classifications, the distribution of number of services varies quite widely. Six R1s accounted for something close to a third of the total number of services we found. So there's quite a bit of internal stratification in how active universities are in this space. You'll also notice that general research data management services are unsurprisingly the most common type of research data services that are being offered. This reflects investments that institutions have been making to support open science and data sharing and also shifting regulations by the federal government and other funders related to data management and sharing. I also just wanted to point out in light of an earlier panel today that approximately 72% of the services we found in both R1s and R2s are consulting-based services. The number of those compared to the number of training-based services is very favorable towards consulting and advising services. This, again, I think reflects the value of those services, but it also poses some of the problems around scaling that we talked about earlier today. Libraries are still the primary provider of research data services, but as you can see from these slides at both R1s and R2s, other offices on campus are providing significant numbers of services. The research office and its kind of cluster of research cores and institutes are perhaps the second most likely people to be providing services, and in the full report, we'll talk a little bit about how the profile of services that are being offered differs across which unit on campus is providing them. And finally, I'll just say that, as I mentioned earlier, we'll publish findings from this in early 2024. A few things that will be in the full report that I didn't get time to talk about today have to do with what the landscape looks like in Canada and also at baccalaureate institutions, more detailed breakdowns of the subjects and formats of research data services, particularly any characteristics that are related to what unit is offering them, and also information and data about the distribution of research computing services and data repositories on campus. Thank you very much. I agree it was that good but it was worth breaking the no clapping roll. All right, so I'm Trevor Owens. I'm here to talk about the STACS platform, a system for onsite access to rights restricted digital content at the Library of Congress, where I work. And so STACS is an access system for rights restricted content. It's content the Library of Congress has custody or ownership of, but is not a rental or subscription set of material. It's content that we can make available to STACS terminals placed within our reading rooms and to LC staff, including staff in the Congressional Research Service. Users can search, view and print portions of works but they cannot download or export content. It's a Python Flask elastic search application. You can see a picture of it here on the side where you can also see a rundown of 170,000 books, nearly half a million newspaper issues. It's an exciting, growing part of how we provide access to our collections. So some context on why we built STACS. First off, access to rights restricted content is a key part of our digital collection strategy. I don't expect you to be able to read all this here, but if you do wanna check it out later, it's up online as our digital collection strategy. A big part of this is that as we work towards an E-preferred approach to building our collections going forward, a vast majority of the materials we acquire are not things that we can make openly available online. Expanding open access as much as possible is a big part of our strategy, but we're also focused on a coordinated program of policy and infrastructure to enable the broadest possible access to rights restricted content. So with that, some why of STACS. So as I mentioned, significant portions of our collection materials, whether it's things through copyright deposit, purchase, gift, transfer, or exchange can only be made available on site at the Library of Congress. Another area is that as we shift preservation reformatting away from microfilming to digitization, we're getting more and more digitized material that we can only make excessive, that comes with rights restrictions. Here you can see a wall of book covers. An exciting part of the material we get in STACS is that a lot of this is things from, say the cataloging and publication program where we're getting a lot of widely distributed books that are published in the U.S. So here you can see things like Killer Bees and Fire Ants and a book about Minecraft. So there are public access terminals for the STACS system in almost all of our reading rooms. There's a full list of them here. And if you wanna see what that experience looks like, you can see Marcus who's one of the digital collection specialists that is really heavily involved with working with STACS, here using one of those terminals in part of our main reading room. But you can see they're widely available across the space. The way that the access restrictions works is that anyone can go to any of those terminals and use them. If you're curious about how that works in practice, so all the material that's accessible in STACS is discoverable through our catalog. So you can see here the ugly caterpillar is a children's book from 2014. It says on-site access. You go into the actual item availability on the record. You'll see a link that says available on-site via STACS. And there's a handle and if you're on-site and you click that handle, you go straight to the work where you can see it and search it. And if you're off-site, you go to a page that directs you to the way to get to one of the reading rooms. So here's a little bit of an overview of what's in STACS. So we're now over half a million newspapers and legal Gazette issues. This is largely made up of copyright deposits. So registrations for e-print newspapers come in and are made available in STACS. That's what the Wichita Eagle is here. But then along with that, we also have a huge amount of materials that we're now digitizing that are newspapers from around the world. They go into STACS for access, 170,000 e-books, 700,000 journal articles. But then from there, it goes down to a lot of other formats, music scores, moving images, mapsets, et cetera. And so that is a quick tour of STACS. And I think I can pass this over to our next speaker. I'll walk slowly. My time clock won't start counting until I get there, right? So you can write down the URL. Okay, thank you, everyone. I would like to talk about LUX very briefly with you all. So what is LUX? We think of LUX as a groundbreaking discovery, teaching and learning and research platform, thereby, of course, fulfilling the mission of the university that provides unified, focus on that unified, digital access to the collections of our museums, libraries, and archives at Yale. We launched on June 1st this year with a total of 42 million records and comprising 17 million objects, 13 million works, and millions of places, concepts, people, organizations, and events. And if that wasn't enough buzzwords about why you should care, here are some more. So we think that LUX has an intuitive and highly functional interface. It's built on linked, open, usable data, again, focus on usable, because that enables maintenance and adoption beyond just Yale. It is reconciled and enriched from more than 20 different external data sets, giving access to a vast amount of information that we do not manage at Yale. That happens automatically, and of course, at scale, with 42 million records, we cannot, even with students, do that by hand. And it has all of the functionality that you would expect from a discovery interface, including text, search, and facets, but also leveraging that linked, open data for graph queries. So what were some of the things that came up, which we did not expect? So from beyond LUX, but within the cultural heritage organizations, we found that participating in building data for LUX enabled both the University Art Gallery to contract with an external vendor to rebuild their site based on the data that they provide to LUX at a fraction of the cost of building their previous site. For that, they use external infrastructure, but the Peabody is taking that one step further by using the LUX infrastructure to build their collection site on top of the data that they provide. Going even beyond cultural heritage, it has incentivized people to think about where we can use knowledge graphs at Yale beyond cultural heritage. Can LUX discover relevant research datasets? We have a project which is sponsored by the University Librarian, the Vice Provost for Research in the CIO, to investigate that question over the coming months. Are there benefits to describing core university functions, such as where do you get chicken nuggets from for folks who were in the last session? And of course, not to do with chicken nuggets, though reception will see if there are any. We want to use the data to build AI services that don't suffer from hallucinations by training on some of that core curated knowledge. And if anyone has been playing a drinking game on the number of times folks have said AI, congratulations, you are still vertical. It is after five o'clock. And finally, beyond Yale, perhaps to your wall. So since launching LUX in June, we have had interest from more than 50 organizations who are around the world, including many of the folks here in the room, as to how we did it and can they learn from it? Can they adopt it? So we are currently cleaning the code in order to make that possible. We'll publish it on GitHub in the next couple of months. And we proposed a 12-month project to the IMLS for next year. We'll see if we get it. If we are successful in getting that funding, we will host a meeting here in Washington, DC in exactly 12 months from now, following from CNIFE forum 24, to discuss two primary things of interest. How do we govern this in terms of the data model and the code, the processes and the knowledge? And what are the collaborative solutions that we as a community can come up with to move beyond those first initial technical barriers to entry that can then allow you to demonstrate value internally to your stakeholders in order to then take it through the entire course of the work to come to a product? So if that sounds interesting, perhaps not the chicken nuggets, then please do get in touch with me. My email is on all those slides. Or find me at the reception in a few minutes and we can discuss further. Thank you so much. So hello everyone. I'm obviously the European guy tonight. My name is Juner Roche. I'm from France. I'm the university librarian at the University of Lille and I'm there tonight because I'm also the president of Liber which is the European League of Research Libraries and the voice of research libraries in Europe. Actually Liber is the largest association of higher education and research libraries in Europe and I will try tonight in the five minutes to give you a flavor of what Liber is delivering. This slide is summarizing the main activities we will have. I will get back to the ones in Italic later on and comment briefly the other ones. So first of all, Liber is a networking organization just giving you two examples. We produce a quarterly publication for our members. So 700 people received every other month our internal publication and we also have what we call the Liber Insider which is for everyone. So you can register for free and get access to the main information we provide. We have thousands of subscribers for that publication. We also provide resources and guidance. We publish them on our website. We publish them on YouTube and we publish them on Xenodos so you can get access to hundreds of publications for free videos and so on. We are also working on learning and teaching and provide a lot of content you can reuse again, accessible on our website. We have a publishing activity because we have the Liber quarterly with a high level publication where we publish practical cases and also research articles. And we have a lot of advocacy activity towards the European Commission for instance. What I would like to also highlight is the main events we have. So we have a lot of activity during the year. We have an annual conference, a large one every year. It's open to everyone. So you can register and come and join us next year. We have webinars in common just like the one we had in October with UNESCO and La Referencia. We have what we call a winter event which is more or less an internal event just like you can have in ARL or with CNI. We have architecture seminars and the next one will be in spring in Belgium. And we have, we develop master classes. This is an example on citizen science but we will develop over in the future. And of course things like journeys and other things. We have leadership programs, especially two programs. The emerging leaders which is for second tier librarians. So people who are not university librarians but would like to become in the future. And we have library directors, library journeys for experienced librarians through the world. So it's open to people not only in Europe but also in the rest of the world. We also have a large part of activity about international projects. We have something like 10 permanent staff and half of the staff are working for international projects. For this project are many European projects because you probably know that Europe is spending a lot of money trying to develop high education and research programs. And a lot of them are for libraries tackling with issues like open science, innovative scholarly communication, digital skills, research infrastructures and services and citizen science. So we have there the names of the different programs like shock recreating Europe, Palomera, Diamas project. You maybe know some of them. You have all the details on the website and of course I would be happy to have further discussion about that with you. Nearly the end of my presentation, what I also wanted to stress is the Libre vision for research libraries in 2027. So we have fundamental preconditions in the gray area in the bottom of the picture which are namely upholding rights and values and upskilling the library workforce. And we have let's say three main areas, three main directions which is to have engaged interested hubs to have state of arts services in libraries and to work on advancing or open science. So I will attend the reception. Please come to me and let's start the conversation and don't miss the Libre breakfast round table tomorrow at 7.30. Thank you very much for listening to me. Hi everyone. Thanks for hanging around just a few more minutes. I know we can hear the clinking of utensils next door and the smells wafting in. So I appreciate your patience. I'm Diane Goldenberg Hart with CNI and the first thing I'd like to do is thank our lightning round speakers again. Thank you for those wonderful talks. So I just wanna say a couple of words about breakfast tomorrow morning. We're going to have a few tables reserved for discussion on defined topics. You heard from some of our facilitators just now in the lightning rounds. And there should be up on the screen a complete list of all of the discussion tables that we are setting up for tomorrow. I wanna note that the list that's in the printed program is not the most up to date list. We have some updates. You see them here and they also are on the online schedule, the SCED. In particular, I want to note that we have added a couple of topics, two general theme topics. One is on evolving licensing models and strategies and Lisa Hinchliffe will be facilitating that table. And we've also added a table on AI and policy that will not have a facilitator. This is the first time we're trying that model and with that and all the other tables we welcome your feedback. So just in a minute now, we've asked a few of our facilitators to do a very quick roundup just about a minute each on some of the topics that are on specific programs and initiatives that we thought could benefit from a little more information and context. And the last update I wanted to give about the program is that we will not have a table on information infrastructure and grand challenges from Don Waters, but Don is here and I'm sure he would be happy to chat with you about his project. So without further ado, I'm going to hand it over to Dylan. Hi everybody. Karim Bukita and I have been tasked to take the AI table tomorrow morning. So we will be hosting a conversation about AI and higher education contexts. It'll be wide ranging. Bring what you want to talk about. We're focused primarily on research and teaching applications inside higher ed. We'd love to learn more about what your institution is doing and thinking about this topic and we'll have some things to share as well. Thanks. Good afternoon everyone. I'm Salwa Ismail from UC Berkeley. My colleague Todd Grappone and I will be hosting a breakfast table, 7.30. Talking about how libraries can improvise campus-wide research data services. So for those of us who are not doing super fabulous, super innovative, super cutting edge, how can we move these services forward that then can organically become more coordinated across campuses. So at UC Berkeley, we've reenergized our library data services program in partnership with our campus IT, research IT, College of Data Science and much of it was inspired by our Ithaca SNR big data study and at UCLA, they actually did a campus quite comprehensive study through a survey of their faculty members and then developed a roadmap on this. So join us tomorrow to talk through the approaches we've taken that are taking us forward as we talk about comprehensive, iterative and improvised research data services. Thank you. Everyone, I am Susan Ivy. I'm from North Carolina State University but I'm here today representing EDUCAUS Research, Computing and Data Community Group, also known as RCDCG. So what is the EDUCAUS RCDCG? We're a group of professionals. Many of you in this room are probably a part of it already. If you're not, I hope you'll consider joining and learning more tomorrow at breakfast. We're a group of professionals mostly at higher ed institutions that support researchers as they conduct computationally and data intensive research and all of the things that go along with that as we support that work. So what do we do? We have open calls throughout the year virtually and we also participate in the in-person EDUCAUS conference. We have meetups and we're also considering other ways to leverage resources that EDUCAUS makes available to us for things like working groups in the coming years. So if you're interested to learn more, please come see me tomorrow morning at 7.30. Hi, everybody. I am Alicia Salas. I am a co-lead of the Helios working group on shared scholarly infrastructure and also university librarian at the University of Oregon. And I wish I could go to all of these breakfast tables tomorrow morning, but I'm hosting one. So I wanna invite you to join me. Helios stands for Higher Education Leadership Initiative for Open Scholarship and it's an initiative of over 95 research institutions across the United States at this point. And it is a presidentially driven initiative. So driven by a commitment of university presidents to work towards aligning incentives for open scholarship within higher education and across sectors, including government and industry and higher education. So I would like to invite you to join me at my table in the morning for breakfast to chat more about that work, ask questions, learn how to join or share ideas and current Helios members and non-members are equally welcome. Hope to see you tomorrow. Great, thank you to all of you, to all of our facilitators and to all of you for attending. And with that, we are adjourned for the day. We'll see you next door at the reception. Thanks so much.