 One more community call, the first one after December, so we will have another one in November, in December this year, so it's always a place to provide you information about some novelties, ongoing developments in the provide service in the related open air services and with the services from open air related with the activities of providers of content for open air infrastructure, so everything around the open air provide dashboard and then some other things related with this, like the guidelines for example. So for this session our idea was just really to we didn't decided to discuss any topic, usually we have one main topic for discussion, open air graph or the broker service, so we decided just to highlight some novelties, some updates, also to demonstrate one feature that was requested since a while, I must say that almost since the beginning of open air dashboard, of open air provide dashboard, the multi-user access functionality, and then to get your feedback for some new features that we are working on and we would like to have your feedback, but okay this is a community call, so always open to discuss other topics if you have any doubt, any other topic that you want to discuss feel free to ask, okay. We have time during the call or at the end, so one moment at the end for discussion, but whenever you want to ask questions just write it in the chat or please join because this is a call, it's a community call, so join the, connect your audio and ask and talk with me, so this is the agenda and let me start with the, okay let me see what is happening here, this is why I didn't want to have this surprise, okay, so recent news from provide, multi-user access functionalities finally working in available which is really great, in the beginning we said that this was really important as an improvement from the provide dashboard, but we didn't have it as a priority, then we decided that this should be a priority, but different other dependencies of the federated authentication etc that we have told and now it's working well from the tests that we know, so if you have any issue we'll demonstrate this in two or three minutes. A reminder for all of us that we have a feature with the first one in the available in the validator, so please use it, in the screen, so here in the validator, in the in the validator area where you can test the compliance of your data source against our guidelines or for literature or for data repository, there is available this fair assessment box here to perform a fair assessment of your metadata is a simple validation, interesting I think, so we and it follows the same process of all the other compliance tests, so it's interesting and you can get a report with feedback, so if you are interested on that okay you can ask questions but we have the recordings from the previous community call that in fact was dedicated to this new feature here in the provide dashboard, you have the slides and the recordings but if you have questions, so we are able to reply to your questions. The other novelty that we want to highlight is regarding the guidelines for something that we are working on, my colleagues from the University of Bielefeld that are part of this important task of updating the guidelines already presented in the previous community call, also during the open science fair we share that we really want to get your feedback, so if you just if you wish to share your thoughts, so just go to this link, you are available, I have it open here, the guidelines website of openair, so you can access this draft and check, so there are also here the way that we can get your feedback, so you have a google document that my colleague Andreas that is also here set up and I think this is quite useful, I need the help, someone mute, okay, so this is I think something really important, so we want to the idea is in fact that we want to integrate these kind of things like the fair enabling in also in our guidelines to see these guidelines as an integrated guidance for us where we have not only where we merge the guidelines for literature repositories and the data repositories in one single document because this is the challenge that we have, lots of content providers of openair are in fact providing literature and data or other kinds of research outputs, software records, so this is really important that we can merge this and so we have already here a version covering some of these things and so it's good if you are willing to check what we have done to make comments, questions, feel free, okay, from in terms of recent news this is what we want to highlight, so if you are interested in the fair assessment that we have in as a better thing, so just check the recordings from previous previous call, so let me check, we can share here the links in the chat, some of these links, maybe it's good also if we share the link for this presentation already during this call, okay, perfect, so if you would like to ask questions, I was checking the chat to see if there is questions, we also have a Google document, we can put in the chat also if you have questions, not sure if my colleague Andrea can help me with that, sharing here the link, I will share the links, perfect Andrea, thank you, yeah, so about the multi-user access functionality I will demonstrate it, with just three highlights the way it works, so we have the, this is something that is really relevant, you as a provider of OpenAir have access to the provide dashboard, you have a one single login to manage your data source and to have access to all the features, so to update the information of your repository, to check the broker method at events, to check the user stats information or to enable that service, to check the monitoring history, but so you can now provide access to other people to do it and to update that means of your data source in OpenAir Provide, so just go to update, where we have an area to update, where we update also the interfaces, if you have a new OAPMH interface, you can use this and then you can update and invite other people to become an administrator of your data source, so it's a simple integration of registration of an email, what is important here is that the thing that is not so simple is that you need to make sure that that email is connected with an account, an OpenAir account, this is important, so this is not an invitation, due to some limitations in the way that we can solve this issue of the multi-user access, we set up it in this way, so it's quite simple, if you have an user, someone that have already an account of OpenAir that you want to add mean, you just invite it and it works perfectly, if you want to invite someone that don't have an account, first they need to create an account in the OpenAir website and then you can invite him or her to become an admin of your data source in OpenAir Provide dashboard, okay, simple but with this, sorry, with this, with this difference, okay, let me do a quick demo, yes, using the Google Chrome, so just to check if you can see my screen, so you can see my screen, I was not sharing on the dashboard. Okay, thank you, thank you very much, so the place where you can update this is in the, you can have new admins in this area of the date, okay, and you can update information, you can update interfaces and there is this part to update the admins, okay, just ensure that you invite someone to do this, I'm gonna invite myself, okay, now, so just need to invite someone that have already an OpenAir account, this person will receive an email and this information will be recorded here for your knowledge, okay, it's a simple process, it's something that was requested, I hope that it works, if you have any issue just say it now, if you want to test it right now, test it because then we can solve any issue that we have, so this is a simple way, I think this is quite important, what will happen is that now not only the person that have access to this account have access to all the information of the dashboard but also to other things, so in the account of this admin, a new repository like this one will be, okay, therefore for access, let me check if I can, I think I need to log out, yes, it's better if you log out and then log in, yes, in fact I'm not sure about my mail but let me see if it works, if it doesn't work we test with another, if it doesn't work it means that it's here, okay, I was not sure about this my mail, I'm using another because we changed the account, okay, so it's already here in my in my data sources, the University of Minio repository is already here available for me and then I in fact can have access to the exactly the same things that the account of the original account, the owner of this data source have, so I'm using here Firefox just to test my Pedro principle account and in Chrome I'm having the Uminu account, University of Minio account and so University of Minio account only have one one repository, in my personal account I have other repositories so I have already access to University of Minio repository, so it works as you can see, I didn't test it before, it's a live demo, so we can do that, so for example for our data repository we did it, I already did it with my colleague Andrei, if I remember well, yes, so I invite others to become also managers of this data source, the data repository of our University and so I was the original one, the original person to validate to register this data source and now Andrei and Paula also have access, so please check, hope it works for you, I think everything is working, the question is really this part that we alert here is that to make sure that the user already has an open air account, okay, with the email address that you are inviting, if he or she have, so no issues with that, okay, this is interesting in order to avoid sharing accounts like some people do, sharing passwords of different accounts, so this is better because then you can, and this is really important because also for different scenarios, use case scenarios, people that are leaving the institution, these kind of things, so this is really interesting, okay, let me see if you have questions here. We have one question, I think you are ready. Yes, okay, I didn't reply exactly, but I show yes, this is, so they have exactly the same rights, they become an admin of this data source, like the other, the original one. We can improve that, Julian, your question makes sense to have different levels of permissions, but for us it was a bit more work, we need some improvements based on the structure that we have, but we decided to release as soon as possible because this was something that lots of people were asking for, but feel free to share your thoughts about I can imagine some use cases, but Julian if you have in mind any specific use case scenario that you think that it's, so you as an administrator have access to all things and the other people only can view, for example, this is something that we can improve, so the next developments for this feature I think it's good if we do it, it will be a benefit, but for the time being all the features will be available here, okay, so I remind once again about, so if you don't see, if you have a login and provide, okay, provide.openair.edu and if you don't see data source is here as you expected to see, okay, just contact us and we will provide you the information, so what is the account connected to your data source or how to change it, so please contact us directly, we can, to facilitate you can contact us, so you can send an email to my colleague André, you can do it via the Openair app desk, but you can also do it directly to André, then in a simple process we can update that, okay, so this is what I want to share, this is also interesting from some cases that we have people here that are, for example, members of Openair acting as a national open access desk, they can support some group of interim managers at the national level, so sharing this kind of permission, so I think it's good if we can do it, and the same for some other use cases at the national level or institutional level, I think a normal case is that for big universities, so usually having only one account is critical, so we have different people, for example, from different faculties that may want to have access or need to have access, for example, for the enrichments to set up some notifications to receive enrichment metadata in order to to update their records, their content, so this is clearly a very good feature for that, for these cases, so faculty departments in universities, so I think this is quite interesting, and even for some services that are delivered at a national level, I think this is also great as a facility. Okay, so in the chat, no more questions, my colleague Andrea already, Briana, yeah Briana, Briana is an Openair national open access desk for Serbia, have 24 positions in the account. Yeah, Briana, sorry for that, sorry for how we now have this feature available, it will save a lot of time in the past for you, yes it's true, but now it's here and you can make use of it for other purposes, but not for your personal. Okay, okay, so not sure if there are questions in the document, if you want to put questions in the document, maybe things that you want to address in a different way so we can do it. Okay, so now the idea is that we discuss some topics about the, okay, about the, for the discussion, the idea is to just to share things that we are working on, and if you want to share your ideas, feedback, just do it, connect your audio, just give your feedback, so there are two things that we are working, there are several other things, but there are two things that we want your input that your input is critical. It's about the registration process and about the user stats, its information and to get your feedback. About, let's first start with the one that maybe it's easier and then my colleague Dimitri, if he wants to join, he's the product manager of the user statistics, he can join, so here what we want to highlight is that we have the users, let me check here, using the University of Minio account to make it more easy, what we have is that we are already, we are prepared, we are ready to deliver information compliant with the counter release five, okay, and we are preparing the information here to make it visible in the here in the user statistics service, okay. Currently, so we have this simple information and you can get the statistics reports, but based on the counter reports that we have available, but we are preparing things to the counter five. Dimitri, do you want to explain as what are the types of reports that we will have available if you wish to join? Yes, hello, I have just posted a link from the counter code of practice release five reports that will be offered in this new interface. The main reports, instead of this list, we will have four types of reports, new types, the one is which is called a platform report, which will provide the main information for repositories. We will offer the platform master, this is called platform master report, the other report is platform usage report, which is an aggregated report for repositories which is broken down by metric type as defined by counter and when we say metric type, the metric types are the number of views, the number of downloads, or the number of unique views and the number of unique downloads. So it's a kind of an aggregated report which is a new report offered by counter code of practice. We will offer the platform item report, which is similar to the report offered now for the counter release four, which is a report for its repository and you can select repository and the particular item that you will want to display the statistics. And finally, we are offering also the counter data sets report, which is a specific report for data sets. So these reports can be checked on the link that I have just posted and maybe I think by next month or maybe during November they will be available in this either phase two. Okay. Perfect. Maybe we can share as a novelty, even if we have it in beta, we can share it in beta to people already to test. So the main idea is to keep these reports also available as a functionality here, but to have as the main reports, these two reports that Dimitri mentioned. So we will keep this one, but we will have new. We are redesigning the page here to ensure that it's more easy to use, but based on these new reports, I think this is an important improvement. So if you didn't have enabled this service, you can use it. So I can in fact, let me check one thing. So it's quite easy for you to enable the service in the users here, you will receive information. Okay, this one is interesting. Okay, let me check first the other one. And then I can explain everything. So the process is quite simple. So you just receive instructions to enable the service, you can enable the service here, enable metrics here in the, if your repository, if your data source don't have access yet to this service. And if you want to test it or to make use of it, the process is explained here. So this page to enable the service is available for those that then don't have the service enabled yet. So you just need to enable the service, then you will receive and the information available for you will be similar to this one, to this case that I have here. Let me just open, okay. So providing the information about the ID and authentication code and some other information, if you, depending on the type of software platform that you have. And we are available to support you in this process. Okay, after that, enable, perform what you need to perform in your side, in your platform. You will have access to the service similar to what you are seeing now here for this specific repository from University of Mino. Okay, thank you Dimitris. If you have questions, just ask, feel free. The other, the other topic is about the registration process. Currently, we have the registration process quite well defined for these four types of, of data sources. Publication repositories, data repositories, journals and aggregators. Literature repositories and the data repositories, we use an alternative directory. So that the repositories, the list is provided by referee data, the, the, the first source of, of information and the process initiate only if the repository is registered in the referee data and the similar situation using open, open door for the literature repositories. What we want to, to ensure is that we are working on the, the registration process for Cree systems aligned with the directory from EuroCrees. But what we, if you have any remark, any idea about that, any strong opinion, just share it here. What we are working trying to define, it's the work that we are going to, to design during October. It's the, the catch all registration. So we, we are aware and this is the reality that are lots of, of hybrid repositories that are, they have all types of research outputs. In fact, several institutional repositories are becoming also hybrid, are becoming catch all. This initially, they are only for publications of, for literature, but now they are also available for researchers to deposit the research data or to resist the software. So this is becoming more, more, more tricky for us based on this simple process that we have established in the beginning. So we want to allow registration of catch all and then to play with the, the different directories that are part of OpenAir. So we will also integrate apart from, from OpenDoor and, and, and, and, and re three data. So we have the, the Drees from EuroCrees and also fair sharing. So this is, this is what we want to ensure because currently what we have is that because of this process of registration becomes our life more difficult to manage. And for some, we have two entries. We have an entry for the data source to collect publications and an entry, another entry for the same data source to, to, to collect the data. So what we want to ensure is that we have this catch all. If you have any strong, just for you to know, we are working on that for sure we will provide you more information in the coming meeting. But if you have any strong opinion, I see that already beat easier looking for, for the catch all. We have publications research that increase functionality in one repository. Okay. Do you want to share? Sorry for, I don't know the name of the repository. Maybe I should. But if you want to share your case, I think it's good because we, we, we like to have pilots. Just, just share your, your, okay. Okay. Thank you. Perfect. Great. Great. Let's, we will, we will, we will use your case as a pilot like, like others that we are in fact using. So, yeah, this space crease from Jordan. Yes, for sure. You can, you can register in the, in also in the, in the new registration process. This is a, this is a situation that we, the process itself for the registration, the workflow can be simple. What is critical then is all the, the way that to collect the proper, the proper specifications, interfaces in order for us to be able to aggregate your, your data and transform the metadata. Okay. Yes. So thank you for your availability. I have already two suggestions here for, for us to test. Thank you. Thank you. Oliver and, and, and, and beat if you want also to, to share your, I'm not sure if it's the same, I suppose not. Okay. This is what the, the two things that we are working on. If you want to say something about this, just feel free. If you have anything additional to what I said, just feel free or to share some, some of our adopts with the, with our community. So feel free to, to jump in and to, to share some of your thoughts. So these are the two things that we are working on. So the, this novel is in the reservation. So what we want to, to share with you because it was not started before in any of the community calls is about this catch all. So for Chris systems, we are working on, and we, in fact, we are already playing in better with this. I hope that we have soon as soon as possible novelties for those that are, that have Chris systems to implement it here for, but for the catch all, I think it's interesting. You can also, we can also discuss this designation of catch all hybrid repositories, whatever you think that it's better to call it. So we are the community. We can, we can find a better, better name for it. Okay. So just let me see here, just this, this slide to finish the meeting. So not sure if there is any, any, any comment in the, in the document and not yet, not yet. Okay. And I also want to share some thoughts. Let me see if I, if I cover everything. Yes. Yeah. May I say something? Yes. Yes. Okay. So during the open science fair, I attended almost all these demo sessions as for the open observatory, the statistics one, etc. And think that this is not only my case, that it will be good to have one community call explaining the repository managers how the data flow from their repositories to the open air and forward to the observatory or statistics or that kind of things. I think that the people do not understand quite well. Everyone knows these nice schema about what is included in an open air graph, etc. I'm not sure that everybody understand. And I admit that I do not clearly understand how the data are after that accumulated in all these reports, not, not just for the usage, but my point is an open science observatory. Maybe this is just a suggestion for some of other next meeting. Yes. Many thanks, Jan. I think it's a great suggestion. It's true. I think I this kind of for the observatory for sure is important this kind of of discussion around what we do with what we do with the information in that part of our infrastructure is quite important. And what we do with the information from the content providers visible in the observatory. I think it's a great suggestion. Let's dedicate one call also to that or to every thousand as a topic in an additional in an upcoming community call. I must say that during the open science fair, I had lots of ideas for topics of discussions during the open air, these community calls also related with the plan S from from from from open door from some work around also from that NIFUS, the European project NIFUS did also for policy, policy recommendations for repositories. So this is one one one more. So now that I know that the observatory is publicly available there are lots of work around also within YOSC for the development of this observatory. Maybe it's the right moment. Let's see. Can I promise to have it in in this year for sure? And then let's see if it's in November of or December. What do you think, Brianna? Do you agree with this approach? I cannot hear you. I am more than happy with this very active approach. No, no, because I admit that this is important. This is critical because you are right. The type of questions that we receive when people like us that are part of this community but providing content to open air usually have is that why the information in the observatory is in this way if I have it in this way in my repository or if you collect and what is the what is the this path from from this the provide the integration the availability and explore and what we can see in the observatory. So you are right. Everything around statistics numbers. This is critical. So we're right. And also clarify what are the limitations based on the content the type of content that we provide what are the limitations and to put it into work that information to make it feasible in the observatory. Yes, yes. Thank you very much. Thank you. Okay. So any other okay that we have one question here from Oliver about the validator for please be working already is trying some very ugly errors. Ah, the validator. Okay. Okay. Sorry. I was reading when I tested against Tor which I believe are not our fault. Okay. The validator is working well in terms of a test against the guidelines. So we can we can check with you the type of errors. The errors are always ugly when we find errors in the validator. So but we can check. I think it's from from tests that we made they are working well. Of course, we know that it's much more challenging the testing of Chris systems compared to publication repositories. So sometimes there are differences based on the on the interfaces that you shared. So feel free to to ask questions to share. So we can if you did a test recently, we can check it with you and then reply. So Andre, just just can we can we maybe maybe we can have access to this test or we ask if Oliver can share with us the URL that have received by email with the compatibility results we can check. You can see and check the errors. Okay. Okay. Open. Okay, Oliver. Thank you. Thank you very much. I will come back to you. Okay, perfect for me from from our side. It's all so this is what really that that type of of community call after the summer just for you to be aware of these progresses we made in the last months and some novelties things that we are working on to receive your feedback. So one suggestion for a community call and some novelties in the coming months regarding this registration process and also the statistics. Feel free to put more questions. I will just take the opportunity to invite you to the upcoming community call. So we have one schedule for the first Wednesday of November that will be on the 3rd of November. Okay, same time. And check if you I suppose that you are here because you are aware of the community calls but you also receive the newsletter. It is where we always send a reminder. So subscribe if you are not a subscriber or or disseminate this newsletter for other colleagues in your country that may have or in your in your institutions that may be want to receive this newsletter. So always a simple newsletter, three, four articles. But but I think it's relevant for us for our community. Okay. Okay. One more question here to from from from Julian about the any news about the new user interface thinking about new options to accept the client suggested requirements. Yes. No news. No news about that. So Julian is asking about so this parts of the enrichment in order for us when we receive notifications on when we have information here that we can interact with these suggestions to clean our our dashboard in order not to have always all the suggestions. We can we can we can so we don't have we are aware of the three four things that are critical that people think that they are important. One of them was that one. And in fact, the first one. But we don't have any progress yet in terms of the dashboard user interface. So for them to avoid this kind of thing when you receive notifications in order for us to call it because to in terms of user interface, we can say, okay, it's quite simple. We can we can change some things. And it's then we clean the dashboard. What is the the visible part for the end user. But we need to collect this in feedback from you. Okay, we need to collect that this is an error or this is something that it's not from your interest and collecting this feedback. We avoid to send you again the same information in the upcoming notification. So we discussed about this already. We didn't find the clear easy solutions. We find solutions and we have solutions but easy to implement based on the available time from our technical team to make it clear. So but thank you for making this issue visible once again, Julian, because this is important. I know that this is useful. Sharing your thoughts make this a topic for an upcoming provide management meeting. So we will talk about that again. And let's see if we can have more information in the next meeting to make it when we can do these things. So we want to have always some things new to improve the dashboard. And you see that there are some new things that we think that they are the critical ones for the time being, but we can always check the priorities and decide different things. Thank you, Julian, for your suggestion. Okay. I already invite you to the next community call to subscribe the newsletter. From my side is also Andrea already share some links here. So we will come back to you, Oliver, about this test compatibility test with the decrease guidelines and providing support if needed. And this comment from Julian and the suggestion from Breanna. I noted. So thank you very much for being part of this community, for being part of this meeting. I hope that it was useful. I talk a lot. So but thank you. Okay. See you in one month. If you have any questions, feel free to contact us. Okay. Bye-bye. Thanks, Pedro.