 Hi everyone, nice to see all of you here connecting to our Argos community call, the one before the last for this year and this time we wanted to present to you something that is going to be introduced in Argos. It's something that the technical team has been working on based on our feedback, your feedback. We have given this functionality the title of blueprint because this is what it does. It creates let's say a blueprint for how you want to use Argos in the context that you want to create your DMPs or software management funds or other Argos management funds. Without further ado, let me share my screen to see what we have today and get familiar with what we have today and what are the points that this blueprint addresses so that I show you then what changes and an example actually to see it in practice how it will work. Please feel free to unmute. This is not me presenting, this is everyone getting together and seeing something, wanting to discuss particular things based on our topics and what we are experiencing, our ideas. Right, let me change my screen. Perfect. Can you see my screen? Yes. You cannot see the panels or you can see them because I also have the panels of the Zoom meeting. No, we can see just Argos data management plan, the website in the home page. Perfect, great. Then this is what we have today. Argos was designed initially to support the community of open air since it is an open air service and open air primarily let's say not primarily but traditionally has been supporting the European Commission which is a funder and other national funders into their open access and open science journey. This is why the Argos service was centered around that. You can see that this is very evident when you click start new DNP and start wizard. One of the things that you are called to describe is the funding information. This is something that we had exactly as I explained because of the because of that prerequisite. But it's very good that many, many institutions have started introducing DNPs in their policies and their data management policies. Now we have a growing demand of DNPs to be created that do not only serve funders. This is very great. But how do you do that? How do you bypass this, for example, funding information that you see in Argos? So far you couldn't, right? We had many feedback from you indicating that this should change. Some of you wanted more personalized things here. We gathered all this feedback and we found a solution that could benefit, like could be of benefit for different cases, different use cases. And what we did is created introducing a new concept, the concept of blueprints, which gives you the flexibility let's say to create your own structure of the DNP. Not only the template, the template relates to the contents of the content is as, you know, as you were used to creating the template with the questions and the different sections and descriptions and everything. But what you are now able to change as well is this. And you can do that by being administrators of the tool, not as a simple user that logs into Argos. And what you can do is, for example, if you don't want funding information, you can bypass it. And if you want to add more sections here where all the main information of the DNP, like the title, the description, the people that worked on that, if you want more information than what we have, you can still change it. You can shape it as you want. How to do that is by, now we can change the title to show you how you can do that. So you can now use the blueprint to do that. And you can see now on the left hand side of my panel, there are some new things, the new functionalities. One of them is blueprints. I click the blueprint. And I can see the collection of blueprints that I have. Let's say that I want to create a blueprint for an institution. I click create. I add the name of this blueprint. For example, let's say Athena Research Center, which is my institution. Blueprint, let's say blueprint. Or I can, it's up to you how you want to code. And now I can start shaping it, adding some sections. For example, I still want to be able to have a title, a description. So let's say that I also want the main information that are the metadata of my DMP. And I can add a description to this section to provide more details on what this section is about. And I can select from the system fields. There's a dropdown here, system fields. I can select what I want to use from what I wish so before. These are some system fields that you can now instead of having them statically there and cannot change it, you can now take them and use them where you want inside the blueprint. So these static fields are title, description. So before research, organizations, language of the DMP, contact for the DMP funder, grant and project, license and access rights. So now let's say that I want to create my main, let's say the first section, which is the main information with the title, description, the researchers and their organizations, the language, the contact, I still want them, but I don't want the funder because this is, let's say, an institutional aim. It's not the horizon, Europe, for example. It's something very internal. And then I can also, yeah, let's say that I want this title, description, I can give it a label instead of title, I could give it a name, I can label them as I want. Description, for example, for description researchers could be affiliates, for example, if I want now to change how the name appears instead of researchers, organizations, same, I can change it, language, I can give it another label and contact person, for example. And so every system field should have a label because this is what will be available to the users when they will select the blueprint and start adding their input. And we will see how this will look like in a minute. We can have a placeholder for the text that will, for the, let's say, field that will open so that it provides, let's say, a guidance to what input should be completed. And similarly, a description of what this field is about. So this should, this will go, the label is the title of the field and the description is below the title, providing some guidance. As you can see, you can select if you want to have these fields as required or not. And you can also, well, if you want to delete something, for example, if I made a mistake here, I can delete it from here or the whole section, you can delete it from there where the delete button, the delete icon, sorry, appears. Okay, let's say that I'm ready with my main information section and I want to continue with my next one. In my next section, I want it to be about license of the BMP. So I give it this name. I can have a description if I want, but I'm not doing this now in the interest of time. And I see that all the fields that I used, I cannot use again. And that's because this is for the metadata of the BMP and they appear on once. I said that this is an institutional BMP, so I don't want to fund their grant, but maybe I want, for example, the license and the access rights for the DMP. Same thing, I give my field a name by using the label. So now I'm using the same name. And I can add a placeholder text or a description to specify the input that I want there. And again, I can make them required or not. I forgot to say here that let's say that my main information, since I don't have a funder, I want to indicate the project that I'm working on. Now I have the title, the description, but I have nothing. Of course, the description can have information about the project that maybe I also want a different field that specifies the name of the project. I can do that by clicking project. Let's say name. And now I have another field added in my first section, but I don't want it to be here. I don't want it to be at the end. I wanted to be, let's say, after description. So I take it, grabbing it from the bullets, and I'm placing it where it should, what I want, where I think it should be. So now we have a title, description, project, research, organizational language, but I'm fine with that. I'm happy with how it's ordered, let's say. The license in the other section, I'm also happy with how it looks like. And let's say that now I want to create something about the strategy, for example, right, something new that we don't have as we saw before today. Maybe I want to have a section that talks about the strategy of the institution, maybe, or the project. I can give my description and I can use this add extra field button. And when I use this, this again, some fields with a label with a placeholder and description appear, but now they're not fixed as before, but they are open for me to use them as I want. For now, we have only those four options. So these are text, rich text, date, text, date and number, but we are planning to have an upload. So for the cases where you want to upload a logo, for example, and other options here. Let's say that I want the rich text. The rich text comes with those fields and Argos come with the editor on top so you can create, you can use them and you can modify the text, create bullets at hyperlinks and so on. So I click rich text and I want this rich text to be, for example, about the policy. And I can give a description for this policy. Please provide the link or the details of your policy. I can have another extra field. I can have as many as I want. Again, let's say rich text area so that I give the end users the opportunity to add and describe their policy, maybe their project activities that support this policy. And I can again provide them with a description. Please provide more details of how your activities relate to the policy. And let's say I'm fine with that. I have the data, so title, description, everything, the project name, the license, this policy and the project activities. And then I want a section which should be about the data management. Because now I want to know how the data has been handled in the context of the project that this user is describing. And I give my section data management. I can give a description again, but I'm not going to do that now, in the interest of time. And then I can choose the template that I want or the templates that I want the users to be able to use interchangeably with the data sets that they have. So those templates might be generic, like an institutional template or they might be domain specific, like some communities have introduced domain specific templates. So I can add here as many templates as I want, because these are what they, those that they will use, the users will use when I'm going to publish this blueprint. Let's say that I want data sets. And this is a test, this is that I'm now using. So sorry about that. Data management template for testing. This is okay. So this template, for example, is for data management. So it has questions and instructions and everything catered to data. But let's say that I don't want only data. I want also to describe software. You could do that even today in Argos, but now we can shape the blueprint in a better way so that it's more prominent where software information is. I can create another section calling it software management, without typos, in the description and then maybe selecting some software templates that I have. And I have one, for example, is from the Elixir community, the software management template. And let's say that I also want the software system ability institute template. So that because there are different, you know, different approaches similar, but, you know, with differences and they have different questions. So maybe I want to add here both, so give users the possibility to choose its time, which one they want to use to describe software. And I think that's it. I'm fine. I gave them the opportunity to add data software, the strategy and all the metadata that we need for the DMV itself. So I'm going to save it. I can now see it in under the DMV blueprints collection. When it's in draft, of course, those of you who are a template editor or admins and are going to know that when it's in draft, it's not available to the researchers. But if I finalize it, it will become available. So let's use it now. Let's see what we created. It's good. And click start new DMP, start wizard. Now I'm asked, as you saw, the page changed because the only thing that we want now every time is the title in the description and the rest changes. So the title can be DMP for Athena Research Center, for example, project. The description can be description. And then I can select my blueprint or I could actually use a default blueprint that we have here. But we created it. So I'm going to use this next. And now I see how this blueprint is shaped. It starts with the title description with UCR pre-filled because I added this information before. It has affiliates that I can write. Organizations, license of DMP. Again, same again, again added. It has a third section is the strategy of the institution. There is text there that we added that they describe the policy and also make this a hyperlink, for example, to point to the specific reference, the research as a reference and so on. Same for the projectivities. For example, we can detail project activities here. Again, make this, for example, a list or use the header to give it a more, you would say, to make it readable and so on. And then after I have added the input here, I can go to the fourth section, which is about data management. I see the templates that can be used here. And I can start adding my content relevant to the data management templates that I have in my blueprint. So, same here as you know before, manually or pre-filling the information about these questions on the template. So let's say pre-fill and I pre-fill like a data set. This is, this field calls the opener graph. So you can search all the data sets that are available at exploded opener.eu, which are not only from Xenoda, but from different data repositories and also available at re3data. Let's say that this is the data set that I want. And I'm pre-filling it. And now I can see, as I would do before normally, go through the different sections of this template is about the data management and answer the questions as I would normally do. Save it, for example, and then go back, wait, and then go back to add some descriptions about a software, for example. I can add a description for the software. Maybe I don't want to pre-fill this. I give a title to my description or artist for it. And I'm, I can choose which template suits me better at this time. Let's say the SSI is what I want to describe this particular software description according to. And again, I see the contents of this template. It's about software, what software will develop in the next, you know, what are the users and so on. And I can continue, as I would normally do, with completing it. And at the end, what I would have, let me pause, let me stop sharing, show you the download of the export. Okay, search screen. And then at the end, now I downloaded something that I haven't filled in the information. Well, I filled in some of the information. It gets in the funder, the grant, the research of the organization. So I can see the dataset descriptions. I can see, as I would normally see, and then I can see the software, the software section with the descriptions for the software. And this is basically how it works. Any questions? How do you find it? I think now we can open it for a discussion. And we're happy to know your thoughts, because again, this was designed because based on your requests and demands, and we're happy to know how you find it before we launch it officially. Maybe there are things for us, there's always an opportunity to grow. So we are happy to take it. Thank you, Alli. Okay, you can raise your hand and we can give you the opportunity to speak. Please let us know what do you think. Okay, Julia, hi. Another Julia, sorry, Julia Caldón. Hi, I'm always here. So nice to see you girls. Yeah, I have a couple of questions, actually. So I hope they are not too many. But as you know, Alli, we are trying to finalize our templates. So it's really interesting what you presented today. I think it's a wonderful job once again, and it will be really helpful for everybody. I have a few questions, as I was saying. For the dataset template that you inserted when describing the data management, would it be possible to insert more than one template, like the institutional one and I don't know, maybe some disciplinary ones so the researcher can both choose to use the one that we designed, maybe, or the specific one for his topics? That's the first question. And the other one is if you showed us that the system fields are kind of grouped by major teams, like the general information licenses, do they follow some sort of meta-data scheme or some standards for this grouping? Did you follow something or, I mean, do you group them, you inserted these information? Yes, thank you. Okay, first question. Yes, you can, this functionality remains the same. You can prepare, let's say, your grouping with adding as many templates as you want, disciplinary and generics. I didn't do it. I chose to do that example for the software, for example, but you can do the same for different sections. This is up to you how you want to use it. And then for the last question, which was about the grouping. Okay, that's fine. About the grouping. So the grouping you can do as you want to, this is what the researchers will see at the end. But we don't follow that. We have some required fields that maybe we could, hearing your comment, we could maybe make explicit that some of those are required because they should be always there, like the title of the description. Because these are exactly the mandatory meta-data fields. And I'll take a note on that to see how we can do that. But you can group them as you want, basically. You can add the license with all the other. You can have a meta-data information, DMP meta-data information as a section for itself without dividing them. Yeah, that's the idea. But thank you. We should see how we make more prominent which are required. Thank you. I have just one last question because probably maybe I missed it. But when we are designing a dataset template, we have this basic structure which is, if I'm not wrong, chapter section and then question, which is mandatory. Otherwise, we can't move on. Is there something similar for this part of the blueprint? Or we can just add one section and you were saying, okay. No, no. It's two different editors that say that the dataset or the description editor you can use as you used to. And then you can, once you've finished with that editor, which is about the content, you can go and see how you want to structure the blueprint itself. Perfect. Thank you so much. Thank you. You are Kim. Hi. Nice to see you. Hi. Sorry, I was late to the table today. So maybe I missed something, but it's very good to be here again. I just wonder, when you were talking about the system fields and the extra fields, could you make some of those repeatable? I mean like researchers or organizations, for example? So the system fields are those that correspond to the metadata. So they can only be used once, but if you want to have another field with this or researchers, for example, you can add it as an extra field. Extra fields can be used several times and give them the title of researchers, for example, if you want to reuse something in that way. In the future, we're going to have, you know, not only free text options as an extra field, but also APIs there to select, but at the moment, we don't have that. Yeah. Thank you. Thank you. Okay, I see one question in the chat from Caroline. Hi, I have a question. Hi. I don't know if you already mentioned this, but does the system automatically alert me when there is a discrepancy example since it has been collected process, but there is no consent for uploaded? No, that's outside of the blueprint discussion, but thank you. Thank you very much for sharing it. You're talking about notifications sent to you as with what role, what is your role, for example? Are you the DMP author, the data decorator of the DMP, the librarian, or the data steward? Okay, okay, as a data steward. No, at the moment, you are not notified about this, but stay tuned for 2024, because in April, things are changing dramatically on that aspect. There are notifications, correct? Yes, that is the yes. Thank you. Overall, again, do you think it solves the issue of being able to have more flexibility and skipping the funder if this DMP is created for a different case, or even a training, maybe a training activity where you need nothing, just a plain field, or also for things that are not DMP specific only? Because again, we see that the landscape changes, not only data sets are now, although data set templates exist, but software templates, and there are questions also, and things happening around other outputs, templates, and so on. Do you think that that pops? Oh, I see a question in the chat. Hi, David. David asks, can ARGUS be used also for transnational access programs? There's no, let's say, limitation for what you want to use ARGUS, if it has the templates that you want, or even if it doesn't, we can create them. We can work with you to create them. And if it works as you would like to, of course, you can use it. Yeah. Okay, Julia. There is also a question from the third document. Thank you. Thank you, David. Happy to work with you on that further. Pushing from the side, great. We can construct a blueprint by reusing bits and pieces. Nice. Suggestion, introduce some info by hovering over the various bits one can choose, so we have an idea of what is used. Introduce some info by hovering over the various bits. So I'm not sure. Maybe go live if you want to speak. Thank you, though, for the suggestion. But yes, it would help if you could explain a bit more. Oh, she's in Africa, don't worry. No problem. If you can add on the document just a few lines of where exactly you think this is about the sections, where is this about? That is sort of a shortcut to give an overview of what the bits consist of when you choose them. Ah, okay, not really. Okay. Yes, I see what you mean. Okay. And that's not it. Thank you. Anyone else? What are your thoughts? Do you think it solves those issues? Yes, Teresa. Hi. Can you hear me? Yes, but not that well, I think. Well, thank you. That might be a bit off topic, but I presume that might also offer an option to add funders that are rare, small organizations. I think, sorry, you can't hear me. I have troubles hearing, I don't know why. Okay. Teresa, maybe you can type on the notes or maybe it sounds from me that there are workers and probably try to speak again. Oh, it was only me, because Dita could hear you. Can you please try again? Can you please try again? Maybe it's me, sorry. Teresa, can you hear us? Yes, I can. Do you want to try again? Maybe we can hear you, because some people heard you, so maybe it was me. Okay, could you use this? Thank you for adding that in the chat also. Could you use this feature to add funders that are rare, such as small private organizations? Yes, you can for sure do that, because you are right. At the moment, Argos has a certain collection of funders, and these are funders that we also work in OpenAir. So we have, let's say, their data, because they have monitoring dashboards and so on. And yes, so that way you can use it to add more funders here. Yes, for sure. Thank you. And I like to see you find more, more cases where you want to, how you want to use it. That's beautiful. Thank you. Any other question, feedback? Something you would like more clarification on? Okay then. We have our next and final meeting planned for December 13th, for obvious reason, because after the last Wednesday of the month, it's the one that we should spend with family, probably around the table, eating and drinking and having some good time. Yes, so we planned it for the 30th of December. I hope to see you all there. We will have more things to share, maybe a blueprint, an actual blueprint, a real case, to be presented also. Thank you very much. And yeah, see you very soon in a few weeks. See you soon. And if you would like us to tackle a specific issue, please feel free to contact us and suggest some topics. So don't be afraid. It's a co-creation activity here and the community call is to involve you even more in our services. So thanks for participating today and see you soon. Always, yes. Thank you, Julia. Bye, everyone. Thanks, everyone. Goodbye. Thank you. Bye.