 So I, good morning, and welcome to this open air public webinar. This webinar will be about Zenodo the open digital repository but before we start, I just want to give you some housekeeping rules that you already know so this session is being recorded. We asked all the participants to have your microphones and cameras off while the speakers make their presentations. If you want to participate, you know you can use the chat to introduce yourself to interact with other participants or write questions and address questions to the, to the speakers, or at the end, we will have a Q&A session where you can raise your hand to speak or just write your question or comment in the chat. The presentation and the recording will be made available via email and via our channels we are going to upload the record in the open air YouTube channel and the presentation also in our website. If you want to share any comments in social media, please tag us and identify our accounts on Twitter on Facebook and on LinkedIn so share this activity and your comments about this session. So, as I said today, we have this public webinar about Zenodo the open digital repository, and we have our colleagues from CERN responsible for developing this tool, Chosebanito and Pablo Panero. So, now, without further ado, I just give the floor to Pablo and thank you so much for being here today to present this, to present Zenodo. Thank you. So, hello everybody. Just before we get started quickly, can you see my screen. Yes, yes. Okay, thank you very much. Thank you very much, Paula. So, my name is Pablo Panero. And today I'm going to talk to you about Zenodo. But before we dive into what Zenodo is and how it works. I want to take you through a very quick story, right. I'm a researcher and you're on your way to work. It's the morning. It's very early and you're slightly sleepy. So you lost your laptop. We forgot it there. And I want to bring your attention to the second paragraph which says crucial scientific data plus many years of work inside and all of that was lost. Another potential case which is that, you know, a colleague was working late at night and wanted a coffee but the machine short circuit and burned the laptop down. It might be slightly an extreme example but all the work, all the data was lost. Maybe less extreme, but who here has never lost a pen drive or just simply deleted data by mistake. The result of all these actions are quite catastrophic. So to say, there's studies that show that 50% of the links in papers are inaccessible after 10 years. So if you're, you know, doing your literature review and you want to cross check some references or get the data that was used to try a new technique, you cannot because you cannot access it. And if you go in line to that and take it one step further, for example, 80%, 89% of the 53 most important cancer research papers are irreproducible. There was an effort that took around 80 years and 2 million US dollar trying to reproduce this research to see we're basing ourselves on correct assumptions or not. So this is a waste of money and time we should be progressing we should not be repeating what was already done. So it is clear that we need to improve. We need to improve in how we disseminate an archive information and research to make it accessible so those links, you know, when you click you can access it to irreproducibility. Eight million eight years and two million US dollars should not be that amount should just be one click a person says okay I want to see if this is valid. I do one click, and I can check it. And also in reusability. We don't know what we do today. What's going to be used for in the future. As an example, she blocks from the 18th century that were used to navigate the disease to know what they were going nowadays are used for climate research. So we also need to enable that. So this could be summarizing what we need to improve in how we do science to do science we need to be able to explain how we got to a piece of knowledge to understand it, and then be able to repeat the process to the how we got there to verify. So then we can progress. So we don't redo what was already done. So now you might be wondering. How do we improve. How do we do that. Well, I'm here to talk to you about another right. But that's a very beautiful page but what actually is another. So in a nutshell, Senado is an open digital repository for the long tail of science where researchers can publish their research outputs artifacts like posters presentations, data software everything that's related to their research in three simple steps. The first one is to upload the data right then to describe it to give some information and finally publish it to make it available to the world. So let's go in a in a bit more detail on these on these three steps. So the first one is actually to upload the files. At least one, you need to upload a file, it doesn't matter the format we accept every format. And there's a limitation on 50 gigabytes per person or record per publication. Once you've uploaded your, your data, you need to give information about it. Senado has a very rich but flexible metadata schema based on data site. And there's a lot of information that you can give about your, your publication. And once you do that, you just need to click one button, the publish button. That's how you will make it available to the world. And you will get this, what we call landing page. There is a place where you get displayed all the information that you gave us, plus the data plus other things like views and loads about your publication. And that way you also get a DOI or digital object identifier, which can be used to site. For example, your data and your research and other researchers can also use it to site your, your, your records. But you may be wondering why do I, it's just a fancy blue box, but is not a do I, it's an identifier that will always resolve. It will always point to, let's say your data, your publications. So all those 50% of links that were not accessible after 10 years. Now they are. It doesn't matter how things change below with the URL changes or not the URL of the DOI will always resolve to that data so it will always be accessible. So you, when you go verify sources or to access data sets or other researchers will never be in this situation. But okay, the fact that data is not available because the link doesn't work is not the only problem. It also the data might change. Okay, so if you change the data with which you you made a certain publication that does not apply. So in that sense, after publishing a record in Zenodo, the, the data cannot be changed. You cannot modify the files, and you cannot update them. You can edit the metadata imagine you forgot to mention something in the description or there's a typo or you want to add something else, you can, but you cannot modify the files. Okay, I had a data set two years ago, I did a publication with it but now over the next two years, we will do more data in and it grew. I want to also publish that. Well, you don't need to do it separately, you can create a new version. Same that we do with software version one two and three you can do the same with data sets. Okay, and your publications. The, the old data set is still available. And it's still valid for the old publications and the new one will be available for the new publications, and they are related so people if they access the old data set they will get a banner on the top of the page saying okay there's a new one in case you're interested. All your versions and all your records you might be wondering how many people are actually interested in my work how many people are downloading my data or viewing my publications. So for that we have what metrics and statistics is like Instagram likes but for research. We use the counter code of practice for research data usage metrics or make data count, which is basically a standard on how to count views and downloads of these publications. You can do it in the same metric, and it can be compared. Imagine you publish your data set in Zenodo but you know you know the repositories to it will come the same, you can compare and also aggregate and see the full impact of your research. So you get all these by following three simple steps and publishing on on Zenodo. The next question is, Okay, I uploaded in Zenodo and I uploaded many things but my Institute or, you know, the people of my project, we want to have our own place our own group because we only are interested in in this part. Zenodo has a lot of information a lot of records and we want to search among only our content. So for that we have what we call communities, which is basically a way to create semantically meaningful groups, like for example, all the related data set research or the lucerne open repository that is there the NASA transform for a sense project. It's a way to group content. But okay, I talked a lot about features and so on. Let's see how it looks a bit in reality. And so for that, I'm going to show a few videos. If I put it in full screen does it still show or we need to share the other screen and someone quickly confirm. Okay. Okay, thank you very much. So on this first step, we're going to create a community. Okay, we're going to create one of these semantically meaningful groups. So first of all, you know, you go to Zenodo. I'm using what it's called Zambok does another door, which is exactly the same that Zenodo, but it's just for testing when you are not familiar with the platform and you want to play around. So first of all, I would sign up. Okay, I would need to create an account, you can do it by, you know, just giving your email, or if you already have a gift or key account, you can log in or sign up with that. In my case, I already have an account. So I go to the login page. And once I go in, I go to the communities tab on the top. And there I can search what are the communities that already exist. But in my case, I will want to create a new one. So I go to the bottom on the top right. I can create a form where I can put an identifier title, give a description about the community and what's saying, what is the purpose of it. Explain a bit the curation policy, what are the conditions for for a record to be to be accepted in this community. And finally, you can, for example, give a web page if you have an external one. In this case, I'm just putting open air for example, I didn't, but it's a good practice to do and then you fill the capture I was able to find all the buses in the image and finally you click on create. This will take you to a page where you can see, for example, the direct URLs to perform certain actions will be seen more in in the next videos. But you can see that on the right you have your communities and then you can search for example, they upload URL to send to other people so they can add content to your community. And now that we've created a community, we can also create a record. So we can basically upload content. It's not required to create a community but I'm doing a full example you can simply, you know, create the records and do not add them to a community. In the same way that before I log in, in this case I'm log in with GitHub so I so it's a different account from from before. I go to my uploads, I create a new one. And the first step is to choose the files. So I go might choose the file, I took the first slide of this presentation and I click on start upload so the files start going up. Then I fill in the data there's four pieces of information that require, which is the type that I put on top and then the publication date, the title one author and description. And also the do I if is not mandatory to reserve it beforehand, as I just did. If you don't once you publish one will be assigned automatically, but in case for example, you want to know what's going to be your do I because you are already writing the bibliography for your publication and you want to be able to cite it. You, you can already get the UI before publishing. And yeah, I'm feeling the rest of the form. Okay, I skipped the orchid but you can also add it and then there's plenty of information. You can choose a type of, of access. Okay, you can say it's open access or you can say that the files are embargo restricted or fully closed you can choose a license is a search box. So, by default is created commons attribution for but you can search for I don't know GPL a GPL and many other variations we harvest them from SPDX. Same with the grants, you can search for a specific grant and in the bottom you have many collapse fields that you can give plenty of information about your publications if it's a, if it's published in a journal with thesis or many other pieces of information. I go to the top, and I save. Okay. That means that it's a draft, it's the information that I already filled in is safe and I want to add it to a community. Disguise to the one that I created previously the opener webinar. So I search for opener. And I see the, the actual opener community so I search for opener webinar, and we can find the community that we created in the previous video. Click again in safe and publish. It will tell me that okay, there's a that afterwards I cannot change the files, I say I understand, and I publish the record, and I get what's called before the landing page, which I can preview a file. I can see my views and no load, nobody did it yet with zero. But this means that the record was published. It's in Zenodo, but it's not available yet in the community that we created before. For that, we need to go to the previous account. Right. So, for the person that owns the community. We go to our community, we click on actions, and we want to create this means that the person that owns the community has the right to say okay, your record is accepted, or your record is not accepted. Does it fulfill the criteria the creation policy or not. In this case, let's say, yes, I could, you know, access the record to verify it, but then I can also just click accept. We can go to the community. And we can view. And we can see that the record is there. So, this is basically the end of the of this part of the demo, and we learned how to create a community. In case we want a specific grouping of our content, how to upload content, and how to accept or reject content into our community. But it may be that you have many publications per day, let's say you are 50 or something it is, and you want to automate this process or you have certain tools that you want to integrate with Zenodo. Zenodo was filled with REST API first in mind that means that everything can be all the actions can be carried out by doing the HTTP requests. So you can integrate your systems with with Zenodo. And also, in case you want the opposite action not just publish but get content from Zenodo, you can harvest. I don't know, for example, a community using the OI-PMH protocol. And I've been talking a lot about publishing data, publishing data, publishing data, but in order to reproduce to enable progress as I said at the beginning in science. We also need the code. We also need the scripts. How was that data used. So for that, there's already a very well known and popular code repository, which is GitHub. And if you have your code there, every time you create a tag or a release, which is basically a snapshot of your code at a specific point in time. If you have the integration with Zenodo configured, then a publication will be directly done in Zenodo. So then you have your paper, your journal article that is published. And then you also have the data in Zenodo. You have also the code in Zenodo and everything can be site. And it's almost ready to reproduce. We have the data. We have the software, but someone has to run it. Sometimes it's easy to run things, but sometimes it works in computer, but it doesn't work in mind. If this were the case, there is another service at CERN, which is called Rihanna from reusable analysis. And you have a link to their documentation on the top right of their logo. And how this would work is that they enabled you to actually run the code. If you create what's called a workflow file, which is basically telling how the code should be run with data and so on. And you can find more on how to do that in their documentation. And you will get a banner like executed launching in Rihanna. And that means that with one click, it could be fully reproducible. This disintegration is still in the prototype phase, but it's working. For example, there you have someone clicked on that button and started executing the access mortality data processing. Those two million US dollar and eight years of work would have been summarized in one click. And with that, I conclude that that is Zenodo part and how to use it. And I hope by now I convince you on why you need to use repository. Basically to prevent research invalidation because in Zenodo, for example, data cannot be changed cannot be removed. It will be there when someone comes looking for it. And we need to improve site ability and find ability. It cannot be that when someone clicks on a URL from a research paper, it's not available anymore. In the repository also, you might think, okay, I can just put that in a server, I have a home or in Google Drive or something like that. But in that case, you are in charge. It might be that 20 years from now you don't remember that you put that there you run out of storage you're doing a cleanup you remove it. And there's nothing telling you, hey, don't remove this because it still might be need to be found for this paper, or a company. It's in control. And we already have cases like a mercury a little bit bucket or Google code, they were faced out. And basically, those links are very hard to find nowadays. And by now also I convinced you of using Zenodo but we need to know when to use another Zenodo is digital repository for the long tail of science. If, for example, in your domain of work, there's already a repository because there are many. It's highly probable that those integrate better with your tools. So, if that's the case, use them. If your institution provides a repository, maybe it's better to use them but there's many that do not have a home there's many research outputs that there's no place to put. And that's why Zenodo exists for is for the long tail of science. And you might be thinking that there is not many people, there's not many research like that but there is. Although in numbers there's around 3 million records at the moment, half of those 1.6 million are text publications. But I want to bring the attention to 220,000 software publications that accounts for approximately 80% 85% of the whole world software device, those are hosted at Zenodo. In India, we have 1.3 petabytes, which accounts for 10 million files. And we have up to today, there's still one month to go in the year 25 million visitors. And if you see the graph on the top right, we are growing very fast. We have around 300,000 active registered users from 7.7,500 research institutions. And from those institutions the users 50% are in Europe, but the long tail of science is not only in Europe we have users from 153 countries. It's very spread, it's very diverse for example the top institute in terms of users has 500 users so it's not just one institute using Zenodo. And then, if you belong to the long tail and you want to publish something you might be wondering why Zenodo. So far we have a very good track record over the last 10 years of experience in the field. We are open source, you can find all the code of Zenodo and the framework below in Invinio, in GitHub. So in that sense we practice what we preach. We do our best to adhere to best practices in research. So just from publishing Zenodo you get a lot of things to help disseminate to index your publications in many places, and so on. And there's a sustainability and archiving plan. And Zenodo is hosted in CERN's data center and is in our best interest to CERN to help improve how we do science. And as part of a large organization such as CERN there's many services and technologies that we already have available that we can make use of. And I hope now I convince you why to use Zenodo and you know when to use Zenodo, but it might be the case that you have certain restrictions. And you want your repository, for example, my institution, we need the data for our publications to be hosted in our service because of some law. And you're not alone. There's many of those that we call Zenodo clones. We wanted a repository with the functionality that Zenodo is providing, but they need to be, you know, hosted on their servers, for example. So they took the code from Zenodo, from GitHub, and they deployed it on their site. The only issue is that Zenodo is a service. It's not a product, so it might be that we implement new functionalities, the code evolves, and we unintentionally break something that was working for you because you did it differently. Or it might be that someone we don't know it's implementing a feature that we are also implementing that feature so we are duplicating efforts we're redoing the same thing. And from this, a project called Invinio RDM was born. It's a turnkey research data management solution, based on Invinio and Zenodo, and the idea behind it is that you get a repository with features like Zenodo, and you can just brand it you can change how it looks you can configure certain functionalities and you can get your own repository without the problem of it maybe breaking in the future. It's a community effort to maximize impacts and optimize the efforts and we're doing it with 25 partners all around the world. There's institutions, there's businesses, there's everything. It's a very welcoming community. And that's online, you know this core server. And when I say as I don't mean just certain people. This is a community project there's a lot of people there's people in every time zone, almost so there's always someone answering the questions. There's a link on the top right. And sometimes, you know, when the world conditions allow it, we also do live events it's always nice to meet in person and to collaborate there you can see us playing with stickers in a workshop. The whole project is again open source and their MIT license. And if you want to know how you can collaborate and what's the code of conduct and so on, you can also find it on the link on the bottom right. But coming back to the project. In the new RBM, it's the idea of having a repository that you can configure to your needs. It's a collaborative repository platform. And we want to empower users like GitHub does with the organizations they can manage the members in there, they can manage the pull requests to add code to the repositories and so on. And it was born with two guiding principles, scalability, because it needs to power very big repositories like Zenodo and user experience. We want our users to be the utmost happy when they're using our service. And how does it look today. So, there's already many instances of a mini RBM as you can see everyone looks different on the top left you have the default like you install it that's what you get. And then you have the one from Technical University of Grads the technical is University of Vienna. Prism from Northwestern University in the US. There's also the latest production ones, Caltech data from Caltech library. But it's true that none of these are Zenodo. That's what we call now the Zenodo RBM. We're not changing the name but Zenodo RBM is basically the project that we are announcing later today. And it's the umbrella of the migration from the current Zenodo on top of these new product calling the new RBM. And we are aiming for that to be in production in autumn 2023. We will have regular communication about it in the usual channels, Twitter blog posts and so on. But let's go to what's new. Why are we doing that migration. So, going on the steps of the publishing the first thing was to actually upload the data. You can see how to upload it change a bit. You can see on the top right, the quota then you select your files. And actually, you see that if that loaded immediately, there's no need to click on the start upload button. And on the left you can see imagine you have a list of 100 files you can say which one is the one that's going to preview in the landing page is not always the first. Going to the second step which was filling in the data. There's now auto completion for many of the fields there's a better search and suggesting filtering and again auto completing the values for example for languages. You can start typing in G and it will suggest you all the available languages. This is also true for languages, subjects, authors but for licenses, we improved how to choose a license you can click on that license and you can filter on the top right by data and software. And then you can also search for example for creative, and you will get the creative commons licenses there's also a description on it. We have improved authors. So, we have integrated with orchid. So that means that we got the dam from all the orchid database. And now when you want to add a creator of your publication, you can just search by the name for example I'm searching for my colleague Jose, and I click on all the data gets refilled. The orchid identifier, the affiliation and so on. And then you save. And that's it. It was easier you didn't need to pre-fill all the information on each creator. Then the same was done for affiliations. We in this case we got the raw dump. And now when in this case I refilled, I didn't search for a user, I put my name, and I want to say that I, you know, I'm affiliated with CERN, so I search and I can find all the affiliations that are in the raw dump. Might also be that the affiliation was not found so you can also add in this case I'm just typing another because I know it's not going to be found. So you can add your own. And then that's it about how to fill in the form. Once you publish, you can also get a link to share before is just the link or the do I but now imagine your data is closed, and you have peer reviews or you want to share it with your colleagues. You can get a link or embargo, for example, and you want to share with your colleagues, you can get a link and, you know, choose if they can edit the metadata if they can just view the files and so on, then you get a link and you can share that with them. There's no need, like in the past to do a request. And finally, the biggest change, which is in how we manage communities. We want to empower the users to self manage their community so now they can manage members and that's what we call inclusion requests that if you're familiar with each have you could understand it as a pull request, more or less. But let's look how that that that works. First of all, explain a bit the video so on the top left, there's two browsers and on the top left. There's me, let's say Pablo so this is simulating two people. And on the bottom right there's, there's Jose. Okay, and we're using as another RDM instance, also will create a community and reproducing more or less the same things that we saw in the previous in the new scenario, you can see the existing communities and you can create a new one. You just need to to keep the name and then the, the identifier. That's what's going to happen. What's going to be available in the URL. And afterwards you can see that you can give a lot of information about it at a website description and so on. And then there are other tabs that we're going to see later about requests and members and so on. But now imagine that me Pablo, I want to upload a record and I want to add it to that community that also created. So I go to my dashboard, where I can see my communities my request but in this case I'm interested in uploading content so I click on new upload, filling the form. I'm just uploading the file so I choose it and it uploads. Then I don't have a UI. So I want one. I fill in the resource type title. I add the creators. I will search in this case, for example, what was it. And I will add myself, not pre feeling but just, you know, inputting data that is not in the database. I do have an orchid but I didn't add it for this demo. And then after that, there's more information in the bottom but I need to be simple in this demo. I save the draft and I start looking for a community. The opener webinar is the first but just to showcase that you can search my search for webinar, and the community will appear I select it. I save the draft, and then I can preview preview doesn't mean publish preview means that you know this is how it's going to look once it's published this is why it's going to look. For example, you wanted to check if the HTML that you put in the description displays properly or if the review file is the correct one that you can preview and then submit for review. This is not publishing this is submit for review this change from the past. And you can see on the first thing that I did. It says that I'm giving view and edit permission to the curators to the people that own the community to actually edit my metadata my files. Then you can send a message. Okay. And you submit for review. You can see that he started an inclusion request, and there's a place where the, you can have a conversation and discuss things about the record in case they need to be changed because of curation policy or similar things. So now we go back to Jose Jose will go to the community and then to the requests and see that. Okay, Pablo wanted to add this record to the community could accept or decline as before but now can also go check it and have a conversation. You can also saw it and then things that something needs to be changed can edit by himself, but can also say, okay, I'm not going to edit, but I'm going to ask Pablo. Okay, I would like you to add a description on the files and change the title with this format for example. Once it commented. Imagine Pablo did it. And imagine it implemented the changes. And then once they can go and accept saying okay. Now it's correct. And accept the publication. Now we could see the record in the community we go to search tab. You can see there, the record. It's in the community already. But time passes the community became very popular, and there's a lot of requests, and there's a lot of records that need to be checked. And Jose cannot check all of them or imagine someone, the owner of the community is retiring you want to allow more people to to curate the community. So you can manage the members you can invite people to help you do that. In this case I'm going to invite Pablo because I know he uploaded good content. So I search for for the name or the email. Okay, and I can say in this case there's several roles but I'm going to say it's a curator. So Pablo can actually accept those records in the community. We send the invitation. It lasts for 30 days and you can change the role and so on but now we go back to Pablo, Pablo will go to the dashboard, the request tab, and we'll see okay I've been invited to this. You could also click on it and again have a conversation, but you can also accept. And that means that, for example, now Jose can go to the members tab of the community and see that okay. Jose is still the owner but there's also Pablo which is a curator. And that way you can manage who has permissions in your community, who can help you who can have multiple owners for example you can also remove users if needed from that community. And that way we are empowering the users to manage their own groups, let's say. On the demo of community management. Okay. So, this was a lot of information, a lot of new features. If you want to play with it. You can find it in Zenon.dashrvm.web.com.ch. This is a new site we put on is the foundations for this migration project that I mentioned. And it's the place where we will, you know, try new features you can also try them, and we will test with our partners like OpenAir, Dryad, and so on. But a heavy disclaimer, this site is under development that means that there's no guarantees what you publish today there can be removed a few hours later or a few days later. Hopefully not but it can also be down at times. So it's just, you know, playground site. We will keep you updated again on the progress in the blog post and Twitter and all the usual channels. So as I conclude the presentation, I hope I convinced you to publish your research artifacts to make it siteable. And I hope we can do it easily. Thank you very much. If you have questions, more than happy to answer. Thank you so much Pablo for for your presentation for for being for being so detailed. And this was very enlightening presentation about the possibilities of using Zenodo and the. And now with the, with the very new RDM also, we have we have some questions here, I will, I will go through them. I think Pablo just answered one. I will try to until the, the time we have to to address all the doubts that were posed here in the, in the shot. So, did there on says a quick question will I support the presentation so Bernard for Pablo already is Jose already answered Lorenzo Manela says is there a way to edit the curators contact within the community. So today only we only one contact can be set as curator and modifications look impossible. It would be nice to have multiple curators or at least included options to share curation feedbacks to additional email address. Thank you. I think in the presentation you already answered this. No. Yes, so this is one actually it is one of the features we get requested in Zenodo in the actual Zenodo right now you cannot do it it's only one owner one curator. But as I showed in the in the community management once we migrate to to Zenodo RDM these get gives you a lot of power over it you can choose multiple curators multiple owners so the answer is yes, once we migrate. It's, it will be possible. Yeah. Okay. So, another question from if it's a news flakos is there as another API API, something similar to AC valve. As another API, you can find information about it in the developers to send another dog. That's a documentation for that and I'm not sure I understood the last part. Similar to SCV. I don't know if if he genus is here and want to open the microphone and maybe to help us out understanding. If he Genesis is from Elsevier, like an API from from Elsevier. I'm not familiar with the with Elsevier API. He wants to add some words to this question. Yes, yes. Okay. I'm not familiar. So, but we, I just share the link to our API. So it's for his playing there. What we can offer, we can do API. Thank you very much. I'll check the Elsevier API later on. Thank you. And now Teresa Gomez Diaz says hello a question about licenses. I have tried to have other CC license then CC by, but it's not easy. Could you please show the CC licenses that are available in the deposit page. Yes. So, basically, in the I just shared a link. Okay. So basically all the licenses we have available are taken are harvested from spdx.org. And it's true that one of the things, for example, right now in Zenodo is not easy to understand that the license field is a search box. So when you click you only get for CC by for some other licenses. But you can also search by it and you will most likely find the one you're, you're, you're looking for with up. We have also improved that in Zenodo RDM you can filter and you can search in a better way. And the list is on the link that also sent. I think I pass one of the questions previously. Why don't Zenodo use handle identifier also. So, so John Prada is asking. Maybe I can take this one. If it's okay. So, so we, we did use do I right. I mean, in the other day we want to provide only one person to identify. And our choice was the eyes if somebody or there are some communities out there that require handles and they want to have it in their own repositories like with a new inviner at the end that is coming out. They can actually set up and configure whatever identify they want to, to use and if it is hundreds that's a possibility. Yeah, from our side, we only provide the eyes. Thank you. Thank you. There's another one from Bernard, who is asking, when you have several versions is the limit 50 gigabytes limit for each version or for all versions together for each fashion. Thank you. And then we have here Teresa Gomez Diaz, the license already if he's any of our the Costa. Is there a way to create the community and gather all the related to that community records that are already uploaded. So, at the moment, when you create a community, you will need to find a way to contact the the authors, the people that did those uploads so they request an inclusion to the community. So at the moment. Yes, this is just to complement what I will say correctly. So he's right. And at the same time is something that we foresee to have in the future in. We don't know if it is going to come directly with the first version of Senado Rdm the say, but we, we, this is something that's been requested several times and we, we know it's important. So we will try to put in place a mechanism to, you know, to try to get these records into your community and some, some way of communicating with the uploader to make it possible. Thank you. Someone wants to address the question I hear a microphone on. Sorry, I'm on with the microphone now. Okay, thank you. We have three questions here from Juan Pereira. For the purpose of digital preservation, how is the file format identified and validated in the model is droid pronoun or GHO VA used for example. Pablo, do you want me to get this one. Yeah, that's okay. So for the time being, to be honest, our main goal is to enable a way to all users out there to, to share data in and to give the right to this data in a very simple way. So we don't do any post processing after that. So we don't control whether, you know, the type of the file is preserved for the long term. It's something that we're exploring. We have a parallel project to Senado here at CERN, looking at how to improve the long term preservation aspect of, of the content we are carving. But for the time being we just simply get the files, we store it, we keep it in our storage systems replicated and some, but we don't, we don't look at the other type of the file or do anything about it. So it's a natural Pablo. Totally correct. Okay. And Joanne asks also our statistics saved for future memory. Do you mean that in the migration, like if we will migrate the records and the statistics will, will be preserved once we migrate. So Joanne, that was your question. Or if you prefer you can open your microphone. If it goes more in the preservation side of, of it is basically what was answered before. Hi Paula. Joanne. Yes. My doubt is, if we might, if in the process of migration of Senado to a new version of Senado, if you lost the, if I lost the statistics in this space, this is a problem for example. No, the statistics will also be migrated. Okay, thank you. In that aspect we're trying to do it as transparent as possible so let's say at some point we're migrating to Senado at the end but except for new features and things like this data should will not be lost. Okay, thank you. Okay, because as long as another question is when the platform is updated does the auto still have access to statistics form from the past. Sorry, I didn't. When this platform is updated does the still have access to statistics from the past. Yes. Things are migrated as they were. Okay, okay. Another one from Bernard is integration with GitHub only or we can use alternatives like GitLab. So, I know at some point there were some works to do a GitLab integration but the current integration is with GitHub. Basically, there's also work on the GitHub side that they have to enable the repositories and so on and integration is with GitHub. So, okay. Thank you. I hope Bernard this answers your question. And then Sylvie Lebrass asked when you were presenting in venue RDM, could you tell us more about metadata, the flexibility about metadata? Yes. So, the schema of venue RDM and therefore Zenodo RDM is still based on data site. We keep evolving also with the new versions of data site. And in terms of the flexibility that that means that basically, there's very little data that is required. And then we put a lot of information on it. And again, the schema is actually the one from data site. I'm going to try to put in the chat the documentation page that explains every single field in detail and what are the options and so on. And also one more thing is that in this Zenodo RDM, we are introducing a new feature which is custom fields. And it's just that we can. So the installations of, in the end will come with the capacity to expand this data model to, yeah, with, as the name says with custom metadata. And then there will be integrations with, for instance with a specific vocabulary for specific communities like mesh vocabulary for health sciences. Another one, Christine Huffner says, if, for example, a publication later proves having false data of being pleasure. Can it be removed? Is there a kind of an ethics commission that could decide these kind of actions? So we have, sorry, Paula, on this one. So we have a very clear sense of use as you can find in the footer of Zenodo in which we explain, you know, all the actions and everything that we do and how you can use Zenodo. So if there is a copyright infringement, and this is one of the reasons for which we will take down a record. So there are just a few reasons for that and then we will do it. Yeah, so it happens sometimes. Unfortunately. Thank you. Thank you. I think we only have two more. One is for Gordon Melsey. Will the Zenodo API change after realization to Zenodo RDM? Yes, but no. So there is a new API that improves some some workflows, but there will be backwards compatibility. So that means that if you have an integration, it will still be working. There is a new API that improves some workflows, as I said, but it will all still work. Alicia asks, are there plans to expand Zenodo into a bigger research platform like Google Scholar, for example, by harvesting metadata from the other non-Zenodo repositories? I think those are two different questions. Yeah, objectives or goals on the platforms, but maybe I'll say if you want to. No, you're totally right. We don't plan at all. It's not at all in our goals to go into the aggregators role, which aggregators, that's what they do, right? So they can harvest content from many different sources and then unify the search. So the difference between aggregators and repositories, like Zenodo repositories, get content. They can harvest the content from their sources, but maybe here is just, you know, doing a bit of PR for OpenAir as well. There is OpenAir Explorer that is doing that for research in general, but they're harvesting many different repositories, not only Zenodo across the Europe and I think even across the world, right? And they unify this and create a big research graph with content from everywhere. So now we are not going into this direction. Yes, yes. And you all can explore a little bit of discovery portal from OpenAir in explore.openair.u. Yes, André already put the link there. Thank you, André. I think we have one more. It's the last one from Ilra, as in, I'm sorry if I don't pronounce the right name. Could you please elaborate more on the integration of Rihanna? So the integration with Rihanna is still in a prototype phase, right? And so I cannot give too much, yeah, thanks Jose for sending the link to Rihanna. But basically the idea is that if you comply with the format of files and the definitions of the workflows that Rihanna accepts. And then for example, when creating the Zenodo record, there is a workflow.jammel file explaining the steps that need to be run for the analysis to be run in Rihanna. You will get the batch on your record to launch on Rihanna. That also means that, you know, it needs to all be functioning in Rihanna. Okay, I hope it helped to clarify a little bit more. So I think we reached the end. I'm just sharing an evaluation form that I would like all the participants to give us feedback about this webinar. And I would like to thank again to Pablo and to Jose for this amazing webinar that you give here. We had a huge audience. And I think you made a huge effort to explain everything in a detailed way and even now at the end to giving answers to all, at least we try to clarify all the participants here. To all the participants, thank you for being with us. And Jose and Pablo, thank you so much. And please follow our activity, open airs activity in the website and social media. So we will meet soon here online. So thank you so much and have a nice day. I will leave the session open for at least for a few minutes for you to copy past some links that you would like to have. So thanks again and have a nice day. Thank you. Thank you. Thank you.