 I would like to welcome you all to the second RPO training in the framework of the National Open Access Monitor project for Ireland, and paving the road to 100% open access. First of all, I would like to tell you that I try to focus this second training to specific aspects regarding the monitor and the RPO when the repository monitors and dashboards, respectively. I will go through details during my presentation, because I believe that most of you have already attended the first RPO training in November, and you have a general idea of the project, how open air functions, the workflows, and how we build the National Open Access Monitor for Ireland. Of course, any questions and any predicures you would like to ask regarding any of the processes, please ask, even also when interacting with me during the presentation. It would be better if it is an interactive session among all of us. So this is the outline of my presentation. We will have an overview. We will talk a little bit about the open air graph and data quality, and then we will go to the aspects that I have already mentioned regarding the monitor, the linking functionality, the functionalities, and the options that the primary dashboard managers of the RPOs have in the IS monitor, the open org platform, and a few cases in regarding the duplication and the disambiguation of your organization, regarding the data sources, the repositories. We will talk a little bit about the open air guidelines, the compliance, the registration to open air provider, how we cope with the existing, the registered repositories, but also the repositories that were not registered in open air and were not compliant with the open air guidelines. As a final aspect, we will speak a little bit about the APCs and the data that we get from open APC garden institutions. And we will also talk about the next steps and how we will go in the work in progress that we have until the delivery of the monitor by the end of June. So what you have already know, the monitor consists of five dashboards. It's the national dashboard, the dashboards for the research funding and the research before organization, the dashboards for the institutional repositories and the researchers. And our focus on this training will be on the, for the RPOs, plus the research, the RPO dashboard, the RPO and the repositories dashboards. So why an RPO should have a dashboard and how to use it in order to establish a national level visibility for his research. They can compare the open access performance against other peer institutions and should compliance with open access mandates and uncover weak spots and insights in order to guide evidence based decisions inside the organization. Of course, these are aspects as we can use the pilot platform. Of course, we cannot understand the visibility aspect of the dashboard. And regarding the compare the open access performance against peer institutions, you can do it. You can view indicators in the cross RPO topic. You can compare by the number of peer-reviewed publications, the number of open access peer-reviewed publications, the golden hybrid open access peer-reviewed publications, the ones with an orchid ID and several other comparison charts. As you will see in all the charts, the RPO that exists, the RPO whose dashboard we see right now is in the first column here. And this is for, in our case, the Trinity College. And of course, there are also Zoom capabilities for its chart in order to see the differences and the numbers. In the RPO monitor, we have two views, the indicator view, as we have just seen, and the research output view. To the indicator view, you can guide to several topics from scholarly production of the RPO. Well, you can see the publication, the peer-reviewed publications, the open access peer-reviewed publications with license, followed up by the access rights, the open access routes, the fair aspects, APCs, the cross RPO as we have already seen them, the academic impact topic regarding citations and downloads. And of course, to the browse research products, where you can view in detail all the research products that are used in order to build the monitor. So regarding the repository dashboards, and mainly for the institutional repository managers, why do you need to have a repository dashboard to ensure open access publication from the repository are accurately reflected. And in order to facilitate the comprehensive coverage of the monitor of Ireland by having more data sources for the research product coming from the RPOs from Ireland. Now, if a repository is registered with open air provide, first, they can elevate their records, the metadata with precise validation and the enrichment of their metadata. As in open air, we can provide them with richer metadata that we get for the same research products from other data sources via the open air broker service. I will go through in detail in the next slides. Of course, they can gain insights from detailed user statistics through their repository, the downloads, and simplify open access compliance to promote effortless content dissemination. So this is a screenshot of the open air provide platform. When apart from the details regarding the aggregation and the record collection from the repository, the enrichments that have been made, the downloads metrics and indicators from the repository. And for the repositories that are registered in open air, they have access to the open air provide service as you see right here where they can register, validate, and then these records. Of course, all this as a prerequisite for the repository to be compatible with the open air guidelines. And all these usage counts which are also visualized in the repository monitor here in the National Open Access Monitor for Ireland platform where we can see the publications, the peer reviewed publications, and the open access with license peer reviewed publications that come from the repository. And with several breakdowns by fields of science, SIGs, and of course by access rights where we can see mainly in the access right topic the open access versions of the publications that are released from the repository. So if you watch the guide in the open air graph and the data quality, this is the workflow, the graph, the open air graph pipeline where we aggregate through several data sources and also through open air provide from the repositories that are registered into open air. And we perform various tasks that enrichment by mining the duplication and enrichment by inference. And after finalization we have the final product. And the Irish monitor sits right here where we get a subset for the open air graph for the Irish monitor. And after the user feedback, which is your feedback regarding the data quality, we perform the same workflow in order to improve the quality. And another schema here for with the architecture of the open air graph and where the Irish monitor stands, of course, the open org's platform that needs to deduplicate the organizations. And of course the open air provides platform with all the services of the validator, the guidelines that the data sources need to be compliant with in order to register to open air provide. I will go through this slide quickly as it is states that the sources that contribute to the graph, to the open air graph. And we have a very large number of data sources from Crosser, DataSide, La Refinancia, DOE, HA and AFRST. So additional tasks in order to improve the data quality in open air graph, we have the deduplication task workflow where open air graph measures duplicate records of the same scholarly work and it offers these duplicates through open air explore the different versions. I mean, if we go to the browse research products and we go to a specific publication, for example, at the top level here, we can see all the data sources that this publication has been collected from. The specific publication has only one data source and this is Crosser. This publication, for example, has eight versions and as you can see, we perform deduplication, but we also keep all the versions of the publication from the respective data sources from universities, institutional repository, from archive, DataSide, European Union Open Data Portal, Sigma, AWOL and Europe PubMed Central. We have performed enrichment through text and data mining, where we perform affiliation citation and concept extraction with document classification regarding the field of science and SDGs and similarity assessment, cleaning processes with independent continuous aggregations where we utilize vocabularies to harmonize the diverse data source records and thus we ensure consistent and accurate bibliographic records. And of course we have additional disambiguation that we perform for journals, publishers and licenses as we receive also these with different names from different data sources. Additional data quality enhancements for the RPOs and the repositories. For all of them, it's the linking functionality that we offer through the RIS monitor. We will talk a little bit about this in the next slides. There is an abduation via the OpenOrcs platform and of course the registration of the repositories to OpenAir Provide and the compliance with the OpenAir guidelines. So linking functionality. You can log in to the RIS monitor via your institution account. Once you log in, you can access the linking functionality from the top right corner of the platform by selecting the initials of your name and the link option, where you can associate any research output with projects, communities or other outputs. This association, these links will show up in the next OpenAir OpenAir Graph update. Here I would like to mention that the OpenAir Graph workflow updates every month. So any change that we make concerning the content and the data itself will be depicted in the OpenAir Graph and of course in all the services. In the next update, it will be in one to two months. It depends on the date that we perform the updates, the changes. And of course a log for all these linking actions will be always publicly visible in the platform and this is in the resources and help, web statistics and activity logs in the monitor logs tab, where you can view all the actions that users perform in the monitor platform. And this is from, of course, all this data is anonymized. These logs have all the actions that we offer through the RIS monitor platform from the claiming of a work from an ORTID ID or the upload DOIs functionality, where a user can upload the text at the CSV file of containing DOIs and the RIS monitor platform performs a check to see which of these DOIs are present in the RIS monitor. And of course we have been developing a new functionality which will be available in a few months, where also primary dashboard managers will be able to upload a set of DOIs, position identifiers, mainly DOIs from these research products, that they want to be affiliated with their RPO. If these DOIs, for example, are not affiliated yet in the RIS monitor, because we could don't have any affiliation for the DOIs, a primary dashboard monitor can give us these DOIs and we perform this affiliation. This is RPO. These are two screenshots from the linking functionality, first one where we select the research products, the research output, and the second one where we select the projects and the confirmation of the linking. So the duplication of the OpenOrbs. OpenOrbs is a platform developed by OpenAir in order to perform this aggregation of the organizations, because we receive the same organization with different names from a variety of names, according to the data source that we collect information from. And the OpenOrbs is a platform where we deduplicate this information and we assign all these different names to one entity. And thus this information passes as a deduplicated information in the OpenAir Graph in order to have one name for the RPO. In the end of April we are going to have a dedicated OpenOrbs training webinar, the first one from the three that we will give for the RIS monitor project, where you will see in details the platform and how to perform the disambiguation of your RPO. So in OpenOrbs there is a specified specific process on becoming a curator. First of all you will need to register for an OpenAir account and at the first login in the OpenOrbs platform, by using this OpenAir account that you have created, you will request to become a curator and then OpenOrbs team will process your request and you will be able to curate the information for your organization. Currently we are in the process of contacting all the primary dashboard managers of the RPOs that have already been registered to the RIS monitor platform in order to perform this process. We will be sending the emails in the next days. So one important question that has been asked by many RPOs and we've also saw it also in the survey from the island that the RIS project has conducted in November is that there are several organizations, several RPOs that are not displayed in the national open access monitor. What happens with this organization of these RPOs and what should I do if my RPO is not displayed there? When you can't see your RPO this means that your organization has not been incorporated into OpenAir and thus into OpenOrbs platform. The process to fix this and to add the organization first of all is to contact us in order to identify the issue. The second step is every organization in order to be incorporated into OpenAir needs to have an organization ID, the most common ID and the most that is used. Globally the ROR ID and this organization should request a ROR ID in order to for OpenAir to be able to incorporate it into the infrastructure. So once you request a ROR ID and you receive it you can inform us and then we will perform all the requested workflows and we will process your organization. The next steps is to process all the RPOs that you filled the survey the national open access monitor island survey and do not have a ROR ID and we inform them about the specific process. This is just a simple screenshot. I'm not going through details on the OpenOrbs disambiguation because you will have a dedicated webinars for the platform. I would like just to mention that for the initial phase of the monitor we have performed a deduplication of the main the biggest RPOs from Ireland. We perform the deduplication ourselves and for example this screenshot is from the National University of Ireland main from the main university where the deduplication has been the initial deduplication has already been performed. Of course apart from the deduplication there is also the disambiguation of the parent and child relationships where you can have schools and departments for each RPO. This will also be covered in the OpenOrbs webinars. So we're going to the primary dashboard managers. What extra things do what I can do more as a primary dashboard manager in the RS monitor. This is my question. So a primary dashboard manager first of all it has access to the sandbox environment of the RS monitor where they can verify data quality and check any new or updated metrics and indicators because whenever we perform any updates on the data on the content or we have new metrics and indicators this first pass from the sandbox environment and once verified they will go to the production environment. Second they have access to the OpenOrbs platform as we have already discussed and of course they also have the ability to add to invite and to delete other users as managers. Now to access my admin account as a primary dashboard manager after designing you can select your initials on the top right corner and then select manage profiles. So how to do it once you're assigning and you select the manage profile options you will be shown all the profiles that you are assigned the role of monitor or primary dashboard monitor and by clicking you can view the admin account. What actions can you perform in the admin account? First of all you can change the details for your app you can see the display name the locale if you want it to be in english or europe locale the name as we have already said we can add a description and also a logo for your app and of course you can also invite other users as managers. So let's go to the repository part section and the OpenAir provide platform and the compatibility with the OpenAir guidelines. First of all OpenAir provide this one stop shop web service or data sources, institutional and thematic repositories, data repositories, channel aggregators and other entry systems who can interact with OpenAir by sharing and exchanging metadata and content and of course they also have through OpenAir provided also have front and access to many of OpenAir's backend services. I will go through quickly to the functionalities in the OpenAir provide platform first you can use the validator service in order to validate the metadata records against the OpenAir guidelines to measure the compatibility with the OpenAir guidelines you can register your repository in order to be aggregated by OpenAir you can see details regarding the aggregation history how many records were collected how many were transformed you can have enrichment of the metadata records improving them and you can use the OpenAir broker service to download these enrichments and use it for your repository you can enable the user account service in order to have global metrics and a comprehensive view of the downloads of your repository and of course you can get notifications alert regarding the arrangements errors or other any useful information regarding your repository. So compatibility with the OpenAir guidelines especially with the latest version of the OpenAir guidelines version 3 and version 4 you have improved interoperability since you meet the latest IT and repository standards because when you are compatible with the OpenAir guidelines you have a more contextualized content a more flexible content thus you can use different and improved vocabularies and of course your content is embedded in the enrichments and infrastructure ecosystem as it is aligned with the OpenScience mandate standards and it will be in its supports it will support well-established metadata schemas and namespace abbreviations as the OpenAir guidelines follow well-established schemas and abbreviations. Of course it is your role to fairness because if you are compliant with the OpenAir guidelines then you are also fair enough as the OpenAir guidelines cover most if not all aspects of the fair principles and of course it is your anti it is your gateway to the OpenScience cloud as thus if you are compliant with the OpenAir guidelines and you are aggregated by OpenAir then you will be automatically onboarding to the EOS product catalog and marketplace integrated platform and this is a link regarding the details on the upgrade the compatibility of your repository with the OpenAir guidelines to the latest versions where there is also information about registration into OpenAir Provider. So what are the key points to follow in order to comply with the OpenAir guidelines? First of all you should expose your repository metadata via an or a IPMH endpoint as stated in the profile of the OpenAir guidelines webpage you can follow the instructions to populate all the fields you should at least populate all the mandatory fields in order to be compatible and or the mandatory if applicable fields and of course the more fields you populate the more better will be the data quality and the more better will be the results in your RPO dashboard. So in the question of how do I expose the metadata of my repository there is a for version 3 and version 4 there is a publication respective publication it's another for version 4 is this one where you can see apart from the documentation that exists also in the website you can also see record samples and the metadata the excess decimals on the metadata that you need to form on your metadata records. So regarding the validation of the registration the validator service assess the metadata quality basically you run a test to set the compatibility against the OpenAir guidelines you get a score a compatibility score the percentage on how much compatible you are but this metrics serves as an indication only and does not confirm full compatibility also you get a detailed report on the number of records that are passed for each guideline and an indicated number of failed records from your endpoint with warnings and errors in order to see what is the problem. So there is a station process in OpenAir Provide you can follow the link in detail to see how to register after you perform the registration the aggregation team will evaluate the compatibility with the OpenAir guidelines that's why I told you that the method from the validator is not it's just an indicator metrics because we also evaluate the compatibility after your registration and you can see it in the OpenAir Provide platform in the three metrics that we have in each interface we have the desired compatibility level which is the compatibility version of the guidelines that you have selected for your repository the compatibility level is the one the current compatibility level is the one that has been written by the validator tool after you have registered the interface and the compatibility override field is the actual compatibility level which is the one that is populated by the aggregation team so regarding the Irish monitor currently we have 13 institutional repositories registered with OpenAir three of them are compatible with the OpenAir guidelines version three and ten are compatible with the OpenAir guidelines basic version and version two and we also had eight institutional repositories that were not registered with OpenAir for the repositories that were not registered with OpenAir we initiated ourselves the registration process and harvested the metadata records and we have adjusted the transformation rules internal transformation rules that we have for each repository in order to transform to custom transform the metadata records thus ensuring the enlightenment with the OpenAir guidelines as much as possibly we could the primary focus of this effort was on crucial fields crucial fields for the harvesting process and were applicable of course the identification of publications the crucial fields we tried to map were the business identifiers title author publication date resource type of course and access rights information we one of our next step is also to contact the app users that we have performed these actions the institutional repository and see how we walk through the next steps on maybe complying with the OpenAir guidelines such we need to have more improved information for the IPO and the repository so our work in progress is as I already said to check and refine all the repositories the Irish from Ireland their compliance with the OpenAir guidelines and their aggregation in order to improve the data quality and as I already said for the non-compliant repositories we are facing difficulties in identifying the correct fields to map to the OpenAir guidelines for example we have the dc for a from a repository a specific repository that was not registered with the dc the dc doubling correlation field which in that repository is used to serve the pages and identify of the metadata record on the specific the specific metadata record while in the guidelines this field is used to identify the position identifier of any related research product and not the product itself so also a few words quick words regarding the apcs as you will see in the apcs topic in the apio monitor we have three sub topics we have the apcs reported to open apc by any co-authors institution we have the apcs versus transformative agreements and we have the apcs reported by the institution itself in open apc so what are the differences between those these two the first one are the apcs that are reported to open apc by any co-authors institution this does not mean that the specific institution the specific apio actually paid the fees for these apcs but the second we'll let the apcs that were reported have been reported by the specific apio in open apc identify the publications that their apcs were actually paid by the institution and one thing that we have identified in several apio with island is that they don't have they haven't given the apc from apc information to open apc get and additionally there will also be a webinar a training webinar for apcs from open apc in april or may it is to be scheduled and you will all receive an invite once we have the date so the next steps first of all this is the link that for the first bullet you can see the link of our help desk where it is the place where you can use the link you can use to contact us or regarding any issue you might have with the platform with the monitor so therefore for the primary dashboard managers they can register and request to be a primary dashboard manager of rto via the dashboard manager application for or via the help desk url above as i have already told you there is there are going to be training webinars for the open aux platform and the apcs you will receive invites once we have the date the dates confirmed and of course we need to have work in progress regarding the institutionary repositories following the opener guidelines and registering registering with the open app provide and of course for the latter our main goal is to upgrade the compatibility of all repositories to at least version 3 or version 4 of the opener guidelines and this could also happen by aligning with the national open access repositories initiative led by the university of galway and which it developed parallel with the monitor and we are in contact with them and of course with you and very much for your time