 Okay, welcome to this open air providers community call. So the place and the moment in the months where we try to provide you some news about our recent developments in open air, in which concerns to repository managers, so the different managers of data sources that we have in open air for you to stay up to date in terms of developments regarding the provide dashboard, the different services in functionalities in the provide dashboard about the interoperability guidelines, your presence also in the different services that we have in open air. We always try also to inform you and also to collect feedback that is really important for the developments that we do as the open air infrastructure is made for you and by you, so with your content that you are providing as providers of different kinds of research outputs in open air. So today we don't have a main topic for discussion. So we decided to share four recent developments as we have lots of things to share and some of them at least to we want to receive your feedback. This is why we decided to not to have a main topic for discussion. So after the basic updates that I will provide now, so we will discuss some recent updates related with our interoperability guidelines for repository managers for and also for Chris systems. We will talk about the Chris validator share with you some news, then we want to present to you and discuss with you. This is a bit strange, OK, but no, no problem to two topics. They use as counts so that we have available in the dashboard. We want to tell you what we are planning to do in terms of integrating the counter five in reports in the dashboard and to collect your feedback. And also for Argus, for our data management tool in open air, what do you think it's interesting to have integrations between the provide dashboard and Argus and the repositories and Argus. So it's really a short discussion about that. So let's use these four topics. We will discuss it, present to you the novelties, get feedback from you during this one hour. OK, and I see that already we have more people joining, which is great and welcome to this community call. So recent news or developments, so just to inform you that the graph version that we have currently in production that we can see in exploring that you can see in the access, the information in the dashboard is from 19 of March. We are already preparing the one for April, and I suppose that until after Easter and until the end of April, we will have an update of our index. So be aware of this. I think it's always interesting. Be aware that we have this page here where we usually present explicitly what was the last date and if there are any relevant updates for you to consider. So we also put their relevant updates from our infrastructure or from the content providers. Let's say another thing. So we are preparing, like I said, in the last meeting and we want to put it in production. We just revise it with everything in terms of the legal statements there. So the open air acquisition policies and the terms of use are the same since 2018. We have published, they are available, publicly available. All the data sources that join open air need to be aware of those data policies. But as we have a long process, we started with the driver compliance, then open air version one of the guidelines. So we have hundreds of data sources integrated in open air before our policies were updated and made available the last version in 2018. We have more resources that were in open air before 2018 that they have updated after 2018. So we have decided to make an effort to make everyone that is part of open air contributing with content for the infrastructure to be able to update the terms of use and to do a check that they continue to agree with the terms of use. So we have that in beta. We will put it in production. We want just to share it with you. So it's really ready to kind of just receive a small consideration from our lawyer. But everything is ready. We can present to you. I will present to you what we have. Then we have other updates that this is what we are going to discuss. And then also for you to be aware that since 2019, we have a trailer board where we put to the plans for development, what we see as the wish list or things that we are working on. So be aware that we have this trailer board and they can also share. We need to do some updates. But during 2020, we never did any update to this trailer board. But we need to do it. And we will continue to have this trailer board as also a way to communicate with you and for you to be informed about what are the things that we are working. So usually we present this in the community calls. But I think it's also important for the service itself to provide the support to have this trailer. We have for the different services of OpenAir. We also had since, I think, 2019 or in fact, I'm not sure if it is 2019, but we have this trailer board. We have updated in 19 and 20. But then in 2021, we have decided to frozen that. But OK, within other decisions for other services, we will update it and keep it up to date for you to be informed about the terms of use. This is what we have and what we are going. You, all managers of data sources, we'll find in the dashboard when we put it in production soon. Let's see in the coming week, maybe I suppose we can do it in the coming week. So you are going to see pop up window for your data source, like saying, OK, thanks for being part of OpenAir. Please update your your terms of use or so. And we have like kind of check button for the set the terms of use and the degree with the reuse of full text. So and at any moment you can do it in the registration process, you can do it. Everyone will receive will see this pop up window. Those that are already registered, those that are that will register for the first time. And they will have a single step specifically for the terms of use. So we want to make it more explicit than in the past. And at any time you can come to the update tab and as you can update the OII PMAs interface or update the managers that have access to your data source, you can also update the terms of use. OK, and this is important, really important for us. I hope that you can do it after this is important. The most relevant thing that we would like to share is that this disagreement with the reuse of full text will allow us to have a better practice in terms of collecting the PDFs and the full text from your repositories. So it's important always to say that OpenAir does not provide full text files for public distribution. OK, we only use it for test mining to enrich our graph, but then always we link from our services to the original data source. We never link to the PDF. So we don't store the PDFs and make it publicly available. We store the PDFs just for the proposals of backend services in reaching our graph. And of course, by enriching our graph, we are enriching the type of services that we can provide to all OpenAir users. This is important. We don't do the type of things that, for example, we have in core. So I'm already sharing my screen. Can you see it? Yes, OK, OK, just to confirm if I'm sharing the browser. So when someone arrives to the dashboard for the first time after we put this in production, you will see these terms of use for the data sources that you manage. You can do it also in the update tab here, where you're going to see update the terms of use. OK, you can update this information. So as I was saying, this is important because of this sentence that we have here. OpenAir will not provide the full text files for public distribution. The users will access from the original data source. This is just for us. We don't do the type of things, for example, that core does where you can you can get the PDFs directly from core and you don't provide more visibility to the original data source as we are doing in OpenAir. This is an important difference that we have and that we want to keep doing. And this is why it's so important for us to update and for people to be aware of our content acquisition policies and our terms of agreement with the providers. OK, if you have any question, please feel free to ask about this. OK, so we have it in beta. We can check it in beta, but we are going to put it in protection soon because it's ready. It's already revised it. In fact, we did a small revision of a text and my colleague, Stephanie, from Athena, from Athens, did in fact this update this morning together with my colleague, Andreas, so everything is under control and proper prepared for this. OK. Important information for everyone, so feel free to ask questions and so we can do it at the end of this update, but feel free. So we have here an interactive session because I will ask several colleagues from OpenAir to join in to speak. OK, first important information was the terms of use. Now the second one is about the origin Europe. So we so something that is natural. So we already start to receiving several requests from repository managers or from project coordinators asking about how to present the the metadata about outputs from horizon Europe projects. There are more and more projects being approved and being and entering into into an implementation phase. So but unfortunately, we have a slight delay to integrate the list of projects from the European Commission in our infrastructure. And I try to I just prepared we just I just prepared together with my colleague, Andrea, this slide before this session just for you to share with you what we are doing in terms like for you to have a clear idea that you you we can answer all your questions. So what we need to do for the the full let's say the full implementation of the projects list in our in our infrastructure are to work on the three or four areas. So on the interoperability guidelines on the integration of the projects in our infrastructure on the integration of our of the projects in the different services of open air and then also to provide some support some training about the open science requirements in horizon Europe. So you can see this in this timeline. OK, let's say what we are working now and we are ready ready to present something we we are integrating the some like the the the way that we are implementing the the open science requirements from horizon Europe in the bibliographic specifications. Let's say from the from your data sources. So in fact, we are not changing let's say we are not changing the guidelines we are just putting in the guidelines some examples or creating a kind of appendix specifically the way that the repository managers can address the the the specifications from the horizon Europe. OK. So this is what we are already working and we are already we have that those examples for version three of the guidelines. Then we will work after this session in this creating this page in the guidelines website to clearly state what we need to do to to to met the horizon Europe and open science requirements upon access requirements. So we did one page for the horizon 2020 so we will do a similar one to horizon Europe, but I think it's important to make it more explicit. Then our our with the support of the open air training support and training standing committee. We we are already ready to start delivering some guidance about the horizon Europe so we are preparing three different guides that we will put available soon during April and May you will see in the open air website three guide guides. So one is is for the open science requirements in the in the in the preparation of proposals in the grant proposals. OK, so some tips about how to address the open science requirements from horizon Europe already in the phase of the proposal. Then another guide about and then two guides one specifically for research data for the research data management and sharing requirements. And then the other one for the open access to publications requirements. OK, this is what we are going to have for everyone for you. Then you can reuse also for your research institutions, your universities, et cetera, and for project coordinators. These guides are in for researchers. These guides are for for all our stakeholders. Then we need to integrate the projects in our infrastructures integrating the projects in our infrastructure. The projects from horizon Europe will be made available via our APIs. OK, which also includes specific API for, for example, for this space as we have the book access to projects from horizon Europe from FP seven. And naturally, also this list of projects can be consumed by you programmatically. And of course, we will be made available also in the different services. So in the node or in the claim service of of Explorer or in Argos. So this is something really that we are pushing a lot. It's not it's something that is not fully dependent of open air. So we are dependent also on receiving that information from the the core. This system, the system that provides support to the European Commission, European Commission for this regards that related with the rising Europe project. But so we are in touch with them. So we are pushing a lot to do this as soon as possible because everyone needs to be to have that information as soon as possible. Because some repository managers are already receiving requests from project coordinators about this. But you can already do something when we do this. So we will be able also to organize some webinars. It's in our pipeline to do it as soon as possible. We are expecting to have in the first half of May, these webinars for project coordinators and researchers that you it's also interesting for you. Webinars specifically about the horizon Europe open science requirements and the way that open air can support and help project coordinators. OK, I hope this slide was useful for you for you to be aware of what we are doing. We are pushing to do everything that what what we have here in April and May. OK, we need to have it because the community needs to have this as soon as possible. And so in May, I hope that we can we will be able to to see everything then. Andreas, do you want me? Do you want to join me and to tell our colleagues what we did in terms of the guidelines so related with the horizon Europe? So and then also related with the version four of the guidelines. So yes, Peter, hello. Thank you very much and also welcome from my side. As Peter said, the first step for in the roadmap was to updating our guidelines regarding the new horizon Europe projects. For this, we integrate a new example for horizon Europe. The horizon Europe is short called as a G. And here you see an example for the info you will semantics that are used in the version three of the guidelines for literature repositories. You have on the left side, the info, a grant agreement. Then the funder is the commission and then the funding program horizon Europe. After these horizon Europe was this the grant agreement number. And then there's something more you could provide an information about your projects here, but you shouldn't. And this is a small change in the chain of the roadmap. And you will see you could see this example in the latest version of the guidelines available through the read the books you see here the link. You will provide it also in the chat afterwards. The next was to remind something regarding the version four guidelines. The guidelines for version four is mostly called as literature guidelines, but it's not dedicated to literature publications. It's mostly for institutional and thematic repositories. So thematic and institutional repositories could have more than literature publications. And in this we are introduced the metadata format, why underscore open air. And in this we have a separate namespace for dedicated elements. The namespaces air and the elements for in this new namespace are you see here resource type funding references, license conditions, and versions files and so on. So there are some dedicated elements explicit for the metadata format. Why underscore open air. The guidelines are published in December 2018. And you see on the left side on the right side here the screenshot from the guidelines for version four. The new additional information that we have in the new release candidate for version for the version 4.1 is to have a back practice example for the YEPMH batch size. Mostly, you know, the batch size for repositories for the YEPMH interface is 100 records per page. And then you have resumption token or and and so on. In the last years, we see that are the repositories, the records and repositories are growing up. And we have some we made some tests and see that if we have if we could have a batch size over 100, that is better for our harvesting system for our application system. And we come up to have an batch size between 100 and 500 records per page. It depends on the resources of the repository. If you have if you have the resources for more than 1000 records per page, that'd be great. But if you have more than 100, it would be better for us. So thank you very much for the Chris. Yes, before before this, Andrea, just me just to reply to a question and then you can move to this. As we have Oliver here with an important question about the previous topic about the the date of terms of use that we are doing. Thank you. Thank you, Oliver, for your question. Why is it necessary to accept the use of PDFs if you keep the practice of not to provide those full text directly? So so we have decided mainly the two or three reasons are that. OK, it's a question of good practice to do this explicitly in terms of acceptance of the of the of the terms of the terms of agreement with our with our policy in the terms of use. The second one is is what is real was critical for us is that so as we are aggregating the content, the collecting content from different data sources since 2000 and in 10. So within different policies, some data sources have updated other know. So some have joined after we have this last version of the policy since 2019. So we thought that so at some moment we need to do a kind of of reset of this of this policy and I'm asking everyone to to to proper update based on the current policy. So those that in fact it will be a repetition for some we understand that. But in fact, it will be like the the the first time formally that some data sources that are like like let's say old or early adopters of open air. That are explicitly presenting and agreeing agreeing agreeing with the terms of use so this is the in fact the main reason so it's a good practice and it's because of all this history of open air. And and and we are we are we also discuss it and we can we can we are happy to receive this question in other comments so we discuss it a bit if we should put it like if it should be in the same line in the same line like accept our terms of use for metadata and for full text and just people do it at the same time we have decided to put in to separate like check check boxes. Just to make this more explicitly and to be complete completely transparent and then also to clearly explain what we do in terms of our policy with the full text so Oliver. Maybe you are right of the of what is behind your questions but so just a question of being, let's say, following a good practice in being pragmatic and transparent. Okay, I can I can come back to this at the end if you have more questions Andreas feel free to to add something to my answer or just to continue to the open at risk validator. So I would like to continue. For the open air Chris valley data yes. So, maybe you are also affected from the announcement from record to not update to the end of public updates for Java eight. And the Chris bullet data is based on Java eight and the Chris integration for mayor is very important. So we decide in the last weeks to updating the stand along Chris bullet vector first from the base Java eight version to another long term version and you see here. Long term versions are 17 by default. And there is also the opportunity to have other versions below 17 the less the late, the latest long term version here for Java. And in this context, together with our your Chris partner. We started these updates around the base version of Java. And I would like to thank you. Thank you guys also in the call I think for this help and assistance here to make it possible to have a new release for the open air Chris for the data. In this case. Another is open source. Everyone can contribute to this Chris through the validator source here. And I think we are happy or Andrea is happy to share the new link of the new release. Thank you very much. Thank you. Thank you. Thank you. Thank you, Chris. Yeah, feel free if you want to say something so. Thank you, Andrea. Yes, it was a cooperation between myself and Andrea. Make it work, which is great and I hope you can also benefit from it. The Chris guidelines are also undergoing some improvements and we hope to make them available soon. Many thanks. Many thanks. So we already cover two topics. So we have we have two other topics. So the user statistics and the and the and Argo so we will spend a little bit more time with the user statistics what we are integrating now what we have what we are integrating and we also want to collect your feedback so we have our colleague Dimitris that is the the manager of this specific service. That some of you are already benefiting others that are not benefiting you can always go to the open air dashboard uses counts tab and enable the service and you will receive some instructions on how to proceed. And what you need to do in terms of interaction with with open air and Dimitris will ensure this contact so Dimitris. Okay, thanks Pedro. Welcome to this community call. The upcoming updates regarding the usage count service are related to the new version to the support of the new version of the counter code of practice release. Five reports which are planning, which we're planning to introduce and included in the provide dashboard. In the in the, as you may aware in the current status in the current version of provide, we are supporting the counter code of practice reports we are offering the main five reports we which are provided by the counter which are defined which have been defined as I think 2012 from the from counter. And it's the release for of the code of practice we are offering the article report the item report, the repository for the book report for a number of successful request and book report for a number of successful sexual request. The upcoming updates are related to the new version the counter released five, which will be released in in the provide dashboard the next months. This version this new release will include the only three main reports and one specific report for datasets. The next report will be the platform master reports which is a report summarizing the activity for the repository, the usage activity for it for the repository for its month metric type and item type. I will go into more details for metric types item types are articles books, data set, etc. The platform usage report which report summarizing usage activity for this particular repository again broken down by month or metric type. The platform item report or the platform master report which report specific for items which are requested by month metric type item type and repository. And finally we are offering the reports for a particular item type the data sets. Again, which are requested request by broken down by month type and repository this is a report which is provided by the the make that account initiative and has been also specified in the by are supported by RDA. So the metric types, this is the most important change that are that will be that will be included in the in the new version of the counter release five reports. Now we are talking for for four different metric types the total item request total item investigations unique item request and unique item investigations keep in mind that the version of release the release for version supports only one metric type which is the initial support only one metric type which is the number of downloads. In opening we have extended and we added another metric type which is the number of views the metadata views. So, from two metric types we are moving to those four metric types. And there's a little change in the definition and the semantics. Pedro if you please move on to the next slide. So, the metric types encounter code of practice release for definition are the total item request, which represents the counts for for art for lower article full content views across all formats like HTML and PDF. This is the only one which is equivalent to the release for metric, which is defined in release for us count and corresponds to the number of downloads for a particular item. The unique item request is corresponds to count the unique article full content views within a given session, regardless of the format if it's PDF with HTML. So, in this metric type refers to a unique to the same session. So, if a user views an article in PDF format or in HTML format in the same session, this will don't really count as a single number as one. The third metric type is the total item investigations which which is a something with that is has been defined in the counter release five and count the total number of times. A particular item has been accessed either metadata view or full time access full content access, for example, download or download over PDF or an HTML view of the article. And of course the unique item investigation which counts unique article investigation and the request within a user session. So, these are the four metric types that are included in the counter release five update. And this is a pictorial view of of this metrics of this metric types encounter at least five, all accesses to an item are considered investigations. For example, a view of an abstract the view of an HTML full text or a PDF or even download the PDF or view of an article preview preview, all these user events are considered investigations. The difference is that the if you access the full text or download the PDF or view the PDF of a particular item. This is considered a request. So this is the main difference from the counter release for metric type encounter list for metric times we have only have, we only have the item views for open air and item downloads as they as they initially defined in the protocol. For counter release five, we have investigations, which correspond to any kind of access to the, any type of access to the item and request, which correspond to the actual view, or the full content of the of the item. So, just an example scenario, for example, a user Susan is researching the history of portal in the repository of you, of Minio, and from a list of search results, she opens three articles abstracts. So the counts are for total, we have three total item investigations and three unique item investigations. After reading the abstract Susan decides to download the PDF for two of the articles, and the counts change to five total item investigations since we have three, let's say views and two downloads. The unique item investigations remain three. Since we have two downloads, we have two total item requests and two total unique item requests. So this is the big difference in them in the release five. In the coming updates, we have the option either to continue supporting the counter release for and counter release five at the same time so we are offering both type of reports, or decide to remove based on your feedback of course decide remove the counter release five reports. If you want your feedback, if you would like to maintain both release for release five reports, and if you think that the release five for reports are no longer of interest and should be removed. A quick note that the graphs, the charts that will be offered will be remained as as they are, and we will continue to provide the, the number of view of metadata views and the number of downloads for each item. This is different from the counter reports that we are offering with the new metrics. Please give us your feedback if you want to keep this both reports, this schema with two different kinds of reports or remove the release four. Thank you. Thank you. Thank you. Thank you, Dimitris. So now if you can provide us if we have here for for minutes for you to share some thoughts so please just unmute yourself and give your opinion so the information the information is visible in this uses counts area. Okay, so to enable the service and to, and to, and to access the reports. So now you will we have this as we have the in this screenshot, we have the access to this for reports we want to, to make the the other reports related to the counter five available. We are open to to the feedback. I must say that we we have we already discussed and then we have an opinion in them in the management team of provide that we should stop providing the counter four and start with the counter five, but this is just our idea so if there are a strong opinion from from from users that they want to keep for some time reports from counter four, we can we can receive it if, if, if any of you want to, to, to give your opinion feel free. So, to write it in the shot or to, or to, or to unmute yourself. Anyone with a strong opinion about this that we should just move to five and and start offering the five set of reports so this with with this different types of metrics. We have some time for that so we only have one more topic for discussion about Argos but I think if you want to give your opinion if you don't have access yet to the to the to the service that's, you can enable the service. See if I, if I see it here. I was talking about this just to make it more explicit because I was, I was doing. I was sharing the, the example in beta. Nothing. So this is what you see as a repository that they have access to the, to this service you can see it and then you can get the, the reports based on this and run and run the query that you want so we want to. We have the flexibility and just put here the, the, the, the counter five that will become the supported report for us to make it available for you. I think we do with good quality why I have a lot of quality as we have updated the statistics are being updated in line with the index update which is something that we really want to offer a service with quality. Okay, feel free to give your opinion there are some users also here from Portugal for example that's already using this long time so if you have opinions just share it here in the, in the, in the shot okay. Perfect. Let's move to the other topic and then if you have any comment about this you can give and offer your comment at the, at the end of this meeting. The last topic is about, let me check if my colleague is still here yes. So it's about, so we can have, we can organize our ideas to organize a specific call with having the Argos and the integrations with provides and links to repository managers. Discuss it in the in one call only. But this is already to open a bit the discussion and for you to start thinking about what are the relations between these two services and what are the what is the relation between the services that repository managers, manage and the Argos as a tool to deliver and prepare data management plan so we have one slide for you to share with you so we will present what are the, the, the basic ideas behind this integrations. Thank you brother thank you for having me. Yes, so Argos, as the better mentions is a DMP tool is a tool that creates machine actionable templates for data management plants that researchers use them to write their to answer the questions and then read DMP and submit to the project that is either at the European level or at the national level, wherever they need to thank you very much for the billy goes there, wherever they need to adhere to the policy. They have to about RDM. So, Argos is not just a tool that creates the MPS but also connects it aims to connect and really does connect different data workflows together. The vision is that the data management plans are semi automated with validated information so that researchers have less of a burden when it comes to writing the DMPs and also enhance the data sharing incentives. So, they feel like if they go to share the data in the repository then they will automatically have some of this invalidated information inside the DMPs we have already started doing that and I will add the link for you to see with a feature that pre fills with the data coming from Zanotto, because Argos is an open instance and it integrates with all the open services so currently, the repository that we're using to publish the DMPs but also to get information to add as answers to the questions and the respective questions of the template are coming from Zanotto. But we could do of course the same with all other repositories so the integrations behind Argos and what with our thoughts behind this are twofold so they are two different levels. One is to integrate with Provide, which is a service that OpenAir offers and it targets all, so it informs all the repository managers and then the integration has to do with sending notifications to repository managers when data management has refers to the specific repository for the data sharing, for the projects they are sharing, then a notification should be sent to repository managers, that's the thought, and the repository manager can get an idea of what data are expected to be coming and what's the size of this data and so on. And you know, make any inform those researchers maybe ask the researchers if they need more information about things that have to do with data management plan and researchers don't know for example about backup things about preservation policies, things that are difficult for a researcher to know. And then the second one for Provide is to offer a selection of repositories to publish the MPs for not only Zanotto, but being more inclusive to properly push the MPs with a correct resource type because this is also if we're looking at the whole data that are out there, it's difficult to identify, to find, to exploit the data sets that are about data management plans. So there is, we are using the core vocabulary, and we are exposing the data management plans with the correct resource type and we would like to enhance this practice through Argos. And that is for the Provide side of things, and then we can of course and we will further discuss this in the next collection, to see how integrations can be made at the level of the repository itself. So instead of Zanotto here, you could have your own, and instead of prefilling information only from Zanotto, you could have yourself. And then we start creating, you know, all this, all these links and then coming back to the vision, we complete the vision of semi-automating the creation of the MPs. But yeah, I'm really happy to know your thoughts. I don't know if you ever consider something like this, like integrating with a data management planning tool, or offering, you know, APIs to data management plans so that the researchers can have more validating information to choose from when answering their questions or things like that. I'm happy to discuss them and know your thoughts. Thank you. Great, thank you. Thank you, Ely. Okay, this was really the idea to share with you that we have these possibilities so we can do several things as Ely identified, and we must do those that are more relevant for us, for the users of both services. Having this open air infrastructure, these different services in the open air ecosystem so we can benefit from this kind of integration. So think about that. So we are going to organize a specific call about that. So if you have some strong idea, so we have time now because we have three minutes more. So feel free to jump into and mute yourself and to give your opinion or to write it in the chat. You can always comment also in our Google document that we have can reply later. So if you have any opinion, just share with us. So what I think is important for us as repository managers to understand that. So, this is already working with the nodo. Okay, as a nodo is from the services ecosystem of open air which makes sense but we can do it also this integration to publish the MPs in literature automatically, or to facilitate that integration. I think this is one one use case that I think you should consider and we can think about that. The other that I as as as provide manager I would like really to have is to inform that repository managers that someone in a specific project, have the intention to put that in their repository so we can inform them so we can anticipate this this need. Okay, so a specific researcher stated in the dmp that I will use that repository from from Norway, that reverse Norway to put the data and so to deposit that or to store that so they can we can inform the repository managers, which I think is good send notifications. And, and, and, and maybe the similar situation for those public the MPs that are available. So we can do something with the literature repository managers. So, think about these possibilities I think early was quite clear in the possibilities that we are opening for you. Any comments about this. I think it would be better that we will also have some use cases to show in the in the school in the next call so I guess this will also help. Okay, not sure if Jose, I want to say something or to ask something we just open your, your webcam I'm not sure if you want to say something no, just a curve. No, no, okay, thank you. No problem. Okay, feel free to share your ideas with us so send to help desk at opener to you or directly to Ali to the, and for sure this will be important for us. Okay, to design this possibilities store to. I think it's more important to prioritize prioritize this possibilities what is more relevant for the community and then we can prioritize it as as as services. Thank you very many things for for for this, this presentation and to be able to join our community call. Okay, and we are coming to the end I'm not sure if you have any other question about any other issue we've already replied to some. At least we have this community calls every every month, so the community call is already scheduled for the first Wednesday of May that will be on the fifth of May. No, no, on the fourth, fourth of May, I was looking to 2021. The first of May will be the first Wednesday of the month. So, and we will dedicate some time to organize this call also for you. Be aware of the newsletter, I think, almost all receive our newsletter. If you think that there are others from your institutions or from your country that may benefit from this newsletter share with them please. We send it every like first Monday or first Tuesday of the month also to anticipate this this call so be be aware of that and all the information presentations and recordings are made available in the in the web page. So any other comment any other question. So feel free so two requests, if I may at the end so be aware that we want your feedback here regarding the integration of the counter five reports in the user statistics functionality in the dashboard. Send it to the up there is called directly to Dimitris Dimitris already shared email, it's in the shot. And the same for Argos, if you have any idea check this slide in the slides and if you have any idea any strong idea and you would like to have your repository also integrated like like we have the integration with the nodal state that opinion to to really sending the sending the information to Argos that at opener dot you. Be aware that we have all these plans to integrate to the for the integration of horizon Europe projects in open air so you can inform your project coordinators researchers about this hope that we manage everything what I told you in terms of guides integration of the guidelines integration of the API, etc. Until the end in the coming two months is in April and in May. Okay. Thank you very much so it's already off past three of past two in Portugal of past four in Turkey I suppose I saw some colleagues from Turkey also here. So, bye bye all. So, thank you very much for joining this community call I hope that it was useful to receive all this information and thank you very much for all my colleagues to to support me in this in this community call today. Dimitris, Andreas, Jan, Ellie, and of course my colleague Andre that is here in the in the back end providing all the needed support information. Bye bye also I will keep the call open just for you to copy paste some of the links and then we close it okay. Bye bye.