 Thank you for joining. I hope that more people will join for sure. More people will join in the coming minutes so I can start doing the introductions and then we will have more people to listen to the core of our call today. So this is the 12 community call for all the open air content providers managers targeting different kind of people. I know that all community calls we have new people. New cameras, which is great. So we usually we like to talk about the novelties, the recent developments related with the open air infrastructure services. But those services features, functionality is targeting repository managers, key system managers, editors, those that are contributing with content for open air. Today we have a dedicated session more on the side of the broker service and the power of the broker. Let's say I just put this title, but we will because we will listening the results from a project from our from the open air innovation tender that we run and we will have a presentation from the company for science that did the great project, my perspective, and bringing innovation to the space and reusing the content from the open air graph and specifically from the broker service. And then also one of my colleagues in open air, Claudia Wazzori from CNRST will also detail some some important recent information related with the broker APIs. So this will be the agenda. I will come back to this agenda. So and for this, for this, for the main topic that we have, apart from Claudia Wazzori presentation on the broker service and overview of API. Andrei Bolini from Representing Gear for Science will detail the results of this project, which I think will be, from my perspective, a great benefit for all repositories community and also, I think, a little bit for also please community focus on this space. I know for this space community, but I think it's a great example also to serve as a guidance also for other software platforms. And Jordan, our colleague, the repository manager from the University of Trieste will also join this presentation. We'll also join Andrei Bolini to present the use case specifically for the University of Trieste that they have already, in fact, implemented or kind of do a kind of demo. OK, this is our agenda for today. And as you know, you can ask questions. You can also put other additional problems at the end that we can discuss. Just my highlights for today in two minutes, usually I have always this slide to present some to detail some some developments, recent developments, provide some also some information about ongoing ongoing developments. This one about the multi-user access, something that you are asking a long time ago. And we are almost there. This is related with also our authentication service. In fact, you can already see something in our beta service, which are we playing with in order to prove that we are almost there. And you can test if you visit beta.provide.opener.u, you will see already a bit of what we want to implement related with this multi-user access. This is just something that, for those of you that don't know, is just a way that currently we only have one login attached to manage each content provider in open air and this is just a facility in order for the one admin that they have access to the login can also provide access to other users to play with the dashboard of that specific data source. The other thing is what was the bug that it's fixed. It's already in beta and in production in the coming days, if not this week. For sure Monday or Tuesday next week. So there was some disalignment between some graphs between the explorer, between some content providers who had the graphs updated. Others know this was related with a migration from our machines and clusters. And now almost all graphs from users counts are updated. So please stay tuned and for sure in the coming week, we will have it in providing production, okay? Broker APIs, some recent developments. You can also check information in beta, but Claudia will present it. We'll detail that in the presentation. And in terms of support information, there are some new fact sheets that you can use to learn a little bit more or to share with others in your institutions or in your countries that are targeting content provider managers. About the multi-user access, this is the way that we are going to have it. We already presented before, but our idea is that here under update in provide, you will have a new tab to manage to update administrators of your data source. So this is something quite interesting. You can invite others to join. It's important to say that you need to invite people that have already a login, okay, in OpenAir. It's not an invitation for new users. They need to be users in OpenAir, and then you invite them to play with the information from your data source, which is good. And we are almost there. Also important to highlight this graph that I have already talked about. They are already also in beta. You can check and we will put it in production as soon as possible really in the coming days. This is the promise from our great technical team and the fact sheets. So you can find all this. There are lots of new fact sheets also for other services and for other topics from OpenAir, also related with open science policies, requirements, research data management. We did a lot of updates of this new fact sheets with the new layout, etc. So just visit openair.u slash fact sheets. But there are two targeting Loupository Managers. Okay, there's all the new information that I want to give. If you have any questions, just put it here in the chat. I can reply. And I already and I also can reply. Feel free also to ask your questions using the audio. Now it's time to this presentation that we are all waiting for, the results of this great project. Andrei Bolini from For Science will detail this. You both can present yourself at the moment to spend time presenting with you both. You can present yourself and detail this project and the result of this project, the target and the scope. So this is something that it's quite a benefit for this place, Chris, and this place Loupositories in version 7. But the type of implementation should also guide the implementations in other Loupository platforms. But, Andrei Bolini, please, I will stop my screen. Thanks, Pedro. Thanks for this nice introduction and the great news that I see from the openair team. So I'm Andrei Bolini. I'm the technical director of For Science. We are a service provider for this space, very strong position in the space community and the interval source community in general. I'm a long-term space committer together with other colleagues in For Science. I'm very happy to have this chance to present to you, to all of you, the result of this project that was part of the Openair Innovation Program. The project is named Openair ELD as a acronym that means Reach Local Data with Openair Graph and is target mainly to the space platform. But as Pedro said, we have a lot of result and idea that can be easily used in other platforms. So the project goal was to, we have proposed and we implemented two services for this space and this space, Chris. So it's important to know that this project work both in the case of a basic space then in the case of the space Chris flavor that I hope many of you know is the extension that For Science brings to the space community. The two services are named Data Correction and this service is based on the notification broker service of Openair and aim to improve existing data in the repository. So essentially using the intelligence from the notification broker, we will make actionable to suggestion of the notification broker inside the repository. The other service is named publication claim and allow the repository manager and the researcher to identify new content that is already available in the Openair ecosystem information space. So going just to spoiler the result, the two product features have been both implemented. The project, I'm happy to say that it was successful. We have a website where all the documentation about the project is is available. You can check on is a GitHub website and you will find all the details both in terms of the user interface then in terms of the implementation. The service code is on GitHub and it's available for both playing this space coming in the space seven version then included out of box in the space Chris. It's include all the aspect of the space source code. So there is a part for the back end for the API one for the Angular user interface and information to the pointation of the rest contract. This project target for version seven. So to come in new version of the space and the space Chris. And adopt the paradigm of the space seven platform. So there is automatic test for both feature and these are in place for back end and front end. So it's fully compliant with best practice of the space community. During this project, we have run a pilot installation to test the services on real data with a real institution and Jordan is here with me today. I will tell you the result of this pilot. And it's also important to know that we have an acceptance test for a list of functional tests that the user can perform on the platform to verify that the product work well. The product architecture is based on the OpenAir REST API and the OpenAir broker. So the OpenAir REST API are used to query the OpenAir graph to search for new publication that are related to the search at your institution but not yet known to your repository. So essentially you search for all publication of your researcher in OpenAir. And the results are stored in a temporary solar core for better management in this space. On top of this solar database, we build REST API so that the Angular user interface can access this data but also other script or any other client can access this REST API of your disk space to build additional service on top of what we build using the OpenAir REST API. The same route is more or less followed also for the OpenAir broker. When the project started one year ago and also now there is no yet a public API for the notification broker but what we have agreed with the OpenAir team, we have worked together to design this public API so we bring use case idea and we have agreed about the format to exchange the information. So essentially what is done now is then the OpenAir team send to the repository manager periodically a JSON file with all the detail about the notification broker have discovered. This JSON file is loaded in a solar core and using this data this space provides all the user interface that are required to work on this data in the repository. So try to give a bit more detail about the due service. The data correction is ready to do the scenario where a manager of a repository that is already indexed in OpenAir so is the tool that is attending this this web call essentially. So you are a content provider you have access to the content dashboard and you know about a notification broker. What we try to do is to fill the last mile of the notification broker dashboard. Essentially the dashboard of OpenAir you will get a lot of detail about missing information in your local record or round information that can be corrected and things like that. But if you want to apply this suggestion to your repository right now you will need to log in in your repository headed to the item manually and copy and paste information from the user interface of OpenAir to your repository. What the service provides is a dashboard inside your repository so as a repository manager you log in in this space you will get all to the tail of the notification broker inside your this space and you can immediately say this suggestion is good I want to have this additional persistent device to my item. I want to add this missing abstract. I want to link this item to my project. It's also important to note that there is also a cold backflow of this information. So we take care to notify OpenAir of what decisions you take around the suggestion that they have done. This is really important because allow in the future to improve the capacity of a guest single OpenAir because they can better understand when some suggestion was faced positive or was rejected for other reasons and can improve the intelligence of the notification broker. The second service is the publication claim and it's based on a very common scenario. So a new researcher joined your institution but probably this researcher many times researcher move from one institution to another. So there is a nile probability that this researcher have already content deposited in other repository that have contributed this content to OpenAir. So what we propose here is a way for the new repository to log in in your system this space will query automatically query OpenAir using the detail of your researcher. So basically the name and scanning all the results from OpenAir if could decide which publication seem to be related to this researcher and suggest to the researcher to immediately import this publication to the repository saving a lot of time researcher to prevent marble input. Jordan I would like to you to talk about the pilot. Yes, hi to everybody. So I am Jordan Pistols the repository manager of the University of Prieste and it was a great pleasure to participate in this pilot with the data of our repository. The sound is not great Jordan I don't know why could you just Yes this is the microphone. No, no, yes, no, yes. So let me start. So I am the repository manager of the University of Prieste and it was a great pleasure for me to participate to this pilot with the real data of our repository and let me say to see the real power of broker service and the researcher graph. Let me start with this auto citation because it was a great improvement for the broker service. I finally see the suggested data of the broker service in the place where I need this data so directly in my repository. The great integration helps us as a repository manager to quickly decide at the reach the data that we have in our repository directly in the environment that we are used to work and manage. I see it as an all-in-one solution previously I have to go to the open air site, check the data, copy and paste them in my repository. The next slide is Andrea the next slide I can okay yes and about the publication claim service let me say that this was the real practical usage of this service that open air give us. The real thing that I think that is great is that this is also integrated in our repository but let me say this is also a real time saver for the researcher because when they log into the repository the publication claim service will suggest them all the new publications found in their searcher graph that are not present in our repository and then they could automatically import them. Going next so what we have done in this pilot project we tested all the various functionalities that for science give us with some tests but we also improved this adding some other tests that I found that could be a good test pilot test pilots. Using these services in the repository I also suggest some new improvements and also new features because you understand that when you start using as a repository manager these functionalities you find that some new ideas or improvements could be done and so we help also for science to fix some bugs that I find and they also work on the performance improvements to deal with larger repositories because let me say we have yes a repository but it's not so huge like others our repository see 20 000 items let's go further to see what we have done so the first two suggestions that we at the end of the pilot that we have found are these two so that for the data correction service it will be fine that the JSON should be pushed directly into the repository or downloaded from the open air dashboard because now during the test Andrea helped to talk with the development team of an open air they give him the JSON and I have to upload it in the repository and it will be fine also that this JSON should contain all the information that are in the open air dashboard. About publication claim let me say that I am the right person that have done this test because with my last name that is so particular I also find that the rest API doesn't work properly with all Unicode characters so I didn't find my publications and another improvement that could be a rest and point to use and explore the portal with all the fuses search that is available on the web portal that we are used to query avoiding the need to guess or ask the user so we as a repository manager to use the index of the authors or of the title but this you can see in the demo slides that we are going to see now. Let's go with the slides about talking about the demo. Yeah so we can also make a live demo but I'm not sure what would be faster probably the slides because we have a lot of content so one important thing is then all this process all this service requires some process to be run on the on the display server a nice feature of a display seven is the possibility to run some of these process directly from the user interface and we are may we take care to include this new script in the one that can be run from the user interface so essentially in this screen you see that there is a new import notification broker events that can be run from user interface you can upload the JSON file that you received from the open-air team and it would be processed of course you can do that also from the common line and let me say that it was one of the great improvements because when I start I found in the documentation that they had to go to the console and okay but I have no access to the console and they quickly improve this with these scripts that are available at the web interface for the manager and then if possible you can also include already some information about the versions as someone already asked in the chat Jordan already answered but just to clarify before this demo the version yes I will say again because it is important so it's for version the source code is included out of box with this space Chris seven if you download this space Chris seven from github it's not yet a final release I think that many of you know that this space and this space Chris seven is still under the loadment essentially it's we hope to present them at the open repository but you can download the source code from github and for the space Chris seven this solution are already included in the source code you just need to download the space Chris and you get this feature available active in your repository for the space this feature are present as a pull request to the community so is not yet merged with the official main branch and due to the schedule of this space seven I'm afraid to say that probably this will be not part of 7.0 at least this is what the community suggests has to really focus for 7.0 on the existing feature and don't try to have too much complexity in this release but I hope that they will be merged as soon as possible maybe in 7.1 in any case when 7.0 will be out when you start to use this space seven you can apply the patch manually to your repository and immediately start to use this feature uh these other screens show how the uh different topic of the notification broker are presented in the administrative user interface of this space so you see that there are more persistent identifier or some missing persistent identifier more abstract missing project more project that was found and the number of event that was received so more than 5000 persistent identifier 53 abstract and so on unfortunately in this data we also need to note that there are some rumors some noise from the notification broker related to self persistent identifier you can click on the number to to get the details so for instance this is to the table to see more persistent identifier you see here that there are some do i suggested but you can also get a medid or other identifier for your publication one suggestion that we received to the pilot from Jordan was to make this persistent identifier actionable so all the link that you found in this interface allow will open uh the the detail in a separate tab so that the reception manager can immediately check more detail about this do i to verify if it is a proper suggestion or not and once that you verify that you can just decide to accept the suggestion or in your suggestion reject the suggestion essentially the if you accept the suggestion what will happen is then the additional persistent identifier will be added to your local metadata to which metadata to exactly which metadata and in which format can be configured but we provide a default configuration that makes sense for most for most installation the difference between in your and reject essentially is because reject the mean that the suggestion is is wrong as the your decision go back to open air is important that you can in your suggestion in some case because maybe it's outdated because you have already included this do i manually in your repository or because you prefer to don't store the the pammed id in your repository so you just decide to ignore to clean up your dashboard but you want you don't want to notify open air that this is a wrong information and if i could add this is what i say with one click in the repository i get quickly the data because with one click i accept it and the data are in my record of my repository without copy and paste or other work thank you yeah and the screen and the option that you have depend on the topic so in the in this case when you work on on a project this is the more complex scenario that we manage essentially open found for a local publication suggest you link this publication with an open air project these are all to the tail that come from open air so the project title to code the founder funding program you can click on the project title and it will open to the tail on to call this database but you can search your local displace installation for for this project because maybe you already have in this place seven this project as a local record and if this is the case you want to be sure that you can link your publication to your existing project without duplicate this data but if this is not the case you can also just say import the project and accept suggest so essentially this simple button will do two things will create a new item that is with the detail of the project that will represent the project and will link your publication with this project this is the screen about how you can search for the project on set the project has been assigned at the UC that there is bound to local record you have to handle here that you can click and see the detail of your of the local project you can eventually remove the the link if this was done wrongly or if you change your mind and on set you import the project the decision is saved so the dashboard this item will be removed from the dashboard and all the link will be established the same end-to-end process apply also for the other service you need to run a process on a daily or weekly basis to search for new publication for your researcher you can run over all the research in your repository or you can force the script to process a specific researcher and you can do that from the command line but also from the user interface also that you have run this project this process you will get a list of of researcher for which the system I found suggested and as a repository manager you can manage the suggestion for all these researchers so you can decide eventually to centralize this service and have your librarian to import new publication for your researcher now for your research but the same interface is also available to the single researcher of course the single researcher can only manage his own list of suggestions so in this case I have the suggestion for my colleague Claudio Cortesa and you will get a sorted list by score where the score is give you an idea about how many evidence are present that allow you to allow the system to guess that this publication is really altered by by Claudio in this case out of box by default we have just two score in the system one is based on the name so one of the find that we immediately know when we start to work with the rest api of open aid is then right now it's very difficult to make a great query on open aid so you get a lot of noise because for instance if you search for my name Andrea Bollini you could find also um um publicate are altered by Giuseppe Bollini and Andrea Rossi so if you mix my first name with the first name or another uh author and uh and the surname so the first score that we have implemented is one that the look really to the single string auto string and clean up everything that is uh is wrong due to this uh uh this high level of noise uh the second score that we have included um also as an example as inspiration to build additional intelligence is one based on on to date that are available in to repose in the research profile so you can have to be a day or you can add the education the graduation date to to your researcher if you do that essentially the system will consider more uh reasonable some public that fit uh in a range of year that can be configured but is close to your graduation and at the start of your career uh it's nice to say that uh uh just with this two score uh we move from uh more than 300 suggestion for uh for Claudio to um to 100 and if we also implement the date this will go to around the 50 uh suggestion that is very very close to which was the actual uh suggestion for cloud uh so you can also select multiple suggestions and just import all all together also in this case uh we record the fact that you say that is uh if i have wrong suggestion and uh this additional data can be used maybe in future to implement a new or new score that we learn from what the users say so here you say i see a detail of the evidence for uh for this for this publication so the name Claudio Cortese exactly the full name was found at position four of the list and the date scorer cannot say anything because in the Claudio profile there is no uh appear date when we make uh this screenshot when the researcher login in the system uh they will immediately get a notification about the new suggestions the new publication that was found so if you are an administrator you go over to the administrative menu and we scroll for the researcher but if you are a normal researcher you will be immediately notified just upon login of your suggestion and if you close to the the the alert to pop up you will get this information fixed in your mighty space so you can always go back and see if you have suggestions and find quickly the link to this suggestion uh as an additional value that uh we build uh working on this project was that uh to to implement uh the publication claim service we have decided to reuse internally a concept that was already in on this space seven that was the concept of import from external provider so essentially what we have done is a more general system is not tailored only to open age but can be applied also to other provider and to apply this system to another provider what you need to do is to write a connector that uh allow this space to search to query this provider and in the case of open age this result in two different connectors one that allow us to query open age by authors so that i can search for bolini or for piscan and another one that is to search open age by title of the publication unfortunately these two connectors need to be separated because this was one of the suggestions for the open age team for the rest api there is not yet an api that allow us to make a fancy search over open age but we need to go over a specific index so we can only search for author or search for title if you use this connector directly you will make a search you will get the list of results you can check the detail and import your record in in the system this also allow us to to give a lot of flexibility in the configuration because of course you can map all the metadata of open age to specific metadata of your of your repository so to summarize the functionality are available out of box with the space chris 7 you only need to ask open age to inform the open age team that you want to receive the json file and you will get this json file periodically to load in the system we are open at pull request for for the space for you playing the space there are pull requests for the rest contract the rest api and the angular user interface please if you like this work if you want to see this work adopted by the space community make an effort to go over this pull request if you have a chance make a try provide feedback any feedback is useful so you can help with the quantization you cannot with tests you can just help letting us know how much important is this feature for you to give the right priority compared to all the tasks that we need to implement for this space keep in mind that there is a dedicated website for to the plantation where you will find all the details including the very sensible configuration that can be done for this feature so and a lot of information also about how to extend how to improve for this feature yeah great and rare in the Jordan many things so I don't know if there are any questions for sure just put the questions in the chat but but please feel free to also to to do it online so with your audio and just just ask the questions directly or comment this work so I think this is really great we are quite we are really happy with the the results of this of this of this project and and it's the documentation so the project is really well documented so the documentation is really useful and helpful and so please feel free to to ask questions now we will have a short presentation also from Claudio you can think a bit and ask questions asked also after the presentation from Claudio but so yes Andrea you are highlighting some things you are doing you are running a demo yeah just to keep keep sharing and show that everything exists is these are not more caps this is really it's really working I also work on this this morning because I wasn't reaching some data and it's working it's still working this is great no let me say it's also great because the open air also give me the mails of new features and I found them here so the link with the broker service is it's not only a demo we have a question in the meeting in the meeting notes from Marbelena asking if the publication claim is metadata only right now yes but it can be extended and if you if we found a way to retrieve the pdf file from maybe from unpayable or directly from from open air it's still possible to to import yeah thank you thank you for your question if there are any other questions so we will after the cloudy presentation Andrea and Jordan can can reply but be aware of these developments this is quite important of course that we see okay this is useful for those that are this space users in there that have this space installation that this from these versions are are are expecting where this here and updated of your this space version but the the type of implementation I think is an example for other platforms and the and cloud you will now present some details of the apis are relevant for some of you that are in this call and maybe it's you think that for some of others this is the information for the the IT department of your institution so you can point them to this presentation and to this recording so cloudy will give now some details so cloudy thank you for joining us now thank you Pedro welcome everybody let me share my screen can you see my screen yeah yeah perfect okay so first of all it's a real pleasure as a member of the open air team to to see this kind of impact for one of the services that just a couple of years ago was just an idea on pen and paper becoming a reality and actually having such this kind of impact is really really good to to know so thank you everybody for this effort and providing all the feedback that actually drove the implementation and keep refining the concept implemented in the service so I'm going to provide a complimentary view about what Andrea and Jordan presented on an alternative way to consume the added value information that enriches the local collections of metadata so as always the story starts from the original bibliographic records open air ingests from repositories there are different types and in this sketch I just wanted to highlight which are the most important phases with regard to the kind of actions that the broker service performs in this sense as you can see here in the supply chain the first phase consists of harmonizing structurally and semantically the bibliographic records although we rely on standards working with the real data we realize that the records still need to be harmonized as standards get interpreted and in order to have a common understanding about the semantic inside of the records we have to do more in terms of harmonizations and when you have more than 1000 repositories on board the interpretations can be quite differentiated let's say second important step is identification of the applicates as the same record can be found on different repositories where the definition of what is the same is tailored to the opener needs let's say we are not providing an absolute definition of what two publications are the same and to disregard by same publication we intend those that correspond to equivalent objects so pre prints post prints published versions are considered equivalent mostly for the purpose of statistical analysis and monitoring however the broker posed another use case for which we implemented the configuration of our of the open air data application system which i'm going to show in a moment the last important part that is what i lighting in this supply chain is the TDM activity from which open air extracts extra properties that are used to enrich the collection of metadata records properties and links to other objects in open air research graph like as andrea shown before links to research projects so the opener broker service is based on a set of algorithms that analyzes the open air research graph more specifically the target of the analysis is made by the group of duplicated records where the algorithm is able to calculate and derive the mutual enrichments that one record can provide to the other and since open air keep tracks of the provenance knows which repository provided each individual metadata records we are built therefore we are able therefore to build the corresponding enrichment events for the broker service so when a repository manager logins on the provide dashboard it's able to explore the set of enrichments that the broker service can build this kind of view already gives a hint about the numbers of enrichments that can be synthesized from the graph however until repository manager sub actually subscribes to a given topic something like those that are indicated here in the slide like missing or kids for authors or missing project references the broker the broker service will not generate the full set of enrichments for them in order to unlock these repository managers have to actually subscribe to a specific topic this will trigger basically the full calculation of all the possible enrichments relative for that repository for that topic and will make this notification records available also to the new broker public api this api at the moment is available under we will be available under api open u slash broker we are still finalizing on the public and point the introduction of an auto of an authentication mechanism to hand to better handle the rate limits for the programmatic access but the truth is that the api is already available so if you go here you can already access this technical specification for the documentation and the api is composed by two main flavors let's say one is relative to what Andrea mentioned during his presentation that allows users to download files that can be requested at the moment we are not generating them automatically but we can take care of managing these requests and provide the files on demand the other flavor is instead basically based on the concept of a subscriber and subscription id so as i just mentioned the first kind of usage is based on the provisioning of a request through the help desk where the repository manager should indicate the open door identifier of the repository they are interested in the opener team will then provide a new line the limited json record that will be made available for them to download note that this file will contain all the possible kind of enrichments relative to any topic for which the users have performed a subscription instead the other flavor by subscription indicated here is already documented under beta develop open u and this list of comments indicates how a client can be implemented to acquire the information from this api essentially the first request will be based on the subscriber email to discover which are the subscription ideas that will be in turn used to gather the different notification records then since we are in this case the response will be made of several several objects namely they can be possibly hundreds of thousands in some cases the request the request had to to go through a list of responses more or less like in the oa ipm h implementation where the resumption token allows a client to iterate through the different pages the same concept applies in this implementation you should provide a scroll identifier to access the subsequent pages however complementarily to the disk space specific implementation the opener team is going to provide a dedicated api client that is going to be made available under the open air gtab account let's say we are still working on that but any feedback on the implementation for this client or suggestion is more than welcome in the end is going to be a tool made for simplify the integration of the added value built by open air and made available through the the broker service so we are eager to to get feedback on this front and that's it for me thank you everybody thank you gladio for providing all this irrelevant information so for you to be aware those things that are already available those things that we are working and to be available as soon as possible this is important this is why also we have these community calls in order to provide some so information really new for you not sure if you have questions for claude or for andre and for jordan i think it's important if you can ask so we are coming to the end so i will just give some more seconds for questions presentation and the and the presentations and the recordings will be made made available so you for sure be aware of that but what i think it's important for you to know is about these new facilities from open air and the the results from a project that is something real that will at least this place users can can can use and can test and and and and feel free to contact us i understand that for sure we will have one more community call dedicated to this to the to those developments because for sure new this space users will start using this in the future and maybe we can allocate more time in a call in the future to this we are only in march for sure i i suppose in the second semester we will have novelties around this place and but if anyone else can want to to share feel free and read we have any other question in the in the document if if you if you so andre already shared the link here for the document that where we keep questions if you put questions there after after the the the meeting we will reply if we don't know we ask andre and then jordan to reply or claude okay be aware of that so no we have the notes we have the presentations available in the website so many things for your presence one invitation one last invitation for you to join also for for andrea molini and for and for jordan and for all of you to join this this public event that we will do next on the coming week the open air nexus project it's a new project it's a it's a it's not a a similar project like open air advance or open air in the past it's a really small project that is targeted to them to the inclusion of of some new services in the open airport volume of services and the inclusion of the open air services in yosk so this is a a project focused on the development of our services and the integration of our services within yosk feel free to join so andre my colleague andre we also share the link here for them for them for this for this page where we have the program etc the registrations but it's in the old page of open air dot u portal and and stay tuned stay connected with us we will have we will keep our provide community calls every month every first Wednesday of the month so all links are here until until December and then we will put the other links after after September and and the subscribe the newsletter or or disseminate the newsletter in your countries or in institutions institutions if there is someone that should be aware of our offer we we try to send every every month two or three news news items so thank you very much for your presence especially to to andre abolini and to jordan i always have problems saying your surname sorry jordan you need i need to learn it properly don't worry i am the test problems and also the the open air apis and the discovery services also have problems as you mentioned so many thanks for your support and and running this presentation i think it will be useful we know that lots of people then check the recordings in the presentations after so thank you for joining and we can promise that we will do another call about this later this year bye bye thank you very much for your presence today