 Hi everyone, thank you for viewing our session today on lyricists research infrastructure communities. My name is Sheila Rabin. I'm the program leader for persistent identifier communities at lyricists. And I'm presenting today with my colleagues Paulo Guhilde, our orchid us community specialist at lyricists and Hannah rosin strategist for research and scholarly communication at lyricists. Today we're going to briefly explore open research infrastructure goals and best practices, an overview of the research infrastructure community programs that we support at lyricists. And then we will share a case study of putting these practices into action in our own lyricist research workflows. In the last several years, open research infrastructure best practices have emerged as libraries and other knowledge based institutions seek to measure institutional impact, while also streamlining workflows to make people's lives easier. Institutions want to know things like how much funding their researchers have received what research papers and other works came from that funding, or came out of the institution in general, and whether those outputs are being used by other scholars. Of course, we want to do all of this with as little extra effort as possible. We want to save time and reduce administrative burden. And we want to contribute to making research and scholarship more fair, which stands for findable accessible interoperable and reusable, which you might be familiar with from the go fair and fair principles initiative. In order to achieve these goals, the focus is really on implementing machine actionable persistent identifiers that are connected with each other, ensuring that metadata behind these identifiers is accurate and openly accessible. And because the research and scholarly communication landscape really operates like an ecosystem. We all need to be on the same page in terms of using shared standards for identifiers metadata, and also gathering statistics related to usage of scholarly materials. For example, persistent identifier such as orchid IDs for individuals and DIYs for content and objects can establish machine actionable connections between researchers their affiliations and their contributions, while also serving as a mechanism for interoperability and sharing data across systems. And when measuring usage of research contributions associated with an institution within an institutional repository, for example, clean comparable standards based statistics are needed for accurate internal assessment, as well as for benchmarking with peer institutions. The more organizations using these types of open research infrastructure services and their workflows, the more connections can be made between entities, making research objects more fair. To support institutional goals reliant on these shared standards, lyricist serves as the community home for three consortium programs designed to lower the barrier of participation for using open research infrastructure best practices, the orchid us community, the lyricist data site us community for do is and the iris us community which stands for institutional repository usage statistics. So next we will talk a little bit more about each of these programs. Thank you Sheila. Our first program is the orchid us community orchid us community is a consortium of nonprofit organizations with over 150 members including universities, medical schools, health care systems and grant funding agencies. The consortium supports member organizations through dedicated support staff and resources, and provides a national community of practice for adoption and integration orchid, or open researcher and contributor ID orchid this invigorates individuals through a unique persistent identifier and links them to various systems in the research life cycle with orchid being platform independent different vendor and open source systems can link to orchid through API's. These links save time for faculty and researchers through an exchange of information to and from their orchid record, and it streamlines organizational processes and workflow through connections across systems. In addition to orchid if you're not already assigning do is to data sets and other scholarly content that your institution is responsible for, you can consider joining the lyricist data site us community. This program was started in 2021 as a way to lower the barrier of entry for organizations to assign do is to local content, which again contributes to making research and scholarly content more findable accessible interoperable and reusable. Do is and other persistent identifiers such as orchid and roar which stands for research organization registry. Allow us to make connections between entities in the research and scholarly communication landscape, so that we can better assess impact, not to mention that publicly available do I metadata makes resources more discoverable for reuse. The lyricist data site program provides membership cost sharing dedicated support and a community of practice around do is in the US and beyond. There are other data site consortia in the US based on geographic region or platform, but if you're not already a member of data site or one of these consortia, any nonprofit organization can join the lyricist program to get started with do is. Thank you so much for taking our program web page and contact us with any questions. Thank you Sheila. So the last program that you might be less aware of is the iris us community, as Sheila said, iris stands for institutional repository usage statistics. And it's a platform independent aggregation service enabling institutional repositories to share and expose usage statistics down to the individual item level based on the global counter standard. The program shows in detail the process of using iris basically institutions install the iris tracker iris collects raw download data for all item types and processes that raw data into counter conformance statistics. That means that anything that can be counter compliant is counter compliant and anything that is not covered in the counter standard is made as conformant as possible, even though it technically doesn't count under counter. Those statistics are aggregated in open access statistical reports which can be exported in various formats. Because reporting is open access institutions can easily share usage information with individual researchers and administration. Compare usage information with peer institutions and use usage information to identify national or even international trends. There are many benefits to iris because it is counter conformant repository usage can actually be compared with usage for more traditional forms of published content within a library system, allowing for better holistic strategic decision and because iris data is open access. It can be easily studied by multiple levels of individuals both within an institution such as librarians individual scholars research offices and deans, and in higher level granting and funding agencies to aid and decision systems. There are two types of reports platform level usage and item level usage within each report you can look at investigations, which is the counter language for saying how many times users land on a page versus requests meaning how many times they actually open the research material on that page. And on the right side of the slide you can see a screenshot of a custom item master report from iris and as I said before these are open access so there's no barrier for anyone to see these. You can see lots of options for customizing reports, including filters for institution, the repositories within an institution if there's more than one timeframe and even item type iris currently supports. D space e prints equal a big share haplo pure portal Sam Vera work tribe and most recently explore iris as you can see is platform independent. It already works on multiple platforms and can be programmed to be incorporated within any other software available. This means that repositories whether across institutions or even within institutions can be compared to each other regardless of almost any platform they run on. As I said there are current integrations for iris listed on the slide but we're also working with institutions who have completely homegrown solutions, and they can create their own integration so there's really no barrier to using iris. So, let's put all of this together into our small but mighty case study. Normally, we as lyricist staff would not have the opportunity to implement or use the products we negotiate for the library community. But we had a rare opportunity to bring all of these services together thanks to the implementation of our new research repository lyricist research. We've released this summer on our d space direct platform and it contains all of our survey reports grant related reports and our internally funded catalyst fund white papers and presentation slides. And I'm just going to quickly go over how we're incorporating these services into our repository, the steps may seem basic, but they actually point to the ease of incorporation for each of these three services. Now, you can see from this very simple screenshot here if we go to one of our reports the first thing you can see is that we have implemented do wise, because we are actually lyricist itself as a member of the data site us community. And we've implemented do is for all of our materials in the repository regardless of content. So if we go into the data site form. We have the opportunity to identify authors based on what data site calls a name identifier which allows you to input an orchid ID. This means that orchid recognizes the do is registered within our repository. And if you within orchid allow data site to discover works using your orchid ID, they can actually be automatically automatically uploaded to your profile. So we've created a policy that anyone who receives a catalyst fund grant from lyricist is required to register an orchid ID, which allows us to properly credit them when their materials are uploaded to our repository. The last piece of the puzzle is iris and this is the one we're actually still working on. So, as I said we have the DIY is assigned and within the DIY metadata were able to input orchid IDs. We have not yet installed iris and this is because our hosting services are systematically upgrading to d space seven, which has the iris tracker protocol built into its implementation. So once the lyricist research repository is updated to d space seven, which should happen by the end of this calendar year. We're implementing iris so that we, along with all of our catalyst fund partners will be able to see usage of our publications using counter conformance statistics. And actually there's going to be a new development within an iris to search by item level do is. So really all of this comes together to create a really clear picture for the researcher or the author to be able to get credit for their work. Now these are fairly basic uses but they are still incorporating all of the tools and bringing value to our researchers and our partners who interact with us, both within and without lyricists. We're looking forward to new developments in all of these communities happening in the next year. And we just want to say thank you if you're interested in learning more about iris please contact me Hannah Rosen at Hannah dot rosin at lyricist.org. If you're interested in learning more about orchid please contact Paulo Guhilde at at his email. And if you're interested in learning about the data site DOI consortium you can contact Sheila Raven at her email. So thank you very much for taking the time to watch this asynchronous presentation and have a wonderful day.