 So today we have our ninth community call, which is great. It's one year of community calls. It's good. We hope that they are useful for sure. Some of them were quite useful for some of you, others not so much. But the idea of these community calls is always to share with you, with those that are providers of content to open air, to share with you the developments, the issues that we have, the novelties that we have to share with you, and also to collect and to welcome your feedback about the service. But today we can say that we have a special call. We have in our minds two or three topics that we want to discuss in the coming calls. But today we have decided to have a more interactive session. I hope that you can provide your opinion about what do you think are the critical features for the future of this service. What are your ideas about if you have anything from a kind of wish list, functionalities wish list that you would like to contribute to. So ideas for the service. So in the second part of this call, I have two or three slides in Mentimeter to welcome your feedback. I hope that you can collaborate and contribute, but feel free to turn on your camera and microphone and contribute. And as for all the other community calls, we have always a moment that we would like to share some of the recent developments. So you can also put in your, let me ask Andrea to share here in the chat the link for the notes and the agenda where you can provide your feedback and comments. We will put always the link for the slides and the recording. We can also share, so be aware of that. But let's start with just three things that we want to highlight from recent developments or novelties to share with you. You remember that the last call was dedicated to these changes that we are preparing in our broker service related with the enrichment metadata events and the way that we collect and offer the service to you. We cannot have today, Claudio, what's sorry, with us to provide us an update, but we are aware that things are almost finalized, the developments, and then we will have time in November to put it in production. It's always critical when I promise something for the current month. And maybe Stefania, my colleague Stefania from the technical team and one of the managers of Provide, he's here with us, will complain with me. But I hope that we can deliver by the end of the month, if not really at the end, we can do it early in December. But I think we can promise for November a way to present this new way of delivering events in production and also the public API with the events. This is the promise that we have and the technical team in open air from Italy, from CNRST, together with our colleagues in Greece, Athena for sure, so they are doing an extra effort to provide this. If I just put here a slide just for those that were not in our last call, just to explain what are the main changes here related with this new way of delivering the metadata events. And we have in this phase one, the identification in our broker service, the identification of the metadata enrichments. You are aware that we have different types of metadata enrichments divided in more and in missing things that you may have in your repository and we are providing more information in things that you are missing. You don't have in your repository and we identify the metadata enrichments for your records, links to projects, the open access versions, abstracts in the metadata, et cetera. And the changes here is that here where you see notifications event, the top 100, this is the main change. So what we are doing right now for a question of scalability of our service and the quality of delivering the service is that what you will see in the dashboard on the area of the metadata enrichments is only the 100, it's a sample of 100 metadata events concerning that specific type. And then if you want to have all that we have for you, you need to subscribe. So for those that have already subscribed some events, you will see all events, but for those that didn't have subscribed yet. So what you are going to see is 100 links to projects or 100 PIDs that you don't have in your repository. And then if you want to see it all, but you will see, okay, 100 from 1500. So you will be aware that, sorry, we have 100, 1,500 total enrichment events for that specific type. But we can only offer to you 100. For now, if you subscribe, you will see it all, okay? This is the main change. And we will provide information in the public API to be consumed by your repositories or the services that you want to develop using the API in the dashboard. So you create the subscription as this diagram represents in phase two. And then you will see in the notifications area all the events related with the type of subscription that we did. If it's a subscription for all metadata enrichments related with that type or if we have any filtered by date or by anything. So this is the novelty. For those that are more experienced using this area of the provide, you may think, okay, it's a kind of, so we are losing any information. So it may have true, it's true. But in fact, with all the expansion of our research graph, we have much more content and we generate billions of events of metadata enrichment events. So we need to proper manage our infrastructure and for a question of scalability, we took this decision. I think immediately we think that you will lose something but in fact, it's something better for the end user and we hope that we can put it in a clear way in the dashboard that we will ask you for feedback. Maybe in the coming, in the next community call early December, you have already a way to check that and provide us feedback. So just to remind some of you that I've also joined in the previous session but I'm aware that there are several people here today that were not in the previous session where we had Claudio and Claudio have explained this in detail. So the other thing is that there are some slightly changes in the dashboard, the user interface and things related with the registration. So the area of updating the information of your repository. So you can have, if you do an update, you will have a field to send a comment, to send a message to the aggregation team, to the open-air aggregation team. We realize that we have some issues in terms of communication with the end user when they update because this is not clear for the aggregation team, what was really the update and then we need to use other channels and help desk to better communicate. So we decided to improve this. We have it in beta, we just need to ensure that we put it in production soon but this will be available soon, you can check. Some of you are aware also of the changes also for scalability reasons that we did in our user statistic service. So we have a new back-end infrastructure to manage this service and we are in the process of migrating all the data, which as we are in production, which make us to be not fully aligned with the information that is available to you in the dashboard, there are some issues. In some repositories have already the information fully correct, other repositories don't have so some repositories will find information really up to date to October 2020, but others will find information, hold information but so we are migrating this data. The information we have is that this will be completed during November, so in fact the coming call in December, we wanted to have about the user statistics, so by that moment these issues will be already solved. And we have already talked with some repositories that the information is working well, you can also apply for reports, socialite reports, et cetera, but in some cases it's not working well. Okay, this is what we want to highlight. Maybe we can also share, I'm not sure if you can see. Maybe Andrea, we can also share the link to the users counts website, just to people, it's a new website where you can check for useful information about the service to understand the service. We, as you know, we are trying to make all our processes more clear to you, to the end users. We want to be more transparent in terms of all our processes and our information. So we have then some new website is concerning specific services and one of those websites, it's the users counts open air, so that you see now I'm sharing my screen, so this is the website where you can check the way it works, what are the, what are the, the way this service, it works and what we are delivering in this service. So we did also a website for the graph, Andrea will share it also, graph.openair.eu. And this is in the same, the line is the same is to provide all the needed information about the services. So we have the information and provide the support information, but then it's important to have other websites to provide this information. And the users counts website, it's to explain all the services, all the relevant information around users counts. Okay, please feel free to ask questions. If you have here in the chat about any issue that you have with your repositories, if I am not able to answer for sure, there are some colleagues here with me in the call that may be available to reply or if we cannot reply, so for sure you will have an answer from us today or tomorrow by our technical team. We did during, during October, open air have organized the open air week with in the week before of the open access week. So every, every day we had a session and one of the sessions on the third day of that week was related with the provide and the guidelines, the user journey and provide and the interoperability guidelines. So the recordings are available and the presentation. So if you were not able to, to saw this session to follow this session, so you can check the recordings. And if you think that it is someone interested in your institution to know more about this, just share this link with them. I think the session went quite well. And we can say that it's time to celebrate. This is the ninth community call and we have started in one year ago. So we have organized eight community calls. We missed the several community calls during the July and the August. Also it didn't organize a community call in January. So we have already one year of activity. The main idea is in fact that you are all part of open air. You are open air. So the data source is part of open air, a repository manager, an open access journal editor, a data archive manager, a crisis, the manager is part of open air. So feel part of open air. So feel part of this community and participate in this community call. So we have discussed the six main topics trying to address the different components of the provide from the research graph to the broker service. We did also one detail about the only aggregation workflow in open air. So six topics already discussed it in total, more than 300 people have joined. And so we had several speakers from open air and even some people outside of open air from some of you that we have invited to share your experience. So we had also in that some to share some music cases. So we want to keep these community calls. I think they are important for our transparency to be closer to you, to you to welcome your feedback. So let's keep with these community calls. So now let's try to have... We don't need to spend one hour in this call, but I think it's important if we look at 15, 20 minutes and then we can finish a little bit early. Let's try to check for your feedback and please feel free to put your camera and make microphone on to share your thoughts. But here the basic idea is to welcome your feedback. I have three millimeters to share with you. But think about what are the features, functionalities that you would like to have in provide that they are not here or improvements that we should have. So think about that and then share with me. Before that, I would just try to... As I think we have already received some questions in previous community calls about the future of the service as open air real open air advanced project will hand in February next year. So people start asking about the sustainability and the continuation of this kind of services. So be sure that provide open air is here to stay. Open air in terms of an infrastructure will be insured by AMCA by an organization. So we have a legal entity now with more than 20 members from different countries and open air services will be are and will be part of the European Open Science Cloud. And this is a slide that usually our open air directors and the technical director Paolo Manghi and our director Natalia Manola usually use. And I pick up this slide just to explain that provide as you can see here in this diagram have an important place role in this European Open Science landscape. So the idea is that we will have different data sources in this environment in this landscape in this European Open Science Cloud. And the open air providers, the open air data sources will be data sources of YOSC via open air provider. Okay, this is important to state and this is clear. Within a different project there are several YOSC related projects as you know, thematic clusters, infrastructure projects and regional projects. Some of you are involved in some of these projects. And in another project in the YOSC Enhance project they are developing guidelines for this data sources compliance in YOSC and they follow the open air guidelines and the open air data model will be integrated and embedded in these guidelines. So be sure that if you are part of open air, if you are part of open air provider, you will be part of the European Open Science Cloud. And we will have in the development of future of YOSC scientific product catalog that will rely in the open air research graph and open air research graph. Additional to other things is relying in your content in the content from the different data sources from your partner. So I think this is important to state, be aware of that. For that reason via different YOSC related projects so the provide services is sustainable for the coming years and this compliance will be supported by open air that will be here to support you as providers of open air and then providers of YOSC via open air. And because of that then we will have this, we can provide different services as you are aware about other kinds of services, the discovery service in explore or the different functionalities that we have in explore, the monitor for funders and institutions, all the APIs. So we'll be available in our ecosystem, in open air ecosystem and the important components of the scientific product catalog will be inside the European Open Science Cloud. So in a simplified way, maybe Paolo Mange and Natalia Manola can explain a little bit better but in a simplified way, this is a way to express this. So we are here to stay and the provide it's important gateway to any entry point, sorry, to the YOSC. I have another slide. Another diagram explaining things in a different way. Different services that we have, that we will also build in future projects. That is there will be an upcoming project also only for the technical part of open air that will be open air nexus that will start next year. Where you can see this layer on the bottom here where we have the APIs, the research graph construction and the provide that are here in this ecosystem of services with the pillars of all the services that we are offering. And they are part of, as you can see, YOSC data sources. So they are part of this idea of the YOSC data sources. So this is just two slides to explicitly say where are we? So what is our place and role in European Open Science Cloud and be aware that we are doing important developments in future projects, in this new project open air nexus, small projects targeting specific developments, technical developments and the interactions with other services where the layer of our graph and provide the pillars of these developments. Let's use some minutes to receive your feedback. So let me check, I need to put the present, okay. I hope that some of you can join me in this meter in order to feel that there are interactions with me with the people who work with me, let me close by Skype. Let me check if this is working, I hope that this is working. So go to menti.com and put this code. Of course, we don't need to record everything in menti, just go to menti.com. Eight, nine, eight, nine, nine, nine, nine, nine, nine. Eight, okay. Okay, it's working. So if we can have more people with me, just go there, just click in the like button in order to be aware that you are in, at least 10 persons, perfect. Let's wait a little bit more so you can connect this menti. I will have an open question, but let's start with a simple question just for you to start thinking about the way that you see the service, how do you assess, how do you evaluate the service? How do you globally assess the value or the interest of the dashboard for content providers? So the dashboard is available since October, 2018. We have improved it during 2019. We have released a new interface version in May, 2020. So for sure you have some well-suceed interaction with the service and other things. No reply here to Skype that are people waiting for me. Okay. Okay, thank you very much for your reactions or if you. Okay, so people are more or less happy with the way that you can use the enrichment method and the validator and the broker and the results of the broker service, but not so much with the user statistics, which is correct because we put in production this service with some gaps and we have improved it in production which is not good, but so we are here to fix and we are here to improve. And for sure everything will be much better. I think that in the future. Okay, thank you. Thank you for your replies at least we have 10. Thank you. Feel free to now, no, no, it's a moment that I would like to have your, we can record here in this many meter about if you have any request, any particular request if you want to share desire from you to have an update here in the provide service, any new functionality, any particular request or even if you want to share the expectation while do you see the development of this service feel free to write, but also please join me, feel free to turn on your camera and share with me your thoughts. We have almost 30 participants here from different countries. And so feel free to share your ideas. So this will be great. Having only Pedro sharing his thoughts is not really a community thing. It's an individual. So if you want to join and to say something even if you don't want to write it just feel free based on your experience or even in your successful or unsuccessful experience with our services feel free to join and to give your opinion. This is what we thought for this community call to share this recent developments, novelties to better explain the changes that we are doing in the broker to explain you the place of provide in the development of YOSC and as a YOSC data source and now some time to also to welcome your feedback. At least I would like to finish the call a bit early. We don't need to spend one hour, but I think it's important. So if you have something to say just jump in and share. And even if there are other colleagues from open air and want to highlight something that's just feel free to say. So okay, thank you for the first input and this is true in some cases. I'm not sure if for some cases of some repository managers we know that they don't receive the alerts and one of the, not the only reason but one of the reasons to do improvements that we did for the broker that I've already explained in the beginning of this call was also related with these bags on the notifications and with the errors that we found evaluating some of the feedback, some of the users feedback about some errors in the notifications. Emails were not sending out so we have started analyzing and then with this increase, this expansion of the graph we have realized, okay, we need to change and we have decided to put this new workflow in place of the top 100 events and then subscribe and send it and we hope with that, we can fix that. We can, for sure, we need to have your feedback in the coming two months about if you are receiving or not but I hope that we can fix that and thank you for this feedback. It's quite important and useful. From my experience, the validator for open air crisis not working very well. Are there any plans to improve, fix that? So, thank you for the feedback. We did the first release of the validator for crisis after some tests, not sufficient test to put something 100% sure in production but we have released it because we thought it was important to start already testing the compliance but we know that this is not perfect. This is why we don't have it yet. Also in the, we don't have yet the registration workflow for crisis because we also so additional to the registration and we need to have a directory for that. We also run validation but maybe some of my colleagues also from the aggregation team can say something about because I am aware that we want to improve this validator but thank you for your feedback. Yeah, more export functionalities. Thank you very much. This is important. So from within this release of this new way of delivering the events we are delivering this new API and we are delivering the possibility to download also the CSV file with the events. I hope that we can deliver that on time and in a way that it's a benefit for you, the repository manager to allow two managers for the same repository. This is important. Stephanie, do you want to help me and say something about this multi-user access? I know that you are not the right person to ask you that but I think you can help me or if you have something useful to say or because we had this since our plans but it was not a priority as we had any other issues but this is the thing it's quite important and I think we have already found a solution to address this issue faster than we thought initially. Yes, hi, Stephanie here. Hi, Stephanie, thank you. We do have a solution for that. We had the priority to release the new block implementation in beta so we can move to production as well as some changes in the registration workflow but if we agree that this is the next priority we can go on with that as our top priority for the next release. Great, thank you. Thank you very much for joining me and then to share this for sure. I think this should be a priority because there are lots of people requesting this and it should be on the top three priorities because if it's not a big effort I think we should put it. Yeah, implementing the possibility of making the enrichment of our content more automatic. Thank you very much to share this also. This is important. What I want to say about this is the following. As you know, you may know, I'm not sure if you clearly know, Open Air Open Tender Skull in 2019 and several companies, research groups have applied and one of the companies that have applied and that is in fact developing a service is ForScience and ForScience is developing a way to develop an update and a functionality in their disk space crease installations to consume the broker events and to automatically ingest in the metadata and the possibility for you to update the record. And for sure, this will be okay. We can say that this will be from the tender and on the coming year will be available only for this space crease installations but the way they did it, it's easy also to implement maybe for some other versions of this space and the concept I think it can be reused in other open source softwares or in other solutions. I think this is important. Thank you for this. Even if it's only five inputs, they are really, really important and I hope that my colleagues like to hear. I think the Andreas is here. Andreas, I don't know if you want to say something or if you need, if you want to say something about the need of improving a bit the validator. It's not your responsibility to the validator but as you are in charge of the guidelines we may have, we may run some tests and then collect some more feedback about this and we can improve a bit the validator. If you think that is useful to share your opinion, please join me and share. If not, I will let me open the... I will just stop my screen for a second just to find here. I think it's useful. Based on this comment that you raised about the way to automatic consume, let me... Yeah, I found it. Let me just... I see Andreas that your audio is on but I cannot hear you. Sorry for that. Yes, I cannot hear you. There is a noise. Let me just share with you. This is not... I cannot advertise this too much. I hope that we can have a community call in January dedicated to this use case, to what I have told you about the... for science is doing. These slides are... This is from a development that they are doing. I'm not sure if I'm 100% authorized to disseminate this, but we are in a community call and we are all a community and I think this is important. Just for you to see, because I did some print screens, just for you to... and I hope that this is useful for you. You can see, for example here, the way that they are doing is that consuming our broker API, so they receive, they are integrated here in the deposit workflow in this space crease, and you can see that they have here suggesting from the broker related with the enrichment missing project and then you can ignore the suggestions and reject the suggestions or import. For the project, let me check if I have another example. I just did some print screens. This was a meeting last week, so you can see that the idea, the concept that for science is implementing is that the repository manager, the crease system manager can manage what are the enrichments that they want to have. Then they check the enrichment, if they select enrichment missing project, they will see this and if they want to import, this will open the record and the added mode of the record and they can update the record based on the suggestions from the broker. This is an example. So, of course, open air can support this, but this is quite difficult to ensure. This is a community-driven development for sure because what we need is to have a close relation between open air and the software platforms. Via the tender, we have the possibility to have a close relation between a company and open air that are offering services for a specific software platform, the space crease system, and this is, I think, great the work they are doing. You see an example here, if you want to import the data of a project in the way that it looks. I just want to give this information and to share with you. I will send an email to the foresigns to say that I have used three or four minutes from this call to share this development that they are doing. They are finalizing the second phase and they are moving for the third phase where they are going to test with some real installations, some clients, let's say. Okay, thank you very much for your input. I hope that this was useful. If you have something to say, I will keep this metimeter open. You can write after the call. I don't want to lose much more time from your time, but thank you very much. The contributions were quite important for us. Thank you very much. And I hope that in the coming call some of these suggestions that you made, we can give you some updates in the coming tour during the coming year, some of the other, because all comments that you made are feasible things, so I think we can address them. Thank you and thank you for that. You can also contribute to the ways how you see to optimize these things between the exchange of metadata and full text. This is something more related than the guidelines and the aggregation processes. This is not the core of this call, but I just wanted to put this question. The metimeter is open. You can write during the afternoon if you want to provide here some comments and feel free to do that. And with saying thanks for your contribution, I will just finish this call. Once again, saying that all the recordings and the slides that we usually do and use and present in the community calls are available in our specific page, so you can, after the community call, see the recordings or share with your colleagues if they are available in the newsletter. So every first Monday, Tuesday, usually Tuesday of the month, we send out this newsletter. If you don't receive it, please check in your spam or if you don't receive it, it is because you need to to subscribe and please subscribe. Come to OpenAir.u newsletter provide slash newsletter provide and you will have access to the subscription of this newsletter and also to all the other newsletters. So we always want to align the newsletter release publication and the community calls. So feel free also to share with your colleagues this newsletter and with other colleagues in your institutions or in your country. And many thanks for your contribution for this community call. Thank you for my colleague, André, that is always available here to support. If you encounter any issue, I always say this with a login to the dashboard, okay. Please send a direct email to, you can use the help desk, of course, but you send a direct email to André. André will share the email here also in the call because we always do it. And with this, if you don't have any comments, any questions, any urgent issue to solve it in our provide, I think we can finish. You already heard a lot of time my voice, so this is time to say thank you for all of you that have joined this call. We will have the upcoming call in the first Wednesday of the month. So you can check it in our portal, open there. Then you go, and with this I finished the call and you go to support the support board. There is a specific page for content providers community call where all the recordings are available and also the upcoming calls. So first of November and then the second of December we will have the community call. So it's already scheduled. The second of December see you in the second of December. If not before use the open air provide service and provide us feedback because this is important. And we hope to have novelties during November related with the broker and the statistics. Okay. So I wait to have good news for you in December also related with that service and to have better evaluation of our user statistics also and then make it more useful the broker notifications as you have asked. So thank you very much. And have a nice rest of the day and the rest of the week. Okay. Bye bye all. Thank you very much.