 So welcome to this community call dedicated to the open air content providers. So just before we start some information about how we will organize ourselves and how can you participate so the idea of these community calls is that we have like half of the community call off of one hour so 30 minutes we will dedicate to a specific topic. I will do a specific topic that we think are relevant for the, the time. So now we will dedicate our 30 minutes to guidelines version four, and then 30 minutes 25 minutes to questions to comments, apart to the presentations that we gave some clarification and then, of course, open to other issues that you also want to integrate. So we don't want to make it an Arctic so I will be, I will invite you just to mute your microphone so for this first community call we are just testing out with everything will work so we will give you the possibility to turn on and turn off the microphones we will be able to mute everyone, and then mute so this is why I'm asking you to mute in order to not make noise for the, for the, the others that were presenting. So but this is open so you can also put a question or a comment in the right moment. So audio or you write it in the shot. Okay, this is we really want this to be participative so the main objectives of the community call is to give you to provide more created information, more detailed information in some improvements some of the services some of the, the, the developments that we are doing in open air infrastructure in the different services or in the related topics or interoperability guidelines, control vocabularies or other, other topics that are relevant for, for the open air infrastructure, let's say ecosystem that we don't, we also depend on others. So provide some information but also have your feedback for our service but not, but not only to share some relevant developments in your, in your systems in your, in your repositories or other kind of research systems that are relevant for the community. Okay, so it's really a participative call that we want here. So that's a lecture 30 minutes for a topic 30 minutes for open to all of you to talk. So this is why I, so I invite you, you to, to note your questions and comments about this first presentation and then you can make your questions at the end it's better. So this is the way we will work. So in the coming minutes, I will share in the chat document for a link for the notes of the meeting where we will put, we will share the main comments that you are doing and the link for the presentation so I will share that in the coming minutes. But this first call this first in this first call I would like to use this first two or three minutes to, to provide you some informations about recent developments so this we will use also this first part of the, of the presentation to, to share those the novelties let's say. So I want to highlight three, three informations I will share all the links here. So, the first one is I think a relevant achievement that we made so we have now a public roadmap for the provide service, provide service with the, the main service for the content providers services and functionalities available so we have decided to create a public roadmap in order for you to be aware of what we are doing currently to improve the service and what we plan to do. And in some things that we also considering so maybe I can also share my screen. No, it's not working. Okay. We have this provide roadmap where you can see what is in progress what is planned, what is under consideration you can also provide and make some questions suggestions here. Some of the suggestions for example that we have here under consideration came from the workshop that we that we have organized recently for example in Kawar in open repositories or recently also in Spain by the end of September. And some of the suggestions from the repository managers are, or other content provider managers are here so you will be aware so the link is public I will also highlight it here, or my colleague and we will also do it so we will share this link here in the chat for you to know and we put it in the notes. This is the first information that I want to provide you. Then the second one is about some some some small improvements that we did in the provide the dashboard. So things like so we want of course to to to work on a relevant relevant and a big update in terms of user interface. I hope that we can have that in the coming in the coming year but for now we are doing slightly changes. Also, taking into consideration some of the suggestions from the users. So one of one of one that I will just highlight to one is this my data sources at the glance. So, we have created this box here in the right side of the of the screen, where we have some of the main members that say often of your repositories, we want to make it visible. And this is what we have in in in in the roadmap to change this interface but at least you already can see in the first page, your numbers, the other small in yes but but but I think it's important this is why I'm sharing this is also about the it's it's related to the collection monitor so the collection monitoring provide is where you can see how open air is aggregating your content your the content from your repository or from your service and when we did that aggregation where when we did the transformation and we have had it here as you can see now in the screen. The light, which version of your content is indexed and publicly available in our explore service so let's say for this specific repository the repository from University of New, the version that is available is this one and it's highlighted here in blue, which version do we have we are going to continue is aggregating the content but you can be aware specifically in the collection monitor, which, which content version is available in the in our index. Okay, this is what I would like to highlight from the provide service and also a last comment that maybe Andreas will also talk about so we have already the rules of the version. So you can use it on the version for of the guidelines integrated in the validator. So you can test using the the validator tool in provide your way IP image interface against the guidelines version for go rules. So we are in a testing period, let's say, but but it's in production so you can use it if you find any, any, any bug, any issue that you think it's not working well just send us your feedback but it's already available so you can also test. So we have, if you are experimenting, experimenting any issue with them, accessing the service login issue, assessing the provide service this is also the right moment. So my colleague and Ray will share the email, and you can contact him directly or send a message here in the chat, because then we will try to find what is the problem. Sometimes we have managers of repositories that cannot access because of the account is related to other email that from someone that already leave the institution or a mail that doesn't exist anymore so try to solve these issues. So, this first call is dedicated to the open air guidelines version for as we are in an important moment of a take of these guidelines from by the community. And we will share the, the specifications. So my colleague from University of Bielefeld, Andreas will present the main specifications and what is new in this version for the guidelines. And then we will have use cases, you can also share your in the second part of this meeting. We will have some repositories in Spain that are already implementing this guidelines and exposing the content based on this guidelines so Emilio from Spain will share what they have done for those repositories. And my colleague Jose will present what we are developing in Portugal, and they're the network of Portuguese repositories. So we will have a use case from specific repository and from also an aggregator national aggregator, and then also the Latin network of repositories la referencia will also share what they have in their plans they it's not use case of implementation but in fact, is that just to showcase that we are that the guidelines are being used it also in other parts of the world, and what are, what they have in their plans. So now, I will give the floor to Andreas. So, just to move with the presentation. So, Andreas, I will make you presenter and you can do your presentation so we will start with Andreas from Bielefeld presenting the specifications and then we will have the use cases. If you want to put questions during the presentation you can do it in the chat. Okay, at the end, we open the floor to you also to make questions out of you. Yes, the floor is yours. Thank you. Thank you, Peter. Thank you. And hello everyone from my side also. So I will present the guidelines literature guidelines version for it's coming out in the last year. I have a feeling that I have a little bit, a little bit more slides. But I think I skipped some slides during the presentation. Okay, guidelines and recommendations. The agenda is short of you and very briefly repeat about the aggregation and the teacher guidelines version for as you know, is integration scenarios in open air. We directly have us from repositories or from journalists or we are harvesting indirectly from aggregators or publishers. You can climb articles and we set references via personal identifiers. So there are a lot of types of repositories and these repositories have many types of research outputs. We have the for a big four publications data sets software and other research products. And we are wasting these from institutional repositories thematic repositories also journalists publishers from data repositories. And you see here and short overview about about the connection that institutional repositories. Oh, by the way, you see my mouse. Yes, yes, yes. Institutional repositories provide information about publications article preprints also about data sets also about software and so on. And these types will aggregate. Yes, we have different guidelines. First of all is the literature guidelines or now as institutional and thematic guidelines for repository managers. For Chris platforms current research information systems for data archives for software repositories and other research products. If you like where you can take a look on guidelines at open air but you are for more information here. This was a for review guidelines in general is our very good tools for repository managers to define and implement their local data management policies and so on. And these guidelines give you the requirements for some of my says strategy for European Commission or for for other national funders in open air. We can harvesting from the bin and begin of this year, the access content and also the non open access content. And this is a switch in the content acquisition policy of our mayor in the last year. The guidelines have also autos to met some requirements for open access from the Commission and give you a more diesel better quality on the metadata on these sites. What's new in the literature guidelines version four. It's based on doubling core and data site. It's has separate metadata format prefix, why e underscore or mayor. There's no sets that must provide. And it's fully compatible with the new content acquisition policy. The next is the use the consequent use of contract work couple race from the configuration of open access repositories there are access rights resource types versioning and so on. And we support from the new literature guideline version for various of different identifier types. Do I handle orchards is me for different types of things of articles of authors of organizations, and there are a lot of personal identifiers around and the new guideline support these pits. Also, new is you can create hierarchical level by a container. This is part of an article can is a part of it can be a part of a journal or chapter is a part of a book and a book is a part of a series. And also a poster can be a part of a conference so you can create hierarchical level on these objects on guidelines of mayor. You can see the application profile here so short screenshot. For this one. The guidelines are also published in. You can read this document there. So what are the metadata goals for these new guidelines. There are. Metadata to for more discoverable or citable that ability so. You have. And better quality on these meter data where we use the core vocabulary for accessibility accessibility and reuse. We take the articles in conflict and consensual. A relationship with other pro other objects research projects research artifacts and so on. And of course it's better for interoperability and reporting for these. First I give some small. Examples here. We have seen property is the field creator level is mandatory and what is the new element of this is data site contributor or title mandatory and data site title. Now. So, for resource type. Specific way or air. Resource type. Was a separate resource attribute. And these. Journal type is literature. The core vocabulary type is referenced and the name of journal article. So. A lot of. What. In the application profile to for discovery and such ability. So why a citation title is one that the title title name of this container. Is in which this work is published. Also for volumes. For research accessibility and reuse. We have access rights that are also it's data site rights and license conditions. Here are license condition. This attributes at the start date dates and. The UI of creative creative comments. For reporting. We have funder references and embargo periods here. Short example for interoperability. We have alternated identifiers in the example. It's not that if identify the URL and you give some. So for mining and downloading. Full tax if the full text is available. Is there are file with access rights. Mind type. Object type as attributes and the link of the full text. The implementation as Peter said is the validator. For the rule set of guidance version four is released. It's can be used in production and environment and also in the better environment. Data source registration updating is on capability level we integrate F the new compatibility level of for the version for integrated. The aggregation. Of these new. These repositories that support. The version for the literature guidelines are in preparation. And also in preparation is the visibility of these new data. As I mentioned before. In the dashboards. Explore or provide and so on. Here, some guideline references for the teacher guidelines version four. You can contribute to these. One. In different ways. I like to highlight the. In between of guidelines and repository platforms. This is an open table to for common commenting. These table has the repository platform the versions and which version of the guideline. Would support. Software platform and versions. So, we will share the links as Peter said in beginning the introduction. And for contribution and feedback. We have dedicated Google Doc document. And that you can show what is also. Questions, but also you need. No account to commenting. Leave commenting about the new guidelines and attributes and so on. For the other GitHub and annotate the unit. Accounts you can send emails. And so on you can. Also you can contact the new hearts. So that's from my side. A short overview. A short and quick overview about the guidelines version four and the next. I hope. My colleagues will do presentation about the implementation of these new application profile and attributes. Thank you. Thank you. And thank you also Milan that have already provided here. Relevant input here about them. Some dead links that we have. That we should fix this. Okay. Thank you. Can you can also share more. After can I can I can ask. Okay. And the namespaces for. A namespace open air do you see my or. Must not resolve. So we can declare this namespace and these namespace. Must not have nine point. This is an XML. You can I can give you the links to the. Three C and we can share this information, but these endpoints must not be. So please share in the shot. Okay. And we will proceed with those use cases that I think it's quite. Relevant for us here to. To be aware then what is being done to implement for sure. These three cases, but for sure from you, we also have others that can. Let me check. I'm trying to. Make Joseph presenter. It's not easy make presenter. Finally, okay. And then now we will proceed with the case from Portugal. From our network of repositories in Portugal and Jose will present it. So, Jose, the floor is yours. Yes, and you will see my screen. Okay. Yes. So I will present part of the implementation of the opening guidelines in rock up project. Very quickly, what is work up project. It's a national initiative in Portugal. So it's a project that focus on a network of scientific resources like repositories journals, other portals and research data repositories. We also integrate recently la referencia contents into our national portal, for example, and to integrate all these repositories and journals from the Portuguese outputs. We have from the beginning. So a little bit more than 10 years now a content policy based initially on the driver guidelines and later on the open air guidelines. And we plan to continue with this last guidelines also as a content policy at the portal level. So we have also an additional particularity is that part of this repositories and also journals but the focus here is the repositories. We have hosting service for this place. And we have 28 repositories right now. So, 28 repositories that we manage directly. This, this is also part of a set of services that has a common vision where we try to put the researcher at the middle of the context and then interact with other systems. So this is also the way we would plan to implement these guidelines and the way we want to share all this information, not only at repository level, but also through other services in which we interpret in this case. So our actual context at the national level is that we have right now at how hosting service 28 repositories with the space five version. So, our first thought is to define that we need to manage the information we have right now. Another aspect we are trying to promote is to include as many more identifiers we can into the repositories right now, to be able to expose that information in the open air for format. By now we don't have yet all the information we need to be totally compliant, but at least we can have a great level of compliance, even without many changes on the repository so I will present the change we have done. And what we are also working right now is to focus on the future, and mainly on the use of the space seven, where we want to provide this compliance by default on the new this space version. So, this is the actual context we are working on the actual repositories we have and also work for a feature updates that will focus on that. So many implementations we have done on this repository is first on the way we will put the information into the repository. So, the biggest one is the way we can now incorporate authors as an entity of the repository so we can put a person with an identifier and a description of that. And also, we change a little bit some other fields and also other options that we have, based on this recent guidelines. Another aspect is to expose all this information in the new metadata profile. So basically, what we have done is, is a mapping of the existing fields we have on the repositories to the new metadata schema. With some fields, we managed to introduce additional information. And we also developed a mapping an automatic mapping of the project prefix to an entity. So, usually we use the new for rebel name, I will show you just after that. So, the functionality to have the new user as an entity is when you are on the this space form, you can put a name and search for an identifier regarding that person. So, we have two main data source in our repositories. One is orchid. And another one is the idea or see a VTI which is a national identifier associated with a curriculum system. So, we search for that name on these two systems, and we have the possibility to choose from the results list and then add this to the list of the authors on the repository. When we do this, we can also include additional information that is not visible there. But for example, if you have a sculpture ID, a researcher ID, or any other identifier in orchids, or in your curriculum. We include this at this level. So, this has been one of the main developments to allow the use of the author identifier. Another aspect is that we continue to manage the funding information on the repositories based on the prefix from open air that came from the open API. So, we have to manage an automatic way to disaggregate this information to create automatically an entity. Let's hear some examples of repository in production. And I will give you here some examples. So for example, when on your repository you have here, a person that is identifier with this little icon. And this is that this is an entity. And this entity on the user interface is show this way. But when we go to the way the image interface. So, we have the different forms of the name, and also the different identifiers that are available for that particular person. So, adding the prefix and the information from funding, what we do automatically is based on that initial prefix that we still maintain by now. And probably will change in the future but by now it's the information we already have. And we do expose that based on the different prefix we have so he see will be always European Commission and European Commission always had this specific crossref from their ID. So, these two information we put by default. And the funding stream you already know, and then we have here the project ID, which means the word, a word number, and we expose all that information to that by now automatically in the future. What we plan to have is functionality to search for a particular project and have something similar to this so instead of searching for a person we search for a project. Other aspects based on the existing information we have is for example we some some fields we get them automatically in this space for example. And then we have all the information based on the guidelines like the version the where else all the file, the different license and the dates of the license, the new rights access the new types also by now. So, this is what we have already done. Also, we made in some cases, a mapping of existing information for the new information and, for example, this table show us that we have fewer versions on the driver version vocabulary to the new one so it means that this new vocabulary is richer than we had before. And this is an example of the versions but it's the same for the document types, for example. Additionally, from the repository will also continue to manage this information later. So, by now, for example, if repositories not yet compliant with the guidelines, we already manage all the information at the portal level based on the guidelines so it means that every document types we map to the new guidelines, the versions also the right access also so the information that we expose at the portal level. It's already based on open air for guidelines and all this information we show it in two ways for the end user interface and then also through an API for integration with others. So, the idea this page is not yet in production but what we will have in the future is to put some identifiers regarding the authors on the search portal, or the license and the different types of information we already have. Another aspect that it's very important in this process is that we use the Arvester software, which is the Lareferencia Arvester to transform the information from the basic open air guidelines to this new one. So, we transform some fields, we make some validations to be able to show that information at the end based on these reports at the search portal level. So, we do this for all the resources integrated in the portal and not only for those we manage. Also, at the portal level, we use all these values, and you have here some examples like the core types to be able to show some statistics about the repository for example in this case. And we have a page that is based on that information, which is all this information we have show based on open air for guidelines. Additionally, we also work on a working group from this space to be able to implement the open air for guidelines directly into the new space, where we we try to incorporate the concept of entities into the space repository, and also have everything that is needed to be open for compliance when the space seven is released. So, this is the link where you can see all the meetings, all the actions we do, etc. And why we are trying to push this new guidelines for the repositories for the publisher, the aggregators, and also the repository levels. And it's because we need to be interoperable with all these systems and we need to manage the information the same way. So this is why we try to define like a semantic level that will be the same for all the systems, or at least will be more accurate than the information we had before. So, thank you. If you have any questions you can contact us regarding this. Thank you, Jose. So, if you have questions just type it in the chat. Let's hear now. Emilio, that will share some recent developments also in the several repositories in fact in Spain. Okay, perfect. Okay, you are already sharing the screen. Thank you, Emilio. I cannot hear you. Can you check yourself? Okay, perfect. Do you hear me? Yes. Okay. Okay, thank you Pedro. Good afternoon to everyone. I'm just putting this more informal, but each of us can. Okay, I'm Emilio Lorenzo from Abra Consultores. We work on the space repositories on the Spanish and Latin American market and we have made some options to open air for on several space installations. We are going to present some of the problems and suggestions that we can make to you about the open air for guidelines. How can some, the space 5 and 6 version can be adapted without many, so many problems, right? Okay, I come to yes. The presentation is adapted from a post that we present some five or six months ago on the Open Repositories conference on Hamburg and we can see the material on this URL and basically that in that moment we have, we only made one adaptation of institutional repository of Wilba University, that is the space version 6 and after that we have made some other four or five implementation on the space 5 repositories mainly in Spain, right? Well, some of the things that you have to take into account when you try to adapt an existing the space repository existing in because well, we have we have heard some moments ago about the space 7 but many of you are going to to co-exist with the space version 4, 5 or 6 on the next year, so probably you have to make some major adaptation efforts to comply with the new guideline. Well, the first thing is that one of the objectives of I think the space version sorry, Open A version 4 is to increase the association of authors to their personal identifier. This is a thing that many funder agencies and many other agents as Open A are looking and well, if this we forget about the driver guidelines about names and we have to improve the precision of the identification of authors. So many of you have probably are thinking or have already implemented the Orchid idea and the repositories for their own authors so you probably have to see on exposing that information on the OIP image interface. Depending on the version you are using and depending on the design or decision that you have taken in the past this information will be located in entities as the Portuguese example or in authority models or in other solution but you have to see on exposing that information as precise as possible. You have also to make some big efforts to improve the funder information that is available in your repositories. Now many of you are compliant with Open A version 3 probably you have the all the info European agreement syntax. Open A version 4 is much more extensive demands many more information in fact you have to plan for funder information entities to make a whole set of information about who is funding your paper your items so you have to make some big adaptation to fulfill this requisite and then you have to plan for new description and vocabularies you have on your repository the old typologies you have the version typologies and also the access right typologies you probably have to you have to be compatible with the new core vocabularies you have to transfer or to include or to add these typologies this vocabularies and also of course you have to to adapt the new schema it's an application profile it's called the name space and then you have to modify your interface for be compatible with these new guidelines well talking a little bit more into details well how do you plan or adapt your repository for for outside information mainly also Joao has talked about if she's exposing not only the architecture but also research and Portuguese CFAN identification well the normal solution or the basic solution is to expose the architect depending on where do you store your that information you have to take some technical solution depending on that information you have to expose that information in a data side contributor element with many attributes you can even expose the affiliation of your author etc on this space the normal way or the standard way of storing this information at least on more or less completing implementation is a new solar cord it's called Autonic Cache Solar well we have used that source as a generator of this identification but probably there are another design option to fulfill this as I told you before you have to plan for much more precise funding information instead of the grant agreement info or rapid semantic grant agreement information well there are now a lot of information about the award number, the funder information the ISNI or the DOI information of the funder just to be more precise on that information this is one of the aspects that we forget to take into account in the University of Wellow implementation we thought that some normal transformation will be enough but we have to take this information from open air service on the API or other possibility that Pedro has talked before yes you have to expose a different set of vocabulary the problem we found here is that if you want to keep the compatibility between open air 3 and open air version 3 and version 4 you have to expose a complete different set of typology and other aspects so there is a range of solutions from a double meaning to transformation to lose even compatibility we take the solution of only transform on the OI crosswall the driver vocabularies in the core vocabularies so we have some lose of precision on driver typology there is article journal but the equivalent of the corresponding terminologies on the core vocabularies is much more precise journal article a lot of variation from this vocabulary you have to think about it at the end you have to create a new point of harvesting we define a new context for this open air for compatibility and of course you have to define a new metadata scheme that is OI slash open air you can follow this link to have a look to how this records appears of course in another context of the OI interface still exists the compatibility with open air 3 and even the previous version thanks for your attention we will answer your question on the next minute perfect thanks for your details I think it's quite useful because these are the type of issues that others also have so Luntaro let's close this round of presentations with your presentation from the Latin America Referential Network thank you all I will not present exactly a use case but the actions that we are taking regarding Gailan version 4 I will talk about what we have done in Gailan 3 we had some infographic and provided that information to the notes as you may know we have a national note structure we do dissemination to the national notes and then the national notes do the same thing repeat the same actions to the repositories we have provided webinars for national notes and the La Referencia Technical Council represents that also webinars directly to the repositories in some countries that actions were about version 3 but we are moving now to in the past months to the version 4 our team is active and expert group and reviewers of the version 4 and we also we are finishing a review and a translation to Spanish of the guidelines and we will disseminate that document soon in the same format that Opener is doing we have and so we are planning and executing webinars for the national notes we started some months ago and we will continue that actions during the next year of telling to the notes about and the repositories about the core vocabularies and all the elements which is that involves the evolution to the guidelines version 4 in the other hand we are doing some actions in La Referencia software the national notes are using our platform and we use it also in our regional aggregator we are building a new version with the concept of entity and relation models sorry sorry sorry nothing, nothing, sorry so we are doing this with the software to push for the implementation of the next version we think that we can use the new version of the software to accelerate the adoption of the new guidelines by providing some services to the repositories to migrate the legacy metadata from version 3 to version 4 we will do a proof of concept of this idea in the next month and hopefully I can present some results in a call if you like so we will provide the version 4 Spanish translation in December I think that final revision is now so we will provide and publish the results, the document in December and we are also adapting our recommendation to the La Referencia notes including all the news on the adoption of the version 4 guidelines and we will continue the dissemination to the national levels and webinars to the repository during the next year so I think that's all the work in guidelines the person in charge is Paola Sulević she's connected she's our person in guidelines and she is the one that participates in the groups and also I think that we can ask questions if you like so thank you very much great, thank you thank you also Paola because I know that is a presentation from both so I hope it was useful for you to have these specifications of the guidelines in these use cases or to be aware also that we are behind Europe and we are close working with at least 10 countries from Latin America