Yeah, community matters. Amnesty International Cup 26, we are so happy that we caught up with Agnes Calamard. And she is the secretary general of Amnesty International. Let me say that again, she's the secretary general of Amnesty International and she's in Glasgow and catching up with her is really special. Thank you very much Agnes for appearing on our show. Thank you, thank you Jay for welcoming me. So Amnesty was created in 1961, which was a very, what do I say, kind of an activist time. And it was created to deal with global issues on human rights and atrocities. And it doesn't take government money. I really liked that part. And it has a following now of 10 million people who support it and it operates all over the world. And we're here together. So I'm really happy to meet you. So can you tell us more about Amnesty International? So we're gonna handle on what you do and what it does. Well, I think you've already presented its history. So it's a 60 year old human rights organization, probably the unique human rights global organization because it has members all over the world. It started working mostly on prisoners of conscience on political prisoners focusing on imprisonment, but has progressively increased the scope of its focus, you know, included the death penalty as a very important thing that was done in the 70s. Until now where, you know, we are really covering a very large number of violations, including those related to climate change. Civic and political rights remain at the heart of our work, I will say, but we do have a substantive amount of work focusing on economic and social issues, including those related to climate change. And we try as much as possible to demonstrate the interdependence between those rights. So while protest, for instance, and associations are very important or expression, are very important rights, which are probably part of the most, you know, frequent issues that we cover. We will demonstrate that those rights are violated in the context, for instance, of people protesting working conditions or of people associating for trade union purposes. So really making an integrated story. It's not about civic rights and economic rights. It's about really demonstrating the interdependence of everything we do. That's so important. Totally, I totally agree. It's all connected. And I guess to ask you why you are at climate change a conference, why are you COP26? You've already sort of answered that. But can you tell me why you're there? The way you see it and what you're doing there? And then I'm gonna ask you what you're finding there. So first we're here because the climate crisis is a human rights crisis. I think, you know, everyone knows by now, unless you really are completely rejecting scientific evidence that the climate crisis is here, that it's largely, if not mostly or only related to human intervention, to human actions. We know that the climate crisis is resulting into, you know, disasters around the world from mega fires to drought to flooding. We know that the climate crisis is increasingly the source of international warfare. People fighting one another because they are losing access to their livelihood. They are losing access to their way of life. They have no other opportunities to pick up, but to pick up arms. So conflict and climate are very closely related. They have always a little bit been, but it's certainly now becoming a major characteristic of the world we live in. We know that people working on climate, working on environmental issues are among the most vulnerable to arbitrary arrest, to disappearance and to killings. The largest number of human rights defenders killed or imprisoned every year are those working on environmental issues and on climate change issues. So we know that behind climate change, there is right to life because people are dying because of climate change. There is right to health. There is right to a healthy environment. So many human rights are embodied in the climate issue and the climate issue is about many human rights. So we need to really tell the story of climate which is also a story about rights, rights being violated and rights that must be appellant. And the COP26 is the moment where in theory, the international community should come together and say, right, we're facing the most incredibly challenging existentialist threat of human history. That is a global issue. It's a common issue. It's not a problem that is only being confronted by some people, even though some people are bearing the brunt of it much more than others at the moment, but it is a global issues. It is potentially life threatening for our planet and for human beings. We need to come together. We need to find solution to it. That's what COP is all about. It's about the international community coming together, looking for solution to a predictable forecasted global disaster. It may be increasing. It's not happening all at once, but we know it's happening. We know it will happen and we know that no one can escape from it. We've had this, we have confronted very dramatic situations before as an international community. In fact, the multilateral system was born out of World War II. It was born out of the Holocaust. It was born out of 60 million dead and second World War. So we do have a history of coming together and saying, what are we going to do to avoid what happened and to create a future that will be devoid of a global war? And to do so, there is only one solution, Jay, and that solution is to put people at the center. People, people, people. And I'm saying that because right now here at COP, we do not have people at the center. What we have are a range of issues, including profit, including national interest, including market, including the industry that is largely behind the climate crisis. We do not have people, people, people. And that's why the search for solution is so difficult and is escaping us right now. So what are you doing to change that, Agnes? Amnesty International is an organization that communicates in every way possible directly and through its supporters, followers, members. Amnesty International has protest, has supported protest on critical issues over these, what, 70 years? I get that right, 60 years. Amnesty International has advocated in legislatures, governments and with the people, as you say, but what can you do in a COP26 that is focused on industry, on government, on profit makers rather than on people? Yeah. Well, we're there to remind everyone that the people matters, people count and people will help them to account. There are 40,000 people at COP26, 4, 0, 0, 0, 0. Most of them are people coming from civil society, coming from indigenous organization, coming from communities on the front line of the climate crisis. So people are at the meeting and they are trying to make their voice heard. They are facing difficulties because access to the conference has been limited. We cannot access the negotiation, most of us cannot. There are even many groups that cannot access even the main location of the meeting itself. So people have not been really present, even physically within the negotiation but we have been all around it. And many of us are still quite close to the negotiation but that's not good enough. How do you feel about that? Well, I mean, civil society for the last, since the beginning of the week last week have been voicing very clearly, very strongly their concern about that situations and have asked for better access. Some progress has been made, not enough. I think it's got to be a lesson for the next COP. We cannot tolerate the situation where civil society organization cannot be present at the negotiation and contribute to the negotiation. Now, I understand you can't have 40,000 people in one meeting room, so there are some logistical issues but there were ways of accommodating certainly the coalition that represent thousands of people. So Amnesty is there in a very unborn way, I will say, because there have been many other organizations that have been working on that issue for much longer than us. We are here at COP to support those organizations. We are here to support youth groups. In fact, Amnesty came with supporting a number of youth activists. We are here to support indigenous communities and we are part of coalitions and the coalitions around climate change are very important, they are the means through which our collective voice is brought together. Otherwise, we will be far too dispersed. So I just want to highlight that because it's important for people to understand that, yes, there are a lot of us, but we are very organized. We are organized in coalition, we are organized in constituency and we are working together day and night to find common position, to find common ways of articulating our global demands. To a large extent, many of us have found agreements around many of the positions and that's good because we do need to articulate a united front, to present a united front on some of those very difficult issue that we are confronting with at the moment. Where does Greta Thunberg fit in all of this? Is the group that surrounds her within your group, they have the same views or are they different? Where do they fit in COP26? Yeah, they are part of the youth activists, they're very present everywhere you go in every coalitions, every constituency as strong representative from youth organizations. Yes, today evening, in fact, I had a meeting with a number of them from the Philippines, from Canada, from Russia. So the youth is extremely central to the way the civil society coalitions are organized. They are at the heart of the vision that we want to communicate. They are the messengers of many of the messengers we want to send out to the world. So whether it's Greta or another young person, they are very much present and very much there and it's not just Greta. And I mean that with all due respect, I think she's wonderful, she's very strong, very articulate, and she has put forward a view that is very much a reflection of where generation stands on many issues. So she has all of my respect for having done so at a very young age, but there are many others like her currently in Glasgow. So Agnes, you spoke of articulating your demands your demands, the demands of amnesty and the people who read with amnesty and the people who you've been talking with at COP26. And you, let me add that from the newspapers, it seems that the powers that be, that are on the inside track of COP26 are trying to fashion an agreement, okay? Like the Paris Accord kind of agreement, maybe more advanced. And it hasn't happened yet, but that's the effort. So if I ask you this, if you were in the inside, if you were in that negotiation, if you were in with the insiders discussing what is going to be in this agreement, what demands would you include? What provisions would you insist on? Absolutely, well, look, I'll say three or four key issues. The first one is around the demand around the maximum or the minimum or the temperature increase that the world should tolerate moving forward. Right now, according to the latest report in fact published today, it appears as if the pledges made by government will lead the world to something around 2.4, 2.7, temperature increase as compared to the pre-industrial stage. Maybe it doesn't sound like a lot.  And it will translate into millions of people losing their life and millions more losing access to their lands. So that temperature increase is simply a death toll, a death toll for many people right now. What we need according to the scientific evidence is 1.5 degrees maximum. And we're very far from that. Why? Because countries are not pledging and are not acting enough on the pledges that they have made. So the pledges are not sufficient and the actions are even less sufficient than the pledges. So we are way off mark when it comes to that very basic demands. So that's the point number one, we need to see more pledges and we need to see actions with those pledges. The second related issue is that the international community, instead of determining that they really need to move to zero carbon emission, is actually tip-toeing around it. It's like procrastinating. And their way to procrastinate is to come up with all kinds of mechanisms, allowing them basically to sell their carbon emissions to others, to buy the lack of carbon emissions from others and for some to actually profit from this weird carbon emission business. And that has led me to suggest and to point out that it is a sign of our time that when confronted with the most dramatic crisis ever that the world has seen for centuries, our response is to come up with a money-making mechanism, even that's a sign of our time. Instead, we need pledges. We need government to say, by 2050, if not earlier, I will have zero carbon emission. What it also means is that governments must take actions towards putting an end to the fuel industry None of that really is being done except by a few minority governments right now within the Western world. So that's a big problem. Third issue is financing. Why is it important? The climate crisis came about through human work, human intervention, human industrialization. That has been mostly done driven by Western countries and a few others such as India or China and China very much so. So those countries are largely responsible for the climate crisis through their carbon emission over centuries. The people on the frontline of the climate crisis have actually done very little to contribute to it. They are indigenous people. They are people living on low-level islands. It is only fair, therefore, that those responsible for the climate crisis should pay for it. And that's where climate financing play a role. That financing should have two functions. It should mitigate the effect of the climate crisis and it should create the means through which people can adapt through the climate crisis. A lot of money is required, at least 100 billions per year. At the moment, we are very far from that objective. The hope is that by the end of this week, governments may have managed to make a commitment to 100 billions by the end of 2023 and possibly by the end of 2022. They are also suggesting the most positive readers of what's happening that we should be able then to increase the contribution so that we have more than 100,000 billion per year after 2023. That is what is being hoped for. It's a very important element of it because the countries from the global south cannot pay for climate mitigation and climate adaptation. They do need the support from the global north and it's not a support. It's actually a form of reparation for the harm that has been done. So in addition to adaptation and to mitigation, we need to look at a way of repairing for the damages that have been caused to the environment. That's a third dimension of climate financing and the most complex one at the moment. I'm really trying to summarize something that is very technical, very complex and I will not be the best person to elaborate on how complex the financial mechanisms are. But we are advocating for this 100 billion per year and more because more is required. We are advocating for the global north to be able to cover the cost of mitigation, adaptation, but also the cost of the harm done to the environment and to the climate. So as you can well imagine, nothing is easy here. It's all about money plus, as you probably have heard on the radio or on the news, we are confronting very well resourced lobbyists. So for instance, the fossil fuel industry, which is largely responsible for the climate crisis at COP26 at the highest, the biggest delegation of all, followed by a few countries that are also the biggest climate crisis producers, Brazil, Saudi Arabia. China is not there, but I understand that they make their presence feel very much in the negotiation and they are not very constructive in the negotiation right now, even though they are among the biggest producer of carbon. In all those negotiations, human rights are central. Like I said, it's not about money making, it's not about profit, it's about people. It's about people at the frontline. People in the low level island. It's about the workers employed in the fossil fuel industry. We need to help them find new skills. There needs to be new jobs for those communities that will be affected by the transformation of the world that is required. So it's always and only about people. Yeah, so that leads me to a question about amnesty. Certainly climate change creates problems in human rights because the world is completely connected. And similarly, and it's also part of the same bailiwick, COVID and the notion of pandemic and endemic conditions going forward also creates inequities and threats to human rights for sure and war. And of course, COVID is connected with climate change. So if you take the logic of it, Aristotelian logic would tell you that if you can solve climate change, these other things would be improved, knock wood, knock wood. But my question about amnesty is this, you kind of have a conflict because you want to stop the inexorable climate change problems, but you also want to protect human rights. And you realize that stopping climate change will help human rights. But what about your efforts at helping human rights now directly? Not as a function of climate change, but what you've always done to try to humiliate violations of human rights.  Well, it fits very well. I mean, let me be clear. We are not a climate justice organization. We remain a human rights organization. But as I have mentioned, I think earlier, if I look at a two or three key dimension of our work, it is freedom of expression, freedom of association right to protest, non-discrimination, economic and social rights. So let me take the example of the first. Freedom of expression, association right to protest. At the moment, some of the most violent repression of those rights take place in the context of people defending their land or people defending their livelihood. So when we do our traditional quotation mark work on freedom of expression and association, we are often drawn into environmental climate change issues because they are just there. And frankly, even when they are not, if you look at workers issues, that repression in the context of people fighting because they've lost their jobs or because they are confronting corruption, climate is never very far from that and the transformation of the environment. So our traditional areas of work does lead us to confront the implications of climate change. And even when it doesn't, it's still a very important piece of work. So we are working for political prisoners in Russia, such as Alexei Navalny, we are doing work with Iranian defenders or Saudi journalists being imprisoned, you know, all of these are a central component of our commitment to rights and they will always do so. But I just wanted to point to the linkages and to the integration of the human story. And the other issue that we are very concerned about is non-discrimination, is a right to equality, whether it's around gender equality, LGBTI, racial equality and so on. And equality are deeply, the quality is deeply affected by climate change and climate injustice is first and foremost a question of equality. It's, you know, the people that are facing climate injustice of our people who are already very vulnerable in the same way than the pandemic affected people that were already the most vulnerable.  It's very much the same. It is indigenous people. It is minority groups living in certain kind of environment that are on the frontline of the climate crisis. So climate is also a question of equality and inequality and that too is something that we do very much. But again, I also want to point out that we do work on gender equality even if it's not related, for instance, to climate. So we do a lot of work on sexual and reproductive health. We do continue to do an advocate for LGBTQI rights and that is and remains an essential part of our work. So, you know, as an organization, we do try to carry forward those issues to somehow demonstrate the integration, the integrated story of human rights and how all of those things are linked with one another. Yes, there's one other thing I wanted to talk to you about Agnes and that is this. We touched on it in our conversation before the show. You know, just in my lifetime and my life experience what I have seen and read and heard and thought about, it seems to me that the issues you describe, the injustice, the violations of human rights, the atrocities, the racism, so forth, are getting worse. I mean, look for example, just one tiny example is Roe v. Wade in the United States. It seems to be going away a step backward. And there are many places where there seems to be a step backward. Amnesty International has its work cut out for it. Going forward you have more challenges, not less. And I think of, you know, Ethiopia and Sudan and Wanda and I think of all those countries, Nicaragua recently, Venezuela and South America. When I think of China, I think of human rights going backward. And I'm not sure how to deal with that. I'm asking how you deal with it, both as Amnesty International looking down the road of what might be a more difficult world, a less just world and individually how you feel about it because you're doing it every day and you're scoping on all these things happening everywhere with your huge organization. How do you see the future?  Now that we're approaching Christmas, you know, it's the dark side, it's a Christmas future. What is it for Christmas future for us? Look, you're perfectly correct. As an international community, we are confronting an unprecedented number of challenges that feed on each other. We've already spoken about the climate crisis which is really existentialist in its impact but it's not the only challenge of an historical nature we're looking at inequality that is increasing within state and between state. It had decreased for decades and now after 2008 and the financial crisis, it has skyrocketed. We're looking at an industrial revolution around information technology which is fantastic in many respects. That's why you and I are talking but as, you know, very dramatic and possibly again existentialist implications. We don't know and we do not control that innovation. We do not know what artificial intelligence will bring to the world and to our societies, biotechnology and so on and so forth. But what we do know in that it's gonna transform us deeply, it may even transform what it means to be human. The demographic divide is another big challenge for our integrated community. There is an old getting older, rich Western world and there is a young, very young youth in South's restless world. In some countries, in the global South, the medium age is 15. In our, you know, in a country in Western Europe or in Japan, it's above 50. So that too is, you know, it's a force for the world. It's a fantastic opportunity but it's also a very big challenge. Refugees, migrations are linked to that demographic divide. They are linked to climate change. By the way, I forgot to mention that earlier. You know, they embody refugees and migrants really are at the intersection of all those terrible challenges. So that's some of the challenges we're confronting. In addition to the fact that right now the international system is being reshaped, the US, China, Russia are all vying for hegemony and superpower. The multilateral system is crumbling. Frankly, it's not resisting that particular fight. The normative framework that was established, the UN Charter, the rules that brought us together after 1948 are disappearing, being challenged or not being obeyed or, you know, for whatever reasons. We're really looking at a possible normative counter-revolution internationally or domestically. You're mentioning the United States. Almost every democracies is looking at a major crisis is in the middle of a major crisis. So that, I mean, as a model of governance, I think democracy has reached an historical extremely problematic stage in its development and it could all but crumble also under the assault of populism and anger and frustration and fears about the future and so on and so forth. So, yes, I think it is fair to say that we are looking at and we are in the midst of a very, you know, really unprecedented, difficult environment. And the question I ask myself, Jay, and the question I've asked of my colleagues at Amnesty is looking at it. If I look at it from a Eurocentric standpoint, you know, from the standpoint of European history, we have to ask ourselves whether we are in the 1930s scenario looking at World War II and Holocaust, you know, Allah 21st century, or whether we will be able to be a 1948 generation. That is a generation that will be able to rebuild the world without going through a third world war. And, you know, endless numbers of genocide. That's a question I'm asking myself because I actually believe that historically speaking, this is the challenge we are confronting. Of course, myself, I want to believe that the world somehow will be able to say, we want to be that generation that will rebuild the international system that will rebuild the rules without having to destroy them first. That's what I'm hoping. That's what I'm acting. That's what I'm doing. And that's what Amnesty is doing as well. Agnes Calamard, Secretary General of the Amnesty International, you touch me in my heart, Agnes. Thank you so much for coming on our show. I hope we can circle back and talk to you again as time goes on. Thank you very much, Jay. It's a pleasure to have joined you. And if I may just say, yes, we're looking at a difficult, extremely difficult scenario. We are looking at a very historical challenge for the international community. But I just want to end on a note of hope. Around the world, people are not passive, Jay. People stand up. People go to the street. People raise rights. People go on the offensive. And they can do so without the use of violence. There are movements around us that we can join. There are many people who go on, who try to protect those that are most vulnerable. Yes, there are a lot of people attacking refugees and migrants right now, but there are also quite a few that stand up with them. So we can stand shoulder to shoulder with one another and we can confront those challenges. And there are movements around that are doing just so. So if I have to end with a note, just join them. You know, be strong. It's tough out there. It's very confronting, but we can do it. Agnes Calamard, Amnesty International, from your lips to God's ears. Thank you so much, Agnes. Thank you very much, Jay. Thank you very much. Aloha.


Okay, I think that the trickle is slowing, so I think everyone is starting to arrive at the webinar, so we'll just kind of ease into it. First, I just want to say hi and welcome everyone and just say thank you for joining us. This is a webinar about leveraging open ecosystems to enhance reproducible workflows. So I am Nikki Pfeiffer, Chief Product Officer at Center for Open Science, and I am super excited for this webinar today. One of the things that I enjoy most about working at COS is the mission, which is to increase open this integrity and reproducibility of research. And what's the best part is that this provides the opportunity to develop open source software for our communities, and to be open about our roadmap and our development plans, even going as far as collaborating with our user communities and what those priorities are and what their needs are that we will work on. And lastly, prioritizing an open API for access to the OSF content so that we can increase that transparency, accessibility, and even interoperability with other systems. And to create this community for developing innovative workflows that anyone can use with the OSF. So for me, this just kind of encapsulates a really great group of wonderful use cases and examples for how that actually takes shape in real life. So I'm going to turn it over to Eric, who's going to talk about a little bit more about how that works within an open ecosystem. Thanks, Nicky. So I'm Eric Olson. I'm on Nicky's product team here at the Center for Open Science working primarily with the infrastructure that we developed to support those missions that Nicky has spoken about. And I would like to talk a little bit about the mission in terms of a contradiction that our mission statement calls out, a seeming contradiction where we talk about infrastructure, research infrastructure as a research commons that it wants us to be flexible enough to respect the very many different ways that researchers approach their work based on their disciplines or their regions or other needs, but also specific enough to be a solution for problems that researchers are trying to solve. So it might seem like you're trying to do very different things, but here we think of them as part of our strategic plan that really if this is a community effort, as Nicky pointed out, but these are dialogues and really not contradictions that clash if they are creative tensions that give us opportunities for creative solutions. And for us, the primary pieces of infrastructure that we've developed to support those workflows is the OSF. And workflow support and management tool, it has features that support each element of each phase of the research that researchers, any researcher is going to be doing, they may do them differently based on their disciplines or their data needs or other approaches, but they each have some needs at these various phases. So the OSF and other interfaces and tools within the OSF that we have developed over time have been in support of that mission of supporting with infrastructure and making possible better practices within these workflow phases. And quickly, one of the ways, or really the primary way that all of these features at the OSF come about are a combination of several factors. We have integrators, which we're going to talk about here in just a moment. We have members and supporters on that mission slide, so a little bit of the groups that fund the COS through various grants and other support. We also have members through a number of our fee-for-service tools, including universities and publishers and funders. And then we have users, researchers that contribute and use data on the OSF and the technical outcome of all those things coming together as the OSF as a tool. But really it's all a community effort between these groups and ourselves sort of acting as a facilitator where they're all, you know, coming together and overlapping to turn that into a specific workflow management solution with the OSF. And again, looking at this workflow sequence here, one of the primary benefits of using the OSF and one of the exciting parts of working here is that it isn't just the OSF in the vacuum, it's actually a lot of tools from across the life cycle and across the landscape that are integrated with the OSF. This is only being a few examples that we have built connections with or have memberships with like across the rap and data site, or we've built integrations with a number of storage providers and citation managers because research communities came and told us that was really important to them and would strengthen the OSF and their workflows. But there are many, many other connections with the OSF that are made possible by an API that we've spent a lot of time developing as its own tool, you know, alongside the OSF as a user interface, making sure the API is is highly well documented and highly usable. And that's not just an us effort, it's an effort of many different groups across the community, including the gentleman what we'll speak to today. And the API for those that are not familiar is a interface, a tool, a way for our systems that normally would not be able to communicate with one another, they use very different kinds of information or languages. It gives them an information information and the ability to talk to each other, so they can exchange information when otherwise they probably wouldn't be able to or would be very difficult for them to be able to do that so we're going to see today or a few examples of research communities or individuals that based on feedback from their users or across their communities, they saw a value in using features or elements of the USF by way of the the API to strengthen their tools and by effective strengthened the USF and how valuable the USF can be. So you're going to hear from several speakers and then we'll have some time to reflect on each of their individual tools as well as how they interact with each other and with the USF and with other parts of their community toward the end so use your, your Q&A box and drop things in we'll reflect on those towards the end of our afternoon together and otherwise we are ready I think to hand off to our speakers. Yeah, great thank you for sort of setting the stage I think you did a wonderful job Eric and I appreciate sort of the articulation of the interoperability because I hear that word it's really important for tools to be interoperable but really understanding what that means from a real example use case is what I'm excited to hear more about from our speakers so I think to kick it off we have Lenny from protocols.io who's just finished a new integration with OSF for sharing open protocols.  Absolutely. Thank you. It's a pleasure to be here and many thanks to the Center for Open Science for organizing it and for the invitation. I'll spend, I think I have 12, 15 minutes I'll spend just a couple of minutes with very quick background of protocols.io and then really focus on why integrations and API from the protocol side and from the Center for Open Science. Why this is important and I think you're going to hear me reinforce many of the things that Eric just mentioned. And I'm not going to give a demo of the functionality and features of protocols.io because I don't have enough time, but I am going to go through the slides that we typically present when we talk to researchers about protocols.io or universities and I think it will highlight why the interoperability and integrations are so important. And our mission is very similar to that of the Center for Open Science we're trying to improve their reproducibility of published research. And I always start with this favorite tweet of mine from a biologist who says I'm looking for a protocol in 97 paper is described in 96 finds 96 papers described in 87 finds 87 paper and it's paywalled and this is a biologist at UC Riverside. So you see campus they have a lot of subscriptions but not to this particular paper so it's a common and frustrating experience it's not particular to biology here's a physicist. Devices were fabricated as previously described previously described previously described and the original references devices were fabricated with conventional methods. And this is very common we all those of us who are researchers we've all come across papers like this and I have a long collection of tweets and blog posts around exactly this. But the one other slide on this I want to show actually refers to work from Center for Open Science and collaboration with the science exchange company where they try to reproduce this is the reproducibility project cancer biology. It was a big effort to take 50 published cancer papers and independently reproduce results from them and when the first five papers going through this project where you finished there was a lot of media attention to it and one of my favorite. One of my favorite articles on that is at young and the Atlantic who wrote that one of the hardest the hardest part of this project by far was figuring out exactly what the original labs actually did. Scientific papers come with method sections that theoretically ought to provide recipes for doing the same experiments but often those recipes are incomplete missing out important steps details or ingredients. So, the mission of protocols that I owe is to make the method sharing easier, more reproducible capture the important information organize it, and make it easier to share and collaborate before during and after publication. It's very much in line with the mission of Center for Open Science. The main benefits are that using protocols that I owe publicly or privately you have communities or internally in your group you have protocols organized in a single place. There is concurrent editing history of changes as people come and go the knowledge stays and you move away from the situations that we saw described in the previous slide where no one knows what exactly was done for a particular paper and then when you're publishing you have a DOI, you have a citation protocols that I owe you can link to exactly the steps from the paper of how the research was carried out and hopefully you get also more credit for the method development. At this point, so we launched in 2014. At this point, there are 9,000 public and over 30,000 private protocols and protocols that I owe and we're growing at about 1000 new protocols every month from hundreds and hundreds of scientists. And our business model it's important to highlight here is similar to GitHub where everything that's public is open access free to read and free to publish. And if you're using protocols that I owe privately. Whether in academia or in industry, that's when there's a subscription fee and so there are over 500 journals that encourage in author guidelines using protocols that I owe to share the detailed methods. And then there are the funders that recommend or require protocols that I owe universities that kind of similar to the membership model with OSF universities that have been signing up for internal campus wide use of protocols that I owe. The reason I highlight the business model and all of this is it really does tie into why we have the API's and integrations and so typically just before this I would have done demo of protocols that I owe and then before I take questions I always finish with this slide which is preservation and backups. And you can see OSF is on the slide and I talk about the fact that we have public API's just like Center for Open Sciences OSF. We have integrated export into Google Drive Dropbox OSF and I'll talk about that obviously in much more detail in a few moments. Daily backups, we send every all of the public protocols to clocks, we mirror everything in that's public in a GitHub repository and through Internet archive. And this is a really important slide, especially when we're presenting not just to researchers but to universities to librarians. There's a lot of trust. And when we talk about why are in API's integrations, why is this interoperability important. In my mind there's two answers to it. One is the researcher, and that's the key reason because exactly as Eric was saying, there are a lot of tools, there are a lot of platforms, there are a lot of interfaces that researchers use. There is great resource from the Harvard Medical School Library, and it's a survey of different electronic lab notebooks I think there's 30 in this list so this is a matrix of what are the pluses and minuses what are the different features but you can't expect your user to be on one platform or using one tool. Right. And given that there are a plethora of electronic lab notebooks repositories right and lots of different places where the scientists are if you don't have API's you're limiting yourself and you're limiting the functionality and usability of your tool and your platform so one obvious reason to have the API's is to allow the integrations and to be where the researchers are and facilitate their workflows and make it easy to connect to the other tools. And the big part, the second component of it from the protocol's IO side is the trust right why I show that slide whenever I present around preservation backup is we're for profit as I did say what our business model is, but open access or not for profit or nonprofit. There's always a question from the researcher from the librarian there's always a question of trust will you be around tomorrow. Are you sustainable. What is your governance. If you're for profit.  If you're stable. Why you tomorrow right and maybe the organization that buys you doesn't have the same principles and ethics that are in line with what the librarian is seeking and so we highlight the integrations we build the API very early on and put a lot of efforts into documenting it because it's a key part of the trust and going back to that slide. It's not just these integrations behind the scenes if you start thinking about who are we plugging into this entire ecosystem just as I was showing. Right. What you sign in with orchid when you publish a protocol. If you added your orchid ID, it will show up in your orchid outputs. We send women to do why we send everything to crossref. The internet archive integration actually comes through crossref they're using crossref to mirror our protocols right so you can see that these are just some of the things API and here are two of those 30 lab notebooks in the survey that are using protocols that IO API is to connect to us and pull protocols from us there are many many other integrations taking advantage of protocols that IO API is and you can see it by directional right like we're connecting to SF we're connecting to Google Drive and that really is the future and whether you're for profit or nonprofit. It makes business sense. It makes sense from usability and the perspective of the researcher to invest in APIs and invest in integrations and on that note. I mentioned internet archive and on that note. The next question is why did we recently integrate with OSF I'll show, you know it's a simple integration well documented APIs on the OSF side. So that made it easy to connect. Why did we email OSF and say we'd like to connect, you know, what are the next steps. It's actually because of the presentations to librarians and universities where they would ask. Over the past year I think there were two or three presentations where a librarian from a different university would say, are you integrated with OSF we have people using OSF and the next thing we did when that question popped up more than once the next thing we did is we went to some of our users and turns out yes indeed they're using OSF and they would welcome the integration not just with Google Drive and Dropbox. And at that point, because the OSF APIs are well documented it becomes a no brainer that you want to do it. Both for the presentations to librarians for that trust aspect and for the researcher right so those two key reasons. And so here is the file manager on protocols.io you can select an entire folder, all of your protocols all of your files, one at a time or in bulk, click export, navigate to copy to OSF. And you say this is the file that I'm about to send to my OSF account. And here is where the OSF API comes into play so you get authenticated we're pinging OSF you sign in your authorize connecting once you've signed in. I just tried at 130 this morning after giving a talk to a Japanese group. So this is something that works it's not just it's not photoshopped it's real screenshots from this morning. So this is my OSF route. I would select where I would like these files to go. And then it takes a couple of seconds done synchronizing with those steps so this is on protocols.io and then I navigate to my OSF space and there's the file uploaded today at 130 in the morning. And it, you know, it is an investment to develop API's it is an investment to document them and keep them up to date. It is an investment to even, you know, even when someone does have good API's. It's an investment to connect to them right so we did have to have our engineers connect to OSF, even for this simple workflow, but it pays off. It's worth it for the researcher. Our users welcomed it. Here we are on the webinar discussing it and I whether, you know, just to finish up whether for profit or nonprofit I don't see how you can really be a stable and trusted player. Participant in this ecosystem. If you're trying to encourage collaboration, reproducibility among researchers, you can't not participate in that collaboration and integration with others as as a for profit or nonprofit. So I'll stop there, and we'll be looking forward to the next presentations and happy to answer questions at the end. Thank you Lenny that was fantastic. And I'm yeah personally really excited for this it's been one that I've heard bubble up among different research communities over the years so it's it's great to see this come to fruition. So I don't see questions and we're going to save any anyways to the end. But if you did think of something while Lenny was talking make sure to drop it in the Q&A so that we can pick that up at the end. Okay, so next we've got Stefan and he's going to sort of talk a little bit about Jupiter workflows and OSF. Hello everyone. So yeah, my name is Stefan Boilman. I'm a research fellow at the School of Information Technology and Electrical Engineering at the University of Queensland in Australia. I'm not a developer of any of these APIs, but I'm user. So I'm, I would just show a workflow that we did for a recent paper. And based on that workflow, always have the OSF team got in touch with me and asked if I could present what we did there and maybe it's useful for for someone else. So let's get started. Well the first thing that I often hear from colleagues and especially older colleagues as well open science is easy right. You simply put all your data in a zip file, and you upload it to Dropbox and you paste the link at the paper right that's that's what you do. Why do you spend so much time on making things nicer for users. The reason is that I think it's not that good, because if you if you think about it, if a user has to download two gigabyte file just to see which functions were used. That's not so cool. Then also, if I just put my MATLAB code and my data together. I'm relying that the user has the right MATLAB version. I'm relying on an assumption that the reader has a MATLAB license at all. It might not work. It might not work in a few years. Maybe MATLAB is not around anymore. So I don't think it's it's it's that useful for people. Then also Dropbox is great and it's around for a few years but what if and Lenny also mentioned that what if Dropbox gets bought out by someone and they close that free service down what if Dropbox runs out of money. What if they just stop that free service then you have a link in a paper and that paper is a record of your research and suddenly that record is not there anymore. And I actually had that problem in one of my earliest papers have a link in there and the service was closed down a few years later so I actually was affected by that and I started really thinking about this problem. But then a trivial thing I found a bug and it happens all the time because the more lines of code you write the more bucks you will have. So, I haven't had a single paper where I don't have a mistake in there. And I always had to do something afterwards to fix it. So then the problem is, what do you do right do you just exchange that whole zip file and fix the bug do you just leave it in there do you add a little text file and say oh by the way that's actually wrong and it should be that. Yeah, it's it's a lot of open questions and as I said I ran into these exactly these problems while reproducing other people's work and also with my own work. So I was wondering, can we somehow do this better. And well this is, this is where I am today so I would say the first example is where I was a few years ago. And this is one of our recent papers where I really tried to to learn from my mistakes and try to do it a little bit better. So, first thing is, I put the code that we used in the paper that reproduces the results of the paper. I put in an interactive Jupiter notebook that runs in the browser that runs on Google Colab. So Google Colab provides a lot of free computer resources including GPUs. So it's a very nice way so that people can quickly play with the code. And the good thing is, oh there's a hand up from Aaron, do you want to ask a question or. Okay. So yeah, they can run it interactively in the browser so there's no setup required they just click on a link and it just works they can just play with it. And I think this is super nice and accessible. But of course the problem is if Google Colab would get called to tomorrow and Google is known for just chatting down their services so I was aware that I can't put in a Google Colab link in my paper because Google Colab will probably not be around in five years. And then, yeah, that's that's then where OSF comes into play because OSF is probably around for 50 years because they have a preservation fund. So I thought, okay, let's combine all of that and OSF so I will show a little bit how we do that today. So, and this is the thing, the platform that's why I just said a cloud based platform, because there are alternatives to Google Colab I just used Google Colab because it was around. And I have the link of that in the OSF repository so I can easily change it later down the track. Then also, instead of dumping my code in a zip file. It's of course on GitHub because GitHub is super nice for for people to interact with the code to fork the repository to fix bugs to report bugs to discuss the code so it's it's very nice easy way to share the code. And then also, GitHub gives me this nice feature that I can have a commit bug where I said this is the code that was used for the paper. So I'm already assuming that I will find the bug. And with that paper actually haven't found the bug yet in the code so if you find one let me know and we can fix that. And Lenny already said that as well, what if GitHub is not around anymore what if GitHub gets bored I mean we were lucky with the Microsoft acquisition that Microsoft actually wanted to develop that further.  Then again, I have a link that's not working in the paper. Yes. In this case, I'm, I assume that GitHub is so relevant to a lot of the research community and a lot of people out there that GitHub will not just simply shut down so here I took the risk, and I actually put it in because I thought usability here is better. But I have a backup, of course, so the GitHub is linked to my OSF. So in case GitHub goes down, GitHub is preserved in my OSF and I will show later that this is part of the snapshot that that get that OSF does off that so it is preserved, but here I took the risk that GitHub might not be around. But if GitHub goes down I think we have bigger problems. So, and then finally, well, yes, as I said I combined all of that on OSF. So here I can update the data, I can update the links, if bugs were found I can, I can preserve everything that I showed there in a timestamped snapshot which is the registration feature which I show later. And all of these examples use a lot of APIs from all these tools from from GitHub from from Google Colab so I want to show a little bit how to tie this together. So let's get started. Okay, so the first problem I had is how do I get my data nicely accessible in this cloud based platform because, yeah first I have to get my data there. The problem is that a lot of researchers use high performance computing systems. And also, we're not just creating 10 files or 100 files. My files usually are a million files. And this is bad. If I want to take the browser upload feature that OSF has an upload a million files. Well this publish when this paper will not get published in the next 10 years so I will just be too slow. So I need something that just does it nicely from the command line that I can script. And also, I'm probably not just doing this once because as I said I make a lot of mistakes so I probably have to do this multiple times. So, the first thing is, let's connect a storage back into OSF so of course you can use the OSF storage for this as well just to keep it simple for now but I just wanted to show that this is possible so in Australia we have a really cool storage provided by our infrastructure provider on it which is called cloud store cloud store basically is an own cloud install that gives every researcher. One terabyte of storage for free and if you ask for more you get infinitely more storage so it's it's basically our research storage. And the thing is if I would use the OSF storage I'm limited to five gigabyte for private projects and 50 gigabyte for public project. As I already said, a lot of our data is bigger than that so it wouldn't fit into that so that's why having these external storage providers is really really useful. And the setup is quite simple so you have to set it up once for your account where you authenticate and then you edit as an add on to the project where you want to use it. So these full webinar on storage integrations of OSF already on YouTube so if you if you want to look that up it's it's nicely described how to do this and how to add your own storage apis. But I must say the list is already pretty complete for storage apis. And this is also fairly straightforward. And if you, if you struggle for example with own cloud I wrote a little example on my blog, where I show how to connect an honored cloud store to OSF and just go through really all the details and if you're interested. Okay, so now we. Now we need to upload up and now we need something to upload our data there from our high performance computing system and there is another really cool open project and this is not maintained by OSF this is a community of OSF users that had exactly the same problem as I did they had millions of files and they wanted to upload them to OSF and also download them. So this is an OSF command line client. It's a, it's a project that started a few years ago and they're still quite actively maintaining it and fixing bucks, and it's an easy install so it's just if you have a python install ready it's just pip install OSF client, and I've never had any issues with it it's super easy it doesn't have a lot of dependencies just install it just works on almost every system I used. Then it's as simple as navigating to the folder you want to upload to OSF and then that folder can have a million files below you do an OSF in it in that folder from the command line. And then what that does is it asks you for your username, and this username is the OSF username, and then it asks you for a project ID, and this is the OSF project ID. Here one little thing if you're trying that. I had problems in an earlier version with OSF client with the OSF command line client when I used institutional lock in so when I use something like orchid authentication, because the problem is this project did not implement correctly the token, the authentication token in the background, and this authentication process actually failed so I had to create a true OSF account with my university address, and then it was working because then I didn't need the authentication tokens, but I just checked the GitHub repository and that bug was fixed they realized that they hadn't implemented this token correctly. And it looks like it's working now, but since I now have my own own cloud, my own account on OSF, I couldn't test it with with my orchid account. So, yeah, it should work. Then let's test the OSF client so if you just do OSF LS, what will happen is it asked you again for your OSF password. And then it shows you that cool I put a test file in my own cloud that I have linked to OSF, and then I see that I have a screenshot in there, just as an example if that whole integration works. So that's super fun, we can see the files. So now, how can we upload our files them. Well, it's as easy as you could imagine, it's just OSF upload, and then dash R is for recursive. The dot means I want to upload all files in the current directory, and then OSF storage slash data is the target OSF storage in this case means that it will end up in the OSF storage, and data is a sub folder where it will end up in. One interesting thing, if you exchange OSF storage to, for example, own cloud, it will directly end up in your storage integration that you did with own cloud. So it's really, really transparent just ends up on your institutional storage. So now I don't have to figure out how to connect to my own cloud because also they have their own token system. I could use something like our clone and try things but the thing is with OSF you have one interface and it just connects to all the different back ends and you don't care if own cloud goes away tomorrow. Well I just uploaded to Dropbox or I just use anything else. Nothing changes for me it just changes what word I put there. And if you try that the project, the OSF client project has a list of supported providers storage providers and not all providers are implemented yet. So I added own cloud yesterday to the list. And if the pull request gets merged it should work. And also it should just be a name of the storage provider that they have in a list because that's how to identify if the storage provider is is actually valid. So if anyone from the OSF team is keen, you could if you could add all the storage providers that you provide with the correct mounting names on your system to the project. That would be super fun because they have an open pull request where they say well we don't know how OSF calls these things, and we don't have, we don't have accounts and everything so we can't test it. But yeah, so if anyone is keen to do that that would be super cool. And now we got our data there. How can we now use that data for example in our Jupyter notebook because I said I want to pull that data for the users and just make it super nice. Well and lucky us again it's very easy in a Jupyter notebook, you can install everything you have so this is Google Colab as an example. If you add an exclamation mark it means you will execute that command not on the Python interpreter but actually on the underlying command line so you have a Linux system running below that. So you can just run pip install OSF client and then it will just go and install it and since it's a super small package it will just take a second. Again if you're interested in more details I also wrote a detailed blog post about this last year. So if you want to play with that go for it but it's it's really just a few steps that I'm showing today. So then, if we want to use this OSF data in the Jupyter notebook, the easiest thing is to make our OSF repository public, because then we don't have to handle any authentication again. And this is the point in the end I want this thing to be public so let's just do that. And then to get all my files that are uploaded there. So again a simple command OSF dash P for specifying the project clone and then the dot says where you want to have these files and then dot means here. And then if I do an LS I see it pulled all my data from OSF so it pulled the OSF storage it pulled own cloud. And that already works so they can pull all storage providers, they just can't upload yet to all storage providers because for this they need to know which ones exist. So if they are there, they will just pull everything. So that works really very well. Cool. So now let's let's look at GitHub. As I said, GitHub might close down one day and to avoid problems with this is, of course, I connect GitHub to my OSF account and you also see. GitHub is supported as well in case you want to use that which which I did, and it's also working very well. And it's the same procedure you authenticate once and then you add it as an add on to your project. And then it's there. And now that's a really cool thing that I was actually surprised that it works. So GitHub now has my Jupiter notebook in there because I version control it with GitHub and Google Colab actually just saves directly to get up so it's super easy to update your notebook and then it's tracked on GitHub, which is such a cool thing again because it's an API in the background to very different services just talking to each other. And yeah, when you when you have the OSF GitHub integration on and you click on your Jupiter notebook, it actually renders it in the OSF interface. And what I did is I put a Google does that actually they put a little open and Colab button on top. So it looks like on GitHub where you can just click on it it brings into Google Colab, and it will just run that. And yeah, as I said, if anything of this goes away if GitHub goes away tomorrow well I just put it on on GitLab if Colab goes away well just put it on Asia. It's total flexibility and it's really I can just reiterate what what Lenny said it's it's really you need that flexibility you need that because this stuff has to be around for 10 to 20 years because we're doing medical research, and it might be interesting for people down the track what we did. Good. Last thing, how does OSF help us to preserve all of that. And I'm not sure if I'm misusing a feature there, or if, if that is the way to do it because I was looking for a snapshot feature where I can just take a whole snapshot of the repository and archive it. And the way to do it, I think is using a registration so maybe some of them was I've gone correctly there if that is the right way to do it. But what I basically do for my project is at the point of publication, I file a registration of the project. And I just say, this is the state of publication. Please go away and archive all my files that I have and put it in a snapshot and preserve it in a, in a basically immutable snapshot that that no one can change and that also doesn't go away so this works very well for me. And yeah, now the cool thing is I have a snapshot of the paper when it was written when it was published. And then I also can update code later. So then people have the state of the publication, but also the publication is still alive. It's not just that dumb PDF record that never changes but it's actually more people go there, and they actually can do things afterwards update. As I said, there will always be bugs that will always be changes. So we need to be flexible to that. Yeah, so I hope this was interesting and useful and you saw that it doesn't take much to create reproducible workflows. Once you have such a great open ecosystem around us that just enables all of us to do this so you just have to have to know that it exists. But in the end, it's just a few clicks. And it's actually easier than making a zip file and uploading it to Dropbox I have to be honest. So this is pretty much what I had prepared today. If you try anything I showed today you run into problems. Feel free to get in touch with me. I've had many of these issues and I might have seen that that error before. So I might be able to quickly help. Then I thank you for your attention. I think the OSF team for organizing this webinar inviting me to present one of these examples for an open workflow using OSF and then I'm looking forward to your questions later. Thank you very much. Thank you seven that was awesome. I loved one the Easter egg you left in your code for us all to find as a challenge. And then the fact that you, you've already added and contributed back to the OSF client tool with the own cloud capabilities there. And just really quick before Aaron takes off. But if you want to start getting your slides ready Aaron that would be great is just see there's a question. Yeah well I also want to touch base on the use of registration for the, for the workflow that you were talking about and that's absolutely one of the use cases for it so I think that was a beautiful illustration of that. And there's different templates. So the one you showed was a pretty rigorous template that asked for a lot of input there's also the open ended registration template that doesn't ask for as much it might be the best way to just provide a description of sort of the archiving that you're planning to do. Great. Good. Yes I was already wondering why I have to enter so much for just reserve the record. Yes. Okay, that's good. Yes, and I was a question and chat does the client work with two factor authentication. I haven't tried it I looked through the code and I didn't see anything that wouldn't appear to work with two factor authentication, but the team is quite open for these things so if you, if you propose that and you implemented it was very well documented and the API date they use so it should be possible if there is an API in OSF for two factor authentication I think people could could implement that easily. Okay. Yeah, I don't know either but we'll certainly find out and try to get an answer, either during the webinar follow up after. Alright it looks like Aaron's already and loaded to share a little bit about workflows with our and OSF take it away. You're muted still there Aaron. You did. How about there. Good. Much better. Okay, can you see my slides okay. Great. So thanks for having me. I really enjoyed those. Those two talks I did not realize OSF could render Jupiter notebooks that is super cool and I'm looking forward to trying that out. So I'm coming at this from a slightly different perspective. I am the lead developer and maintainer of OSFR, which is an R package for interacting with OSF and it's built on top of OSF open API. So I have my contact info here if anyone wants to get in touch offline with any questions, but I'm going to give you a little bit of information about me, how I got involved in this project and the motivation for it. So I am what you would call a recovering academic and I'm currently a software engineer at TileDB, which develops a scalable universal data storage engine. But my background is in computational biology and I've actually spent most of my career in research and the origins of OSFR date back to when I was an assistant professor at Virginia Commonwealth University, splitting my time between research and developing VCU's data science lab, which was critical to the development of OSFR. So this is an organization I co-founded with my former colleague, Dr. Tim York, who is the DSL's director. And it's focused on helping VCU researchers and students take advantage of modern computational tools to improve the reproducibility of their work through training and collaboration opportunities. And we were motivated to do this based on our sort of own experience with collaborators and sort of witnessing firsthand the non-optimal workflows that people can use to manage the research and work with their data. So there's sort of this problem that computers have become an essential tool in research but training with basic computational skills is not usually part of standard training curriculum. So for me, you know, someone with a computational background, my research toolbox includes things like R for performing analyses, GitHub for managing my code. These tools, for a lot of reasons, but most importantly, they allow me to automate repetitive tasks.  But I don't really know how to do anything that doesn't involve using a keyboard. So most of my research involved working with collaborators who would actually, you know, generate the data. And these are, you know, incredibly smart and skilled individuals, but it's not reasonable to ask them to learn something like get so they can push their data to my repository.  If attachments were too large USB drives could be involved. And you know, all these sort of things that we know don't represent best practices for research reproducibility. And so one of the first things we focused on at the DSL was getting researchers to use OSF to manage the research. So we signed up VCU as an OSF institution, we offered introductory workshops that really focused on, you know, how much more your, how much more efficient your research could be. If you base it around OSF as the hub. You know, it, it, we would highlight things like centralized storage for your research materials automatic version control the ability to selectively add collaborators, all those things that make OSF great. And generally, adoption was quite high. And I think a big part of that was, you know how relentlessly focused COS has been on keeping OSF interface, you know, very approachable and user friendly. But for me personally there was still a missing link which was no direct connection to our, which would create, you know, a lot of additional opportunities for automation and generally making the computational side of research, a little more efficient for people who use OSR. And so I was delighted when Courtney Soderberg and Tim Errington who work at COS approached and asked if I would be willing to work on an R package. I think I literally jumped at the opportunity because it was something I, you know personally really wanted. And I figured there are many other researchers out there using are an OSF, who would also benefit. So I had practical considerations that made OSF are possible though that I wanted to point out, you know the first was I had some protected time to work on this. Because of my involvement with the DSL, which supported half my time in the VCU office of research who provided the funding they agreed this was a worthy project to work on. I didn't have to, you know, work on it and nights and weekends was something I could actually dedicate a little bit of time to. And I'm just mentioning that in case there are any funders or developers, you know who never tried getting funding for a side project. If it's something that's really contributing to, you know, the open science community it's it's worth trying to to get some funding for that. The second part of that was OSF API itself. The first time I looked it over I was incredibly impressed by how comprehensive it is how well documented everything is, as Lenny mentioned building something like that takes a fair bit of time. You know it's not something that happens automatically you really have to put work into it. But the benefits are obvious right now we have this wonderful resource that other people can build on top of and continue extending this open science infrastructure. So if there are any other tool builders in the audience, I highly recommend checking it out so really is a delight to work with. So let's talk about the package itself and some design considerations that went into it. So, OSFR provides a high level interface to the OSF API. So it's not a one to one mapping, you know, of our functions to API and endpoints. The trade off is, you know, we support a much more limited set of actions than the API offers, but we use those as building blocks to provide interfaces that are more convenient to our users. So, you know, for example, the API lets you upload a single file at a time. OSF Web Interface lets you upload multiple files, but you can't upload folders, right. So OSFR like the Python client that Stefan mentioned supports recursive uploading so you can upload an entire project all at once, which makes it very easy to replicate a local project on OSF. And, you know, the OSF API it's incredibly comprehensive let's do all kinds of interesting things with registration and pre prints and so on. And OSFR basically ignores anything that's not directly related to project management. So we provide classes for representing, you know, three basic types of entities projects and components, files and users, and then a handful of functions for performing the most common kind of tasks you would perform on those entities. So things like creating projects uploading files, moving them around, deleting if you're careful, those are all the kinds of tasks that fall squarely within OSFR scope. So the last important consideration was user friendliness. Like OSF itself, I wanted OSFRs interface to be very approachable. You know I wanted students who were just learning R to be able to use it. And the data structures that our users are most familiar with our data frames, which is how our represents two dimensional tables of data. The first row that we retrieve from OSF is returned as a data frame, where each row represents a single entity. So here in this example we have a data frame that contains two OSF files. And you can see what the file names are the unique identifier that's assigned by OSF. And then we have this third column called meta. This means all of the JSON data that's returned by the API. So this includes everything OSFR needs to represent these objects and perform subsequent actions on them. But they're deeply deeply nested data structures that can be pretty tricky to work with. And since most users don't need to access them directly we just kind of tuck them away into this, this third column here. So OSFR for our users in the OSF API in general is you know we can close the loop around this incredibly useful hub for managing research and create a workflow that anyone regardless of technical skill level can participate in with without having to sacrifice efficiency. So for me it meant all of my projects start with a script that downloads the necessary data from OSF. All of the results from my analysis are then uploaded automatically so it's not a step by I forget later. And then my collaborators receive notifications that hey you know there's a new set of results or tables for you to look at in everyone goes home happy.  So we're going to use OSFR to create a new project on OSF and then populate it with some files, just to give a sense of how it works. So I will switch over to our. Can you guys see our studio here. Cool. So the first thing you have to do is load the package so library OSFR. And it's installed I have generated a personal token, which authenticates me as the OSF user, we have documentation available that explains a little more what what's involved with that process. So I'm going to create a new project called COS demo. I'm going to assign it to a variable just called demo project here so the function I need is OSF creates not component we're going to create the project. The title is COS demo, and I will make this public. Just to keep myself honest so we can verify everything actually worked correctly. So I'll run this. The output from that is a data frame, you can see here. This tells us, again, this is the title of the project. This is the unique GUID. So if you navigate to osf.io forward slash B97HM this project should now exist. I'm going to populate it with files so I have a couple of Word docs in my working directory here. So I like to keep things organized so I'm going to create a component called, let's see, research materials inside that new project. And then I'm going to create a subdirectory inside of that component called survey, since these are two documents from a fictional survey based project. And then for the last step I will actually upload the files. I can use an r function to identify all the Word documents or doc x files in my directory. And then we'll run this. We will use the correct name of the variable. Run that. I should have had some filler material here in case the upload took longer than expected. There we go. So again the output is a data frame. These are the two files we uploaded. You can verify everything worked using osf open. Give it the demo project variable. And that should open up your browser to the project. So there you go. We have our COS demo project. It has one component research materials, and then our subdirectory with our two files. Let's go back to the presentation here. Okay, so that's, that was all I have. So in the slides, I have a few links if you'd like to learn more about the package. So there's a website with all the documentation the source code is on GitHub. And there's also a blog post that was published by our open side that used the open science framework in the context of someone who's a really are heavy user and sort of comparing it to GitHub, you know, how do the two services compare and differ. Yeah, so I'm looking forward to any questions you might have big thanks to the Center for Open Science for organizing this. And that's it. Thank you so much, Erin. That was, that was fantastic. I learned so much I'm actually not an R user so I got a little tutorial on how that works. And it's, it's a, it's an awesome package you built and I, I think it's very beneficial to the community to see how it will work or how could benefit them. I am sort of thinking at this time we should turn over to any questions that have been surfaced and Eric I think you either have some pre plant questions for us or we'll read from the ones that came up during the talks. Yeah, I, there may have been some raised hands among the panelists while we were going so if you do have one. Otherwise, I will throw one to you, one at a time and can think about them a little bit. I have one question for Lenny. So you showed for example your protocols are PDF files and I'm wondering, is that the preferred use case does protocols I also support structured data so like we have MRI protocols that are basically XML files that have a structure like 100 parameters and then they are hierarchical. Is that anything that that protocols are our supports. Sorry, I that that's the limitation of not giving a demo protocols that I owe is very rich supports components timers gives run functionality versioning for King, and it's set up for dynamic and interactive protocols discussions on step level right materials, their videos and side steps images table so it's, it's very rich content and the API access so with OSF integration and dropbox we just exported PDF and with clocks for long term preservation, but the API access to protocols that I owe we also provide Jason files with all of the structure. And of course the whole problem that I owe is that it's not the Microsoft Word document, right it's not a static PDF, but is dynamic is cool because that's a limitation of some of the tools we already used to do this yes because it just supports text and yeah no Jason things and that's really cool. Okay, great. Thank you, Stefan. So, Melissa and the Q&A panel has given us a really good question. So Aaron just mentioned a few minutes ago that part of the way that what the OSF started and was able to to become the tool that it is today is that he and his team had some protected time to contribute to that community develop tool. So how can funders or workplaces or universities identify when there is a right time to invest into the resources and the time for you and folks like your yourself to put that time and energy into those community develop tools like that. And when should they be contributing to those open source tools that that their communities, possibly rely on quite a bit. Anybody can pick it up but Aaron you were you were the initiator on this one. Yeah, I think that's a really good question. You know, it's so much of research depends on open source tools, and it's really amazing how often, you know, these widely used pieces of software are developed as side projects. And there's sort of a fairness component there, you know, because so many people extract value from them it seems like someone should be willing to invest the funds that provide the protected times to continue their development. So I think we just have to be more honest about how time consuming it really is to develop these tools, you know, it's. It's not something you can necessarily develop just you know on your lunch hour every day, you know, development takes time but it also takes time to respond to user requests and bugs and make fixes. And I think part of it is, you know developers need to need to speak up and say you know I'm developing something that does create value for the research community and I think you whoever that is should consider funding it but I think you have to be able to demonstrate the value you know part of the question when is the right time to maybe consider asking for funding and I think you sort of have to be at the point where you can demonstrate that it's going to benefit others, you know, beyond yourself you've solved a more general problem for people in the research community. Yeah, Lenny is a link in the chat and I think everyone can see you want to tell us a little bit about that one Lenny. So just an example of a funder that recognizes us so chance or group or initiative, the link that I shared in chat they're recognizing that it's not just okay we've built something who is maintaining it who is continuing the development community and those are things that often with open source software, we're not cognizant of we just rely on volunteer time and it is a big problem but I see more funders recognizing like Gordon Betty Moore Foundation chains Zuckerberg initiative Sloan. Welcome trust and their, you know, OSF itself is an open source project that's philanthropically supported. There used to be more awareness of it more advocacy and less of reliance on goodwill and perpetuity right and funders do need to recognize that it's amazing when people volunteer and create something. But these things need continued support. So if there is community use adoption and reliance and something you have to come up with ways to support it. That was a great question. I totally agree. I can just add one little thing to that. I think often it would also help if people instead of starting a new project would actually look around what are already existing project and maybe help contribute there so that's one thing that I think is often a little bit underestimated because people often say oh it's so easy to start your own project but then exactly what Lenny said it comes in and you have to maintain it and if you started something yeah you can't just drop it. Yeah, they're already a lot of great tools out there so I find that just going to a community that already does something and say look, that is a feature that I could help with. Can I integrate that in your project and then people often quite happy to take that on board and that could also be one one way of helping but yeah. My users can help is to cite the software and their research that they're extracting value from. That's an easy way to signal to funders that this is a critical component in my workflow. Yes, please do that researchers in the audience that would be great. Well, I really have a few more minutes here. So I do want to quickly. Actually, Aaron do me a favor there and showed off the documentation API documentation earlier but let me drop that link in the chat. And I'm not going to go and give you a tour of that, because I think we probably have seen a better examples of what the OSF can do, then I can show you and in two or three minutes scrolling around in the documentation today so thank you all for providing such strong insight into how the the API works and why this documentation is valuable. So really, I would want to wrap up on. If we could each of us in a couple of words. Talk about where you in the case for those of us that are trying to develop or partner in development with resources like this these these open source. Community develop tools that require you a number of stakeholders what's the next challenge for us. What's the next action we can take in order to meet those those challenges that are 2021 and and beyond Aaron you want to go first. Good question. I think COS is a very prominent research organization I think you know you guys have a big platform. And I think this webinar was a great step towards maybe publicizing some of the, the community contributed tools that have been built on your platform. Because I don't think there's much awareness about them so I think that's something that could be improved upon that that sort of benefits everyone. I know that sounds great and we will if I haven't, we didn't say it earlier this is not the last API or community development kind of event that we're going to do this year and there's something you'll see many of in various formats throughout the year so I know there are several API developers in the audience today so I'm not forgetting about Joe we're going to get to you. So, it's fun to tell us a little bit about what you see as a as an action that we can all be taking that just on the USF itself but sort of in this space of developing and using as a as a community. I think, as I said, contributing rather than reinventing I think that's really good. Because also I see that, for example, a lot of people try to build new services where already service exists so yes if people more people go and figure out okay, what does OSF actually offer and I didn't know a lot of the things that actually OSF can do, and had to go and figure it out I think communicating what's out there and building that community supporting each other because it doesn't need much support sometimes you just need to be pointed in the right direction so if you can build that community of developers that people can help each other see what other people did I think that is really really helpful. Yeah, and that's that's pretty much it and keep. Yeah keep keep the service running basically for the next 50 to 100 years so we can rely on it I think that's that's probably an important factor for a lot of users. Yeah, it's perfect. Thank you. That's very, very important to us to certainly and as much as we can support, not just ourselves but all of you is really important to us and please don't hesitate to reach out to us with opportunities to help you. Lenny. I'm going to mention something that's hard and relates to part of Stefan's presentation where he was talking about, you know you just you shared a link to a data set to code but in five years can people open it. Right, and this is something that is on my mind a lot has been for years I don't know if this is for 2021 if this is something for OSF and Center for Open Science to solve. But all the wonderful integrations and exporting that we do. You know it's, it's critical it's important you have to rely on something being there and not disappearing yet being dynamic and versionable so those are all great things but we export PDFs to clocks. Internet archive is mirroring PDFs, but I did say that we support videos, you know people are adding lots of links to the project to the data to the protocols their links to YouTube, or maybe they've uploaded a file to protocols that I know and maybe protocols that I owes around in 50 years, but can those video files be open. Have we done the real preservation if we send the PDF with the link to YouTube and maybe that doesn't render in two years. So I think PDFs are good start the low hanging fruit but that is not enough. And if we want reproducibility and real long term preservation in a way that Stefan was talking about. That's a huge challenge and proliferation of different tools and different places where we put the data and the videos and all of the files. And the file formants doesn't make it in easier. And even if you have the file how many of us can open a disk kit with a PowerPoint file from 1999, or just 20 years ago we're not talking 50 or 100 years, or even 10 years ago right I think that's a good point integration and preservation we have to start thinking about what do we do to multimedia what do we do to ensure that those links keep working. I wish I had a solution for it. Well, for today we will take a well articulated problem statement I think that was terrific and and the next webinar will solve it. That's the plan. All right, Nick you want to take us home. Yeah, no I thought this time we spent was wonderful I want to thank everyone who joined to listen in and thank all of our panelists partners in the OSF community development work that think we've all invested in in one way or another I just want to say how much I appreciate your time in articulating your use cases and examples with the community and we'll record this so that we can keep it going and share it on and it's Eric said there'll be more of these types of webinars to come so stay tuned and we'll be sure to share those next coming up opportunities. So thanks again. Goodbye.