 And today we would like to highlight some relevant updates that have some impact in our dashboard for content providers and some of the services that we have. So let's say that we usually we provide, we talk about the novelties and we usually try to have a main topic for discussion today. The main topic in fact are those novelties. And at the end I will talk about what we want to discuss in March that I think we will have very good also community call in March. So for this call, basically what we want to do is to highlight what are the novelties that we have related with the broker, the broker service, so the metadata enrichments that OpenAir can deliver and provide for our content providers. And some novelties about also the API's gateways that can be of interest for some of you. And then some some work that we are doing on updating our interoperability guidelines that I think are also important. In some cases they we are talking about things that are in production. Other other cases we are talking about things that are it's ongoing work. So it's just for you to be to be aware and I will try to I have some slides, but I will try also to demonstrate things in the dashboard. For example, usually we prepare always this one slide with some recent news. So about the broker, this is what I'm going to present. So there are already things in production that the broker is as represented in the in the last call in 2020. So there is a new way to deliver metadata enrichment events. And it's important for you to be aware. So you need to play with this information in a different in a different way. So we will demonstrate that. Also metadata, metadata enrichment with the information of our kids is also already available in production. And we are presenting in a in a new way. So I think this is important to our our team. I think did a very good work to try to better present it for us the information that we have about our kids. So I will demonstrate that also also related with the dashboard and the user interface. We have some minor updates that so we are always trying to improve a bit based in our also on some feedback that we receive from you. But one of the things that we we finally found find time to work. It's about the multi user access. As you know, you can only access the dashboard, the provide.opener.eu dashboard using one login only. And several of you, some that are part of this community call today and others repository managers have already asked it. As to to to to be able to have more than one login to access the information about the specific data sources, specific repository. And we are working on that. It's not possible yet, but at least we have already the solution identified and the way that we are going to do. And I hope to have novelties for you in the community call of March, if not in production, at least with a specific timeline to everything production. The multi user access was a request from from the community, but in fact was not in our top list priorities to develop new features. So but now it's it's it's then after we solve the issues with the broker and the metadata enrichments, it's now the priority to deliver. And also, as you know, open air. So aggregates, of course, content from repositories via a way I PMAs interface, but also provide no IPMAs interface with the access to all content that we have. But we are in fact shutting down the same point. So maybe maybe it's not too relevant for the majority of you that are participating in this call. But so maybe there are some services that are consuming our information from from these endpoints. So be aware that we are also due to some scalability problems. So we are shutting down this service. But we are not, of course, but we are still providing access to the bulk content of the open air infrastructure. But it's via via Jason Demps that we have available in Zinodo. So there are records that we generate three or four times per year that we put available all the content in one single file. So you can access via Zinodo to this Demps, to those Demps. OK, basically, and about the guidelines. So I will present it. But so just to say that we have decided to work also on the kind of verification of our guidelines. So to check our guidelines are contributing also to our content providers become compliant also with the fair principles, but basically the fair maturity indicators that were delivered by the RDA majority working group. And we are working on that. This is just also to inform you about. So I will now just highlight some things from the broker service. And then if you have questions, feel free to ask here in the chat or just turn on your camera and microphone and ask him. Let's have a conversation here about this. So from the broker service, as you know, now we have a different approach to deliver events. If some of you in this call need to have some more information about the broker. I have a slide here, but I don't want to present it with the schema of how we are now delivering and working with this broker service. But I just want to highlight now that in the dashboard, what you see now is a sample of enrichments per category of enrichments. As you know, we have more metadata and missing metadata. So we are sending you enrichments to improve your quality of your metadata. So when we are sending metadata, enrichments of something that you have already and we are sending you more or something that you don't have missing enrichments. And now we only send a sample of records. So we only per topic, we can share with you 100 events. Then if you are interested, if you have a specific interest to receive notifications from a specific type of event from a specific category topic, you can subscribe. And only after you subscribe, you will start to see all the enrichments that we have for you. So we have done these changes also to provide more scalability to this service because our graph is expanding a lot. So it's important these issues around scalability and also sustainability for the future to keep this service relevant for you. So you see the sample. Then if you are interested, you can subscribe and so you can, in fact, click in a specific topic like here, the project in this, in this slide. So missing the links to projects, you can click, you see 100. And then if you are interested, you just subscribe and you will start receiving. And if for your project, for your repository, sorry, we have like 1000 records that you don't have a link to a project funding project that we have that information. We can send you 1000, you can see 1000, but only after you subscribe. The way that you that you can do for subscribers is the same as we didn't change that. But now I think we realize that this, this, this subscription is more important because now you really need to subscribe to see all the enrichments that we have for you from a specific topic that you consider relevant for you. So and then to subscribe, you just need to, to, to, to click in the events in the specific topics, if you want to receive links to projects or if you want to receive more PIDs or abstracts, missing abstracts in your repository, you just click in that event. Then you can refine a bit. So if you, for example, if you want only to have, let's, let's see this slide better, if you want only to, to have a specific dates from, so only links for projects over the last three years or from a specific subject. So you can, you can refine that and then you can, you can subscribe to, to this event. So, and this is, this is the way that you, you, you can have to, to, to make a subscription is the same way, but now it's quite relevant because to receive more than the sample of 100 enrichments, you need to subscribe. And then the results of the subscriptions will be available only the notification. So if you check the topic in the enrichment, you only see 100, but then if you check the notifications, you will see all the enrichments relevant for you from the last period that we have generated new method that enrichments and that we have updated the broker, the broker service. And let me, let me demonstrate this part. I think this is the moment to demonstrate this part. So I'm accessing the provide dot upon air dot to use service. And so we have access to the dashboard as for all the other community calls because I know that there are new persons here. If you have any issue accessing the provide dashboard provide dot upon air that you and the, you cannot see your repository or your, your journal. So please just contact Andre Andre, my colleague will put the email here. So you can contact the, the open air up desk, but you can contact directly my colleague and read because then we can solve it. We can solve the problem. So we know that there are some issues with that. The login sometimes. Okay. So here in the dashboard, what, what you see now different is that I was, I was sharing via those slides is that you see the enrichments. You have the sample of 100 records. Okay. And you, you can just click missing the abstract, for example, you will see one of the records and then you can subscribe can refine here in this button here for specific dates, and then you will see the results and then you can subscribe. Subscriptions will be visible in in your notifications and every time we run. So last time that we regenerate all the broker. That was before Christmas. And we are running in fact this during this week. A new update. So we will hope to have that information available on the coming week new new metadata enrichments. We will see all the events that you have subscribed and the total number of events that we are sharing with you. So, for example, missing the orchids here or missing PIDs, for example. So what is new now in the then I take this opportunity. If it is clear if it is not clear, please ask question or just do it via via. Jordan is asking so that the if, if, if notifications are being we have more questions. Okay, let's start with this question from Jordan if the notifications are updated monthly. This is the the the objective of open air is to have notifications updated monthly. Yes. So the maximum is to have it every month and you will pay. But if we don't have an update of the broker enrichments, we don't have new notifications only if we have an update of the broker. So and and as we have changed the broker service in December, we have generated new. And now as we are doing some changes in the open air infrastructure, specifically the open air research graph, we have a slight delay but but not not not so much. So we have this enrichment from mid December and we are going to have only almost two months is after. But the objective that is after the February, we I think we will be able to have it every month. Let's, let's hope that we can have this depends on the So because the big increase expansion of our research graph was in the end of last year. So now I think we can manage to have every month. Yes, Jordan, the answer is yes, but we cannot promise to have it but as we have this month we call we can So always provide you an update information about that, but be aware that this week we are running updates and next week they will be available. And thank you Jordan for that question and thank you Julian also. So Julian is this in this notifications part when we have say hundreds of enrichment's possible but not all are pertinent suppose somehow false positive do we have a way to dismiss them and not see them again. Yeah, great question Julian. And this is quite important. The answer is no, or the correct answer is not yet because this is something that we really want to improve. And, in fact, due to another project related project. So as you know, open air some of you may know open air is have a It's running an innovation innovation project innovation tender. And as a result of one of those projects that was developed by the company for science. And open air in fact already prepared the back end to receive this kind of interaction with you. So, to receive your feedback about for example, I don't want this, I reject this event or I discard this event. So until now we don't have a way to record this and we can only provide this service if we find a way to record, because of that other project that for science is developing for this place Chris, and then in this place seven, let's say, but specifically seven, that in fact will be the topic of the coming call so in, in, in March, we will have for science doing a demo of this, of this, of this service. And then if Jordan can also join me at the end, Jordan can also share something about this because Jordan. So the question in the shot also is, did the pilot test of this service that we are going to present in March. So, in fact, this way of discard and reject events is working already in that implementation in this space Chris. So we are already we are already starting to record those events from this space Chris, a way to use method that enrichments in this space Chris. So we will have the same approach in, in this service. Hopefully, we will do it as soon as possible. But I cannot promise a date where to deliver this, but this is our also in our now in our list now where it's not not only in our wish list but in our priority list to to for the improvements in our services. Thank you. Thank you. Thank you, Julian, for your question. Yes. Okay, thank you, Julian. So, Jim last day. Thank you for your question question from a newbie. Okay, do you have abstracts that wouldn't be present in crossref metadata, for example. We may have, because as we, the broker compare the metadata that specific repository have against the metadata that we are collecting from different content providers, crossref is also content provider but then other repositories or other editors publishers are also contributing and they may have the abstract and not crossref so we can find an abstract from a repository another repository, and we can share it with you. So, for sure, there are those those cases. Let's see. Let's see if I find a good example here. So maybe if my, if my colleague and I find a good example of an abstract. Yes, this came from and pay wall for more kids. Good. So, for example, here to answer. So, for example, this article. We saw repository from University of Mino so my university don't have the the substrates and the end we can get an abstract from this specific repository from from this university. Okay, from. Here is me Microsoft academic. Here is the the aggregator from from the repository from Russia. So different, different content providers of open air, the usual suspects representatives institutional positives but other services. The academic and by wall or now also from our kid because we have this service of the UI boost that we interact information from the metadata from the eyes and we can, we can also provide that information. So, yes, from this sample. We have different. We are receiving from different cases, but for sure this one is an example from a specific institution or procedure. And I think what I wanted to highlight from the broker is done. Okay. The now. So, our call is my, my, my, my, my, my colleague Stephanie from from a Tina research center that is supporting the technical team. And in terms of user interface. So did this, this change now in the, in the way that we are providing, we have a mistake here in our kids events, no problem. The way that we are exposing now the content. Now it's more clear. So, you see the record. Because we have some issues the way that we can highlight the relevant information for you. So now we, we have them. They are keyed we put the, the, the code in bold, just to highlight. And if you can, if you want to use it, as you know, currently events. You can only use this information in a manual, manual way so you can copy paste and update your record. The service that we are going to present next week, next week in March next month. You will see that this is possible to do it. This is almost automatically directly in, in, in a repository, the system. So this case this space crease or the space seven in the future that was the project developed by for science, which proves that this can be done in other kinds of software platforms. As soon as soon as possible, I hope that we can also finally have good news in March, we will have also CSV file so you can download when you see here, when you see the, for example, the notifications you will see the, the link to the events for open in reach missing open access versions. Zero, click in zero missing options. Let's use 96 so you will see also a file to download the 96 results, the file the CSV file with the 96 results from the metadata and you can do whatever you can do in your, in your side in your system automatically. Or semi automatically. Okay, Andre, do you do we do we do I need to highlight something more from the broker. Just a small point that in the previous slide about the arcade is here we system tell us that find one event one arcade and below we have all arcade is this happens because by now the broker doesn't aggregate all the events per publication generates one event or idea that finds for this publication. Yeah, I think I think this is important to highlight yes, thank you very much and right this is important so be aware that we are not aggregating all the enrichments per record so we are sending individual enrichment so we can we can from the same record, we can send you the DOI that will enrich your content, one or key or two or kids and one abstract so from the same records, we can send you three enrichments. But we, the way that we are delivering the metadata regions are enrichment by enrichment and not merge in one single enrichment record, let's say, okay. This is the services is great is really an added value service for all of us. But of course, it has limitations. I see that someone is with sound if you want to join me. Just, just ask a question. Okay. Not sure. So, yes, Julian, I hope that we can do so for the CSV just one information for Julian and for all for the CSV, we will still have limitations so CSV will be a limit to 2000 records. This is the way that we work also in Explorer, for example, currently in Explorer Explorer. If you do search queries, you can also export the results of a query in a CSV file limited to 2000 records, we will have the same approach for for some cases. If you are subscribing gain Richmond type of enrichment, you, you may found more than 2000, which is a problem for CSV but but this may be a problem in the beginning but then if you are updating your records in your side then you will be less records in the future. Okay. Okay. Let me. So, let me ask him. So if we don't have any other question will start Andre. Let me check if I so we were not sure if my colleagues from University of Bilo fell that are managing the guidelines. In the past in open air, we're able to join because no, we're not sure due to a conflict conflict of other meetings so if they are if they are not here so I will unfortunately, you will, you need to listen five minutes more from me and not from other person. So, this was the first date that we wanted to share with you the broker now about the guidelines. It's another it's not something that you see directly in the dashboard it's about our interoperability guidelines and for you to be aware that we are working in some important areas. Okay. And these updates are from my, from my colleagues from from Bilo felt. So, as you know, we have this, this different types of guidelines for different types of content providers. Since the beginning, of course, the literature guidelines. Then we have expanded to that archive guidelines for research data. And then we have done a work with the Rock Rees also to have guidelines for pre systems that have a new version. And because of the open science ecosystems need to integrate other kinds of research output so we have decided also now to present some guidelines for repository for software repositories and for other kinds of research output so. But these two are more kind of open guidelines but it's so some guidance in order to open air to be allowed to to aggregate content from these different kinds of content providers. Which is, which is good that open air can support different kinds of data sources from different kinds of of research outputs, but it's also a problem because in some cases we have repositories in maybe your case that are a kind of hybrid content providers that the sources that in fact are providing not only publications but also data sets or protocols or even software records. So we need to find a way also to to to merge the guidelines to provide individual guidance but also a kind of fundamental guidelines with. aggregated in one single specification. This is the timeline of our of our guidelines, but the just want to highlight that now what we are doing in terms of updates. So the last in product updates that we did that are one of the things that we are doing in terms of. Now what we are doing in terms of updates. So the last in product updates that we did that are available publicly available work in 2018 and now what we are doing is updating the archive guidelines guidelines for that repositories and working on on the verification like I said so to to check our guidelines. Our guidelines and our the way that our guidelines support also the compliance with the fair principles and the fair indicators. And we also want to have this kind of fundamental content provider guidelines based on this reality that we have more and more hybrid data sources. So my life that my my colleagues from the University of Villa felt want to present today for you to be aware that we are working on this and do you can expect novelties. Towards towards fair principles. So what are we doing that I hope you to see soon as soon as possible available in the in the in the also in the dashboard. The the so the idea is that we can also check the the the main elements from the the principle from the fair principles and how, complying with our guidelines, the different set of guidelines that we have in what way you are also complying with the fair principles and how the guidelines complying with the guidelines can help you to also to be compatible with the the the fair principles this is the main idea and what we are going to do is that we are we will put in the in our guidelines specification guidelines not open to you, you have some examples for example they our ideas also to because we already did that exercise. It's just a way to present them to you so you will see in our guidelines page for the different profiles that we have for the different guidelines that we have, like an a box highlighting and in to what extent you're complying with that specific you are also complying with some principles from the fair from elements from the fair principles okay this is the basic idea I hope that this, this is the way that I am explaining is is clear for you. And we are also doing another thing so reflection of the fair elements in guidelines this is what we want to do. And like to improve the information that we have in the guidelines page but also we are preparing using our validator tool like a kind of examination of verification so our idea is that we will have here in the Okay, when currently we have three types of tests that you can do so you can run validation test against our literature repository guidelines against our data repository guidelines and against our systems, and you will see another box here. I hope to have that soon depends off the our capacity to work on this elements are almost already. Analyzed the question of integrate the rules in our validator so you will see wait just to test this is this this is just a test to help you to have a clear view on what extent your repository. Is fair, let's say in terms of exposing content. But it's not a validation to integrate in open air is just a test. Okay, just a service from open air for you to help you on this compatibility. Okay, this is our idea just to share with you. If you have any comment any feedback that you would like to give us just check because now you are aware that we have this is in danger. Then the other thing is that we are going to work in the hopeful to have in the coming months is also this kind of fundamental guidelines a way that we can have a kind of. We will still have the different types of guidelines to different types of content providers but one. So guideline that we can like kind of merge or more nice and simplify this is the objective that my colleagues from bill of health put it in a clear way so establishing establishing this this fundamental basis for for the open air guidelines and monetization and simplification. This is our idea, because more and more data sources are hybrid in our kind of catch all, like for example, so no we have a zeno that you can put publication software presentations that the sets and more and more institutional repositories are becoming like a zeno catch or positive week, and it's important then that the simplify lives because then the repository need to comply with the literature guidelines and with the data archive guidelines and we should come with the simplify version of our guidelines this is the main idea. So as we have the Chris guidelines so be aware that we will we want to integrate more Chris systems and if you have if you have a system that you think that is compliant with the guidelines just contact us so our team can support because we don't have so many pre systems, complying with our guidelines and we need to test them and to integrate more and more more and more the last slide about this to finish is that so being part of open air contributing with content for open air being part of the infrastructure as a content provider. So complying complying with our guidelines. It's the first step also to be part of the of the European open science clouds open air is is will facilitate the onboarding process for the for the OSC and being part of the infrastructure, the open infrastructure, your content will also be part of the content, visible data, research data, publications, etc. in the European open science cloud this is important to highlight there are lots of work ongoing work related with the European open science cloud there are other projects that are being developed in different areas open air is quite active there and open air is a service provider of the European open science cloud. Let me check if you have more questions here so you have access to the presentation if there is something in the presentation that you you want to share with others or just to check you have us also access to the recordings after we have one question to answer in the Google talk about the IPM. So Andre, the information about the IPM is also available in develop not only in the in better but also in production in production. So you see here that the so the information about you if you want to have more information about this we have updated here everything related with the API is so are available in develop. If they are not yet available they will be available. So Julian, you will only lose something if in fact you are using our bulk access to IPM interface. This is the way the image endpoint from open air was a way to open it to expose all the content from open air to certain parties for those that are consuming for example, EPSCO EPSCO was consuming the open air way IPM interface for their discovery service. Okay. Of course we have already had conversations with EPSCO they will start consuming our bulk content via different way, not via our game, our endpoint. So this is an example I suppose that this is not critical for for because it was because it was are not using this. So, you know, I hope that I can have answered your question. Some like systems like those I am aware that some cases some some repository managers working with the IT teams in their institutions also have used our way IPM engine endpoint to gather all content from open air and to check for example for duplicates in their repository or to enrich their metadata. I know that in some cases I know at least from two or three or four situations, two or three situations that the repository managers or IT teams in institutions have used this, but this is not the normal case. Usually, there are other services consuming open air not not you as a content repository manager. Okay, no, no problem. Yes, Julian. Okay, so let me. Do you have any other questions I think I think we don't need to spend one hour here. So we can finish this call before. Sorry for you. So I was the only speaker. So you need to listen for almost 15 minutes. And please be aware that if you have any issue login, ask us directly and raise here. Send us an email that we always try to solve it because the usual problem is that. So you have your data source linking to a different email. So we need to check them and give you permissions. The last thing that I want to share just before we finish this. So our idea for the multi user access. It's something that everyone is asking us. Okay. Our idea, then if you have better ideas just share with us and send us an email or provide us feedback. Our idea is that we will put here in this area of the update. Okay. The update is the where you can update some information of your data source if you want to change the information about the name or update the, the IP image interface is the compliance level. So our idea is to have a new tab here. Okay. I don't remember the specific name that we have mentioned but let's say a table. I'm not sure if Stephanie is here but the idea was to have a new tab here. User, user permissions where you can manage user permissions and where you can see those that have access to your data source or you can have a user. That is already user of open air provide okay but not access to your data source that you want to give them access to your data source okay we will put this here in this page. Okay, and you can update user permissions and you can give permissions to another user so then two or three or four more users will have access to the data source a specific data source. For example, for this case it's supposedly off menu, I will update here and give more give access to other users. Okay, just to share this with you. If you think that we should put this in another place just tell us but but I think we from our discussions we want to do it here. And I hope that this will be useful for everyone. Okay, another question from Andreas. So Andreas is asking how are the metadata from different providers merged in the items we have examples where it's unclear why which metadata is prioritized. Okay. I'm not sure if I'm understanding well the question but I will do my best. Thank you Andreas for the question. The way that the broker works. It's a. So we have. So we compare the metadata. Do the eyes, based it on when we duplicate, we do duplicate publications, and we compare metadata so for this for this metadata coming from this data source. We have these fields for this one we have those fields and if there are gaps we just do the broker just do the work. We We, I'm not sure if my colleagues, my colleague cloudy what sorry for example from CNR is here to help me reply into this question but what we what we if I understand about what is not clear for you. Okay, what we do is that there is a prioritization to data sources that have higher high quality metadata let's say more metadata fields available in our infrastructure so this is the the prioritization that we have and we also usually give prioritization to repositories to institutional repositories. Instead, for example from from the publisher or from from from others. So this is what I can say in terms of prioritization but I am not sure if I am answering your question if you want to jump in and put your audio one and ask me your questions feel free if not so just put your question. Just share your email with us in the private message if you want and we can reply to you with better information if I am not Yeah, providing all the needed information. Yeah, thank you very much for the feedback I'm not I'm rather new with the whole thing and I think this help just have some weird examples where our metadata has overwritten the publisher metadata and in some cases we get our DOI is used and in some cases not but it's probably best if I contact someone on your site directly. Who can I ask. Yes, you can you can. So my colleague cloudy what sorry, we can also share the email here it's not the problem so we are open to questions. Or you can ask you can send this email for me or for Andre and then we can point you to one day for cloudy cloudy is the manager of the broker, but the way So the way that it works is like I said so we the from all the duplication that we do that we do from all the the the DIY boost also that is being run now in open air so we try to compare metadata so and and it's important to say we also make mistakes so we also deliver metadata enrichment that they are not completely enrichments due to problems with the duplication the wrong, for example, the duplication or wrong other kinds of mistakes that we can do. This is why we also have a trust a trust level in the in the in our services also I want to just twice also point that for example here. When you see the event. We also have we can also not sharing your screen. I'm not sharing this course. So, okay, sorry. But you okay, but not to avoid this time. So just to say that we also have a level of trustness with the with the with the metadata enrichments in some cases is zero one, for example, deliver the eyes or you or is it yes or no you have it or no for other cases. The links to projects. This is different so there is a level of trust because it's in something that is missing and raise for you to understand yes and sorry for that I forgot to mention so some cases we are comparing okay and they and they is already sharing the screen. Thank you. Thank you. So this is the you can also filter by the level of trust but in some cases zero one the others is really it's important to say that we have we are sending metadata enrichments based on comparing and working on the only at the metadata level. Okay, the data sources are providing metadata and we are comparing and delivering the metadata regions but also based on test mining. Okay, and this is important. Sorry Andreas I didn't provide you this feedback for example links to projects. I think I we can say that the majority 80% between 80 to 70% from our analysis. The links the new links to projects that we are delivering for repositories are coming from test mining. Okay, from our test mining algorithms, not from metadata information about projects that we found in other data sources. Okay, this is important to highlight. I think that this was more useful for my answer. I forgot to mention that part of the test mining. And please feel free to contact. And they already shared contact from probably that is the manager of the broker. He can provide more clear information if you have any doubt but feel free to contact me, me or Andre also. Thank you very much. You can play with the play with the metadata enrichments that you have. And for sure you'll find more explanation you for sure you'll find lots of useful information in some cases maybe some, some things that they may be appear like errors or you want, you want to reject this card. Breanna, do you have any plan to have monitor dashboard meetings that are this is the Breanna. I'm not the monitor dashboard manager and doing my best for provide and to have the, the feedback from the community from repository managers and to be able to have open as a useful service for all repository managers, three system managers, etc. For monitor. I think the idea is also to engage with funders and we gauge those that are close to funders supporting funders at the national level. There are relevant progress is in monitor dashboard, but I cannot say more than this. Breanna, my dear Breanna, but I would like to nominate you just to have more work. It's okay I understand I know that person. I just think that maybe you have more information. If they are planning if this group also planning the meeting like this one. The important yes this is important important to say that we open air also want to have this approach of community calls with the with other with other stakeholders to engage with other stakeholders. I'm not sure if this way of doing things is result also with funders. But I think have a kind of calls with the funders I think it's for sure important to gather feedback requirements, etc. And I think this is this is the plan also. I know that for within also a ask future projects. We also want to engage more with the providers and the community calls is an approach that we also want to follow to have more feedback. Thank you for putting the question is important and I know that everything is related information that we are also giving to repository managers and the providers also is also important for funders so. Okay, we reach one hour of call. I hope that. So it was useful for some of you for those that are new I hope to that you were not lost. If you want to receive more information so just contact us be aware that presentations and recordings will be available. So, our next call will be March, March three. So first Wednesday of the month. Please go to the link to the community calls all the community calls are already scheduled you can put in your calendars. Okay, bye bye. Thank you very much. Thank you all. Several colleagues from Portugal also thank you for joining and all the other colleagues many things for joining. I'm happy that you can contribute and give your feedback and your presence here. Bye bye.