 Okay, hi everyone. I hope you're well. Last community call Vargas for this year, because we are having more in 2023. And as the agenda in our invitation mentioned, we are going to talk about two new features that we are launching in this in the latest release that will be taking place right after we are back from Christmas, so in January. And those features are the possibility to deposit your DMP, to push your DMP and expose it in more than one repository. So one is this and the other one is the possibility to create a template that supports a table that is machine actionable. So maybe you want to create a table to list things. That is now possible to do it and I will show you how. Let me share my screen. Okay, let me see this. So let me start by showing you the feature with the table. And this feature can be used as the administrators want, depending on how the information that they want to add in the template they would like to be visible on the export. And let me minimize this to start showing you how to do that. So if you're an admin in Argos, you know that you go to data set templates to create your own template, your own structure with your own questions, the rules and all the things that will make your DMP. So let me create my data set template and let's now do a test for say that we want to create a table where we list all the or basic components, basic information for data sets that we want to have in a collection of data sets. So I will quickly create a chapter for table data sets in a table. Okay, and then I click to add the question as I would normally do. Nothing has changed as you can see here. I can add my the name of the question. I can give a description and I can select the types that I want. So first, I need to know what I want to include in this table. So what I want to include in terms of content. Let's say that my table, I would like it to give any information about the title of the data set, the vocabulary, the data that have been used for this data set, the PID of the data set, a license of the data set and the repository of the data set. So I have five key things that I want to address. I will start by creating them separately. So I will start by adding a free text because this is the field that the researchers will need to add the name for this for this, for each data set. So name, data set, right. Then I can add more below. Let's say that I want to add next the metadata of data set. And here I chose the API so that I enter this information from the trusted source. The one that we use for metadata, for example, is the RDA and University of Bath director of metadata standards. Then I can add another input to include the PIDs and maybe a select to provide options for maybe a DOI. And I can see below how this is done, right. And let's make it multiple, maybe more PIDs are used, maybe it's multiple as well. So they have the possibility to add more things for, provide more inputs and then add one more for the license from the APIs again, the licenses, right, from the API. And then let's say that this is more, let's say that I want the data repository. So this is how it would look until today. You have all these different inputs added right below one to another, making up one question. So this is one question with multiple inputs. And now if I want to change it and view it as a table, I click the multiplicity here. I go up where the multiplicity is. I can specify how many times I want, how many times I want this set of inputs to be visible for people to answer. So let's say I want them, I want 10 times. And I select view inputs in table. And now with this, the 10 times become rows. So that means that I will now view what I did, what I created in a table, which supports the addition of input for 10 rows. And if I go back, I see how this is done. I see that there's one, two, three, four, five rows, five columns. And I can add up to 10 rows. I could have picked another number, let's say 10 for now. Okay. And then I save it. Before I save it, let's see how this is machine actionable. It is machine actionable because for the name of the dataset, I can select this field that is expected from the RD standard to be found in the JSON export. So name of the dataset will be dataset title. Metadata will be, let me see where the metadata is. So here we don't have the descriptions of the data. We have the identifier type. Then for, yes, so as you can see, this is how we do it for every input. So for every input, we go and map it to the RD standard, and then we save it. And if I go back to Argos, as a user now, not as an admin, I can start my DMP. I can start create a DMP. So let me hide video button. Hide floating. Start my new DMP. Start the wizard. Quickly create a DMP. Save it manually. Now if I go here, this is the question that I have created. And I can add the title, choose the metadata, add the PID for this dataset, choose the license. I don't know maybe related comments. And choose a repository where this dataset will be hosted. Save. And I can add more. So as I told you, we haven't launched it. We are still finalizing things. So for example, here you cannot view the input from the APIs, but you can see that in the export. So before it's released, we're finalizing this. Here you will be able to view also whatever comes from the APIs. And similarly, I can add the title of second dataset, add the metadata to it, and provide a PID, and so on. And then I can save it. I can go and check what I have just created. And I can finalize it. Yes, I will finalize it. And then if I export it, for example, in PDF, can you still view, do you view the PDF now? Yes, we can see. You can see the PDF. Perfect. So you can see that it has the information that I selected in this table, right? Oops. Let me go back. Okay. And I could again choose any other export and see this information like this. Yes, I think before I show you the next, I would like to know your views and how you find it. Maybe you want something to change. We have time before the release so we can change it. If something is not very, you feel that it won't be very useful, of how we have it today. Let me see. Do we have any questions regarding the table? Please feel free to open your mics. We have a question in our document. Yes, for Andrea, we have a comment to create. Yes, you have to have admin roles to create a template. Yes. And in our Google Doc, we also have a question. Once the table roles are filled in, can we use the fields on one column as a scroll down menu? Suppose I have an answer that applies to a few datasets and it will be nice to choose which ones via the scroll down menu. So let me see. I don't find this in the minutes. Where is this question? It's below the table. Okay. Once the table roles are filled in, can we use the fields on one column? So you want to be able, like you do in, so as you do in the spreadsheet where you copy and click everything, like scroll through the whole column, for example, and paste it, right? Is this the action? Hello, that is me. I have this question. So suppose you have dataset one BNC and you have all your questions, then the follow up questions in your DMP and say question X applies to dataset one NB. So it would be nice to get to say to which dataset this answer is relevant. And then you would be able to have a nice little scroll down menu with, say, the column name of the dataset. And you could just click and say, oh, it applies here and here. That is the question. I'm saying this because this is something. This is a question and a feature which is discussed in DSW, for example, as well. But from my perspective, it would be a very nice feature. And from the way you show the mapping with the RDA common standard fields, I think. You can do it. I have the feeling that technologically speaking, it should be a possibility in your case. But then I find this extremely interesting as a feature, but maybe not everyone. No, it is, but it's something that we have. We didn't think when we designed this table, but I will pass it over to the development team. And I can let you know next time what might be the challenges. But again, maybe the community might want to say if it's something they would like to see, etc. But again, from your mapping with, for example, RDA common standard, I have the feeling it's feasible. But then that's me. Thank you. Very nice. Thank you so much. Very nice. Thank you. Yes, does anyone support this possible new feature? We have Roddy with their hands raised. Yes, I have another question. So I don't want to interrupt the feedback on that one. But if there's, if there's nothing else. Yeah, okay. So yeah, my question is, yeah, it looks really great about the, about the PIDs. So you got a, I see you've got a, you can add a PID. Could you talk a little bit more about what that means? What, what PIDs are available? How does it work? Because the PID needs to be minted and all those things. So how does, how does the PID aspect of this work? So you, so I just created it like free hand. I didn't use any API, for example, for this or any source to infer information from. So I, for this particular example, I did it free hand. So using the multiple choice field to create it. But there are many ways that we use PIDs, for example, in Argos. And well, which one should I, which one should I touch upon? Do you have a specific? My question is, so if you're, if you're, okay, if you're, if you're, so you get this field, you get this option, right? You see PIDs and you can, you could put something in. But what happens when you put it in? Does that, it's not, it won't just, if I put in a DOI, it's not going to magically produce a DOI for me, I assume. So how does, how does that, how does it work? No, no, no. So let me, where was the export? Do you still see the export now? So do you still see my screen? No, we are seeing your brother. Okay. Let me open it here. No, you can see now. Yes, yes. Okay. So here, for example, so this was a free text field. Everyone can add what they want. Metadata, we get, we infer the information from the director of metadata standards. PID, I did it to give the possibility to add this as an answer by a selection, a pre-selection of answers. License, this was from the, again, the API and I chose creative commons for, so creative, CCBI and repository I chose for the one, and much for the other one, I didn't add anything. So I had this repository. When I use an API to get information, so for the case of metadata, license and repository, there are different things that are shown in the export and in the JSON, according to what is expected and how I have formulated this template. So that means that although here you might be able to suggest the title of the metadata, in the JSON, you should be able to view more things that are related to the data, like the identifier, if it's any language, if it's available and so on. In the same way, if we had a PID API, we could get the title of the system that we want to show here and then decide what information we want to cover in the JSON export according to the metadata, according to the standard, the NPKOMO standard. But another way that we use the PIDs, for example, is to infer information in the template. But this is different from how we use it here, because to be able to infer metadata that are relevant to a DOI, for example, a record with a DOI, that's a different feature, the prefilling feature that we have. And this is, let me show it maybe quickly. Let me add a data set in the system. No, I have to define what it is. Let me quickly do that. Starting with the NP, very quickly, prefill. So when I click prefill, I search a data set that I want that I have deposed somewhere. Let's say that this is the one that I want. I click Next. And so I could search with the DOI that I didn't show you, but I can search with the DOI and then whatever is in the metadata record appears here, as you can see, prefilled in my DMP. So this is another use. I think this is the one that is closer to your question, Rory. Yeah. So I don't want to take up too much time. I've actually, along with some other people, we've just put in a, we have a new RDA interest group called Working With Pids and Tools. So I'm quite interested in this whole issue of how do you incorporate Pids into tools? And it's very complex as this discussion is kind of demonstrating. So yeah, my question, what I thought you were trying to show was associating a particular PID with a particular data set, but that's not the case. No, no, no. I was just communicating the new feature that we're going to launch. And this is the table view that we will be offering from January. And your table tells you what type of PID it is, not the actual PID. It's like a DOI, for example. Is that right? Yes. Unless you define it to be otherwise. So in my particular scenario, I didn't want that. But you may configure an API that supports something else and you can use it here, also in the table, in another way. There are infinite ways that you can use over different inputs and fields that we have that we provide. So it's basically up to the admin to use it. All right, great. Thank you. Thanks, Ellie. Thank you. Any other questions or feedback for this feature? I see lots of thumbs up. So that's good. Regarding PIDs, we have a question from Joachim. I assume PIDs still have to be mined outside the ARGOS, example via data site or mining facility, right? Correct. So they are minted from a repository infrastructure. If there is the case for us, it is the case. And for other ARGOS instances, it's also the case. But we are also, we're having a call again next year with data site. So we're planning this to see how this can be done maybe without the assistance of the repository. So we were contacted basically by data site to check another way of minting DOIs. We also have a question from Roberta asking about how can you create a DMP template or a data set template? I wish I had the time to show you now, but this is not the topic of today's community call. But maybe that's a good thing to add maybe in the next demo. Maybe we can have another administrator demo next year, either January or February. If that is interesting to you, I can make it happen to see how you do it. But very briefly, you have to have admin rights. We provide you with those rights. And then you go, then you will be able to view all those things that you do not see as a simple user. And data set templates is the one that you want to use to create your data set template. Very briefly, this is how it's done. But I noted it to have an admin demo probably next January or February. Any other question? Okay, we'd like to get admin rights too. Okay, whoever wants to get admin rights, please let's contact me or we can leave your email in the collaborative document so that I contact you. Okay. Do we have other questions for this? Okay. If not, then I will move to this, the other new feature, to the possibility to be able to select the repository that you want to publish your DMP and then make all the links with the outputs and so on. And we have expanded this feature to include more repositories. So we are currently working in a national use case where we support two universities to create their DMPs with Argos. And the two universities have two different repositories where they add their publications and their business outputs. So both repositories have the same software, so they're both this space. They don't share the same storage. So the researchers should be able to select which one they want to send the DMP to. And we have created a plugin for this to support it. I will show you where this can be found in the code if you want to have a look in a minute after I show you how this works. And well, yeah, let me not say more things. Let me just show you how it works. So let me say, let's say that I started DMP, DMP, to DMP deposit. And let's see, I selected template and then let's just provide some answer to that. Okay, and then I save it. I can now go and view my PID when I'm ready, finalize it, select the data sets that I want to finalize. In this case, I have only one. So I want to finalize only this one. And now I can deposit. Now, instead of going, giving me the possibility to use only Zenodo, for example, now I have the possibility to use Dataverse or this base. So in this test that we're showing you today here, it's, for example, Dataverse. So let me select Dataverse, for example, since I have showed you how Zenodo works in the previous demo. Again, similarly, automatically, we'll have the creation of the metadata record on Dataverse. And I can view it. Do you see the Dataverse now? Yes, yes. Oh, perfect. And then I can view it. I mean, I haven't added many things. So this is why it's very minimal information that it has. And then, okay, and then if I go back, and I want to deposit again, for example, now the Dataverse is not an option. Zenodo is an option. So I can do both. I can push to both reposters. But of course, this is not something that is very common. Or I don't foresee that this will be done. But yeah, and here you can view the DOI and access it and so on. Yes. And I promised to show you where this is in the code. And it is here. The plugin is here. Where is it? Where is it? Oops. Hello. Can you hear me? Yes, we can. I cannot find the, what happened? I cannot find the zoom. Maybe can you please add something? Okay, in the shot, okay. In the shot. It disappeared from my laptop. If you can try the pressing the alt type in the keyboard to find the zoom. I cannot find it. Maybe cycles through all your windows. Maybe I will stop your sharing screen and you will be able to see and then you can start sharing again. This is the Christmas. Oh, yes, I see. I thought that was someone telling us to stop working and go to have Christmas holidays. But it's, yeah. Okay. Now I see. Thank you, Andrew. Thank you. So this solved things. Yeah, but now I cannot exit. Now I'm stuck in here. Let me do the search screen again. No, before I do, let me add in the chat here. This is where you can find in the code. And now I can share my screen again. And you see, yes, where this is. So here it is with the documentation so that you can use if you want. Do we have questions for the deposit? How do you find the feature? Thank you for would you like something to change and in what direction? Yes, I agree. It's a great push for research in the DMP public. Yes. And we are, you know, we are working also since you mentioned, Julia, we are now merging parts of our workflow to do exactly what you say to close the DMP life cycle and push for publishing the DMP so that they become fair objects as well with all the links to other tools and outputs. So we are doing that and we will have more to say in 2023, early 2023. Go ahead. It depends if the admins or if people that deploy Argos are doing it themselves, we support them. We can support them if they have questions and at least in the long term. And in the long term, I don't know what you mean for the plugin in the long term. Do you mean the Argos in the long term? No, what I mean is when I talk about the admin, it's not the CIS admin I'm talking about. It's the admin, the people who have admin rights in Argos when they do the DMPs etc. That means something that like a skeleton plugin where you put the pop information and then whoops, you have created a new plugin. That's what I meant. Not from the CIS admin perspective, but from the, if you want data, you would admin. If it's feasible, I would just thinking about that. Okay, well, that's a good approach, a good perspective. But it's true that those plugins are meant for the CIS admin, so the people that are working on the platform to deploy things and configure things. Okay, any other question or idea based on what you saw? Or any comments by using Argos, what would you like to change, what disturbs you, for example? And we could simplify it and make it better. Because the table, you came from your input as well. Many things actually came from your requests. Then if we don't have more questions, can I ask, thank you very much, can I ask what would you like, where would you like to concentrate in our next community call? Because we have ideas, of course, that maybe you want something more urgently that we need to show to you. I added the admin demo. I think I will stick to the admin demo. Let's say that either January or February, we'll have it done with demo. Good. We have a suggestion in the chat. Yes, I think Table is helping in this, but about making conditional questions, Ingmar, what about the conditionality? How to do it practically? Yes, so again, there are many ways that you can use the table. Maybe having conditional questions with that is difficult, but I think from what I've tested, it's feasible to attach, let's say, when someone answers one cell in the table to be redirected to, I don't know, question that is below the whole set of inputs of the table. Yes, I wanted to, it was more about that, for example, when you have yes or no question, and you have several inputs, and if you put condition yes and this input, then it shows only first input, and I don't know, and if no, then I mean, maybe I haven't understood it correctly, have to make it, but I would like to, if I put yes, then you can get all the inputs in the same question, or if no, then none of these inputs, something like that. I see what you mean, so you have a question yes or no, let's say, and then depending on if you answer yes, for example, then the table opens, right? Also that could be yes. That is how it happens today, but you say something else, so you say that when I click yes, or in yes everything will open, in no, I want two things to open from the table. Yes, then what you need is to create another, to clone what the whole template is, and delete what you don't need, and attach this to make this conditional to the no. Yeah, like the next question. Yes, so the one. Okay, I was doing something like that, I thought maybe it's possible to do it with the same, with the inputs in the same question. Okay. With the inputs in the same question. Yeah. No, okay, that's a good one. So have conditionals in the same inputs. Yes, let me get back to you on that. Let's see how it works now, and if we have time to tweak it, to support it, and I will fill up with you in an email about this. Yes. Thank you. Thank you. Anything else? If not, in the background, I hear bells ringing, so it's Christmas very soon, so I wish you all a Merry Christmas, or Happy Hanukkah, it depends. And generally, please have a good rest and enjoy your time offline, and yeah, I wish you all the best, and we'll see you very soon next year. Thank you, everyone.