 So, hi. Right. So today's community call is focuses on the template, the checklist that we added, and it will be made available in Argos in the next release about how to create a software management plan. And so what we did was we got the checklist of the software provided by the Sophisticated Institute that was developed around 2018. So it's kind of old news, actually. But it provides a good base for what we aim to be doing in terms of supporting software elements in Argos. So, this is the link for the checklist that you can find on Zanotto. Let me actually also set up my screen to make things easier. Yes, so this is the link that I just shared with you. Oops. Yes, and this is the one that we used. So as you can see, the publication date of this version because this is the latest version is 10 December. And this checklist has information asks actually for information that can contribute to providing a better understanding and image of how the software has been managed throughout the project and what were the different roles in this in software development and management, how the different people involved collaborated, what were the communication tools that they use and how they expect to, or they have shared their software later, and what are the access rights and the license to touch the software and so on. So, giving an overview of those kinds of information that can facilitate better understanding of different elements during the management life cycle of the software. Here you can see one first question is about the intended users and how it is, how we can find how we see it in Zanotto is we find the main question asked, right? Then other questions to consider so they're breaking down the big question with some questions to allow for more details from researchers so to get more information about different things that they would like to check by posing this question, the big question in the beginning, and then there is the guidance. The guidance where you can find how you can, there is instructions on how you can provide your input to answer this question, what type of information is expected and also guidance on where to find things and proper best practices, let's say, that can support your answer to this question. And this is how it goes, so there is a bigger, let's say, question and then questions that break down the main question and some guidance provided. Let me see in the chat. So what we did is we in Argos, sorry, in the test instance of Argos, we created this template for this template that we just saw, right, and we also added an extra element for costs. And this information we took from previous versions of the SSI template, so past versions had many questions here and there in different sections around fees and costing, some services acquired or different things during the software development and management, so we kept it here to check also with you how you would like to, if you would like to have it and if it's useful. And let me now show you how this template looks like if you go to Argos.u, now it's not available, but when it will be available, you click Start, Union DMP, Start Wizard. You add the information for the software management plan, so the title, a description for your software management plan. You add for the researchers that are involved in this data in the software management plan, the organization, so I'm going to skip it because I don't want to take more time. Which is the funding organization, let's say to European Commission. The grant associated to this project. Let's randomly pick one. Let's provide a license also to our software management plan, let's say that I wanted to be creative commons for yes, perfect access. For me, on the fourth step when I'm asked to select the template or the templates that I want. This occasion I'm going to select the template that I just showed you. Of course, you know that you can add multiple so for example if you have a project that you want to use multiple templates and, you know, and select each time for the output that you are describing the correct template you can do it for example I could have here the horizon or the horizon 2020 because I have the horizon 2020 and I know the structure that it has but it doesn't give me enough flexibility to answer questions that are relevant to software so in that case I'm going to add the SSI template to support me in this. And let me save this. I'm just going to profile now I'm going to add it manually. So these also are going to change wherever you see data set from the next release of our goals you will see output instead of data set because we are expanding things and we, and as you know already. The different starting from the European Commission right as a policymaker. So as far as in Europe, they do not only require data sets, well they do not only include data sets as part of the DMP but also software workflows and other outputs. So we're also expanding to support that. Let's provide a title for this software that we will be describing. Let's fill in the description and select the template that I want now I'm describing a data set. So I'm going to choose the SSI template this is the software stability template, instead of something else. And I click next to view the template with me also save it just to be sure. Here, you can see the template, you can see that you have an introduction to what the template is about. So basically explaining some things about the software management plan. And the questions. So what the first question as we saw before on Zanotto was what software will you will you develop so we have it here, along with all the subsequent questions to support more detailed answers to be provided. And the input, where the, sorry, the place where the input can be provided. As you saw, I clicked view more and when I click to do more the guidance appeared so I can click. If I click I don't know if you still, are you still be able to to see my screen. Did it change. Okay, perfect. So now you say yes I picked. Yeah, good. Thank you. And I have to go back and I have to move these things. Okay. So now, let me go back. I give you more to check the guidance and check the guidance and I'm ready to answer so let me add a name of how the, how the software. Sorry, this is repetition. This is not the latest. We already did sorry, but now we can specify the scope of software by providing by answering all those questions or those that, at least are relevant for our case for our project. And you know we can even have hyperlinks here. Here to redirect to add references or redirect to other sources that can support our answers. Just say that we specify this for this one. The next question was were they intended users of your software with these follow up questions to help provide a better more, more thorough answer guidance is this I give you more. And again, I'm able to write in the box below. And then, the next question is about how will you make your software available to your users with again some subsequent subsequent questions, the guidance. And here I can add a landing page. If it's not a landing page. Then it's not valid. The landing page. Yes, I have to do the whole HTTP sorry let me just copy this to do it. Okay, now this is correct because this is a valid, a valid URL. Here I can select the license in the questions if you can check there is one about the license. Under what kind of license will you make your software available so now I can select here. The licenses for example I can, I might have GNU and some components might have for example. And then I can specify what I mean provide more details on the answers that have provided both, but also on the extra law on all the other answer questions that I that were not in the previous boxes. Then fourth questions about how will you support those who use your software. And here is a pretext again so you can specify how you're aiming to do that by answering all those questions what level support will you offer how much effort will you have available support your users, how you will manage their support for health and so on. Next questions about how will use will your software contribute to research and how it will help researchers or others for yourself to conduct research more easily, or to enable research that cannot be done at present and all those different So again three texts for you to specify how you intend to do that. Next question is how how will your software relate to other research objects. And here you can select the publications that relate to the software. So again searches the whole opener discovery portal so millions of publications from more than 12,000 sources journals and repositories. So let's say that this is the one supporting the software and maybe this one. Of course I can. In also search. So now I'm randomly choosing somebody I can also check the specific one that I want. Similarly, I can make the link to the related data sets for the software, maybe that I've used as an input to this project. Again, searches the whole data sets or millions of data sets the whole opener millions of data sets and I can select the whole data sets that relate to this. The same I can do for services. That relates to the software maybe that use the software. And here is the ESC services. So it searches the ESC services. So I can, for example, select the services that have used the software. And again, I can specify my question. And complimentary to just, you know, to making the links because here what you add here will become a related link in the metadata record that will be created for your software management plan. So at the end, when you will complete the whole software management plan here. You will click save you will finalize it once it's ready and then the last step is to publish it on Zanotto, so that you make it find the book. And when you publish it on Zanotto, it's just a click. It's very easy. So when you publish it on Zanotto. Then you will also get those links with this with the identifiers of these publications, data sets publications, basically, and a related a field that shows the relation for the services as well. So all the links will be kept. Oh, sorry, do we have a question. Until until now. Um, right. And then, the next question is about how will, how will you measure your software's contribution to research. And there are some follow up questions that talk about measuring downloads of the software or who has used the software and other types of other means of measurements guidance to support an answer. You know, a thorough answer, and an open ended field here just for you to specify. And last question is about where will you deposit your software to guarantee its long term availability. There are a couple of questions about the repository that it's a repository that will be used and the unique percent identifier for your deposit and all the repository and so on. So here we broke down the input. The input that you can provide to answer those questions so here same way as before you select that is a repository where this software can be found. And I add the preservation statement if I if there is any. So how this how preservation and especially long term preservation is guaranteed. And I specify my answer by also answering other questions from the book. Then this is for the version that I shared with you in the chat up to here up to 1.1.8. The extra things that we added is about costing. And again, we base this. So we took we selected we have the questions that were relevant to costs and fees during the different steps of the of the software management from the previous question from the previous version of the template and the check it. And we provide them here in that way. So, some of the questions relates to charging the users to access the software, or if third party data system database are free or you have to pay for them to get to get access when you're developing the software. And if the repository for preservation is also free, or you have to pay similarly for any communication protocols and data formats if they are free or you have to pay, and you can select the currency and provide an answer about the cost. So, this is the first, let's say, draft, the first version of our implementation of this checklist in Argos, and we would like to know your thoughts, your views, but how you find it is this useful. If you would you like something to change. And just to say that we are starting yes I mentioned the beginning that we are starting this expanding things, especially for software. So first is this template is this checklist that we want to add and we are already working in parallel on adding a version of the data set for data sets, let me also add this link in the chat. Data sets for data sets are like data sets for data sets were created by Microsoft by a group within Microsoft, and they were created again in 2018, yes, submitted in 2018. So this is an intervention yes made it two years ago, and their intention is to be used is similar to a data management plan with sections and questions and guidance, but to support machine learning and their facial intelligence applications. So now we're moving now to this chattivity era, and before, hopefully you can still see my whole screen right before we start I actually asked chattivity, what is to explain me what a software management plan is, and a whole see a whole list of things appeared. So here, even superman's plants are expanding. And hence why we're trying to also have multiple templates for software or other types of outputs to support you. Yes, well enough with me rambling. Let me go back to this template that we drafted this checklist this first checklist, how it looks. Is it useful to you what are the questions that you would like to see and you don't find in this template. Let me stop share, maybe, and open the discussion. So, is this a. Is this something useful to you that's a. And is a question. Either it is or it's not I don't know how to receive. How to receive this. Right. So, have you. Yes, it is. Have you tried to have you. So what are your, let's say, questions, when you when you try to document the software. So you have the template of European Commission, for example, or I don't know what other times you might have. Are there any specific questions that you think for software that today are not available in this template that you're using, for example, the European Commission for horizon. Anyone would like to comment something to make any statement, even. Okay. I find it useful. This was what I understood from the chat. And I look forward to see how it plays I mean, we have to test it are there any volunteers to test it actually. That would be good. If you would like to test it before it goes to production. Can you hear me. Yes, hi. I am Robert. I never, I never documented the software so far. But I saw that in the rise on Europe, the template there is a section in the data management plan, which is devoted to the other research output. So I think I will have to do it in the future. But I was wondering, do we really need so much detail, because the template you showed is very detailed, but the section in the data management plan is not so detailed. That is true and you can answer only the questions that you think are relevant to you. You can choose. It's not. If you if you want to skip some. You can feel free to do so. Yes, Robert, I don't know if you were here last time the previous community call, but there was this discussion about having a software management plan which has more details as you say this as the one that I showed. Having the template as it is, for example, Horizon Europe, which doesn't include that much level of detail. So the very, let's say the request that at the end of this discussion was that it's good, the horizon Europe template it's good as it is it doesn't have to be very detailed. It's not around software for now, but we would need another template that is more detailed. So, if you if someone has a software and it's a very software oriented project, they feel that they, they can cover more by using other by incorporating other templates in their DMP in our goals. I don't know if that makes sense. Yes, yes, thank you. So if it's not a software specific you keep the one that is already there. Yes, the presentation was very interesting and also the paper that you shared in the note. Yes, yes. Thank you. Thank you. Glad that you liked it. And I see also Liz is happy to help testing. Good Liz, I will be contacting you after. Roberto, does that mean that you are also keen in testing it? No, I'm not. I'm not candidate. Thank you. Yes. Thank you. Right. And I see in the chat. Martin, software is often depending on many factors which we can't fully control example software versions of cloud service, etc. How would this be handled in the SNP software management plan? Questions around resource constructions costs for running would be helpful for others who plan to use the software. Yes. So, again, software management plan is not something that is stabilized let's say it's not that mature as the data management plan. And many discussions are happening even these days for what a software management plan is. And if we some even argue that we might not need a software management plan we might need an open science plan or an outputs plan to incorporate everything to keep everything in one plan. So yes, so it's something that is not mature enough. Through we are involved in discussions that intend to provide some sort of standardization to this concept of software management plans. And next month, we are going to have a workshop where we'll try to see how the software management plan, what are the elements that are suggested by different organizations and initiatives like the institute that we showed, like the elixir software management plan template and other sources, and see what are the commonalities and try to provide try to also expand the standard for DMPs around that. So, we're getting there, but we're not there yet. However, these are questions around research conceptions because I will make sure to bring your your point about the research conceptions of course for running to this discussion. And I can contact you and keep you in the loop around that if you if you I mean if you want. Good. Anything else so what what what do you feel. You also feel that it's a very foggy. A very foggy concept. Right. Well then if that's all thank you very much that was short. I will be contacting you. And you will, I mean we'll talk next month in the next community call. And if the release is before that I'll let you know so that you know when the checklist is available and you can use it. If there are no other questions which I'm really happy to stay and answer other questions or discuss other things apart from the main point the main topic. If there are not then I'll see you all again next month. And have a good rest of the day.