 All right, the chat is working folks are already introducing themselves as terrific and please feel free to do that. There's also a Q&A or a questions panel for you to use. And I think we will sort of review what those are here shortly. So, as a few people are still dropping in I am going to turn it over to Nikki to introduce the center and our agenda for the day. Nikki take it away. All right, great. Thanks, Eric. I am going to put the slide deck up for everyone. Give me one second to share that and begin the presentation mode. Okay, so hopefully everybody can see my screen. Obviously, pop in the chat if you're having trouble, but I think it's working. So again, welcome to the optimizing research collaboration for remote teams webinar we really are happy you're here and are excited to sort of share some insights and tips with you about how OSF could help meet some of these challenges. So a little background. My slides are progressing. Oh, yeah, now they are. Okay, sorry. A little background about the Center for open science the organization that Eric and I both work for. We are. We didn't actually properly introduce ourselves. Let me do that real fast. My name is Nikki by from director of product at the center and Eric is also on the team as a product owner for our institutional products. So, the Center for open science has a mission to increase the openness integrity and reproducibility of research. We're a nonprofit organization. And we do develop our own platform that's open source and free for researchers. And is an exciting one. We all enjoy spending our time every day advocating for open science and working towards a culture change. Our organization is built on three main pillars and those pillars are policy which develops incentives and policies to embrace change research to gather the evidence of the change and then infrastructure which is the technology to enable this change. So part of our mission open science adoption and culture change is is the end goal. And that's something we work on and monitor every day. You may have seen this sort of chart before of how culture change really does happen. So we're moving towards early on with innovators moving towards the early adopters majority late majority and then the laggards when you take this and you actually kind of flip it on its side and look at the criteria that really it takes in this in this climate to make that change in order. It's about establishing the infrastructure to make that possible. That's how you get the innovators really moving forward to create a user interfaces and user experiences that really make it easy for someone to come in and begin these workflows and sort of have lower burdens to entry and then using communities to make it more normative using incentives and policies to make it rewarding and required. So when we talk about this in the context of what the topic of our webinar is today about going remote. I think these are challenges we might all be facing. So some of those critical high level challenges are sort of this low bandwidth communication. We're used to being maybe more face to face and interactive with one another and so moving to channels where you don't have quite as much interaction. It's harder sometimes to pick up on cues and relay information the way that we used to also passive knowledge sharing is something that happens when we are in common spaces at conferences and other places where we get to learn and pick up information from each other. And so now where that's not possible. What are some ways we could still meet those goals using the tools available and obviously tools tools are the way in which we're going to have to do this work online and sometimes the tools might have gaps or there might be new areas of knowledge that you need to learn about these tools. And then the lack of organization and management of our of our projects actually makes it harder to work through some of the milestones remotely. So we're going to talk about sort of how we can look at solutions for some of those challenges using the OSF to manage some collaboration. The keys there is that OSF is already built in the value of being open and so it can help you get to more open practices just by moving some of your collaborations into the OSF. Also it has a lot of features that help with project management and so one of the challenges was being organized and able to collaborate so using OSF can help ease some of those burdens. And then lots of different workflows that you might be trying to manage with all your different collaborators in different areas and so there's a lot of features within the OSF on collaboration and managing your teams and access and permissions to to content and files. So we can talk about how that works and demonstrate a little bit of that to you too. And then the other couple areas we want to spend some time on is the versatile wiki. This is a very underutilized sort of feature on the OSF and we've we've got a lot of creative people out there that have used the wiki to solve some of their workflow challenges and are using it very effectively and so I think we'll look at the diverse features because maybe there's new use cases we haven't even thought of and some of you might see those features and come up with those. But then to also sort of illustrate a lot of those use cases for you and how others have used it to solve problems like electronic lab notebooks or online courses syllabi different things like that. And then lastly just looking at the OSF institutions product because it does sort of sit above projects and allow you to aggregate and maximize sort of the visibility of that project work, increasing your collaboration and communication sort of across teams. And lastly, we really, we really want to hear from you. And so one of the features of zoom that we're excited to to kind of bring forward here is the use of the polling function. And so, in just a second, I'll turn it over to Eric to kind of show you how that will work. But essentially, we'd like you to answer those questions sort of in this early period while we're talking. And then we're going to use those responses to help inform some of the use cases that we highlight because you're telling us that those are more relevant to you. Okay. Eric, do you want to talk anymore about the poll. Yeah, I just launched it, Nikki, so it should be, and I'm seeing responses come in so it is available and being voted on already. Awesome. Great. So let us know if you have questions about about the poll either in the Q&A or in the in the chat. Just, just keep responding and sort of giving us some insights. Okay, so I'm going to start to dive in a little bit to to the the overarching principles here of organizing research and managing files to do this. This is a little bit of an overview of some of the things I'm going to touch on. Just quickly hitting on some of the file features that the OSF has built in. Take a quick peek at Quick Files, which is a is a is a feature of the OSF that you may not have noticed is there and has some added value. So to look at how OSF projects features sort of work in different scenarios for collaborative team management and looking at management of collaborators and the project that is linked on your screen. I is going to be the one I'm going to be using for demonstration and we will make it public so you can also explore some of the content there. I'm going to quickly stop that so that I can hop over to the project. Let's see. So real quick. I'm assuming everyone can still see my screen. And I will turn my project public, which is a great demonstration of the first parts of project management, which is being able to create a project in the default privacy private mode, which allows you to do, you know, your work in a private setting if that's of interest, but then to also make it public when you're ready. So I'm going to make it public now so that you all if you would like to go to that URL. So I'm going to go from 4338 to also be exploring the project as I as I'm sort of walking through it as well. So real quick. One of the things about the OSF and projects and files that we've recently added is the ability when you create a new project to select from the storage location. From these four choices. So this allows teams across the globe to move the file storage that's native in the OSF to whatever location makes the most sense for them. So our current locations are United States and that'll be the one that is done by default. So if you don't actually open this and change it then it's going to keep it there. We also have Frankfurt, Germany, Montreal, Canada and Sydney, Australia. I just wanted to show you that real fast and I think it'll help as as you think about using this in your own applications but right now you're looking at the project for this webinar that will also use to illustrate some of the features. Right now I'm looking at my project overview page and I have already put some files in here so that we can look at them through demonstration but first and foremost I want to show you that OSF storage is going to be be there from the beginning because that's our native storage and when you when you select it, you can start to begin some of your file operations you can upload files you can create folders you can download and downloaded zip. I've already created this file and uploaded it so that we can we can begin to look at it. This is what it looks like when you look at a file and one of the one of my favorite parts of the OSF is that files from over 500 different file types and formats actually render directly in the browser. So this is exciting. There are lots of different research use cases where there are 3D files and step files and lots of dynamic imaging files and for the most part. The OSF will support that if you happen to discover one that isn't supported we're always interested in adding additional additional file formats here so just reach out and let us know. But one of the one of the main features that I like to look at here is the ability to look at the different versions of a file and the version history. And one of the things you might notice about this file that's sitting below the file we're currently looking at is called OSF file features dot txt. So the the actual text of this file is in bold that is a unread file update notifications so because this file is is bold. That means that one of my collaborators has actually gone in and made an edit to this file. And that alerts me to say oh something's changed with this file so I can go in and look at this file. And I would then be able to see what's changed and if I'm not sure what change because it doesn't seem obvious to me I can actually go to the revision history. And I could go back and look at the previous version and compare it to the new version. So that's that's some of the native file versioning functionality that's built in that helps when you're doing collaboration across teams when you've got a lot of people engaged in a project and working through the files and making changes and updates it's really exciting to be able to keep track of those in a really easy way the other way in which you could do that is to look through the project logs so in the project you can you can see that the different folks have done different actions on this file and I can go back to the very beginning and see those updates being made. One of the other things about the OSF that's really great for our collaborations is the ability to connect additional storage providers so in the in in that meaning you can connect anyone of the like 11 that we've built integrations with really you know easy you just you just authenticate in and then I can connect my folder from any one of my storage providers if I worked with Google Drive and wanted to connect one of my Google Drive folders I just import my my credentials and then it shows me all the different all the different file folders that I have in my in my drive and I can connect those some of these probably aren't good to connect but I can and just connect them as well. It's just as simple as that and when you do that they're rendering right there in the project and it doesn't it simplifies that workflow even more meaning that perhaps Eric and I are collaborating on this project but he doesn't have a Dropbox account or a GitHub account and that way because I do I can connect that and Eric doesn't actually need to make an account everything that I bring into the project. And I add him as a collaborator with permissions and whether I break that into just read access or read write he can do those same functions on those files as if he were part of part of that tool. All of the a lot of the tools do support version history. It's in some regard meaning if you change things over in in Google Drive or even here on the OSF the versions will keep in sync. Let's see other main functions just to just to run through real fast is also renaming files and folders is very simple you just highlight that file and you can see the functions are up here and I can type in and rename it very easily. Also moving and copying across different components, which I haven't shown you how components work but when I do I'll demonstrate that as well but you can move and copy files across that structure which sometimes is really great if you've got a file in a main project and then you decide you want to build more structure and move files around to prevent access from some pieces of your project work. One of the things to worth mentioning is that we have had several community developed packages that work with the OSF one that just like to mention quickly is the OSF client. So this was a community written command lined program package that talks to the OSF and allows you to programmatically upload and download files, which may be of interest if some of the other tools that you're working from need to to work with data and do additional analysis steps and then want to push back to the final the final pieces. Okay, so the other thing too is all projects allow you to meant a DIY so the the files within it could be referenced from that that same DIY if that was of interest. Okay, the other quick is the best word for this quick tool I wanted to show you also here. Sometimes you don't need to build a whole project structure you literally have one file that you want to share with one other collaborator or multiple other collaborators. And that's really easy to do by clicking on your quick files and every user on the OSF gets a quick files component within their account and so it's it's very easy to quickly upload and download files and also to share them so you can quickly share the files with others you can see you still get the version history parts of parts of the OSF file so it's it's a really neat versatile tool and I think the next level to this would be to move these files into a project and that's actually really easy to do it's just a click of a button, moving them, you just create the project on the fly. So if you just wanted to start with this and see if there's interest in collaboration and then move it into the project and add collaborators that way that workflow is is very easily supported so I think that's one feature that maybe folks didn't realize was part of the OSF. Okay, the next part that I'd like to just dive into a little bit is the OSF as a whole and the project structure and hierarchical sort of accesses that are in here. Take it back. Sorry. Okay. So this is a top level project that we're using for demonstration but what could be done here and I'll just talk through a few examples is is the addition of components that will help you sort of break out the files and add more structure. So I can quickly add a new component. I might call this one data because I know I'm going to be collecting data as part of my example here. I can choose a storage location that's different from the project maybe my data is actually going to be collected in the EU and so I want to make sure that that data is easily, you know, accessed from folks in the EU and put my storage over in Germany. So you can do that you can also easily add the collaborators that you had on the main project by just checking this box and the same with the tags will also inherit the license that you have on the project, but you don't have to. You can leave those unchecked. So when you create this new component you're given the choice to either keep working where you are make more components and build more structure or go to the new component. So when you do this. One thing you'll notice is that it literally looks like the project the only difference is that now you've got this relationship of sort of a bread crumb and a nesting. This means that this component has all its own unique title contributors. It can have its own license, it gets its own wiki, it's still related to the original project but you do have the opportunity to kind of customize this as you need. And so one of the things that is important here is to look at who who I'm collaborating with in the privacy study so for this I've made the project public but my data component is actually private one it's private by default which is the way that OSF works but also I may decide that the data isn't something I'm quite ready to share or I may have privacy or security to manage within that data set so I don't really want to make that public right now, or ever, and that's totally fine. But I may make another component for analysis and connect my GitHub repo and put in my analysis scripts, and therefore I'm sharing publicly with other researchers and able to collaborate on my project maybe on my analysis. If I made a pre registration that's something that would be there to that I could collaborate with others about. So if I look at adding collaborators now this is some of what I think is is really great about the OSF structure first of all I can add new I can add new collaborators really easily I can search for them. They happen to have an OSF project or an OSF profile already built in, I can see that this is another version of me that I'm going to add to the project, and I can choose what permissions to give. And so the breakdown is that an admin is someone that basically has control over the project is able to change the settings of private private Republic is able to manage the contributor list and create the only links they can delete the project they can register the project. And then there's also read write read write has a little lower permissions but still can do a lot of collaboration they can add an edit content content they can add and configure components. They can collaborate on draft registrations and then read users are able to view the project content and also to comment on aspects of the project using the commenting feature. So I'm going to add this person as we write the other thing to point out is non bibliographic is is an option as well so meaning bibliographic they would be in the citation and listed on the on the front page of the project as a contributor. And non bibliographic would mean they wouldn't be, but they still have access to all of the project contents depending on what level permission you give them. I can also select when I add a new contributor which component, what parts of the project structure I want to give them access to I don't have a really robust structure here but if I did. I'd be able to go all the way through all of the nesting and the components and decide which ones I want to give. Nikki in this case access to right now I'm only going to give access to the top level and leave my data still just with me. Just below that you'll see this section that's called request access. This is great because this project was private to begin with, but you can still do this with public projects as well. This takes somebody who maybe is just viewing a public projects and allowing them to actually be a collaborator and listed as a contributor and create components depending on what permission level you give them so Eric's asked to be a member of my project and by default it's going to just give them read access but I decided that I think Eric should be administrator as well because he might need to do some additional functions on this project so by doing that I can click add. And you actually get moved up to the contributor list above. And now Eric has permission to come in and do things I also have another one here. And I can certainly give folks additional permission and if anybody else wants to join the project and welcome to request access. The last sort of collaboration contributor management function that I like to talk about is view only links. View only links are kind of a neat thing that allow you to give out a link to your to your project and this could be in definitely a private state. For peer review or other types of open or blind review. And so by doing this I can name my link. And you know peer review for journal a so that and this one's not blind so I don't need to anonymize my contributor list. And I am going to give this link access to the data. So if I were to share that link anyone with the link would be able to come in and look at the project and look at the data component. So I can share and it's really easy to take it and share that you know copy that to your clipboard and paste that into an email or anything else to share. The other thing is, I can also decide when it's time to stop allowing access and so I can delete that link and know that anybody with that link would not be allowed to access my project any longer. I think that is a good start on some of these. I'm hoping to kind of see some of the feedback and there's definitely more use cases that we could get into. And I think Eric is going to maybe jump in and try to show you around the wiki a little bit. I am going to turn off my share. Over to Eric. Thanks, Nicky side before we jump into the poll I have a few questions here specifically about storage so that we hand those to you. So, it's and has asked if there's a way for or SF stores to sync with some storage on their desktop. Without the use of add ons. That's not that was a project we were thinking about, and actually did do a small implementation on a long time ago but right now we don't have a desktop client for syncing. You could use the client, the command line that I talked about, and probably upload files from that directly to your OSF projects. That would be the only way. And then how much file storage is available per user. Right now it's unlimited. It is something we're looking at for cost mitigation strategies. But at this time there's there's no limit. Okay, I'm going to take one more here. So you would showed us a little bit about how the nested components work and how permissions might work in there. If I wanted to have a component data that a private data component and then two sub components with one being private and one being public with that work. That would work. Again, each component has its own sort of set of privacy and contributor management so it is totally available to be unique from the rest. All right. Thank you, Nicky. So I'm going to share the results of the poll that you have all been taking a look at and working on. And we will come back to some of these other questions and thoughts so we're not gone forever from those. But we will look here at a few of your responses to these just, you know, broad questions. And then we'll look at a couple of use cases based on this that may answer some of those questions that you have already. We had asked based on your experiences over the last couple of months or maybe even before that, did you describe your primary collaborative projects so those that your faculty or stakeholders are most involved in. We have a little bit of everything here with many answering that they are working on on collaborative ways to do data management planning and compliance as well as research teams that may be across campus or across disciplines. So that is something we will take a look at shortly. And then we did ask how you feel the research collaborations have been impacted recently and I think this is probably not a surprise that for the vast majority is at least been impacted to some degree if not significantly. And then we did ask what you found to be the most significant barrier and there are probably many responses to this question that we didn't even anticipate here. And we did get a little bit of every response here with almost half responding to both to lack of communication project management and organizing project materials. So hopefully we have sort of started at least to look at a few ways we the OSF can can help with a few of those things. And in mind, let's jump forward and look at one of those other resources that the Nikki mentioned, that is, it accompanies all of those OSF projects and components, and can help to provide context guidance or, or more than that, based on what your use cases are and that the Wiki. So I'll tell you a little bit about the wiki and then we'll look at a few use cases that I've put together. So the wiki is that component that portion of the project that Nikki shared with us that on its face kind of just looks like an open text field, but it is designed to allow it to be more than just a description. It actually is a pretty powerful tool that can allow you to describe and link things in your projects. So among the things that the wiki enables, it can be collaboratively managed and edited. And so your projects or your wikis don't have to be, you know, you have to worry about two people working on at the same time, Nikki and I could be working on those wikis simultaneously. And providing that kind of information with the wiki provides context for their data. So I mentioned the collaborative simultaneous editing that is using markdown so it's a tool that's fairly easy to use and it's somewhat guided already within the tools that's offered in the OSF and I'll show you in a briefly in a moment. And there's also within the wikis are within the projects permission levels that you can have just your contributors managing those wikis but if you wanted the broader community to contribute to your wiki your wiki dad resources or stories or whatever the case may be that is something you can enable without having to open up other parts of your project you wouldn't have to make your components all editable by the community but you can have that wiki be or a wiki be accessible and editable by the public. And then even if you sort of anticipated a risk to that. And there were changes that you didn't you wouldn't want reflected on your public version of your project, all the versions of those wikis are saved. So someone went and erased all your data for some reason in your wiki. It's not gone. There will be a version that of your last year edits would still be there and so you're not at loss of losing all of your risk of losing all of your data. So with that, let us take a look I'm going to navigate over to the project we were just on. And then Nikki was showing us earlier. And I have since she added me as a contributor to the project I now have the ability to create and link things that I couldn't before. And one of those is I've linked a few projects here. It's in addition to the component that Nikki already created within our project I've linked a few new ones that are very very basic templates for the some of these responses that you've in the polls. So we do have a wiki for the project this one we use as a sort of a broad introduction to this event. It's not a whole lot going on here so we're going to bounce right over to one of our use cases and look at the wiki there and some of these features that we've just described. This is, as I mentioned a very, very basic templates that I've put together from that would be designed to help research teams organize all of the data that you know maybe 510 20 different people are doing different parts of our project with some structure that doesn't have to be unmanageable. And the wiki can be a way to guide teams toward the resources that they need or the places that they need to store or manage their data within the OSF so here is our wiki here and this is of the view that anyone would see this public view here and we have a number of things that are unique we have some header text we have some images and some embedded video so we'll look at the editing interface and how some of that is done and I mentioned that Markdown is the tool that enables all of these customizations and you can see let me zoom in a little bit see this is make our text a little bigger. You can see some of the tools that are enabling things like header text this is all pretty straightforward just these these double pounds here and then perhaps more interesting I can scroll down again. So we get to the images. That's where design section. Right here and so this is linked from elsewhere and we can see our links down here. And so image links we actually have a tool for that right in the interface you don't have to memorize any Markdown syntax in order to use that and just use this tool here to add your images. And then you can also add videos you can embed videos with the same syntax in here I've got it somewhere that I've added them in here right here. So this is a really pretty easy syntax and we've linked the guide to the more complex elements of that grammar here in the tools that can help you with managing those things. But within the wiki here. And then we can look at the version history because I have messed with this throughout the day we have this public version here. And then we can compare that to a version from earlier today probably not a whole lot different. I've removed a few things and added that YouTube embedded video here. And then so this would be that could have dozens of versions for these wikis and you'd be able to compare those to the current public version you can actually have the edit column open all at the same time if that would be helpful for updating your wikis for your teams so that continues to be a resource for them. And then within in in this project I've created a number of components which would for a team with a complex data gathering process perhaps would help to sort of guide them to resources for those particular areas so data related to their experiments they have grant resources they need to be managed those have components, particularly for those and each of those components will also have a wiki that can likewise provide guidance for that particular area for the research team. And then within each of these you can have multiple components I think I do have one with multiple components and I can show you in a moment. So that is what the markdown editing process looks like. And then to have your, you can do other things with your wiki you could even disable your wiki if you really have a project that doesn't need that or it is really just a landing page for your data you can disable that wiki you won't appear on your project at all. As we mentioned earlier, you can control who can edit that wiki so I can have all users of the OSF be able to contribute to this. I don't know if you can see this drop down but can contribute to this wiki. So all they would need is to be able to log into the OSF in order to contribute to that. And then you can also delete these wiki pages if you have something that's clearly out of date that is no longer needed I just can't delete the homepage let me go to my other one that I've created for us, which is about data management, which has a few other wiki features that were not in the research teams one, including having an extra wiki here which doesn't have anything in it. It's just an empty wiki here but just to demonstrate our multiple wikis for any project or component. If I no longer need that wiki, I can remove it. And then so as far as unique areas to data management or areas that researchers would need to highlight in the data management plan that may be a little different than others would be generally sort of answering these questions before their research takes place how they intend to collect and manage and use and store their data and they can provide those here and then also link to the resources that are relevant to those responses so they can link across their project as we've shown before those different components can have different focal points they can link to protocols or supplements in their components and I'll show that list here in a moment you can link to existing or describe existing data that you're using. If you have something that visualizes the way that you're going to use or store your data it's always pretty useful. You can embed files that are from the OSF into your wiki which has a this is all it takes there if you have something that's stored on your OSF account. Really you just use the good which I think Nikki sort of described what the goods are for OSF files. And those will embed in the project this would be if there were you know 100 slides but still in bed in here just like that. And then if you have compliance or legal issues that you need to describe about your data that can also be formatted in a table so that it's easily described and understood for this was sent to your funders or to your compliance offices in your in at the university would have all of these details included you could link to the data itself once it's provided and the markdown for tables is pretty straightforward. So let me go back to the project itself and we'll look at the different components. So as I mentioned this is I wouldn't use this as your template I've linked to examples that would be much better for that but just to provide a sense. You could have guide drawer researchers to create a plan that has components that instead of dumping all of their of their data where the resources relative to how they're going to collect and store their data into one place it's difficult to describe or discover any of that material, they can have those separate components for the particular area so for their protocols can have its own component for their notes and then each of these will have all of the same features as an OSF project well those each of those components will have its own wiki will have the ability to add components contributors, the same as we've seen with the projects. I think we're wanting close to time here so I'm not going to describe or not going to walk through the other ones I've created but I will link them all to the project so that you can take a look at those later. So, if you're not so it's not what I meant. Yes. So I'm going to tell you a little bit about OSF institutions which Nikki did mentioned a little bit. And some of the challenges that we hear from institutions and talking to them about their data management and research communication challenges. And sort of generally across 5060 research institutions and we've talked to and worked with pretty closely is that they find that researchers can be burdened by reporting processes and that's not just a university to researcher issue they have to report to all kinds of different bodies, you know all their funders. Sometimes to publishing journals for conflict of interest all kinds of things that are not terribly well channel the infrastructure is is not consistent for those things in most cases, the tools, if there are tools for some of those services or needs. There's not just one there's many many tools and they're proliferating. So that researchers have difficulties keeping up with what's available to them and likewise to the research support services. And in addition to meeting those compliance requirements and being able to communicate that you've met those requirements is pretty difficult and that's on behalf of the researchers themselves as well as the university communicating that they're their researchers are compliant. There's a lot of information data about what the researchers are doing that don't involve into the line publications. That can be very difficult to track but it's also very important to communicate that your researchers are doing practices of rigorous research practices, but it's difficult to do if you don't, you can't see or understand what they're working on. So OSF institutions is a a fee for service membership model that provides all of those things that the OSF all of the things we looked at today for the researchers is still free for those researchers to sign up for an account that hasn't changed. So what we do want to provide is more insight more information for the institutions that are supporting those researchers in their work. So all of if all of this interesting work is happening at at your institution, then you would probably want to know and we want to help you get that information so we've developed a number of these features, particularly to support the researchers themselves or help you to support them, as well as to give you more information so there's a single sign on feature which I'll show you in a second what that looks like. But it allows your researchers instead of creating a whole new account and new credentials they have to keep track of at the OSF they sign in with your email address and password. A branded aggregate page which collects all of that public information so those projects that your researchers are developing our public. All of those would be aggregated on a page just for your university and their work training that is particularly focused on helping your researchers adopt or accelerate those practices or to help your research support staff support them in that pursuit. Opportunity integrate your own local or cloud storage tools into the OSF those that you have on campus that are unique to you instead of attempting to add more and more tools integrate some of those together and make them interoperable. And then finally administrative tools that provide even more information about all of that work that your researchers are doing and even providing insights by department or teams, based on what kind of information we can get technically. So our goal is to focus on allowing your researchers to spend time doing research, and less time, you know with them trying to do the administrative components or negotiate all of the different tools that they're being asked to use so very quickly I am going to go right back to the same project that we were just looking at. And you'll notice that I think on the projects we were looking at before you can kind of see a Center for open science logo up top and that is not native to every project on the open science framework that is was added because of our Nikki's and my affiliation to the center and this was our project so this is an existing project if I go to my settings. As the contributor. There is a question here about adding an affiliation to this project. I'm scrolling back down here, and I have two affiliations that I have are added to my account by way of my email and credential information as I mentioned before the the Center for open science as well as George Mason University or posting before. And if I want to affiliate this project this data management template with the center and add this affiliation and the components. I'm going to go back to the front page here we'll see this logo appear and if there are, you know, five contributors that all have affiliations at, you know, four or three four five different universities of all of those are members of those institutions they can all attribute their affiliation to this project. And then the center and all of the USF institution members have an aggregate page that collect all of these projects that have added an affiliation to it. So in this case most recent one, or actually several of these today are all affiliated with Nikki and I, as well as with the center so on our branded center aggregate page here. All of these public projects are available visible anyone can navigate to these and see all of the cool stuff that we're doing here at the Center for open science so any of the members would have the information, just like this one and when I go to create a new project these affiliations will be on by default so make it very easy for researcher to affiliate their information with their university with their institution. So that is some of the excuse me. Oh, let me show you a sign in real quick. When your users are logging in for OSF institutions members they have an additional sign in option. Next, we'll see here. So for all of the USF institutions option members they will appear as a sign in option for the sign in through your institution drop down. So there's about 65 members of OSF institutions now any institution can join and make their single sign on information available to their users so it won't be available to just any institution, but rather two members of this group. We would help we would set this up for you we may need a little help from you but this is not something that you have to go and build and integrate yourselves. We would help set this up for you. So that's a very quick tour of OSF institutions and we just have a few minutes left so I'm going to turn it over to you. I have a few questions. You can hear on our list, but then any questions thoughts feedback that you have in our last few minutes please do submit those so that we can continue to talk and then we'll talk a little bit about how we can keep this conversation going. So I have a question here. Oh, never mind. I think the question was been answered by Nikki is quicker than I am. So any other thoughts questions, please do drop them in that Q&A box that you have available there or thoughts about any of those use cases or additional use cases that we haven't anticipated please do drop that Lisa is asking if can you make copies of the template created actually one of the very neat features and something that I was using heavily to sort of create a super basic template where is a is exactly that you can create templates of projects that you want to have the structure from so with something like this is our little research teams one have the not the wiki information or the specific data but the way they structured these components. We'll sign in first, you can do that with either fork the project if this is a project yourself or you're working on with them but you can also duplicate the template of this project which is only going to bring the structure of this OSF project so this is actually something really very neat if you find an example of a data management or research project structure that you've found here, you don't need to go and copy and paste their components or their the structure of their project you just need to use this duplicate template and I get this now as a project that I've created on the contributor has my affiliations on it and it brings over all of the structure of the components of that project so that's a very good question and yes indeed you can create templates of these projects today but of course any others as well lost my question panel here. Okay, have some students doing their research projects it is possible for them to publish their research proposals with the USF. There's a few options there maybe Nick you tell them a little bit about pre prints and how that works or maybe as an option for them. Yeah, happy to. Yeah, so OSF actually operates about 27 different pre print servers, many of which are managed and operated by communities and their discipline specific but some are actually available and specific to country or region so I can, if you go to OSF.io slash pre prints I think you could go there and explore what what the different server options are I'm not sure what discipline you're working in and what your students might actually be most applicable to for some of their research projects but they could certainly submit a pre print there. The communities are actually moderating those and deciding what fits within their editorial guidelines and what doesn't. I will say that OSF pre prints is the one that Center for open science actually operates, and we do not moderate so you could certainly submit to our pre print repository and they would be accepted and and therefore get a DOI and be signable. There's also thesis comments so if their research projects are more like these users or dissertations you could you could also consider submitting to thesis comments for that. Awesome. Thank you, Nicky. So Paul has asked about the costs for OSF institutions. So that is, we have a new website for OSF institutions that is right around the corner. Right now, I have this information and institutions as its own OSF project we like to walk the walk there. And one of the elements is an agreement for services which has all of the details of how the membership with OSF institutions works including the tiers we created tiers so that your institution gets what it needs right now, instead of trying to negotiate how this might work. You don't want to get services that you're never going to use. So we've created these these tiers so that you can find exactly the services that are relevant to you and where your institution is right now and that's something that you and I can chat about Paul and I'm going to drop a link to this file in particular, but this is also linked in the slides. So this is something that we can any of you please please contact me to chat about this and I'm happy to talk about your context for your institutions. There is a question from when here is there a plan to add functionality journals have like reviewing publications formatting services to the USF. So I think part of that might be answered. As Nikki mentioned, there are many different pre print services on the OSF and some of those have moderation. So if that's what you mean by reviewing that is something that each of those communities can do they don't all use moderation but some of them do. So that is something that is a community by community decision formatting services. I probably not. I think that would be up to the researchers and the communities themselves they decide format that if something comes in is not appropriate then they would you tell that author to to make changes but the USF itself is not going to make those demands we actually are very proud of how flexible the tool is in terms of formats and and file types and those kind of things. So hopefully that answer your question when and one another question how to I think you already got it. Well we are right directly on time so I'm going to sign off here with just a word about how to keep talking to us we want to keep hearing from you and talk to you, not just at you but we want to hear from you and what you're working on and what is important to you. So I have a few different things here and there are many other ways you could get involved with these are a few that we talked about today. So if you want to talk about institutions whether you might not be ready for membership or you want to talk about what that involves or you might not be anywhere near that I still would like to talk to you about what you have going on and what your priorities and needs and pain points are. So please come right to me and we will chat. There is also no SF ambassador program and I'll think we talked about that today, but we do have resources about the ambassadors if you are interested in and talking about the SF at your institution. You can also write to my colleague Claire is also here today to talk about the ambassador program. You can attend future webinars we have very many different topics we don't do the same event every time. So take a look at our webinars pages at least one that's in the next few weeks, and we always have new things getting at it. So keep a watch there or on social media to see what new events are coming probably not any in person events anytime soon so keep a lookout for the web events. If you have a if you saw an OSF project today that's you're interested in being involved in in some way, either right to the author of that project or if it's something that's at the USF for the center itself. You can write to the product team or to me to chat about that. And then training, other it's part of institutions membership or something separate. I've linked to resources about training here. And then, if you just not sure how you want to stay involved but you do want to stay involved. Just write to us, we want to talk to you so please don't hesitate to write us or tweet us or whatever is easy for you. We will find a way to chat with you so thank you so much for joining us today. And Nikki have anything to add. Now, I appreciate everybody coming and we hope to continue talking through email or otherwise. Terrific. Well, thank you, everyone. Keep a lookout for my follow up will have these resources and recording I believe of the session. So you won't leave anything behind when you leave today. And yeah, let's let's talk in the future and thank you for coming.