 I guess I'll go ahead and get started. Hello, my name is John Chidaki. I work at the California Digital Library, and as many of you know, CDL is a system-wide group that works across the entire University of California to support libraries and researchers across the UC system. The nature of our structure is that we work very much on work that's intended to be at scale, right? We're looking at projects and focuses that are not on an individual campus but looking how we can affect change across the entire system and across the nation and across the globe. And so the talk today will be about work that we have done with Dryad in that kind of context. And so really this story starts in 2018 for California Digital Library and for UC. At the time we were reevaluating the ways that we were supporting libraries at CDL, the UC libraries, and how we were supporting UC researchers when it came to data publishing. And as a result of that process, we embarked on a partnership with Dryad. We thought about what is our vision for data publishing? What is the purpose of what we are doing and what we are offering? And really came up with this statement around adoption focus, about how do we focus on getting more adoption researchers within UC to publish their data sets? We had a data publishing program previously, but it was one that did not have a high adoption rate. We also wanted to make sure that it was at no cost to researchers. So we know that we wanted to incentivize best practices like curation and like better metadata for data deposits and to ensure that there is discoverability. But we also wanted to make sure that researchers weren't varying additional cost in their process. So we wanted to be able to hold that cost for them. And we wanted to make sure that with adoption comes just the need for embedding it into their workflows, something that is easy for them to accomplish. And also as we were talking about with all projects at CDL, we really wanted to make sure that the work that we were doing is not just for us, but really is something that can build a basis for global upscaling of data publishing practices. And so we set up these specific goals. How do we drive adoption? How do we open up a global community? How do we create a more nimble service? And how do we support researchers' needs and innovate? And came to the partnership that we have now with Dryad. We are now across the entire UC system, Dryad members, and we now have the ability for any researcher within the University of California to submit to Dryad, have their data sets curated and published. We are able to cover that cost on their behalf and we're able to support innovation across the entire globe through our partnership. And so this is really, you know, one of the things that we were really trying to focus on was not just how do we support Nobel laureates and their research, but really how do we support all types of research that go across the campuses. And this includes undergrads and research that's happening in social sciences as well as lab sciences and really about how do we create spaces for emerging topics. So, you know, with the COVID pandemic, we have a lot of research that needed to happen very quickly and get out very quickly, but needed the touch of curation. And so being able to connect to all of the researchers across the UC was definitely one of the things we were trying to do. And so when we think about what we were trying to achieve and what goals we put in place, we, you know, within one year, we saw amazing amounts of success. And some of this has to do with the fact that Dryad had a much more name recognition than our internal data publishing platform. Some of it had to do with the embeddedness of Dryad into the publishing process, but really one of the, you know, the main goals that we put in place for ourselves, the way that we wanted to influence change across our system and across the globe was around this idea of adoption and cost savings and best practices. And in each of those cases, we were able to achieve our goals. And so I think I'll turn it over to Jen Gibson from Dryad to talk a little bit more about kind of the work that's been done in those years just to ensure that that can happen across other campuses as well. Okay, so I bear with me. I just have to change slide decks, unfortunately, and give you a nice view of western Canada. Okay, great. There, hi. I wish I could see you a little bit better. The lights are awfully bright, but it's great to be here. It's really great to see so many familiar faces. I'm Jennifer Gibson. I'm the executive director of Dryad as of week nine. I've been here for eight weeks. This is my ninth week, and what a week to have and to be here at CNI. We may have met before. I changed my name when I got married a couple of years ago. I was Jennifer MacLennan when I worked with Spark from 2005 to 2011, where I had the great pleasure to work with the library community and the library adjacent community. After that, I went away for 10 years. I actually live in the UK now, and I went away to work with Elife, which you may know as a biology and medicine journal and initiative from the funders of research to transform science publishing. So it was a great opportunity for me to work on the front lines with research in biology in the main. I tried to get into medicine, but it's really still a work in progress. I also had the opportunity to work with you all through Force 11, where I was on the board with John for a few years, and through the open access scholarly publishing association where I'm currently the chair of the board of directors. So very parallel initiatives, all intending to advance open research to scholarship very broadly. What I'm here to talk about today is the collaboration between DRIAD and institutional members and institutional libraries. So as my colleagues at Daniela Lohenberg, whom you probably know from DRIAD as well as CDL, and John have helped me to understand, DRIAD is very much a component in a broad and powerful system for open research. So we want you to see us as sitting alongside a lot of other important components, including the other services on campus, which I'll talk about. We are a component and partner to a lot of other services as well, so I'm not going to talk in detail to our partnership with publishers or the work that we're doing directly with researchers, but really hone my brief remarks here on our relationship with the institutional libraries. So we'll talk broadly about that relationship, I'm talking specific to how we connect with other campus services, and then I'll describe the institutional membership program, which I believe was born of a CNI meeting in 2018, and then talk about a few thoughts that I've got for moving forward, all in a very brief 10 minutes or so. So just to reintroduce you to DRIAD very briefly, I would characterize us as an open data publishing platform rather than a data repository. So with you, I think we sense an opportunity to seek much greater engagement with the data in the online environment. But we're also a community with our institutional members committed to realizing a broad sharing and reuse of research data. The platform today represents over 43,000 publications, which in turn represent the work of over 175,000 researchers, 32,000 institutions worldwide, and over 1,200 academic journals. So again, I'm not going to be talking about the DRIAD integration with publisher workflows and our publisher partners, but rather this is a reflection of the data that we have in the system today. The vision of the DRIAD community is not only that we have open access to all the research data, but that data is also routinely reused. So that's the tricky part. As we know, I know a lot of you are working toward a common direction. And the way that we feel that we can help to do that is by enabling and promoting the reuse of research data through the DRIAD platform. And I just wanted to make note that the DRIAD is a 501c3 nonprofit corporation registered in North Carolina, and we were founded by researchers and colleagues, some of whom are here today. I think Jane Greenberg was one of the founding members of DRIAD back in 2009 formally, but I think informally as early as 2007. And the way that I see DRIAD helping as a component in this network is that we make data sharing easy and powerful, so we won't have time to talk about our user interface today either, but it's very easy. It's very easy for authors to submit their data and to provide the metadata that we want to describe the data through our submission portal, and then we make the reuse of data a compelling argument by our presentation of the data very much like what Bob was showing with the web page that describes the dataset and all of the metadata automagically, so we make it compelling the reuse of the data through the platform as well. So now just focusing on how we see ourselves as part of this interconnected system of initiatives working very much in parallel for advancing open research with using modern technology. So DRIAD sits alongside domain repositories, institutional repositories, other generalist repositories, and the data curation network I wanted to make sure and include as well as other services like publishers. So publishers are vast, so I hesitate to say a service, but in terms of making openly accessible research objects from across the workflow, publishers have a function there which exists in parallel to registered reports, protocols, datasets, and software, and data of course is DRIAD's focus. So our institutional members have invested in DRIAD for five reasons as I've come to understand so far. So this is where I'm looking for your feedback. I'd like to sound this out with you and hopefully get some time to chat while we're here at the meeting. So our institutional partners are investing in DRIAD because we're a powerful ally in achieving your open research strategy. So for the reasons that I've just said and that we interconnect with your other systems and we sit alongside other services that deliver open access to the research and the software, we are a powerful ally, we're a complement to your other initiatives and your broad strategy. Another reason why our institutional members are leaning into DRIAD is because the research community and many research communities are already coming to DRIAD. So in evolutionary biology and ecology, the journal editors and their colleagues in research did the work to establish buy-in into open data sharing and to get the platform moving at that time. So there's traction not just in EEB but many other disciplines as well where researchers just have the habit, they have the good practice to go and share their data at DRIAD. So I know from our work before, from an institutional perspective, it can be really hard to get engagement from the faculty and convince them to step out of their usual workflows and behaviors to share their data and DRIAD's already there. DRIAD's already connected to the community so we can offer you that advantage, that traction. Similarly, DRIAD has a really powerful connection with the publishing workflow. So it's not essential that you share data and association with the publication. We will take data that isn't associated with the research article now, but we are connected to the publishing workflow in such a way that when an author is submitting their article for publication, the journal can ask if they share their data. They can send them automatically off to the DRIAD platform, submit their data, have their data curated, and then we'll return a DOI to the publisher so that they can interlink that data with the published article. So that's very powerful. Again, as you know, working within the established workflows and practices of the research community to engage them in open sharing. A fourth reason why institutional partners are leaning in DRIAD is that we champion best practice. We help to advocate and exemplify best practices in data sharing and the potential for data reuse. So we've worked very hard, especially with my colleagues at CDL, to establish very high standards for data sharing. It's a CC0 license only for the data at DRIAD, and we've got consistent metadata capture processes that really aid the discoverability of the data downstream. So we can help. If this is what you like your researchers to be doing as well, DRIAD is an excellent partner to help make that case on campus. And finally, as a nonprofit organization, DRIAD is driven by our mission and our vision, and we want to contribute, again, alongside other initiatives with common ambitions to a global environment for research that is equitable and inclusive as well as open. All that said, one of the key questions that emerges for our institutional partners is how we supplement institutional and other campus repositories, which have already drawn significant investment. So just a couple of points to help with that. The first is that DRIAD publishes data exclusively. So institutional repositories, other generalist repositories, will take content from a wide range of types, whereas DRIAD's focus is strictly on the data. So we're an expert complement to generalist repository work. And the second thing is that you can mirror either the metadata or the data itself from DRIAD into your own system. So you can take the full data, or you can just take the descriptive data and stick it into your data repository or your generalist repository, or just the descriptive data into your catalog. So for example, UBC, which is our first Canadian partner and won't be the last, sends our full data into their Dataverse. Columbia takes the high-level data and puts it in their search, and the University of Helsinki puts the entire data sets into their institutional repository. So again, our aim here is to connect and support and to be an important part of your puzzle and not the entire puzzle. We're not trying to be a one-stop shop. So I hope that helps paint a picture for the opportunity and the value of institutional partnership with DRIAD, but again, I'm here to seek your feedback. So before I hang up, let me describe the scope of the institutional membership program as well and then just a couple of my own thoughts for the potential for working together moving forward. So, so far, this program, again, as we said, so conceived of here at CNI 2018 and launched after that, we've got 44 academic institutions and one research funder, CCI, so far. And the program was designed by the folks here. So we had a workshop with institutions who talked about the value and potential and that's hopefully what you'll agree is what's played out. The institutional memberships represent 25% of DRIAD's non-grant revenue today. These are all of our members. If you had time to read this slide, I would like for you to pick out that we represent large and small institutions as well and that we've got some geographic reach. So we're not as broad as we'd like to be. We certainly aspire to be more geographically diverse, but we've got some great traction with representation in Saudi Arabia, Japan, Australia, and India. So there's a foundation to build on there. We designed the program in a way that's intended to be affordable and cost-effective for institutions of all sizes. So from as little as 3,000 for teaching institutions and 13,000 for the largest research institutions. And I'd like to emphasize here that it doesn't always have to be the library that pays. So the information technology services can see great appeal in DRIAD as can research offices. So I think the point was made earlier also that open sharing is an important component of research integrity. So going back to those offices to seek support is a potential avenue. And also what about the scientific departments? So there's increasing awareness among them about the importance of paying for the cost of dissemination of research and their funders. So that's an opportunity as well. In terms of the benefits of membership, here's what we've got so far. So for the institutional members that join DRIAD, we offer unlimited data publishing deposits. So all fees, including fees for large data, sorry, large files are covered. So the authors will come in through the DRIAD submission portal. We'll ask them if they have an institutional affiliation. We'll send them through to you via your SSO. And then once they're on the platform, they'll see your university branding. They'll know they're at home and they're not going to get a bill for their data. We offer a hands-on administrative dashboard so that you can see exactly what your researchers are doing on the DRIAD platform and how much they're submitting and what the state of their submissions is. Again, they're at the branded instance so your authors, your researchers, will very clearly see their institutional affiliation as they navigate the DRIAD portal. And as I said a moment ago, DRIAD institutional members have the opportunity to integrate DRIAD with local resources. So whether you want the metadata or the full data, you can take it via our API and stick it in your repository or ILS system or another storage system. Our team offers training and support. So from the point of integration, where we're connecting via SSO and getting online with the system, our team will support you and help you to get online and make everything smooth. And finally, DRIAD is again a membership organization of 501c3 and so registered members have the power to vote in our annual election, which is the appointment of individuals to our board of directors. So we see a lot of potential here. It was born of conversations here and we're optimistic about your support and interest in this model, but we'd like your feedback. We'd really like to hear about what about it appeals or what about it you think could use a little bit when we're refining. So I'm here for the rest of the day and my contact information is on the slide so do don't hesitate to reach out. So now I can't help but just offer a few reactions on thoughts for working together, moving forward beyond this. So just having worked with institutions on open research programs before, I can't help but wonder about where else our DRIAD collaboration might take us. So just a few ideas just after these eight or nine weeks at DRIAD. So given my work at Spark and on projects like Open Access Week, I can't help but ask if we shouldn't collaborate around open data advocacy and education. So could DRIAD be a depository or a locus for organized outreach? So from my vantage point, I'm seeing really fantastic resources coming out of our publisher partners that are describing the importance of open data and fair sharing. And I know there are a lot of other organizations in the network who don't have the resources to produce that so is there a way that we can channel them and share them and just make us all a little bit more effective in the community and the education. Second is having worked so closely with researchers over the last 10 years, albeit in biology and medicine in the main. I am, and having spent that time trying to convince them to change their publishing behaviors and how they judge their fellows through research assessment practices, I can't help but wonder what power there may be in connecting reuse with research assessment. So if we're successful in bringing the data to life using modern technology and getting the humans, convincing the humans to engage with it online, will we also be able to get the humans to value data sharing and to give credit to their colleagues for having shared their data? Is there feedback loop that we can create there that will then inform changes in research assessment practice? And finally, I know that there is great interest in helping community-driven and open source initiatives to persist and to thrive in this competitive marketplace. And I'm interested as well, you know, on dryads behalf, I would like to persist and thrive in this marketplace. And I've got lots of plans and ideas and I know that institutions are working on this as well and have some plans and ideas as well. So how can we work together? Where do our plans marry and where do we learn from one another? And how do we build something that stands up in the long term? So that's it. If you have any questions for me, I'm happy to help. I'm happy to help as well. And Danielle is on standby. So thank you very much for having us. I think if there are questions, if you don't mind coming up to the microphone at the front, that way we can see you as well as hear you. I think as people come up to the microphone, I would just say like one of the things that really resonates with me from the discussion is that at CDL when we were doing our evaluation at the University of California, that we were looking at dryad really not just as a resource for the future but really going. So this idea of like being able to meet the researchers where they already were in a platform that shared the values of what we were trying to achieve. Sorry. So my name is Charles Watkinson. I'm AUL for publishing at University of Michigan. And I know you have a sort of vested interest in the answer to this question, but I mean I think it's on all our minds, which is the relationship between institutional repositories and what were called earlier in this meeting sort of generalist data repositories like dryad and it's one of those tricky questions, but it's interesting to see that relationship playing out at some universities. So humanities commons being adopted as the institutional repository at Michigan State University, for example. And I wonder how you see that playing out and the opportunities for a university to ditch their own data repository and really embrace a tool like dryad and just sort of thinking honestly, you know, the pros and cons and just the pathways to that kind of work. And I know that's a huge question. Can we offer two perspectives in dryad and institutions? So dryad, you know, quickly, you know, we are a complement supplement. You know, we want to exist alongside your other tools. So the dryad focus is on data and the dryad focus is on curated data. So not a domain repository not a repository that takes a lot of other objects and we don't have a lot of strength in humanities yet, but we could have. So something to develop. But John, how do you see it from an institutional point of view? I mean yeah, I think that dryad has a lot of different ways that institutions can engage. So it's specifically from UC's perspective, my perspective within the University of California. You know, we are a research intensive system, you know, we are in very similar to Michigan or Michigan State. You know, we have a need when it comes to data publishing that is great. It is even but even with that scale, even with our scale, we did run a data publishing platform for several years and the adoption was very low and we had to be very soul searching in what was that why was that happening. Why does something at the scale of the University of California that has the resources and the ability and the need still struggle to get 50 deposits a year, 20 deposits a year. We are publishing hundreds of thousands of articles but we are getting 20 data deposits and a lot of that has to do with the fact that we even at our scale cannot scale enough for our researchers to see us and it becomes more of a question of marketing and name recognition and convincing publishers that there's a reason to work with UC and all of that kind of dynamic instead of just doing the work and so what was interesting to us was how do we achieve those goals, how do we still support the research and get the, you know, and do it in a way that we consider best practice but do it in a way that doesn't require us to sell our values, you know, or ditch our values and so that's really where we came to Dryad was we did ditch our data repository, we did move to Dryad as Jen said that's not a requirement to get involved in Dryad or anything but for us that was the reason and the reason why is because even at the University of California we couldn't convince you know PLOS or Royal Society or somebody to integrate with our data repository and I don't think we as a library community should assume that's ever going to happen that will never happen so we complain about the fact that people won't integrate with us one by one or won't listen to us one by one but it's just not achievable so it's kind of we have to start being realistic and start thinking about what goals will get us to what actions will get us to our goals and for UC that was us bringing a generalist repository that shared our value you know a data repository like Dryad that was a non-profit who was interested in curation and best practices to be our solution and I personally would say that that's what everybody in this room should do I think that we are we have diminishing returns on our individual implementations and we cannot achieve the goals that we are setting out for ourselves with individual implementations of a data strategy I think we're meant to stop at 11 so why don't we come down from the podium and please just approach us and have a chat but thank you again for staying and I look forward to working with all of you thanks