 Um, nice to see some of you again, um, let's see. So today this is the one, yeah, one communico before the last before we go we head into the to our summer break. Uh, and we have a new release out for, uh, our Argos instance and our OpenDMP software, which is the software that Argos is based on, uh, supporting different instances, uh, in different organizations and countries. So the new instance you can find here of course, I mean, the new release, sorry, uh, in our GT repo. Let me share with you the link, um, here. And we are still fixing, uh, some, some things, uh, that we observed, uh, that were, um, that came after the release. Uh, but, uh, I wanted to nevertheless share with you a few of those developments. So that's why this communico is about, um, is about semantics to show you what is, uh, what we did, how we expanded, uh, the mechanism, the semantics mechanism we have to support more, uh, links in relationships with other outputs. Uh, then what we have, um, done with your profile, um, because now you can link and also unlink your, uh, accounts and show you a bit of, um, uh, like, show you around the new, uh, let's say, relation nodes that we have, uh, launched. And I will start, I think, with the semantics. Please feel free to, um, you know, jump in and ask questions or, in any case, uh, contribute to this, not just a presentation, it's a discussion. This is what this forum is about. Um, let me set my screen, find the correct tab. That's the one. Yes. Okay. Hide panel. Right. So we have a new, uh, so, so far we supported the RDA, DMP Common Standards, uh, properties. And we had a semantics mechanism that, um, allows for this mapping between questions and properties and entities of this standard to be, um, completed. But now, but we wanted to, to move one step ahead and, uh, allow for, uh, links, uh, also with, uh, repositories, uh, especially targeting the qualified references, uh, reference that the European Commission has in their template, uh, the Horizon Europe DMP template. And to do that, we had to, uh, expand, uh, what we already support with the semantics mechanism. And I'm not going to go into the technicalities of, of how we did that. We can check the code if you're interested and, uh, you can feel free to ask questions and we can, um, our technical team will, uh, answer them. Uh, but I'm going to show you how it works, uh, for us, right? For us as, um, administrators or template editors that, uh, that create a template. And as researchers who are going to use this template, uh, what they get, um, what we get. Uh, first I'm going to show you how to create a template with this semantics. So I'm going to the data set templates, uh, here, this, um, function, and I'm going to create a data set template. Let's say this is the test template or related identifiers. Uh, let's give it a description like random, the language that this DMP template is written in, then moving on to the second step. Let me create my chapter. I think we call it qualified references. Let's give a name to the section. This is all just so we can move ahead to the questions and let's add a question. And let's say that in this template that we are working on, uh, we want to, um, show the relationship of this DMP, uh, with the publication. So let's say the links with publications. Um, this will be the name of the question. Uh, I don't give a description for now. And I go to the type to define, um, the type of this question. Um, I want to show that this DMP supports this publication, right? So I want to select the API for the publications, this one. So that I am able to then find one publication from the, um, from the source, uh, and, uh, do and then provide the link. After selecting the publication, I move on to the semantics, um, to the semantics function. And as you can see, all these are the predefined RDA properties and entities, that we already had. And further, we have more for Zenodo, uh, for Zenodo related identifiers. I'm not sure if everyone is aware of what this means, uh, but Zenodo, uh, rest API maybe if I can find this like that. But Zenodo has, uh, gives the possibility of uploading, uh, files and also making, um, links with other, um, files and outputs. So it supports, uh, this outcome. So it supports, um, related identifiers as an array of objects. Uh, and you can see here the different types of relations that, uh, they, the, uh, we can, we can give to this, uh, objects. Uh, this is a drop-down list for them. Sorry, I have to find it. So this is a type, um, this is a whole list of, uh, what, uh, Zenodo in this case, since this is the repository that we are using for Argos, um, uses, this is the list. So you can have site is cited by that this, um, this object is cited by another that you're linking sites is supplemented with is continued by continuous is compiled by so different types of, um, uh, operations and, and relationships. And all of that now is available from, um, here, all these different relations. So let's say that these publications that we are going to link, um, sorry, this DMP that we are, um, going to make this link with his publication, um, is the DMP, let's say, um, has part of this publication. Let's say that this is the relationship that we want for this particular case. Then let's make another one for a data set that this DMP the same. So I provide the question. I find the data set API from here. And then I provide a relationship. And this DMP, um, I don't know, is supplemented by this data set that we will select. Um, let's see how this works. Let's save it also. So this is how it will be available, uh, for the end users. So for, for all of us that would like to complete our DMP, uh, with this, uh, questions with, I mean, with this, um, information. And this is how it will look like. I select one from the API. So I run the select from, uh, the sandbox now. So I'm not very, you know, deliberately do that. Um, I see that it works. So I can now finalize it as I'm ready to test it. Uh, this is the test template for related identifiers that we just created. And, um, let's use it also and see how it works. So I go to my home. I start the new DMP, start wizard, uh, give it a name. And I will skip all the non-mandatory fields. I will just, for ease of time, just move on to completing the mandatory test template. The Nemo's test template for related identifiers of this template. So let's add it. And add, um, a dataset. I mean, um, okay. Now that I can see the content of the template, I see that this is what I made. And I can move on to, um, the, to making the links, right? So let me, uh, see stories. So let's see. I want to link this, this publication and this dataset. Okay. I save it. And I'm ready to finalize my DMP. I can finalize this dataset and then go on to finalize my DMP. This is my DMP. Of course, I skipped all the non-mandatory, um, information. I have this dataset that I just created and I can now finalize it and deposit it. So when I deposit it on Zonoro, click it. I'm asked if I want to use my credentials or Argos credentials if I don't have and if I don't want to, to use mine. Let's quickly use Argos for now. And I have the DOI. So let's visit what I did. I adjusted. I can see the title, me as the author. I cannot see. I selected restricted accents, uh, which is the default. So I didn't change it to open access so that I can see the actual exported files, uh, that I made. But here, uh, on the right, I can see the publication date, the DOI of this DMP and the links that I just made. So remember, I selected the relationship that was about haspart and supplementary material and haspart is the publication. So let's open it. This is the publication and supplementary material. This is the dataset from Mandolin. Okay. And this is, if I go back and export, for example, in Word document, document, click it. And now you see it, right? Yes, we can see. Perfect. So I scroll, I scroll, I scroll and I find the and I click at them and you don't see what's happening because it's happening somewhere else here. So this is okay. So this is what we can get, uh, directed to the Zenodo entries or the other repository entries that we linked, right? This is the part for the semantics. Any questions on that? Any comments, statements, ideas for discussion? Do you think it's useful? Do you think it helps with making the bridge between the repositories and the DMP and helping with qualified references? At least this was our intended, our intention. Okay, Paul, let's, hi Paul. Yes, it's definitely helpful. Hello. Sorry. Yeah, yeah, no, that's absolutely, it's no doubt about the usefulness of this. I just thought I only really listened just not very closely, but it's for the, for the time being, it still seems a bit clumsy and difficult to put in practice, but I guess this time you will find a much better way to guide people, etc. So that's, that's a very nice feature. Okay, thank you for your note. Yes, we're still, uh, of course, yes, we need to see that in a DMP there is not just a test, to test this, this function, that's what you mean. Yes, of course. No, no, I mean, here you have to find all the fields you need, etc. So all this eventually this time you will be able to build some guidance and to even guide the people to answer instead of having to search through something you understand. Yes, yes, I understand. This will come this time, I am certain. Thank you. Now, but semantics is critical, of course. It is. Thank you. Thank you. Anyone else? Yes, we have a question from Alan Borrell in the meeting notes. Are the possible qualifier relationships completely align with the data seeds relationships? Are the, sorry, can I see the question? Are the possible qualifier relationships Are the possible qualifier relationships completely align with the data site relationships? The data site? Yes, yes. Zanotto is aligned with data site. And from a meeting that we had in the past, actually with data site, no, it wasn't with data site, it was with our kid. Yeah. So I have to check, but the Zanotto alliance is fully aligned with data site. So in this particular case, we are just using, you know, Zanotto. And if Zanotto fulfills this, yes. So I think the answer is yes. Thanks, Alan. Actually, I have a question, if I may, if no one is willing, has any question? Yes, please go ahead. Yeah. Look, again, I'm sorry, I did not listen very carefully, but with your, the way you do things, you can choose any type of vocabulary or ontology when you do this, or for the time being, are you tied up with something? We use the controlled vocabularies of the repositories. In this case, it's Zanotto. But you have answered my question. Yes. In other cases where we have other instances, we use, for the example of the vocabulary of data versus instances, so different here. Okay. Thank you. Thank you. Anything else for the semantics? Okay. Then I'll move on to the next. Let's go here. Let's minimize this. Okay. Now it did. Okay. Now it worked. Perfect. So I'm not sure that if everyone is familiar with this functionality, but I'm going to show it anyways, because now we expanded, so we can see it in full, let's say in the complete, in full cycle. Let me log out first. So when I'm logged in, again, excuse this. This is a test instance that I'm using. It's not the production, so that's why you may see things floating around or being mislocated, let's say. So here, these are the different possibilities, some of the possibilities at least, that you can use to access, to log in the Argos tool. And I'm using normally Google. So I'm going to use it now. You could use anyone that you want. But let's say that I would like to use another email. If I use another email that is not the email that is linked to my Google, then I will become another user for Argos, because Argos doesn't know that these two users, although it's me, that these two different email accounts are the same user. And that means that you might experience mis, like invitations that are lost from partners, because they might send it to one of the two, or even an even third account that is not, that was never used to log into Argos, right? So you might experience that, and you might also experience having the DMPs that are different in one account and different in another account. As Argos wouldn't know that you are using two different email accounts, for example, to log in and to do your data management planning activities. So to be able to, for Argos to know, we have already a link functionality, which you can find under my profile settings here. If I click my profile, I can see my profile settings. I can change, you know, different with the data under my profile. And I can also find this, the accounts that I have used to link, that I can use to link my account with. In this case, for me, it's the same. It's my Gmail for, I'm using my Gmail for my Orkid, for my Zenodo, for my Twitter, and for my Gmail. So let's say that I want to link with my Gmail activity in Argos. Also, my Zenodo activity, but with another account, with another email account, for example, with my Athena Research Center account. I want to link my Gmail activity with my Athena Research Center activity, authorizing it. I get a verification pop up. That means that an email has been sent. You could hear it. So I'm going to check it. And now I'm aware that I'm sharing my whole screen. Interesting. Let's quickly check it. Let's confirm, open this to another tab. Okay. And now if I go to my profile, I see that I've also linked my Athena Rc account. So anytime that I will use this account, all the activity will be also kept from the Gmail as well. And invitations won't be lost for my colleagues. And also my DMPs will be in one place in my data system. However, this changes if I want to unlink things. You can see the unlink function from here. And let's say that now I don't want to use this account anymore. Two things that you need to pay attention to. You cannot delete your main email. So this is my main, as you can see. It was the first email that I used. My first login option was login with Orkid and it was my Gmail. So that's my main account for Argos. I cannot delete that. I need to request for a deletion from the Argos team for that. But for the following, for the alternative accounts that I have linked after, I can do. For example, this one, the Athena Rc, I can, at any time, move it from here. Unlink it. I click it. I get this popup that says, by clicking confirm, you accept the transfer of your Argos activity performed from this account to your main Argos account. So everything that I did with this account will be transferred to my main, which is my Gmail. And by logging in again with my Athena Rc account, I won't be able to find what I had already because this will be in my Gmail account. Yes, email. But I will be able to start from scratch. So I will be a new user with a new account on Argos with no prior DMP or activity in it. I click confirm. And I have to verify my account and the verification goes to the primary to the main account, to my Gmail. So I have to check my Gmail. Oops. Let's click the OK close first. And let's click the confirm. And let's go to my profile again. So now my Athena Rc account is not connected anymore. And that's the new thing that we introduced. As we were getting some user feedback, that's why we implemented it. Any questions or things to discuss on that as well? Okay. And then the last thing that I wanted to show, because maybe you haven't seen, oops, there's something in the chat. Nothing. Okay. Nothing. The last thing that I wanted to show is our release notes. This is the current version, version 1.7.4 in the production, not in what I was showing you. The previous was 1.6.1. Again, we got feedback from developers that are deploying Argos in their own VMs, that they would be good also from externals, but mainly from the technical teams, that it would be good to at least give an overview of the new releases as notes and the release notes. So this is what we're doing. So feel free to have a look and check the release notes as well to stay informed of what changes. We keep track of what's new. I mean, we don't add here bullets for any different things. Like if we change a label, for example, we won't add it as it's not something that's worth. And knowing here, we have that in the commit so you can find them there. But here we keep the main, let's say, topics that you need to be aware of. So in terms of what's new, what's improved, like the semantics that I showed before, and the bugs that were fixed. And yes, we hope you like it. At least this is a different way to communicate with you what's happening in different releases. And I remember yesterday, I had an extra thing that I wanted to show you, but I didn't keep a note of that. So I forgot. In any case, the the community call was about those three and those three are required, you know, considerable effort from the team. So hopefully you also like it and you find it useful and you will use it in your own practice. Do you have any questions or anything to discuss around those and not only these or maybe other things that you want to discuss about Argos or another instance of the OpenDMP software. Let's stop sharing and let's see you now. Feel free to unmute and share your opinions or your feedback. Pollock, yes. Yes. I think I've said it already. I never used your tool and I think I'm afraid I will never use it in lack of time. Currently, we are working with DMP Opido, which is the French extension of DMP Roadmap. And personally, I also work with DSW. Maybe you answer this question at some other time, I'm certain. What kind of interoperability do you consider with other tools? We are using the DMP Common Standard. Yes. And I'm also the co-chair of the Active Data Management Plans for RDA. So we coordinate efforts among the different providers. Yes. Of course, we don't want to do something that is outside of open science realm. Absolutely, I agree here. That was just a question. Again, I wish I could play with your tool because you have really features. I said it before that really interests me, but lack of time, I'm afraid just so I pop here and no one then. But thank you for the nice tool. Thank you. Thank you also for getting into a conversation during the calls. It's nice, not me talking also. Oh, I know what that means, how that feels. I know that. Thank you. Any other questions? No comments? Then if not, okay, if not, then we can close this meeting and the next, the last meeting before the summer break is in three weeks. So I'll see some of you in three weeks. Hopefully some of you might be on vacation even better. I hope you have a good time. But in any case, I'll see you later. Thanks everyone. Bye. Thank you.