 Okay, so let's start from the agenda for today. We'll start with some highlights and novelties, so things that we have been working at for your gateway. The topic of the day will be the co-creation of some functionalities. So we have some ideas on new functionalities, but we do want you to participate into the process of design, also to understand which are your, if there are any priority, other things that we should add to our list. And we have the use case from Nea Nias, and Nea Nias is a project that ended and there will be Eva Schakka, who I don't know if she already joined, in fact. Yes, hello. Good morning, everybody. Nice to meet you all. Thank you. So she will present us the Nea Nias space research community, and then we will save some time for the questions and the answers. Okay, so the highlights. We have created a new feature for you to create your own menu. So by default, your own page only features the menu at the top, which is a kind of predefined list of items, but we had requests in order to add a more personalized menu. So this is what we have done, and you can access that from the manage section, from the administration section of the dashboard. You can select pages and menus, and there you will be able to create your menus. So you can create menu items that link to a page internal of the gateway or to an external page. For example, your own website or your own training materials or any other things that you think your researchers be interested in. You can decide to show hide the menu, and you can also select the position. So if it's going to be on the left, as in this case here below, or on the right, as in this other case, or in the center. Another thing that we have implemented is the visibility of the curators, because currently, all the managers or the creators of a dashboard are visible in the curators page, as soon as they fill in information about the short biography. So when you add your image, the information about your affiliation, so when you fill in that form in the personal info part, then you are visible. But sometimes you don't want to be visible, so we implemented this button in order for you to hide. So it's likely the Alice in Wonderland cat, so if I'm invisible, there is no Alessia among the curators, but if I click visible, I am. Some work in progress. We had some requests from managers of different dashboards in order to provide more advanced configuration for this collection of products from the open air graph that should be included in the gateways. So the first one was the selection criteria specific for fields of science and sustainable development goals. The classification by FOS and STGs are better features of our content graph. And currently, it's possible to exploit them for creating your own content for the gateway, but it's not really easy. So we are thinking about something that will enable you to select directly the terms from the control vocabularies and the hierarchy. The second feature that was requested was the possibility to select projects and data sources in bulk mode, because now you have to click each data source or each project that is included in your search, which is a little bit tedious, so we will allow to do it in bulk. So you do a search by a term, for example, on the project, you get a list of projects and you can select them all. And then clearly, if there are some false positives in this list, which are not relevant for your community, you can remove it and that you can do it one by one, because we assume that there will be not a lot of false positives if you select the bulk addition. And finally, the combined selection criteria, what does it mean? It means that basically, what is currently available only on the data source selection, which allows you to create additional filters so that you can say, for example, I want in the gateway everything that comes from HAL, which is a repository, but not really everything, only those products whose contributor is Daria. So that last part, so whose contributor is Daria, is only applicable to a specific data source, but we will enable these kinds of filters to be applicable to everything, everything that is available in the open air graph. So the topic of the day, the creation of new functionalities. We had some ideas with the other members of the open air team, both technical but not only the technical team. And we thought about this for let's say, yes, ideas, and we would like to ask you if you have something to propose or if something is really not interesting for you and we should not work on that. So starting from the gateway pages, currently you cannot create a page from scratch and this is technically, currently not possible, but you can edit the pages that are available. So for example, you can change the content of the methodology page or you can change the page or you can change the content of other pages. But in fact, you cannot change for example, the title of the page. So what we were thinking is if you need other specific pages to be added so that you cannot content in the proper context. For example, there is no page now for you to add the open science practices of your community. So would this be something that you would exploit that you would use or is there any other page that you would like to have in order to add it? Another idea was the Twitter feed. So do you have a Twitter account and would you like to show the tweets from that account or with a specific handle in your gateway? And if yes, where we should put this box with a Twitter feed? Then we have some ideas to help you with the engagements with the users of the gateway, which are basically the researchers of your community. Because currently we don't do basically anything. We completely rely on what you're doing on your side with your community. But maybe we could send some notifications to the members who subscribed to the gateway, trying to make them come back and be more active in using your gateway more than they are doing now. So we could, for example, send notification emails when you as a manager change the configuration or when we see that there is a high impact publication included in the gateway that was not available before. Or we can send a monthly overview of what's happening in the community with some numbers like the number of subscribers, the numbers of applications, the numbers of managers that are fine tuning the gateway and so on. Clearly, there could be other ways. So we are open to suggestions and how to support you to engage with the users. And finally, the deposit functionalities. Currently, when you go to the deposit functionality, you can search on all the sources that are available in Okinawa. Now, we don't think that this is really useful for the community itself for a specific community. And we thought that a good idea would be that you know which are the repositories that are suggested for your community and you can suggest those. So in this way, in the gateway, we could highlight the community specific repositories, maybe with some comments from you that explain why or how to use this repository for the research products. And okay, we can start a small survey with Mentimeter that Julia prepared. And then we can start the conversation. Can you see my screen? Yes. Okay, so you can go to Mentimeter, Menti.com, enter the code or simply scan the QR code. You can click the hearts or the tabs up when you are here. So I can see that more people are here. Okay. Okay, I'm going to the questions. From some reason I can't. Okay, give me a second. I don't know why it's not presenting. Okay. So would you like more pages in the gateway portal, as Alessia suggested? So you like the idea? Yes, it seems. Okay. So now we want to know which page. Okay. What extra content do you desire in the gateway? So as I was saying before, we were thinking about one about open science, where maybe as open air we can start with some general guidelines, but then you can fine tune with specific best practice from your communities. But I don't know if you want to have other pages for other things that maybe you do in your projects or in your initiative. Now let's see. If a gateway gathers input from more than one scientific community, it would be great to display them separately. Even manually filtering the result. YouTube channels. Ah, for demo video results or repository of presentations and slides. Knowing where lists come from would be great. Many filters applied. Okay. And general guidelines for beginners. How the gateway can add to authors to make the research outputs more reusable. Okay. Guidelines and explanation of regulation. Relating data to publications would be good. Okay. I mean, the gateway really has the links between publications and data. So I don't know if maybe the suggestion was to have a page where we describe maybe the process, the processes that are used in order to link publications and data. There's going to be situations more for the university alliances. Okay. What orchid? This is a little bit vague. If you want to speak, feel free to take the microphone. Okay. I will move to the other questions. Okay. So here there were some suggestions that we would like you to rate or to click. But you would like to have what is for you of major interest in the web page. So the first option suggest repositories is for the deposit functionality and the guidelines and open science practices is one of the new page that we propose to have. The Twitter feeds, but we should investigate also the LinkedIn. Indeed. Okay. And the blog items. Okay. Any suggestions for new future contents that you would like? I think somehow they already did in the previous one. Okay. Well, in any case, if you think even later, let us know even by emailing us. Okay. So here it's more an engagement request. If you need some material that you decide as to produce like newsletter or news items for your newsletter, leaflets, templates, I don't know. So anything that can be helpful for your user engagement activities? Tutorial. Okay. Tutorial for users. Okay. So we already started preparing some mini video tutorials, but they were focusing on the administration functionality. So probably we should also think about having tutorials for the end users. And this can be done in collaboration with the team of the Explorer portal as well, because most of the functionalities are in common. Clearly if you want, let's say a tutorial branded for your gateway specifically, we can do that together. And API, I have to say that we already have them. So if you go on the developed page in your gateway, you will find some basic instruction on how to use the API of OpenR. And thank you very much for the feedback that you had. Okay. So I think I don't know if there are any questions in the chat. Let's check before giving the floor to Eva. So yes, there is a question regarding outreach and engagement. Do you maybe have video tutorials on how to use the different functionality of the dashboard for the users and how to link their publications to the gateways? Okay. So yes, this is something that we should work on, as I said. And Irina suggests that Twitter feed would not be a high priority now that we have many living and moving to Mastodon. Okay. So we should investigate LinkedIn and Mastodon, which I don't know. So it would be interesting to investigate upon. And Joseph suggests to be more transparent to the users about the filters that we are applying. And I agree. A question from Martin. Hi, Martin. So we have created about 500 links, but they are not yet visible in the gateway. And sometimes this is possible because it requires a little, I mean, all the things that you add via the linking process is added automatically if you imported the publications or datasets from Crossref, Datasite or Orchid. But if you enrich something that is already in open air, then it takes some more time. And this is because we need to merge the new information that you added with the one that we have. And we do this every time we update the content of the open air graph. But I will check your specific case later after school to see that everything is properly set. We will try to modify the methodology page, but we don't have access to change it. This is instead strange, and you should be able to do it. So I will take a look at this. Okay. Then there was the suggestion to enrich metadata with orchid information wherever possible. Okay. And we already have an integration with Orchid, which allows you to basically tell Orchid that one publication that you found in the gateway is yours. And we are exchanging information with Orchid. So this information goes back and forth in order to reach both the open air graph and the Orchid information. And it's not something that you cannot manually. You cannot type your Orchid. But you cannot be with Orchid and in this way, your Orchid profile is linked to the open air profile. Joseph asks if we exploit other PID systems, so systems for persistent identifiers in addition to Orchid, like Cloud for Institution. Yes, we do. We use RAR, GRID, and ISNI and other type persistent identifiers for organizations. For the authors, we only support Orchid. For publications, we support a wide range of PIDs, also based on what is supported by the open air guidelines for the repositories. So DOI, ANDOL, PubMed identifiers, and so on and so forth. And I think I went through all the questions. So I think it's time to leave the floor to Eva, who will present the use case for the Neonias space research community. Eva Schacke is a researcher at the ENAF, which is the National Institute of Astrophysics. Yes, in Italy, basically in Italy. Hello, thank you, Alessia. Okay, thank you, Alessia and Julia for inviting me to this meeting. Yes, my name is Eva Schacke. I am a researcher at the Italian National Institute for Astrophysics, and I work at the Astrophysical Observatory of Catania. And I will briefly present the Neonias project today with the gateways that we developed within Neonias. I've seen also some people belonging to the project, so maybe they will include the further details. But the Neonias project was funded within the IOSC calls related to publishing to the IOSC innovative services in different thematic communities. The project started in November 2019 and just ended October 2020. With three thematic communities have been involved in the Neonias that you can see here, the underwater atmospheric and the space community. And me working in the astrophysics field, I belong to the space community leading the related work package that was aimed at the development of thematic services in the space area, so for astrophysicists and planetary scientists. So we have developed these thematic services and exposed them through different channels, let's say. We have onboarded the services to the IOSC, so they are available in the IOSC marketplace and the IOSC platforms. But we have also developed our own service catalog that is, however, compatible with the IOSC portal and can exchange information between the Neonias catalog and the IOSC portal. But we have also developed some portals to collect our results and also showcase to the community our results, our publications and the data employed. At the first attempt, let's say, the beginning of the project, we as the space community, we have decided to develop our own thematic portal to collect all the information related to the space community. In this portal, we have collected all the links to join the services, but we have also linked to some platforms such as the Twitter from the Neonias channel, from the Neonias project. And thanks to RSS, we were able to connect to the main Neonias repository to show some blog articles and disseminations articles. Then quite, it was the third year of the project, we started to build our community gateways, one for each of the thematic communities. So you will find one for the atmospheric, one for the underwater and one for the space. And I will show the one that we developed for the space community. You can see here, and you can reach it from Neonias-space-openair.u. And just some days ago, we discovered that this new functionality is about the menu. And in our case, it was very important because we wanted to link with, of course, the Neonias project website, but also we were able to link the three different communities. So if I go to the atmospheric, I can navigate to the atmospheric community. I can go back to the space community. And in this portal, we were able to expose and to show which are the main subjects we work on and the services that we developed in which area you can use them. So we have identified them through the subjects list, but we have used, of course, the summary that is the main page of the gateway to expose our services so that is much easier to reach these services and the related documentation to use them. As supporting organizations, we have included Openair, but we have included all the organizations that are members of the work page related to the space services. Also, what I can show is that these are, yes, decorators and I think this is a new functionality. And we connected our page, not only with the Neonias project that is the main driver, but with other European projects where our services are being employed, for example, ECOGAL, ESCAPE and Vialatte. And then we have also used the links to the Neonias communities and especially we are linked to the Neonias community that has been created for the Neonias project, but unfortunately it is not very much populated. This is just one entry and Cristobal Bordillo is linked in the call so he can say something more about this upload, but this was a great opportunity to promote this latest result from the Neonias that is also a Gold Open Access publication and to access the data that have been used for this publication that has been published in just physical journal letters. So this is basically all. I'm very open for your questions or any curiosity about how we developed something on the gateway. I have to say that we couldn't have much effort on these gateways because we developed nearly during the mid of the third years. So we were going to close the project, but I believe that we will still have time to enrich with the new functionalities these gateways. So feel free to ask me any questions. I know in the call there is Cristobal that is another project curator for the space, but maybe if there are curators from the other two areas from the atmospheric and underwater, please feel free to add any additional details that I may have missed. Thank you. Thank you Eva. Thank you very much for this presentation. So let me check if there is any question on the chat. Okay, since this is not the case. So since we have some more time for questions, I would like to ask you one. So what do you think that was the more complex activity to do to set up your gateway? Okay, to say that maybe the most complex activity and maybe something that needs to be reviewed is the filtering on the selection of the publications because as you can see in our gateway, we are working in areas that are transversal all around the different communities. So for example, if we add a subject, machine learning or deep learning, we get many thousands of publications that are not related to space. So neither to astrophysics or planetary science or astronomy in general. So in this case, we had to change or add additional tags. So for example, we have also put at the beginning image processing that was quite vast and broad subject. So we put astronomical image processing. The same for machine learning, astronomical machine learning. So if it would be possible to add complex relations between the tags with the logics, some logics and or and some more complex filtering would be of help. The same for the data, because we discovered in the data, some data set that have nothing in interest in our community. So this is what we discovered. Yes. One of the managers will benefit from the new feature of complex criteria that we are working on, working progress functionality. Thanks. Okay. And there is a question on the chat from Mattei. Mattei, would you like to speak? What is the relation between the services and the gateway? Yeah, if I call it right. Because on the gateway and I clicked on the services you talked about and I get to this catalog of services, which is a separate thing, right? Yes, it's a separate one. So it's just a link. Yes, you're right. Because the services are apart, they are running in different computing infrastructures and developed within different environments. So within me they are running on a cloud. It is the cloud. But just to make links from there is a way also to make visible our work we have done. Also because in the project we had a very high KPI on users reaching. We had to reach about 1,000 users. So we had to promote as much as possible the services to gather more users. And of course we have also published many results on scientific publications in both area of astronomy, planetary science, computer science, machine learning. So this way was also to collect material and maybe find related works that were related to our studies. Thank you. You're welcome. Thank you. And then if I made then kind of a follow-up question would be and probably would rather go to Alessia. I mean in EOS portal there is the research products plus services are kind of one of the resource types that are being presented. Here not, but in the sense of exactly of this interlinking and kind of saying that in these publications we use this service and this data set was created by this service. I wonder if you have any considerations on the kind of question of what to do with services or representing them there or? Yes, thanks for the question. So all the work to introduce the concept of services in the open air graph is ongoing and we are doing this in the context of the project called EOSC future. So basically we already have an open air portal that shows the services and the EOSC portal is one of the sources from which we collect the information. On the other hand, we have to exploit on how to link the research outputs to this service, which is the most important things apart from the dissemination of the existence of the service clearly. And our text mining team already made some experiments on this but yes these experiments were yes it's complicated and the experiments were run when there were very few services registered in the EOSC portal. So we didn't have many examples in order to understand for example how the publications refer to the service because they are not acknowledged as a project for example. Very difficult yes. So I can only say that it's a work in progress. Okay very good thank you. But of course this may be very interesting so you know and you are acknowledged as a service provider let's say for the results the scientific results that come out from the service. Yes in fact we have been working with several research infrastructures which have a connect gateway and in that case they do not want to have a portal with all the publications all the products about a specific scientific domain but they only want those that have been produced thanks to the infrastructure and thanks to the services that are provided by the infrastructure. And in that case we are in some cases we are able for example to understand which are the publications that describe results which were produced then to one of their services but in other case we cannot because it really depends on the community you work with and which are the practices that they use. And also in some cases for example with the RISIS community which is the innovation and science policy research infrastructure it was very easy for some data sets and services and it was very hard for others. So for example it is more easy to understand which are the publications related to the CWTS dataset but it was very hard to find those that were related to Cheetah which is another one that they have. So even inside the same community there were very different use cases to be to be addressed so this is still a challenge. Maybe there should be a simple mechanism related to such as we do with DOI to cite other papers. So to assign I know maybe difficult to assign DOIs to services because they evolve quite quickly but I don't know something maybe related to the ESC portal just assigning a persistent identifier at least for the portal. Then the service is another thing because it's an evolving software. So are there any other comments or questions? I think this is not the case. So Julia would you like to add anything else before we close? No I really like to thank you for the inputs that you have given to me and if you have some ideas specifically to start working on a template for left leads or tutorials please let me know. Okay. Okay I would still have one question using the opportunity that we are here. I would like to understand the relation between the ESC portal or ESC catalogue and open air. I mean it seems it's quite obvious that it's the same I understand that it's the same technology behind it. But are they completely different threads and partly the data is overlapping as well right and the kind of sources where the data is coming from so I would like to understand how the two relate to each other or not at all. Okay no yes they are related so the ESC portal started and it only had services. In the open air graph you can find research outputs but not the services. So what we did is that we included the services in the open air research graph and we developed the ESC explore portal that shows everything that we add in the graph plus the services from the ESC portal. But one of the tasks in the future was to have an ESC research product catalogue. So instead of building everything from scratch again and re-aggregate everything as open air was already doing it was decided that the ESC research product catalogue could be based on the content of the open air graph. So what we do is that we select from the open air graph the products that are relevant for the ESC and we provide this information to the team who's creating the portal and the index the service that is beyond that yes. Okay and so basically it's really downstream so from the open air research graph there is some set of rules that select a subset of the data that is passed on to do your resource catalogue. Exactly yes and it is kind of re-indexed separately in some other system. Yes yes. Okay cool okay thank you and these rules of kind of the selection the filter how is that defined? For now we include everything that comes from repositories or data sources in general that are registered in the ESC. Okay yeah okay makes sense thank you cool. Then maybe we can expand when we have the link between products and services maybe we should add also those products that are linked to services registered in the ESC but this is yet to come. I would have one more question. Please please. But maybe it's just my ignorance I was wondering how is it in the dashboard of the of the kind of community or somewhere else do I have the option to see the usage or how many people how people use individual or how many clicks views individual resources have or how often kind of is it used actually? You have some information I can share my screen. It's the gate we have today so let's try this one. So if you open a publication and we take one for by chance we should see if there are some information about the usage. So that should be publicly available next to the yes because I mean okay here it is these are for example the treats but we also have information about the download and the views based on the usage counts service. Okay this publicly available information on the level of the resource so to say so I don't have this okay I was wondering something kind of from the point of view of the dashboard if I could have come aggregate the statistics of so how about the problem that's okay. That's interesting so it's something that I will write down. But okay thank you this is already helpful you know and now I stop I promise. No no we are here for for questions and for clarifications so this is why we we want to organize these community calls so thank you for your interest and your questions. Thank you for the great work. So the next community call will be in March there is already the the next call written on the 31st of March at the same time so from 12 to 13 and we will present the new novelties and another community call. So at the moment I'm writing you email one gateway per gateway but I will try to make another mailing list if it's not a problem for you. In a way that that we are trying to be all together and we can we can talk. In any case feel free to contact me and Alessia if you have either technical programs or you would like to have more outreach and engagement for your specific gateway and if you would like to have some kind of material or if you want to start with us the tutorial for users and Alessia. Yes thank you Julia and thank you all for being here today and I wish you all a great day and have a good one.