 And thank you for joining this community call. So can you see my screen, the entire screen, or I'm sharing, I think I'm doing it in the right way. Okay. Yes, yes. Okay, so one more community call is targeting all those that are part of open air infrastructure as a content provider. So providing content from your data sources, data sources that you manage, different kinds of repositories or other kinds of systems that share scientific information from journals, data repositories, et cetera. So thank you for joining. There are always newcomers, sometimes no. Today it's a community call dedicated to the user's statistics service. And specifically for this change that we are implementing related with the counter code of practice reports that we have in production in currently, but we are integrating with the new release. So we want to highlight and discuss a bit with you. We have some thoughts about the implementation process and we would like to have your opinion. So please, if some of you can be active today contributing and providing feedback, this will be useful because we have this community call really to receive us feedback in order to decide what we want to do in terms of implementation. So we will tell you about this, about that Dimitri Spiarakos that is here with us. We'll be the main presenter and we'll highlight what we want to discuss. We have a kind of mentee meter just to support the discussion at the end. So we will really like to have your feedback even for those that are not using. So you can be aware and then also provide your opinion. This is what we want to highlight. So these updates and a bit of knowledge. We have the feeling that the community of repository managers at least are not fully aware of all the changes in with the reports from release four to release five. We want to implement it in provide because we are ready for that, but the community, we are not sure if it is ready. So let's discuss a bit this. Before I pass the word to Dimitri's two or three highlights. Some of them are already presented in beta before, but be aware that we have a new index update. As we told you, sometimes we are not complying completely with the monthly update, but all the technical team from OpenAir is doing really an effort to ensure that we have this monthly updates depending on the integration of relevant data sources or big data sources or the changes in our infrastructure or slight changes in the data model. Sometimes even all the work that we are doing with some with the YOSC development. So we need to do some changes and sometimes we need to postpone some updates. Sometimes we have issues with relevant data sources and we need to postpone the update, but at least if Andre can correct me, at least I think the last two, they went like really monthly. Yes, yes. Thank you, Andre. I would like to thank you, and I would like to thank the technical team in particular persons in charge of aggregation in charge of managing the open-air graph. Two relevant updates. We deployed in production a new version. In fact, we did it live. It was critical because now we are integrating in beta some changes to align with developments that we are doing in the YOSC future project. And it's more difficult for us to manage deployments to test it in beta and then put it in production. So we are doing it in some critical way. So we received from two or three repository managers some requests or some feedback saying that the service in one of the mornings were not able at least some time during two mornings in the last two weeks. We were deploying in production the service. So maybe the service was an unavailable for some time, not too much. But we did these updates. Two relevant updates. The terms of use. So we have it in production. Okay. You are not seeing my screen too. Just for a point. Only the power point. Change this to make it more easy to me. Okay. Life changes, which is always interesting. Okay. Now I think you can see. Can you see? Yes. So terms of use. For some of you, if you join the open air, if you access the open air provide now and you didn't. And it will be the first time after the 24th of May. You will see a pop up window. In front of yours in front of you in the screen to update the terms of use. Maybe you have done that. So the terms of use can be also updated anytime in the. Okay. In the. Always a surprise. His morning was working well. I think it was because I have this open. It's a while. So you will see. Important. Let me let me highlight some terms of use. What is important is to say that. We didn't change nothing in our policy. Okay. So it's always important. I know that some of you already know already heard from me this. This explanation. So it didn't change nothing in our policy. It's just a question of update and have all the providers. At the same page and having the possibility to update the terms of use in terms of providing metadata in terms of providing full text as we did. In the last year. We have changed the update over the last years to our policies and we have done. Changes in the. In the. Different registration process. So we started with registering. Stuff in 2012. Then we did change in our policies. 2014. We have the last update was since 2018. It's important to ensure that everything is working. And provide is not working. But I'm not sure if it is my fault or if it is. And I also have the same issue. So let's proceed. We have slides. And we can proceed. You will see if it at the end, the things are working. I will present it. So access the terms of use and you can see. That this, this update. So this will have a pop up window. If it is the first time at any time in the update tab, you can update the terms of use and this will work. I know that several, we know that several repository managers already did over the last two weeks. So we can. We can do it without any, any problem. Chris system registration is also working. I know that some few have already checked and did the, the Chris registration. I know a colleague, a colleague from Portugal, in fact, did it last, last week live. So this was something that we really wanted. Chris systems are part of open air. And now we can say that the workflow is fully integrated. So we have guidelines. We have validator and we have a registration process. Finally, and Chris systems will be made available in the information in explore in the list of providers. So we can fit them in the be guided by this registration workflow and the content will be made available in the search for the benefit of all the types of services. Also, this is in production since May 24th. We had some issues just after this update for four or five days with a monitor history, but everything was, was solved. So public roadmap is always available for you to, to provide feedback. If you want, we will try to update it every month with the, the new feature. In fact, we need to update all the changes that we did by the end of, of, of May. Let me do another try. I don't have problems to test this life because if it isn't, that doesn't work. This means that this will work at some time. So unfortunately something happens. Sometimes it's not related with the provide services related with the authentication and authentication. As you know, there's always a type of service that sometimes we cannot fully control another try. If this doesn't work, then I passed the floor to the nitrous and we will try to, to do it at the end. Okay. So please don't do it right now. The updates, et cetera. We will try to figure out. So two important updates. Okay. Terms of use are really critical for us in terms of having all people in the same page updates, have an authority to download your PDFs, test mine your PDFs. I insist. As you know, we don't provide direct access to PDFs. We always point to the original data source. We have other aggregators like open air that do the opposite. They direct the to, they download the PDFs and they direct the PDFs in their infrastructure, which is a practice that open air don't do. And we in fact don't like, and we know that the providers that also don't like this kind of approach and open air doesn't do that. So we need your acceptance of the terms of use in order to update and also to download the PDFs to provide edit value services. Dimitris, let's now present this user statistics updates. Let's see if at least those people that are here involved and I see some, I recognize some names that people that are using statistics service beneficiaries. Let's see if we can have the feedback and if we can have them provide them and pioneers. If I might say, yes, yes, yes. Let's see. Let's see if we can have some discussions around. So, and then think together about the changes that we want to do. Okay. Thank you. Thank you. Let me share my screen. Yes. Can can you see my screen? Perfect. Perfect. Yes. Okay. So, welcome to this community call. Thanks for the introduction. I will try to provide in this presentation, a brief introduction to counter code of practice. In general, and what we have to do, what are the actions and the steps that we have to do in order to migrate if the community decides to migrate from and release four to release five. First of all, I would like to give a quick introduction and recap of the usage counts on the usage count service. The usage count services, the use of statistics service of the open air research graph. What it does it tracks and counts the usage events of research products of the open air graph. And when we say research products, we have a lot of data sets, books, et cetera. And this is realized using two approaches. One is the tracking of users with specialized. Service site software, like parties for platforms for like this, like the space or plugins for platform like a prince. Or a generic tracking tool with, which is applied in a web server dogs. And we call this approach, a push since we are retrieving a usage events directly from the providers. And the second approach is by collecting the counter reports from aggregators like Iris UK, for instance, we call this approach pool. And currently we support the release for and release five code of practice reports. So for instance, for, for, from Iris UK, we are retrieving a release five reports only now, because they have stopped publishing counter code of practice release for reports since January 2022. All tracking is performed by respecting users privacy. This is why we use an organization of IP addresses. We are also exploiting what is called the the duplication of actionality on metadata, which is offered by open a research graph that enables the accumulation of users for the same research output, the same research products. So in this way we could have aggregated user statistics for the same research product and from multiple resources. In other words, multiple repositories. The services also counter code of practice compliant, which is the topic of this of the today's presentation. And what it means is that the service provides standard base user statistics. Finally, the user statistics produced by the service could be considered a form of indicator that complement other traditional and alternative bibliometric indicators to improve to provide a co-brehensi. And most importantly, a recent view of the impact of academic resources. And this is what we think what we consider is is one of the main features of our service. So most of you, you are aware of the service you have deployed it. So if you don't please join the service week, we are here to help you with very straightforward process. So now let's discuss how the main topic of this presentation, which is the counter code of practice. This is the timeline of the development of the code of practice. As you can imagine before counter, there is no common standard for user statistics, meaning that user statistics are not consistent and are not most importantly, they are not comparable. They are not standard. The first release of the counter was back in 2003 and has been implemented to support journals and some form of databases. So the metrics that were used to count user events were the well-known metadata views and full text downloads. Since then, there are four more releases with which the most important so far was the release four that include the 24 reports and and cover the variety of research products like multimedia and books. But in 2019, a new release of the code of practice appeared. This is the way user events are counted by introducing new concepts, new metrics, new form of reports, filters for the reports, etc. So this is, in my opinion, considered a major huge upgrade of the counter code of practice releases. So counter code of practice releases the current status of the open-air users count service compatibility. I will focus on the implementation deployment of this. So we have implemented the release four and we support the well-known metadata views and downloads of the counter code of practice using visualization as you can see in the slide like monthly views or monthly downloads. We have also implemented five release four reports in order to be able to view and retrieve the user statistics for repositories. We have implemented the article report which represents the number of successful article downloads request by monthly repository. The item report, number of successful item downloads request by monthly repository. The number of successful item downloads for all repositories participating in the user statistics service and we have also implemented since they have been requested to book reports, the number of successful title request and the number of successful sectional request. These are all here to the counter release for code of practice. And for its report you could apply filters that allow you to select the period of the report, the research product which can be identified by each identifier which could be the open-air identifier, the DOI or OAPMA identifier and you could also select the granularity of the report which could be either monthly user statistics or the total statistics for the selected period. So in terms of filters we have only four options, the period, the identifier and the report, the granularity of the report. This is the tabular form of this particular report which is article report results where you could see the information like the title of the item, the publisher, the type of research product and of course the user statistics for this particular period with metrics downloads and events. So this is the current status that we are offering right now that we implemented it is available in providers dashboard. Now let's discuss the upcoming updates which is the implementation of the counter code of practice release 5 the latest release. As mentioned in the previous slide the code changes completely the way that user events are collected, counted and published. So I will try to explain what are the new metrics and what are the reports for this release. I will try to provide some examples and the comparison between the release 4 which is currently offered and the upcoming release 5. I will try to discuss the new concepts that are reduced like the data types, the access method, the access type and the year of publication which this release 5. So first of all metric types. We have to forget the traditional if we are using of course the counter code of practice 5 we have to forget the traditional views and downloads metrics and move to the new metrics for release 5. Investigation and request. So an investigation is tracked when a user performs any action in relation to a content item for release 5. So for example if a user visits a content provider and views an abstract views an HTML in full text views a PDF, downloads a PDF or views a preview of an article these are all content tracked as investigations. On the other head a request is specifically related to the viewing or downloading the full content item. So we are forgetting again we are forgetting views and downloads and we are using investigations to count every action any action which is related to a content item of the of the content provider of the research product and request in order to represent the to count the view and download the full text download of an item. So a full text download is an investigation and the request at the same time. So new metrics are also using the suffix unique and total to further categorize the metric type so we have the unique item investigations which count unique article investigations and request inside the user session and the total item investigations counts total number of items information related to the article viewed including all article full content views. The total item request which count all article full content views across all formats like for example HTML and PDF which is the equivalent to all the release for metric type which is defined as count as downloads and finally unique item request which counts full content views within a given session regardless of format. So for example if a user views an article PDF and HTML in the same session this will only count as one. I will provide a concrete example in the next slide. So we assume that Susan is researching the history of Porto inside the Umino repository and performing research receive a list of search results and she decides to open three article abstracts the counts are three total item investigations and three unique item investigations so far. After reading the abstracts Susan decides to download the PDF for two of the articles. So the counts change to five for total item investigation three as old views plus two as old downloads three unique views three unique item investigations correspond to the three old views and two total item request and two unique item request so this is the change between the old and the new versions of the metrics. If we want to compare release four and release five metrics we could not download the request as you could see in the graph. We have collected both user events and we represent them both counter code of practice releases in release four and five for since two thousand twenty the January two thousand twenty two since April two thousand twenty two and you can see that download request are almost the same. On the other side views and total item investigation are completely different metrics so as we mentioned an investigation is any action that is performed inside a content provider it's totally different than the old metric the view. So just to recap the code of practice release five metric time features total item request there are considered important from providers that have full text content of course and reports the number of full text downloads or views the total item investigations provided a big picture perspective of the total number of investigations while the unique investigation request are considered powerful metrics for identifying activities within with unique items and titles and they are considered from content providers this is why probably they have proposed and developed this metric they consider most accurate for calculating cost per use since they are operating inside the unique inside the session not on the whole activity so having discussed the new metric let's move on to other concepts which are used in release five for example data type is pretty self is a new concept pretty self explanatory data type defies the general type of content which is being accessed or for which users being reported of course corresponds to articles books collections databases data set journals these are considered data types access type it's a new concept introduced in release five it describes the nature of access control that was in place where the content item was accessed so it's controlled open access delayed this attribute has been this attribute appears in a specific type of report the general type report one and allowed users of open access content to be separated from content that requires a specific license another new concept is is the access method which is a concept that indicates whether the usage related to investigation requires corresponds to a human browsing the content provider the repository for instance or a kind of a robot let's say is trying to access the site generating a number of events this is performed for example this is done for example by using text and data mining software this is what what is called this access method is called TDM so we have the regular TDM excuse me the regular access methods and the TDM access methods corresponds to kind of of crawling the website for retrieving content and finally the R5 also introduces the concept of the year of publication which is the year of publication for the content item access if content is available in print in online format the publication dates of these two formats differ code of practice proposes to use the year of application of the print version of the article all these concepts are new and of course we require further examination and not the short introduction that we are trying to do right now but just just a short presentation to have an idea of the new release so in terms of reports counter code of practice release 5 offers a reduced number of repose it offers it provides 4 master reports and 16 in total versus 24 in release 4 many of the special purpose reports that are randomly used are replaced with a small number of flexible generic reports in release 5 all counter release 4 reports have either been renamed or eliminated in favor of other counter release 5 report options and the most important part is that there are a number of new filters that could be applied and reduce the results or provide more specific results for the reports for example you can use dates or data types, metric types year of publication license types as already discussed and you can also combine these filters to retrieve more specific results this is the list of the available counter release 5 reports we have the master reports and the more standard reports I would not go into details for all these reports just to mention that in our release implementation of the release 5 reports we have developed two master reports the PR and IR the platform master report and IR the platform master item report the PR is the report summarizing user activity for the repository by month metric type and item type and the IR is the old IR1 report for items requested by month metric type, item type and repository we consider these are the most useful reports to provide and we also have developed the platform master report which reports summarizing user activity for the repository by month broken down by metric type in addition we have also added the data set report which is not included officially in the counter release 5 code of practice set of reports however it has been introduced by make that account initiative for reporting user statistics for data sets explicitly so the report also uses the new metrics that have been introduced in the release 5 investigations and requests so that's why we have developed this and we are offering this report as well the three the main three reports that we have developed is the reports that are currently offered publicly from iris UK so we have decided to follow the same path however we are open and we could develop any other kind of report that you might be interested in so this is how the new interface of the providers dashboard with the new release 5 reports could be displayed so we have the platform master report with a short description the platform usage the item master report and the data sets report for selecting the report you could see the filters that you can apply for example you can have the data range, the item identifier again opener DOI or ID identifiers could be used and for a particular report the platform master report you can select the metric type that you want to apply either all of them or a combination of them or a single of them this is a main difference between this release and the previous release where you can only have a minimum set of filters that could be applied so this is an example of a platform report of a platform master report you can have a platform for example you have the university of the repository of Mino and the data type is article and the access method is regular and the total item is the metric type and we have selected the total period as a granularity and you can see the numbers here for this particular repository this corresponds to the platform for a certain period of time finally just to indicate the number of attributes that are available for the master reports for reports and items and with a yellow color we have indicated what we have implemented we consider these are the most important and somehow mandatory but all other attributes could also be included in the if of course the metadata information is available so this is more or less the presentation of counter code of practice and how we could migrate from release 4 to release 5 thank you and if you have any questions I'm glad to ask to reply to you really great presentation Dimitri thank you very much really comprehensive and quite clear this is what we need for this moment I think it was very good for sure there are things that people need to understand better of course there are always the support information from counter code of practice that is being developed and also not for the proposal only for the proposal for repository statistics also for other things that you will know from scientific journals etc so any question any question to Dimitri maybe can we move maybe to the if you don't have any question I think it was I can see one we have a question from Elidik yeah that's 38 repositories in the Netherlands being housed by OpenERC can the metrics also be made for NERSIS for the repository NERSIS I assume that you are an aggregator right yes every time we have a presentation I ask this can you please contact me because we can of course we can you can join and we can retrieve you such events from me okay I will contact you okay if Elidik asks something I also can you say something okay I will share my screen just to show because it is quite easily to show so this is one of our repository Veterina is the name of the repository so in this window this is how it is displayed in the OpenERC Explorer yeah and on the bright side this is how I see it in my provided dashboard which means that I understand these numbers they are collected by the OpenERC statistics but it could not be seen here and the institutions usually use this one yes yes I know as you mentioned usage events have been collected they are displayed properly in the dashboard in the providers dashboard they have been collected until 2022 April 2032 and now we are collecting for May but we have a problem with our statistics tool that displays the graphs and these graphs are not updated so if you check for instance in this Explorer you mean repository I also this is one my second repository and they have quite nice statistics so maybe only this one is something can you go back to days okay can you click on the icon what is the last time you see it 21 this is the problem we have now there is a problem with the stats tool and the graphs are not updated so I think by the end of this week the the stats tool will be the issue with the stats tool will be solved the graphs will be updated but don't worry the statistics are properly collected okay are you the right person to contact if it is not happening yes we are the right person to contact me and Dimitris are the right person to contact to push to solve the issue are not the right persons to solve the problems of the world okay so we have another problem sorry thank you no but we are on track this was discussed in the last in the last provided meeting so as you know we are transparent what is important always to highlight I think the other things are working well what is important to highlight is what Dimitris said the collection of the numbers and the processing of the numbers are working fine everything is working fine in the back end good this is the most important good I don't know how to stop share and I think what you are showing here is also important that we highlight that Dimitris is also working in the future in order to have the statistics integrated in the ecosystem of Fiosk so this is is also important to highlight so let me share the mentee that we have so we don't have too much time but I will invite you just to have some feedback from you and then if you want to turn on your microphone we have 11 minutes just to receive some feedback from you I think it is working well I hope if you go to mentee this is really just to collect some feedback but the most important thing is just to have your feedback for those that are in fact using and I see some Portuguese colleagues Spanish colleagues feel free to talk in your own language if you don't feel comfortable to talk in English I will try to translate the others I cannot say the same for other languages so are you using counter reports in open air provided are they helpful or not so we are mixing here two questions but it is just to have your feedback and for you to check so even if you are not using them some people have enabled the user statistics service just to have the overall numbers we know that but we know that there are people that are in fact using in a monthly basis the reports from counter 4 that we have available so in fact you can provide two answers if you want sorry for those that have already replied and if you want to do any comment about this the way that you use feel free so user statistics is service that you can benefit from from overall numbers graphs as you saw with the demo with the real demo from Bliana the numbers that we are collecting are exposed also in the public web pages of the providers this is integrated in other companies in the landing page of a publication etc but we have also this added value service that you can use to get reports from the reports that currently are available for counter 4 really is ok 15 answers is already good so yes we are using some people are not aware there are some people that are using so thank you very much let's move to the other questions and feel free to comment or to ask questions like Eli and Bliana already did you saw the explanation from Dimitris I think I found it quite clear comprehensive really useful for the community these important differences between investigations so the numbers where we collect the differences the exercise that Dimitris did and I thank you for that Dimitris of comparing numbers just to make this clear I think it was quite useful Dimitris already used the use case of Susan it's not my wife my wife's name is Susan and we live in Porto but Susana don't do research on history of Porto we just I didn't know it's a Porto use name actually Susana ok just to make some fun for this community call ok our counter code of practice release 5 new metrics useful what is your first reaction do you have any comment to this ok I think there are some people that need to learn more and I think this is natural yes it seems so I put yes in the initially in fact I prepared the the mentee saying yes and then I added yes it seems so because there are some people that for sure know that yes but there are others that they have the feeling that ok 16 replies many things so Dimitris feel free also to comment and to add something what is important now if you want to comment this to replies feel free what is important is that this question that we have and for those that are already using the service please provide your feedback even if it is just one or two persons to say if you have a strong opinion just share with us because we are we are thinking about this so would you like to maintain both reports this is the most interesting yes feel free to so those that are using in fact that you see the diagrams that you check the reports please give your opinion because just let's have some more let's have some more answers and then I can say what was my opinion I don't know if I will put some bias but the Irish UK has stopped issuing at least four reports so they have completely migrate to the release file so if you won't have a strong opinion because if you don't use it in the daily basis as you reply to the first question feel free I understand that at least those it was nine ten persons that are in fact using it so if I can have one more reply or two I think it's useful if no I understand because there are people that don't use in fact in a monthly or daily or periodic basis but so you cannot have a concrete opinion okay thank you very much Dimitris this is useful no? it's a problem but I must confess that the first opinion then Dimitris can comment that we wanted to like when we put in production we discard the counter four and we just keep counter five then I was thinking about after I heard Ana Povea that is here in fact after I heard the recordings from a session in Spain from the anniversary of the aggregator aggregator in Spain I heard your presentation Ana Ana is here and I start thinking and then I shared with Dimitris in fact that when I was listening to you in the way that you use and check I was thinking about not doing what we decided to discard four and start only using five and I must say that now I have a strong opinion to keep four until the end of the year and have both until the end of the year and during this period try to take a decision if we should keep four or not for 2023 but let's discuss let's have the last question Dimitris feel free to comment I gave my opinion feel free to give yours we are community driven so the community decides this is a great sentence that's the truth are more detailed reports like not master reports useful maybe we can put again this slide yeah unfortunately I didn't have the time to present all the reports but I agree with the people that I reply that they need to learn more about this they can contact me and ask me for more information but for sure there are very interesting reports my interest in the community especially for journals and repositories for sure we need to document better about this but maybe we can also allocate five minutes in the coming call just to detail some more reports but one of the last slides from Dimitris was in fact where do you have Dimitris I think it's 14 that one is this one yes of course we all need to know a little bit better about this but especially the ones that with license types gold etc yes yes yes I think they will be a bit of interest yes ok 13 answers there are one strong opinion so yes ok so it is already useful for us let me just in this last minute of the call just recap and Dimitris if you want to have any feedback so people are using there are some people that are not aware so in the if you access provided if you have a source that you manage the last tab of provide is the one related with user statistics if you click there you will see the instructions how to enable you just need to click and you receive a tracker code and some instructions then you can contact us and in fact we will know Dimitris in fact will know about your interest ok and in fact sometimes when we have people that don't do nothing we try to contact them and check what is the status we understand that some people that enable are dependent on IT staff from the institution or even a company that provide the support in the maintenance of the repository but we can we can we can provide support and then we need to follow to follow this ok and we are counter for new metrics useful so that there is a feeling that yes and people need to understand better about this and there are some new cameras and this is why we wanted to highlight because we have the feeling that this release 5 is not so well known by the community so it's critical that we have a knowledgeable community in order to take important decisions statistics we all know that are critical for institutions that are critical for repositories and I think we have a robust service in open air in terms of that in terms of back end we need to make it more more responsive to the end users this is an issue we know Dimitris and myself and others and we are always trying to push our colleagues in order to make it more robust in terms of our being more responsive and visible to the community but ok thank you for your answers and ok Dimitris we have here a clear reply on the previous one about the maintenance of both so at least in 2022 and also that we need to provide more information about this this is important for upcoming calls and also for a public webinar so we will do also a public webinar about to use the statistics not only to talk with those that are already part of open air but to open for others to join I think it will be by the middle of July and we will present the whole service there not just what we are providing but also ok just an invitation just to we are closing and then Dimitris can also say something more so just an invitation for about the other calls in fact we usually don't have the call of July and I suppose we will be back on on September but we have the we have the public webinar do we have already a date that we don't have it here do we have a date? for the usage counts? I think it's the 12th of July let me check ok let's put it here 12th of July public webinar about the users stats service ok putting your agenda we will disseminate it I think in fact this was decided yesterday or the day before yesterday ok or be aware of that we will disseminate it but if you want to disseminate in your country or to share with other colleagues so feel free to do it this is for those that are not aware of this service some of you are not fully aware so you please attend to this webinar where Dimitris will provide more detail information so thank you very much I think Dimitris do you want to make any comments or we have thank you for joining if you have not activated the service please do it's very easy we could help you we are offering the tools for platforms like the space and the prints and we are also offering the generic tool that could be applied to any kind of platform using web server logs so I think it will be easy to set it up and configure it and we are here to help you and I think it's a very interesting service yes I think it's important to say that it's a robust service in terms of that it's so and what we need to see it's to go out from our islands from our silo and to understand that having open air a service like open air collecting user stats data from different providers acting as a hub is quite important for the robustness of open science services like repositories for the future to place the repositories in the services that we provide in the ecosystems national scientific ecosystems European so this is important so as open air acting as a hub this will be relevant to provide service for national provide service for IOSC to interact with other platforms we are already interacting with La Referencia for Latin America so this is the added value that we need to understand of course we can benefit individually to have to get the reports for our own repositories and to have a clean statistic but we can also benefit to integrate our stats in our in other services so this is what I think is really important so a correction on the date don't put in your calendar the 12th of July put in your calendar the 13th of July of past 10 century European time so recordings will be made available of this great presentation series and PowerPoint is already shared in the notes so thank you very much I hope that we so checking the questions no more questions so bye bye all thank you very much thank you