 Okay, hi everyone. It's just after one, and I just wanted to welcome you to the webinar on streamlining your research workflow using OSF and storage integrations. Thanks for joining us. We're really excited to bring you all in and explain a little bit more about using the OSF and how you can use them with other tools that integrate directly into the OSF. So hopefully we'll be able to talk to those that are seasoned OSF users that are using the OSF as part of their research workflow, but also to those that haven't haven't yet joined the OSF or thinking about it or interested in in the OSF and how it could support your, your workflow needs. So just a quick background on on the on the Center for open science. We have a mission to increase openness integrity and reproducibility of research. We're a nonprofit organization that develops open source code to support our infrastructure and it's our tool is free for researchers. Let's see my work. So our organization has three main pillars. One, the first is policy where we work with organizations to develop incentives to embrace the change of open science in the research culture. The second pillar is research to do our own collection of evidence to evaluate how the change is progressing. And the third is infrastructure to develop and maintain the technology to enable the research culture change. So you've probably seen this, this diagram before looking at how a culture change can take place. This first step is is looking at the innovators who will quickly adopt new and exciting innovations. And then you start to have some of those early adopters and you'll move through this curve to add more and more folks to this culture change adoption curve. And one of the things that we do at COS is really put our areas of focus and effort against that so that we can support that culture change and everything that we do. So the first is to develop the infrastructure to make it possible for those innovators and very early adopters to embrace the changes and have the tools they need to begin to conduct that in their workflows. And to enhance the user interface and the user experience to make it easy to really meet researchers where they are and to reduce the burden as much as possible. The next is to work with communities to make it more normative within your community to see more of your colleagues taking on these new practices in their workflow and making it more normative. Next is to make it more rewarding to provide incentives in the research ecosystem that support those that are taking on this new process change and then to have the policy that enable this to be more of a required activity among everyone so that there's equity in the practices. So that's just a quick background on COS and the work that we do. And I just want to go through really quickly what we're going to cover in this webinar. So next we're going to work into the OSF and we're going to look at sort of the OSF project space and going to demonstrate it for you and show how it supports the entire research lifecycle. Again it supports transparency collaboration sharing and reusability of research. Then we're going to look at OSF integrations in the landscape. There's several different types of integrations that the OSF supports. And we're going to hone in on the storage providers specifically for this webinar but we want to make you aware of the others. And that the OSF has a public API which allows community developed tools to easily interoperate with the OSF. Then we're going to look at the different specific provider integrations give you a little bit more about the technical overview and how we work with the community to develop what are the priorities within those integrations on the OSF. And then we'll look at demonstrating exactly how you could use an add-on in your workflow and we've got some use cases that we want to share with you today that hopefully help identify some of those areas where it might also work well for you. And then we're going to show you how to kind of evaluate the different add-ons for the different types of functionality that are supported in the OSF that might also help look at what might work best for your workflow. So I want to leave this slide up for just a second to give you a chance to get this link on the OSF because this is where I'm going to be showing you the demonstration aspects of today's webinar but I really encourage you to go here and follow along with us. And it's something that you can look at after if you're trying to think back on some of the things we talked about and implementation into your workflow. This might be a really good resource because there's going to be lots of examples here. So I'm going to leave this up for just a second. One of the other things I wanted to mention about just the operational of the webinar today we encourage you to write in in the Q&A box. Any questions that you have as we work through this you might think of very general questions about the add-ons in general or the OSF architecture or some of the workflows it supports or you may have very specific things about your project needs and how this could apply directly within your workflow. Please ask any and all of these types of questions. We're going to try to talk mostly general today when we answer those questions but the team is also on this call and so we will follow up with you on those very specific questions to help provide resources and answer any of those details so that you feel like you got what you needed from our time today. And so the next thing is that we're going to have some polls as part of the webinar experience today just to gauge a little bit more about what brought you here today what some of your needs are and so that we can again develop more community driven features and functionality within the OSF. So if you don't mind to take a second and answer some of these polls as we go along if you're if you're willing that would be helpful. And I think that's it so I am actually going to stop sharing the slide deck with you and pop over to the OSF in just a second but in the meantime if you don't mind taking that. So I'm going to give you some of those polls to give us a little bit of quick feedback that would be appreciated. Okay, you're doing that. Thank you. I'm going to get ready for sharing my screen. Okay. I think everybody can see the OSF project that I have up. Yeah. Okay. So we'll leave the poll up maybe I don't know 30 more seconds to make sure everybody gets an opportunity to put in their, their feedback. But in the meantime, if you can navigate to the GUID that I shared earlier. This is a public project on the OSF that we use a lot for demonstration and and webinars. So it's something you can refer back to any time that you want. So a couple quick things about the OSF that I just want to give as a, as an overview. The OSF is a collaborative management workspace. It should support every aspect of the research lifecycle, all the way through planning and managing collaborations access permissions to conducting your research, sharing specific data and data sets and other resources and materials, either within your collaboration team or publicly with others. And storing those things on the OSF or in one of the integrations that we're going to talk about soon and then the aspects of pre registration reporting your outcomes disseminating sharing scripts and pre prints to finally discovery and reuse of the shared materials. So so that's it in a in a really broad stroke kind of sense and so here is the much more detailed aspects of that with, you know, a populated OSF project so I'm just going to do a quick tour we can always answer specific questions at the end about the OSF community, but I really want to get into the integrations and those workflows specifically so I'm not going to spend too too much time on that. So at the top you can see this is a new a new project that I've created and I've given it a title. I have some metadata that I can add to my project because it's public when others discover it they can learn more about my project if I add a description. I've licensed this project so that it's very clear how the materials that I've made public can be can be used and reused in the future. There's a wiki space that allows me to share even more content in detail and there's lots of great functionality within the wiki unfortunately won't have time to get into that but I encourage you to explore that for great ways to embed files annotate and share specific resources within your team or with others publicly that might visit. But we're going to look at contributors just because this is one of the very first steps that are really important in setting up your project space, realizing that the OSF project space is very flexible and it allows you to create the structure that works best for whatever your research needs are. So I have added some collaborators but it looks like I've got others that are requesting access so I can add them to my project and this is a really nice feature because it allows you to share with those that you think you're going to be working with but always be open to others joining and collaborating with you and in adding people you can select what type of permissions you want to give them. There are three options which if you ever forget what what what they can do I love this little question mark icon that you can hover over and you can see that. So looking at read they can see the content and comments read and write actually have a lot more access to add and configure components and edit contents and administrators can do all of those things plus manage other collaborators and register the project and also be able to turn something public or private. While this is kind of in the weeds what's important about this is that the OSF project structure allows you to create components within a project so you can see several over here on the right literature review materials data and analysis scripts these are just example components within this project structure but for each of these I can determine which collaborators get access and what level of access they get. I can also decide if these if these components are public or private. This is really important when we talk about integrating with specific storage providers and so hopefully we'll get into the details about that but I just want to point that out right now because if you connect for example your S3 bucket into your data component because that is how your tool is set up to spit out data. You can keep that component private until you've done analysis and anonymize for example that data and put it in a more publicly sharing format. But all of that sort of gives you the quick overview of the way that you could structure the project and be able to control the access to the materials. Another important aspect for collaboration is that there's an activity log on every project which means if several of us are collaborating on everything within this project including the components I can see all of that activity when I come and view the project. So that that means that you know different people can be do be doing different aspects of the work at any time and you can stay up to date with what's going on. You can also set notifications in your settings, allowing you to get notifications about the project activities. So if there are file activities files updated you can set a notification that'll send you an email and let you know who did what and you can do that across your components as well. I find this really handy, especially when I'm collaborating with other members of my team to make sure that I keep up to date with what's getting done and what you know what hasn't changed recently. So I think next we're going to move into the add-ons section. This is obviously the main focus of today's webinar. But here you can see where we have two different types of storage of add-ons. One is citations. So we have integrations with Mendeley and Zotero allowing you to manage those citations and keep track of different things that you've saved in your different Mendeley or Zotero folders. We're going to get into those in real detail in just a minute. I just want to give you a quick overview. And then we have storage. There's 11 different storage integrations with the OSF which allows a lot of flexibility in where you might already be working and allow you to connect that directly with the OSF. And what's really great about the way these integrations have been created is that they allow interoperability. So when I connect my Google Drive, if I make an update by adding a new file to that specific drive folder that's connected to my project, it's automatically reflected in my drive if I were to go directly to the drive. And vice versa. So they're synced together, which is great. And it also means that if I'm sharing my Google Drive in this project, a specific folder, I don't have to share that drive folder with you. Because I think we're all familiar enough with Google Drive to say that I could share that folder but I could also just connect it to the OSF. And I'm doing the same thing, which is really nice. You don't have to think and go outside and do these extra activities. It's all done within the OSF, which makes I think the workflow much simpler, much more streamlined. And then the last part I just want to highlight is, again, one of the reasons we asked the polling question and something I just want everybody here and even seeing this recorded after the fact we're always interested in hearing from our users about what integrations would support their workflows. That's something that, you know, we put in these because these were the ones most wanted by our user base, but there's certainly, we understand that things change over time and that new tools are being developed and, you know, updated in ways that support the workflow much more than maybe they did a few years ago. So that's the kind of feedback that we're always interested in hearing and so I encourage you to share that with us. Our roadmap is very much community driven through our funders and other ways of support. This is the type of enhancement they want to see to the tool to make it more usable and meet researchers where they are. Okay, I think we have one more. Now we have several more polls that we're going to go ahead and put one up right now. And I think Fitz, who is a member of our engineering team who has worked a lot on these integrations and making them possible for OSF users wanted to share a little bit about the technical architecture behind it and what, you know, what makes it so interoperable. So I'll turn it over to you, Fitz. Thank you very much, Nikki. Well, so the core of our file storage transfer system is a system called water butler. And what water butler does is it essentially acts as a translator between the external provider that we're trying to connect to like box or drop box. And into this kind of neutral language that we designed. And each provider that can connect to water butler, that can speak water butler ease, can then speak to anybody else who can speak water butler ease. So that in that way that's how we can make it so that drop box can talk to box and box can talk to S3 and S3 can talk to Google Drive and they can all talk to OSF storage. When we're designing or when we're approaching a new integration like this, the key things we're looking for is how do we manage to do authentication. Because that's a big part of it. If you want to actually connect something specific to the OSF, it usually wants to be something specific that you own. So the provider has to be able to distinguish users and provide some sort of mechanism to securely authorize users and allow them to get access to their files and folders. That's pretty common, but not all providers do that and or not all providers do it well. We've actually had a few that we've investigated where that just ended up being the deal breaker. The way they supported or just their lack of support for that made the integration infeasible. And then the other big thing is we need documentation that describes how you sort of programmatically interact with the files and the folders on that service. And again, most of the big ones are really good about documenting this. If I want to find out how I can, you know, delete a file on Dropbox, they've got a nice little web page that describes all that. And then when I'm writing the provider, I can just take the bit that says, hey, the command to water bottle that says, hey, delete this file and turn that into some things that Dropbox can understand. What we can do with that is going to depend on each provider. Some things like revision support, some providers support revisions for files like they'll actually keep a history of all the changes made to the files. Other providers, I believe on cloud as an example, it's not really support that. So the actual subset of things that we can provide is going to depend on the provider. But again, that's something we look at on a case by case basis. Our best supported providers let you do uploads downloads deletes, move copies, we can download entire sub directories as ips and get revision information, all sorts of really fun stuff. And so if there's a service that you're interested in connecting, that's essentially the first thing we have to do is we have to look at that check verify the authentication component. Look at the file communication component and just make sure they're both up to spec up to stuff. And then we can start writing the provider. And that's just kind of the general structure of water bottle. I think at this point I'm going to turn it over to Eric, or is it Nikki, apologies. Nikki, sorry. Yes, I'm going to turn it back over to Nikki. But thank you very much. Thanks, that was a great overview. I could not have explained that. That's awesome. Actually, Eric's going to get back into the demo he's got his screen shared, and he's going to walk through some of the use cases that we think might resonate with you all. Thanks, Nikki. So, I'm going to pick up where Nikki left off we're going to stay in the same project so that you continue to use that link that we dropped in the chat and we can share again, if there's new folks didn't get to pick that up. And so you can continue to, you can reference us later. And we'll tell a little story here and this is not just one that we've sort of made up but rather based on the experiences of many members of our community that have shared their stories and the whole reason that we we build out integrations the way we do is based on those experiences, learning from researchers and members of research communities. So in this case, this project as we see it's been around for a few months and there's been some activity and Nikki shared a little bit of how the contributors have been added and components and structure have been added. Over time, we can see there's already activity and actually a couple of add-ons already attached and active here. And then I've been added and as part of this project I have some unique contributions to make I may have there's a, you know, a Google Drive folder, active here in a dataverse active here, but I have some activity that's taking place in different providers and in sort of opposing the the story that fits and told us not all of these providers talk to each other by default. So I think we're going to go back and forth over time by an activity in Dropbox that we're going to activate here in a second. By default, I can't just send those back and forth into Nikki's Google Drive activity, but on this OSF's collaboration space, we have an opportunity to bring those together without having a lot of downloading and uploading between hard drives and emailing files. As we were looking at just a moment ago, we can see that Nikki is attached or as connected the Google Drive add-on here recently to the top level project and I have another piece that I need to include in this project that I've been working on in Dropbox. So because we can see the Dropbox has not been connected here yet. In many cases, these add-ons are connected by using an authentication process so that both those providers, this case Dropbox and the OSF can identify that I'm the person and these are the accounts that I claim them to be. So we are trying to be very clear about what the OSF in this case is asking to do. It's asking for several permissions in this case to read and download files from these providers to the OSF. I'm going to go ahead and confirm that. And so now I have the Dropbox add-ons now available in my configurations here and there's no account connected yet, so I'm going to go ahead and do that. And as I said, anytime there's an authentication process, I will be sent to the provider to authenticate that I am the person that I claim to be. So I'm going to coincidentally using yet another authentication process through Google to prove who I am. Again, the OSF is going to ask for those permissions that were clarified before and step earlier. And now I have an opportunity, this Dropbox doesn't have a lot of structure to it, just the Dropbox itself that I'm going to choose from, go ahead and connect it. And so we'll see on our full list now we have the Dropbox enabled, we can disable it if necessary, but we don't need to do that right now. But when we turn to our front page of the project within our files, we'll still have the dataverse that was connected before. We still have the Google Drive files that Nikki connected. Now we also have a Dropbox folder that can be used to move files back and forth. In this case, this file is already on Dropbox. This happens to be a PDF of the slides we were just looking at earlier so that those are now available on the project to reference and download. When you start from scratch and the add-on is not been activated at all, you go through those authentication processes and now we both have the platforms where our files originated connected to our OSF account. We both interact with these now as administrators of this project without needing to have access to those native platforms. So I don't need to have access to Nikki's Google Drive folders in order to see this content that she's indicated as part of an OSF project because we've connected them here. So a couple other, one of the other advantages of the structures that Nikki mentioned earlier with components, there's the ability to have the difference contributors as well as permissions. And then we also have another opportunity to distinguish which add-ons are relevant to these different sections and something like a literature review. One of the roles in this project, age and political identification is to sync up the literature review that we've been working on with the project. This would be a pretty good place to do that. So I'm going to activate the Zotero add-on, which I've already have used before so it's available for me to connect. So if I import these, I'll again, like with the Dropbox, have opportunities to choose libraries in Zotero that are relevant to my work. So I'm not having to redefine all of my categories that I put together in Zotero. They're all going to be here and I can just choose the ones relevant to me. I can pick one semi-relevant to our themes. This is a bibliography I put together for the US Army Medical Research Institute for Infectious Diseases a few years ago. We're going to connect that one. And then when we return to our literature review, we will have a Zotero section, which will populate. Let's make sure we did that right when it has a new folder in it. There we go. We'll use an OSF prepped folder. Go ahead and connect that to our project. Now we have our citations will be listed. They'll list it by default in order that they were added to that library to that folder. And you can change the citation style as well that those will be presented in. So if I wanted a Chicago style to be the first thing that the user sees then that would be available. Or the first by default visibility that that literature review will have on my literature view component here. So now if I'm leaving our literature view component and want to move on to the analysis that we're doing a way of scripts for our analysis likely this is going to live somewhere like get up. So it's not in one of those providers that we've already connected. So in our now we're in a new component here doesn't have those previously added providers. We're going to choose get up again we have our confirmation of the requested permissions. And so what you see here is this pop up is in case the repositories within your GitHub account. For whatever reason their provider is not sending them to OSF and are provided in the list of options that we're going to look at here in a second. There is a way to quickly re authenticate those those permissions and I'll show you that in a moment as well. So with the other providers we get a list of all of your, your GitHub repos that you have permissions for within the GitHub provider, and I'm going to choose one that we've named specifically for this event. I'm going to go ahead and save that. And now among my files, my GitHub repo material will be included along with my other file so again that was an authentication process I didn't start from the very beginning that time but again if you use GitHub before it's very likely already authenticated with with other platforms that's very quick to give you seconds to authenticate those. There's also cases where you may have data being collected from, you know any number of sensors or or other tools that are being synced with with a storage provider that you're using something like S3 is good for that as an API that's good for collecting and and syncing data so that would be data from a source to Amazon S3 as a storage option and then we have an integration available with Amazon S3 into the OSF so through that extra link you can get your synced data included in your OSF project so like all of those other providers that use authentication we still have a trying to display and articulate all of the permissions that we're asking for on behalf of the OSF. Unlike the authentication providers this one looks a little different and this populated for me already because I've been using this but when you set up your Amazon S3 account instead of using authentication it will provide a key similar to if you've used APIs before access key and a secret that were kind of like a username and a password but specific for your account and your material on Amazon S3 so when I use those details specific to a OSF development S3 bucket that we've set up I now have the specific buckets within S3 that I can choose from and include in my project. Go ahead and save that and most of the providers do use authentication but several do use that a similar step with the keys as S3 does get lab being another example data verse similarly using key to define which projects or data verses or buckets are to be included in your integration but the end results we have our files included the same way we did with GitHub or Dropbox they're now included through the S3 add on so if your data is being synced from another source to S3 it can likewise be synced from S3 to your OSF account and then if like Nicky has added on the top level project of data verse object that in most cases if you're adding something from data verse those are finished products those are data products that are being continuously modified anymore but you may be using them as a reference where they are previous version of data that you're trying to replicate with this project maybe that's the purpose of this project. So if we were to pick one of our components to add data verse add on and enable that and if you have data verse with your institution. Then this will look a little different and you would choose a data verse that is at your institution so in a previous step I chose the Harvard version but if your institution has their own instance then you would choose that and instead of getting a list of all of the data verses that are on the Harvard data verse you would just get those that are at University of Virginia or University of Maryland where your data verse instances but I'm going to go ahead and choose a COS data verse when we set up for this and add that to our materials component and then that will be available and visible on our component so that we can reference that previously you finished and completed data that was included in this data verse repository so that's a quick look at adding several different kinds of add-ons for different parts of your research life cycle and as I've mentioned before there may be cases where like GitHub all of the repos that you expect for some reason are not visible when you're trying to add those to your component so to re-authenticate those we have in your personal, your account settings we again will show you all of the add-ons that you've already authenticated or set up and list the projects or components that they are connected with and so in a case like GitHub if I connected GitHub to this analysis scripts component for whatever reason it's really just not pulling in the repos that I expect I can use the connect or re-authenticate step to start that process from the beginning it will give me the permissions again well maybe not well it's very much wanting me to stay authorized but in this case where you need to disconnect this information you can actually disconnect these from both ends on GitHub you all likewise will show you a list of providers that you have authorized connections with that you can disconnect from and especially if you have changed or added a new institution or group in a case like GitHub you would need to re-authenticate those that connection so that you those new group folders or institutional folders would be available repos would be available for you to add to your project so one of the things that's as Nikki mentioned that is you might be thinking about as you're seeing all of these different options is list of things that are available to you some of them may already be using really obvious solution for your data needs or connections to your OSF project or they're available through your institution they have an institutional database or Google Drive provider but perhaps you're still thinking about what is appropriate for you and your projects so we have a on our help guides and we'll put this link in the chat that you can quickly jump in and take a look at this but in the help guides we've have guides specifically to help you connect excuse me each of those providers that we looked at today so similar to those processes that I showed you including reauthorizing some of those that have a clear reauthorizing pack path excuse me that we talked about we also have a page and this is a continuing to grow as we add new content but to help you think about these add-ons if you're starting from from scratch or you maybe have several options and you don't know which one would be best in terms of connecting and using for your projects we have a feature chart that will help you sort of quickly at a glance get an idea of all of the things that these providers are capable of in terms of how they're connected with the OSF so this link is in this add-ons help guide right here if you need to take a look and this continues to to change and evolve as we add new features and new add-ons new providers and this is a selection of the very many different variables that providers can enable and in some cases as Fitz mentioned some things they can't do or they can't do in a way that we could make work within our mission or within our policies but the chart here will give you an idea of what each of those features are and one of the things we provide and try to keep up to date is if you were thinking about starting an account with one of these providers so maybe your institution doesn't provide one or what they provide is not yet available as an OSF add-on then this is a quick look at what you can get if you were to set up an account with Dropbox for example then a free account you could have two gigabytes of storage available to you or with Google Drive 15 gigabytes of storage available to you at no cost you would need an account but no cost would be involved for those and then next to those another number here is if you are moving files from OSF to those providers there are sometimes limits for those as well that are set by the provider so in the case of Dropbox again if you had a paid Dropbox account that had more storage you can move up to five gigabytes of file size at one time if you had a 10 gigabyte file that was on the OSF somewhere that would not move over to the Dropbox your Dropbox provider gracefully and some of these are smaller limits than others and then among the other features that we have included in the chart here to help you make a decision about your providers is when those files are now connected to your OSF project are they able to be downloaded and the majority of those that is the case and then we also try to make file types many many file types render in the browser so that you wouldn't necessarily need to download a spreadsheet or a document in order to to read those from an OSF project they will actually render in the browser itself and when we start getting more variabilities things like if we have our add-on connected to the OSF and we start taking actions on those files that are connected in most cases if we're removing it from the you know that list of files in the OSF that it will also be removed from the provider so it mirrors the same content that's in those providers in some cases that's not the case so that if I remove the file from a GitLab project that I had set up if I removed in the OSF that's not going to delete over in the source provider there's also some things to keep in mind just in terms of if you had lots of collaboration happening and things are changing quickly being able to rename files some of these you'll be able to easily rename the files themselves and the GUID those URLs that are provided would change but the that file renaming would be enabled so you would just want to be cautious if those are things that are already shared and linked elsewhere and then the ability to do some of the OSF functions that Nicky mentioned like creating folders once you've already connected your providers in the OSF and several of the providers you can start creating structure within those those files from within the OSF interface so like with Google Drive when we have that folder that Nicky had already connected if she needed more structure to to do things with those files that would be something she could do from inside the OSF interface would need to do it in Drive to have it reflected in OSF and then also one of the things that we really are trying to do with the OSF has had lots of transparency in the process of what's all the activity that's happening on your OSF projects is similar to following the notifications like Nicky does for her team projects, you might also be interested in having a real clear version control of all of those files some of the providers will do a good job of if you were to update those files have new versions in the OSF that you would have both of those file versions available for users to interact with but not all of the providers will have that feature enabled so there's a few things that you might consider as you're evaluating for your personal projects or as a group, which of these providers might be most useful or most valuable in terms of how they themselves function and how they function with the OSF so that you have the features the most important features for your project are enabled. You know, without having to use things that aren't provided or perhaps using multiple add-ons is great as we've shown. But knowing what each of those are capable of will help you reduce the need of duplicating effort or we're moving files around. Instead, you can all have it connected to that OSF project like we do here with several providers, and we can all use and interact with those together as a group of contributors. One of the things that we've sort of talked about before is thinking about and continuing to evaluate new add-ons or add-ons that aren't yet included on the chart here. That's something we continuously will do. We take the community's needs and recommendations very seriously so as institutions or researchers come forward and tell us that they use a OneDrive for business, for example, that's something their institution enables. We don't currently work on the OSF, but we have partnered with an institution to build that integration that will be available early next year. And that's the sort of thing we would do frequently and definitely want to do more of, but we do that based on what the community is asking for and what they need and what they can partner with us to work on. So the more that you can tell us about your needs, whether we're already helping to provide for those or if we're missing a feature that would really help you use the OSF to the great extent possible, then communicate with us. So we'll put the support desk information in the slides and in the materials that we send you later. So please do talk to us about what you use and what you're interested in using so that we can continue to build those features for you. I think we're ready to turn it over to Nikki to wrap up and to take any questions and thoughts that participants have had. Oh, Eric, so much. Yeah, the last, I guess, 11 minutes that we have, I want to make sure that we that we get to your been leading into the chat there, the Q&A box. I'm sharing my slide. I can't, but just I'll do a really fast recap, which is basically a quick review. So we've shared with you the OSF project space can be flexible to being a cycle that the app has a grations already built into with citation managers and 11 different storage, there's a public API. There's a chance to really catch you, the community developed the API, but maybe we can drop that link in there too. And, you know, the demonstration in the use cases was really just to get you thinking about how you could integrate those storage providers or citation managers into your workflow using the OSF just to streamline the process even more. The last slide has a lot of these links and we'll make sure to pop these into the chat as well. So if there's anything in there that we haven't shared we do, but I want to I want to quickly move over to questions. And so what I think would be the best use of our last 10 minutes is to go to the Q&A box and we can read through some of the questions we've been answering as as the webinars been proceeding but make sure that we have some of our responses and then there's two that we haven't gotten back to answering might go ahead and take those on live. So the first is, let's see if you have privately or through your university like a pager box or unlimited university. Let's moving files. I don't my understanding is whatever capacity you have storage. You also really so that's correct to you. Let's see. Sorry, that's probably replying to the previous one. Yes. Yes, so you connect your box you basically Yes, when you connect when you connect the OSF to your drop backs account essentially the OSF is acting on your behalf. So it will respect whatever limits your are being imposed by that connection. So if you're connecting through your unlimited university box space then you have unlimited space on box. If you connect to a paid drop box then you have a paid drop box you or whatever the paid drop box limits are. And anybody else who interacts with that project anyone else that you've given right access to that project can copy files over there and again it acts on the OSF acts on their behalf. It doesn't give your credentials away it doesn't you can't it doesn't tell them. Oh, here's a username and password now you can go separately they can only do it to the OSF. But anybody but if I if, for instance, Alika and I were sharing an account and she connected through her box space. Then, if I upload something to the box, it would end up on her drive and be subject to her limits, not my own. Great. Thanks for that answer. I think you also answered her other question. If somebody turns on that box and already has lost a storage doesn't affect that. So then we can maybe hop over to a couple of the answered questions just to make sure we give these a little bit of time. One of the one of the questions that was was asked was about storage locations. And one of the things that we didn't, we didn't show you at the very beginning but we certainly, we certainly could is when you create a new project or component, one of the options. So what you're setting up that project is what storage location you want to use. This is for OSF storage, which is the native storage that's provided in each of the projects. And it's also provided through Google Cloud, and they have several different regions that we've connected and so those are options especially if you have those geographic needs for data storage. If you have the ability to support that, I think, likewise, some of the add-ons have the ability to support that too. So consider that as well if that's one of your constraint. Let's see. There are one of those additional questions and they might be close to me. They might be breaking up so I'm not sure what you said in there. I was just asking if you want to take another question from those that have been written in. Yeah, well, I mean, there is an additional question here that just came in a minute ago, talking about contributors is a little outside of our scope today but quickly mentioning and we put in the chat the top factor work that our policy team is doing, which is not specifically about contributors but acknowledging that there are many kinds of contributions to research and that is not just a paper even when a paper is published that there are many research objects that should be included with those as well. Yeah, so as we're in the last couple of minutes here we'll wrap up. I think that Nick made me just share that last slide again while you have it up. There are a couple of resources that are on the last slide there and you'll have those slides available to use if you need to actually get to those again as well as any of the things that we talked about today we'll have some links and the project itself that we use today will be sent to you via email everybody who registered but also if you have additional thoughts, questions, recommendations, feedback, please do communicate with us. I think the best is a good way to reach us just because that will sort of accumulate all of our feedback and knowledge. So that would be terrific to hear more about what you're working on or what you'd like to see added to OSF and there are more comments coming in but I think just so that we can wrap up, we will write back to to those of you that have sent more questions individually so that we can have a conversation about those questions, and we can let you go on time so thank you again for joining us for the meeting today and for all of your questions and your participation and very much look forward to seeing everyone at the next one so thank you again.