 just a minute past. So I think we'll, we'll start and we'll just slowly do our introduction here while people are still getting at it. So welcome. My name is Eric Olson. I'm a product owner here at the Center for Open Science, working particularly with OSF institutions. And that is our call today is in the series of community calls that are part of our community conversation with around OSF institutions with the members of that group. And we're going to talk a little bit more specifically about that in a little bit. I'm going to share my screens. We can walk through a few things together today. Sure I got the right one up. Oops. I think folks are still coming and we're just going to go ahead and get started. So our theme today is really to talk about the OSF itself mostly and some of the features that really makes the OSF a useful tool right now in particular in the ways that research teams, labs, university departments are operating in a different environment than they were a year ago and maybe that then they've ever worked in at least at scale. So we're going to talk about some of the things that the OSF enables that can maybe can can help you and help your stakeholders. I know for a fact in looking at the list of attendees today that some of you know a lot of this and already share this these kind of resources or instruction with your community. So you will see some things that you know maybe I can mix in a few things that you haven't seen before or maybe some examples some useful examples for you that you can use to to share with your group. So we are going to just quickly talk a little bit about the the Center for Open Science and the Open Science framework even though many of you are very familiar with this some of you are new. So we'll quickly talk about what the Center does. So the OSF is a product of the Center for Open Science. We're based in Charlottesville, Virginia and we have at a high level our mission is to increase openness integrity and reproducibility of research where a nonprofit all of our work is open source and the OSF many of the things I'm going to show you today all of the OSF features for researchers all free. OSF accounts are free to set up free to be setting up all of their their projects and they're submitting pre-prints and registrations things we'll talk about in a little bit. We keep those free for researchers and I'll tell you a little bit more about how we do that in a little bit. And our structure as an organization is to really think about how change is enabled in a few different ways simultaneously knowing that just one of these is not quite enough to enable change. So we have a policy team and their work is around cultivating incentives to enable change to brace change across organizations and regions and to understand and share when those changes are happening and the research team that instead of just assuming that all of these policies are are working and that they're all great. We have a research team a medicine team that is actually following up on all of that work so that we can actually demonstrate evidence of those changes of successes and possibly where things don't work. We want to have evidence for that to help us plan our future work with the policy team as well as the next team there the infrastructure team which is the OSF building technology infrastructure that can enable any of this change to move forward in concert with the culture change that is enabling that work here and with that in minds this is an image you've seen in some context or another over the years certainly the diffusion of innovations where we have this is not just in science and technology we see this in in many contexts where there are innovators there are early adopters that they really will jump into something that they see that there is potential as far as how it can improve their work or their practices and they'll embrace that despite possibly bumps in the road as they sort of work to use those tools or understand articulate its value. Lots of users bunched in the middle that will join and follow the successes of those early adopters and then of course laggards that they do or will possibly embrace those changes they just might not do it as quickly as some of their peers maybe they need to be they need to see some of that work in action before they're reassured that it's actually right for their community. So if we tilt this over a little bit it helps us think a little bit about more about how we work here at the center and what we're trying to encourage through those several teams that I mentioned before at the base of this pyramid here and to support those innovators who will jump in and try cool new things we have to make that possible so we'll build and enable a technology that will have some of those really excited early adopters and innovators jump in and try those new things with technology that's available to them and then in order to continue to get more of those adopters maybe they they're excited about it as a as an opportunity but they need just a little more help and being able to actually use those tools so being able to iterate make the interfaces and the experiences even better if we make it easy more will will take part and then the real exciting part being right right in the middle here of the pyramid is working the community so you could build the greatest most interesting technology of all time but if you built it for you know somebody that doesn't exist then it's probably not a great tool or it's not a useful one if there's no one there ready to use it so communities are a huge part of this and helping us understand where the technology even has to go who's using it and and how they're using it and then on the other hand on the other part of that equation the communities can take that technology and make it normative in that they it becomes a part of their community activity their workflow their discussions their conversations happen around those practices it's assumed that having a DOI or data sharing as practice or data as its own object that only works as the community's embrace those as an activity they're willing and and encouraging and then incentives communities can embrace those things but they're not every one of the community is going to jump right in right away people are busy but if you make it rewarding to take place and to take part in data sharing or transparency then even more of that community you're gonna take part and then finally if you if it really comes down to it and researchers maybe resist practices in some cases but if you tie it to their funding or to their tenure through policy and incentives they're much more likely to listen and try some of those things and again we want to learn from their experiences that we can come back and revisit the infrastructure make it even better for them so with all of that in mind we have really been thinking as you have about the the challenges of going remote likewise we are remote over a team that a little over 30 people that very much were dependent on being in person and working together in the office and had to make an adjustment to to all working separately and some of the challenges we face I'm sure you hear a lot about communication is just the technology itself is not always as consistent as we might hope that people have different means of communication at different times based on where they're going to be the loss of passive knowledge sharing which is a fancy way of saying you know the water cooler we're not passing each other in the hall anymore with the you know what's what's new this week I just heard about your your work tell me a little bit more about that that's not happening at least not easily right now tool gaps some individuals on your team may have access to tools or resources that other members don't which make coordination and collaboration that much more difficult and then lack of organization and management that's not being a personnel management but management in terms of if everyone has different resources how are we going to coordinate writing our narrative or editing our the protocols and our for our experiment or submitting our data management plan that all becomes a little more difficult when we can't sit around the table and and talk about it with the same tools in hand so can the OSF help with these things I think so and and this obviously is is somewhat dependent on your communities already interface with these tools and tools like it so I can't I'm not going to promise you that the OSF solves all your problems because I doubt that it solves everything that you're going through right now but I do think it can help you or help your stakeholders with a number of these things that's a number of those challenges that we've identified so we're going to talk about a few of these today where collaboration can be facilitated you know with the OSF some of the project management and contributor tools there I'm going to show you a few of those lost talk a little bit about the wiki and how that tool can provide context for all of the cool things that your researchers are sharing or want to share and then finally I'll tell you a little bit about OSF institutions and how all of those things that we were going to show you today could could possibly provide some insights to the institution itself and where all of those where all of that individual research or energy is is going and contributing to all right so this is the first group of things that we're going to look at today involve the project features of the OSF managing collaborators we'll look at a few things with with files in the OSF and then we'll talk a little bit about how you think about your structure or about how your research whoops how your researchers are thinking about structure so this link right here and I'm going to drop it in the chat as well is a OSF project a public project that I put together just for us and we will spend some time in it and just a moment let me find the chat here make sure I send it to everyone there you go so you can follow along in there as we're as we go so this is that project right there that same link we use the term good which is we're not the only ones to use that term but we use that a lot so that is this number right here and every project and object pre-prints in the OSF every file that you upload to your to your OSF account or project will get its own do it so it is an identifier unique to this project despite many more like it none will have that same do it and then what we want to talk about today is we provide a little narrative to this so if I'm a new researcher maybe I'm a lab manager at your institution and I'm really looking for a way to coordinate some of the work that normally we would be doing in the lab I can't get to my lab right now so I need a little help coordinating some of that that data sharing or some of the the communication that used to happen even writing physically on a on a board or on a notebook how can I do some of this remotely and coordinated in such way that many of the resources are going to be shared by the rest of my team so there's a few things to keep in mind for the researchers think about before they they dive all the way into this do they have data management requirements from their from their funder or from their institutions where are they going to be storing their data or do they need to communicate all of this information who is going to be participating and how are they going to be participating because all of those questions can really determine how their their OSF projects are structured so a few of those things that we'll look about look at here I'm going to move some of the zoom boxes out of my way so right at the very beginning this is sort of our home page for an OSF project we can see that public projects and private projects are distinguished here and I could switch these I could switch a project from public back to private back to public obviously in this case I want it to remain public so that you can follow I'm going to use some of the resources here a private project will only be visible by myself and then others that I add as contributors which I will show you in just a moment public anyone even if they don't have an OSF account will be able to come and read this information through the API would be accessible for someone to come and access some of my files in my work here but if I want to continue to add more contributors to my project I've got a couple of ways to look at our contributor list here and so one is I can proactively add folks to this project um I would look for I'm gonna look for my colleague here who's also on the line with us I can find her on the OSF add her as a contributor and even then I have a few options I want Claire to be participating but what do I want Claire to do um you know she's maybe my my newest you know lab uh a lab member or lab participant maybe she's not ready to go in and start editing data yet I can give her read only permissions so that she can access all of this information on her project but can't make changes she can get read and write access she can add new content to our project but she can't delete my project or register my project or administrator which gives her all of those permissions plus the ability to to delete and register projects um register this project so I'm gonna go ahead and add Claire here there we go and I can change her permissions later if necessary I can also determine if she's a bibliographic contributor um I'm of the mind that most contributors should be bibliographic but obviously there are differences for different communities and different needs where someone who's uh administrating a project or is otherwise involved in and getting this OSF project together can remove themselves as a bibliographic contributor she won't show up on the contributor list another way that that users can add them can request access to a project and this is particularly useful for cases you know if it could be a huge citizen science project or if it's coursework then you can enable access requests so I think the coursework cases are really cool here in that this project we make this project available and share the link with all of my students so I don't even have to know who all my students are I can stick it on the syllabus and send it out they would go to that link and request access to join my OSF project here and then they'll become contributors and that works for both public and private projects so it's really useful for um collaboration at scale so that is request access um so a big part of of structuring your OSF project is knowing what do I need to have in my in my sort of home page here in my the uh first page of my project and then what are really separate um pieces that maybe need need to have its own control can have its own contributors have its own privacy settings and we do that through components and when I go to add a new component they really work very similar to projects it has its own title its own license its own contributors and I have a few examples here that I've set up as use cases and we'll come back to these in a minute but just to give you an idea it looks very much like an OSF project but um it can have its own contributors it can have different uh affiliations and I can make this one private while leaving the rest of the project public so if you have a data set you want to have most of your work um visible and shared and out there in the community but you have a data set that maybe is just not quite ready for that it can't be public just yet for one reason or another you can set up a component with private that is private and that data is not available to to everyone that comes through um you can make it request only only by request for individuals so that you can get a sense of when individuals actually want to come and use your work so one of the things bouncing off of of that you can actually get a sense of how if you have lots of individuals that are coming users that want to come and use your work we have an analytics page that can really give you a sense of where that activity is over right now over a month's time and you can see in a couple of different metrics here measure the popularity or the impact of your your project so forks are this is actually a fork of a previous project that i had set up it makes like in in github makes a copy of the the project um and keeps the the content and the structure intact and then the actually the originals kept as part of the citation here so you see it's forked from this original project and the day that it was forked from so you get the the data provenance there and then um links to this project so if um i continue to set up more workshops and want to use this as an example i can continue to link to it so i can see um how often that is occurring and then projects that um can also make templates of other projects so if i need if i saw like really neat um project that is set up for a as an electric lab notebook for example and i do have an example of this i'll show you in just a a few minutes i don't need all the content because this is going to be for my own lab so instead i would make a template copy which would give me a copy of the structure of the project but not bring over all of that content and then some details in terms of um the the visits that you're having per day and where these visits are coming from so right now we can see a lot of our activities coming from the direct link that i just uh sent you a few minutes ago um some coming from uh my account when they looked at my project list and then some probably through a search or otherwise um on the osf site so we're going to look at files here so um one of the the advantages of the osf here is that i could set up the osf project i've added clear i could add all of you to this project and no matter what as long as you have a web browser no matter what your uh what kind of resources you have on your machine all of this is going to be accessible to you all of this content that i have here now i can structure it to make it easier for you to use um or to to recognize what its utility is um but you'll actually be able to open all of and use all of this uh this structure on your machine and this includes the storage so um there's a couple of different ways to store information um on the osf or store files on the osf so we have osf storage as a storage that we host um we use google storage for this um and there is as of right now not a per project storage limit on the osf there is a profile storage limit so the only a file can only be up to five gigabytes um when you're using osf storage and this using osf storage is is free as part of your account um and when we go we're going to pick the first file here and it will over 500 file types will render in the osf so again you're not going to need a certain special kind of software for the best majority of files in order to actually access and read them um in the osf and we'll have a few things that we see here including um a version history this one only has the the one version but we could see previous versions if those are available um quick share link obviously i have an administrative capability so i can delete these files um if we have non-admin contributors they won't be able to to delete them but would otherwise have access to them and then this is a feature only available on osf storage called checkout where um if this is a file that um we're passing around as a group maybe it's a a grant application and we all need to to have access and work on it we're not going to do it in google docs for some reason or another synchronous platform we need to have real close control um so you obviously don't want to have everybody have a different version they're all trying to compare and contrast them so instead you could have one here on the osf in this case a security overview document i can check this document out and that means now i have access to this document and now no one else on this project will actually be able to make changes to it in the duration that i have it checked out um so that may helps to um facilitate consistency across the project in terms of who has who's working on this right now um and when do we expect changes to occur so osf storage is one option here um now what's really exciting is that um as we mentioned before your research team or the researchers at the get your uh university they may have all kinds of different storage options that they rely on you may have some that you use at an institutional enterprise level um already at your institution that your researchers rely on they don't need to copy and paste their files um in order to get them from uh dropbox to the osf because we have built we call add-ons which are a way to to connect your files no matter where they're stored at least within these add-ons here and connect them to your osf projects and not just generally you can take them very specifically where you want them so you have an o-off process that you're probably very familiar with from using google services and and orkid or others like that um import oops that's not the one i want a little differently help myself out here and we'll just grab a document here from a uh digital humanities conference from a few years ago maybe not uh that's not helping me um so you can add your entire folders of your google drive content uh to your osf project just uh from these add-ons so you can do this multiple times you have lots of uh folders that you include in this process so if you have data across multiple add-ons you can centralize all of those here on the osf on your osf project and then move that data between the different storage options and between the folders that you set up within your project for um organization so if i create a new folder just for new data management plan so that i can keep track of where my plan documents in particular in particular are so you just move those around and get a nested structure just for my files there and then if i need to actually take all of these files not one at a time but as a group get these files and download them so i have lots of data we've been using but i actually do need it on my hard drive now um we can actually download these um as a as a zip we can delete these as a group check out files as a group um even across multiple folders whoops at the project and the component level you can create dois for these to make them um easily shareable the uh project dois are all minted by data site um registration dois are also data site um in preprints those are minted by crossref um and then we have a number of different uh whoops let's go back to our workshop uh add-ons here i mean uh project so i have a number of different components i set up here these are all different very very basic use cases i set up that might be and useful to to review and give you some ideas um about how some of your stakeholders might be looking to use the osf in terms of organizing their their work um so one of the important parts of setting up your osf project is you might have lots of different data or code in here is contextualizing what is going on what we're what are all these files about um what are when you have all these different components how am i supposed to use these um we have a wiki that is specifically designed to provide that kind of information and to be iterative and have version controls so that you can actually see how the project has evolved and maybe the structure has evolved over time so there hadn't been a lot of changes between um the two versions here which you can actually compare multiple versions should there be um yes there was a few of them here before um you see where those changes have occurred over time and then the edit function is in markdown so there's lots of flexibility in terms of what you can do to structure your wiki to to illustrate how your project works and what um it's going to be used for and so um i've used the wiki to um illustrate or to um give you an idea of how that might help with different kinds of project structures so this one um just a very simple template for um a faculty member that might be using the osf for course management and we see this quite a bit in fact um and they will um you have used this as their syllabus and link to uh various resources throughout the the components and then they'll use this wiki to to give the the guidance to what you should be using when this is linking to several of those different excuse me several those different projects and components and then you can embed in this case files from inside the osf you can embed those right into your wiki so that if you have a really crucial image or or video even that describes your project or how to use your project you can embed those right in there um you can have a couple of different wikis you can have many different wikis if those will help to explain the different parts of your project in this case this one is blank but let's go back and look at the structure here so i have components for each of the different um weeks of the the duration well the first five weeks of the duration of this course um and so each of those components can have different content i don't know if i oh yeah i have a few things in here um and you can have nested components you have many as was necessary to to structure your project the way you needed to and then this is an example of linking an external project coming from i didn't build any of these they are linked from in this case james madison university some really cool classroom resources they've developed um these i'm not sure where these are this is about formatting your or managing your data to comply with NIH grants and some really neat stuff so i have linked some of these to each of these different use cases some examples to look at and then these really basic templates as well now one of the things that's changing as i move myself back to the project here one of the things that we see that we're going to see a change in very soon is the the user experience for the project pages and the files pages in particular are about to get a facelift right now it's not the the easiest thing to use we get all of this all of our components and all of our information is listed here on this files page can be a little difficult to to manage we have a new user interface for files that is weren't in line with the rest of the osf much cleaner much easier to navigate to the files that that you need the rest of the features will still remain the same you still have to check out and version history just easier to get to those the metadata fields page down just a little bit here is also getting an adjustment to account to make fair data available for files it's going to be exciting i know a lot of you are busy with fair data initiatives right now so those will be available pretty soon including i'm having funding grant numbers for your files that's very cool so this is not available yet but it's in the very near future so it's a look at files file reboot let me just go back to our components here we'll look at one of the other ones so we get quite a few questions and we have quite a few cases of using the osf as an electric lab notebook el ends are obviously a pretty important tool or resource for for labs and there's lots of ways for them to to create their own lab notebooks or electric lab notebooks the osf is valuable and that it connects to all of the other the other work that they may be producing in the lab or sharing they can link all of that together so the wiki is about they're bringing all of those different phases potentially of a lab's workflow linking to those in different components and then you know in this case also embedded we had a very specific webinar about osf as in the el end that i've linked are embedded here on the maybe of interest but the structure there is about getting if you're at the the protocol space if you're you're working the lab you know exactly where to go and deposit your your data your protocol information if you're at the data gathering phase there's there's a component for that materials and methods results so that there really is not any confusion in terms of where the data needs or where your workflow needs to be at the next phase that we're going to skip ahead just a little bit so that I have time just to talk to everybody before we jump off i'm going to look at the questions here how will the file metadata get attached to a file so the file metadata you're actually filling out your file metadata when you are on a files page here so let me just actually grab a real file that we'll look at so if you actually choose one of the files in one of my projects here grab this one all right now we don't have that metadata module included here yet but you would come to this this file page and when you order when you deposit a file and fill that that file metadata those fields out so right now it's very basic metadata just the data site required metadata but yeah you'll have that those additional opportunities to include new metadata fields in the very near future it's a couple of introductions so low all right let me continue and please do submit your your questions your thoughts as we go here so with all of that in mind considering that many with some institutions you have lots of engagement with the osf already or with similar tools they're doing things like this or they're they're wanting to learn how to do more things like this with the osf what is if anything can be gained from that or gleaned from that from the institution's perspective and that's tricky for a number of ways and I'm not telling you anything you don't know here there are burdensome reporting processes not burdensome in that you're not doing it right it's burdensome because they're doing many of them in many different formats and many different software platforms that they're trying to do they're reporting for their funder for their institution potentially for their publications and they're proliferating tools not just for their reporting but their their stored data storage tools or their data management protocols tools all of those may be different things that are getting spread out their citation software not often are those unified meeting compliance requirements of many many kinds mostly the data sharing depositing data in a place that is appropriate for their based on their funder or their institution can sometimes difficult to get a read on as a researcher and then as an institution you're you might be able to get a lot of information about publications you probably can and you probably do it's less easy to get information about all the other things that researchers are doing particularly if they don't result in a traditional outcome of some kind so OSF institutions as a product builds on top of the OSF that is is taking all of that data that we just looked at that activity we just looked at from individual researchers and distinguishing them by institution so that you can actually see the the activity for your researchers in particular and get more information than than you would otherwise about what their what kind of work they're doing and where they are in their work and where in the university there that work is happening so there's a few things that that operate together to make this this data gathering possible there's single sign-on which your researchers probably use in a number of places now whether they use their institutional details or they're using google or facebook or something that single sign-on really makes that access to the OSF much easier by using their institutional credentials to log in there's a branded aggregate page which aggregates all of that activity that they're they're doing at the on the OSF into one place you could see here's what my institution is doing in terms of open and shareable data training in order to really engage with the potential for a lot of this activity across your institution either as a a general sort of faculty focused training session or as a train the trainers type of session where we work with your librarians or other support staff so that they pick up these resources and use them and and many of your institutions do something like this already opportunities to integrate your local storage tools local repositories or cloud repositories or other tools into the OSF so that it works much like the add-ons do now and then administrative tools that take all of that activity and then visualize it for you at a level that provides some insight into the activity across the lifecycle that is not just the final publication outcomes so we can handle a lot of that infrastructure so that you're not trying to manage it across many many many different tools and then still turn that into to usable data so let me show you a couple of those things oops let me switch my windows here screen shareings fail to start it's not good all right so this is an example of an aggregate page that is pulling in all of the activity in this case that we're doing here at the center for open science all across the OSF and when I'll I'll click on uh well this very first one I'm working on right now and that is here because it's been associated affiliated with the center and as we can see if I go over to the project settings I have an additional affiliation with George Mason University I can also add that affiliation that's not accurate in this case I'm not going to do that and when every time I set up a new project it's actually going to give me or a new component we'll start there by default those affiliations are going to be on so if you're researchers if you're an OSF institutions remember your researchers have used the single sign on these affiliations wrong by default so that every time they start new projects they are going to have those associated with you at the university and they will show up on this aggregate page going back here so these collect all of the public projects from from those affiliated users into one place so in our case we have a lot of things here is probably not a surprise and we can share this aggregate page to give at least the general sense of all of the activity that we have going on here in addition to just how seriously we take transparency and data sharing just because of the just due to the activity here we can demonstrate some of this and what research institutions have been talking to us about over the last year or so is taking this data and more and providing an insight across the institution or within parts of the institution so that they can learn more about what their researchers are doing and so I have an example here of this visualized as an administrative dashboard that takes all of that data that's happening on the USF all that the work that your researchers are doing that we just talked about and brings them onto a single dashboard for administrators at your institution those ones in our staging environment the production one is live now I just don't want to show off somebody's an institution's live data today but this is an example with fake data of us here at the center and see our individuals that are all participating and in the case of institutions that release department level information from their identity management folks can actually take that too so that we can see where there is clusters of activity across the institution so if you had initiatives within the College of Engineering to improve data sharing you held a workshop for them you could check each day to see how those grow after you hold your workshop and then total numbers of projects public and private projects number of private projects would not be available to you in any other way so that's so unique information that you can't get from the API or elsewhere and then the total number of single sign-on users back here we don't have any of the repositories integrated yet but that is something that is getting built or will be getting built very soon so I don't have one to show you just yet but this is the the work that we've been doing here with institutions and really are excited about the kind of opportunities that that might enable for institutions to learn more about the work that their researchers are doing on the OSF already so it's not something new in a lot of cases for institutions it's just learning more about what's already the engagement that's already happening on your campus so we're really really excited about this work so I'm gonna before we run out of time I'm gonna look at some of our questions here and please do send me questions or if you raise your hand we can have you unmute and talk to us for a moment if you have a use case or a question that you'd like to share I've got a question here from Eric would workflow look like for transferring static data to institutional repository so that would work much like the add-ons do now and that's a case that we're already building toward is an institution has a repository that they want to to get more and more of their research or data into a lot of that research data is right now on their their users OSF accounts so that the add-on would enable them to to move that data over to their institutional repositories through the the add-on so instead of copying and pasting or downloading and uploading it all gets moved from the OSF to the repository and do you already have data processing agreements with European institutions yes we have several institutions in Europe that participate and we have a storage location in Germany so for all of the European institutional funder policy requirements for data storage so far on that Germany location has has resolved any of those issues though if you know of any other storage locations that would be vital in order to enable access for a region or your community then please do let us know any other questions thoughts yeah thanks Eric well I want to thank everyone for for coming stopping by and hearing a little bit more about the OSF and OSF institutions I'm I'm going to send a follow-up to you today or tomorrow that has some more information and ways that we can stay in touch I would definitely like to hear more about your cases and some of the challenges that you've been faced with as all of us have changed our operations a little bit over the last few months so if there's a way that the OSF or I can help you please do let me know and and we'll find a time to to talk