 Hi everyone, I'm Malka. I'm one of the outreach interns for the Galaxy Project. I've been working on the Galaxy Mobile Mental Project, maybe for the last three months now. Just to give you a little bit of an overview of what the project is about. Mainly focuses on mental health, diversity, equity, and inclusion. So aims to increase or improve well-being by focusing on these topics. And specifically for the Galaxy community. We use like any other source communities. So the reason why we wanted to do is not really adequately addressed along with the resources along with the factors that continue to mental health problems that could be lack of DR which means diversity, equity, and inclusion. Yeah, generally we have three expected outcomes. One of them is creating awareness. This is this reading awareness about the topics to writing blogs and stuff like that. And the second outcome is the guidelines. It's providing guidelines on mental health and DR for the community. And the third outcome is providing assessment tools for mental health and providing metrics for DR. So one of the ways we try to create awareness is to writing blogs. So far, we've written eight published blogs and two are soon to be published. So the first one focused on the scope of the project. Generally to introduce the project to the community. And the second blog focused on defining key concepts, which are well being mental health and DR. And the third and the fourth block are focused on common challenges that are based in open source. And the fifth block focused on why mental health is important and indicators as well as the responders. And log six focused on creating mentally healthy work environments in open source. And the block seven focused on the both highlights. We conducted a both session and kind of like describes what it was about. And blog eight was about survey results. We conducted a survey and we highlighted that in the books. We have been working on. Okay, let me finish this one and then I can go to just to show you where how many blocks we've written and the content. You can access the blocks here. So far we've published eight blocks. The other outreach me galaxy will be important. And soon, the two of them are soon to be published. So you can ask, you can access the blocks here. And so another way we try to create awareness and just introduce the project to the communities to the boss session, boss session and the GCC 2022. We try to introduce the project to the community as well as give some insights from the community about what, what they think about the project as well as what they feel like the project should do. Another activity that we did is the survey. We conducted a survey to assess stressors used in open source as well as to know the communities mental as knowledge. So overall 14 people from the galaxy participated and 20 people from other communities. So we conducted this survey to help us write the guideline we're trying to write. So the second outcome is the guideline. So the guideline is based on this research, which means that we try to conduct literature reviews and what other open source communities are saying about mental and the UI. And another one is from the information we collected from the survey. This means to the survey that we've conducted and through the insight that we've gotten from the people who participated. And the second one is to the information we've collected to the boss session. So the mental guidelines is where there's a work in progress. It will be published to them as well. So generally it has digital contents include scope and objective of the project, as well as busy concepts. And discussions about mental health and comments on this that are based on open source as well as the survey result that we've conducted and how we can overall improve mental health in open source communities. And another one is the mental tools that we have suggested to the community and their resources resources are anything that helps people with mental health could be links to communities or professional health. So the other guideline is that the UI guideline. There's like a mini guideline. Just to introduce the topic to the community. Introduction to the basic concepts such as the what is and another one is glossary of related words, which means what a line means or what kind of inclusive language we can use. And another one could also be how how to create an inclusive and open source, as well as metrics that will help us measure. So the third outcome. The outcome is the mental assistance assessment tools. We have two mental assessment tools that the community can use. One of them is the general health questionnaire, which measures cycle school justice. It can be used every few weeks. And overall consists of 12 questions with four options for each question. The other one is the mental health adventure, which has 30 questions in total with options ranging from five to six options. And it could be measured. It could be used every month. So just to show you how it works. Maybe I can share this quick and share the links here. We can also try to share it in the chat. Yeah, I'm trying to. We can try to find the link and to share it. Can you hear the link. Yeah, we'll do it until then I can show you how it works. So basically the questioners have four sections for sections with one of them is how to use the questioner. So you can read this before using the questioner is that when you click on the questioner sheets, you'll see a set of questions. If you take the first question, for example, when you click on the drive down menu, you have four options. So if you choose the second one, then the second one is associated with a squad. As you can see, it turned to one. So we click on the third option comes to come back as two. So the overall score is summed at the bottom. And then, and then once you find once you have like the total score, you can go to the interpretation score sheets, and then you can see what the score is. So, basically, if you have to score, if the total score is two means that the psychological distress is low. And if we have like scores closer to 36, that means there's higher levels of cycle school distress. So the mental inventory also works the same. And when you click on the questioner section, you can see a set of questions as well as options. You can click on the options. And then the final score can be found at the bottom and the interpretation can also be found at the interpretation sheets. And then the scores, scores closer to 38 means lower psychological developing and closer to 226 means higher psychological. So the other one is the di metrics. The di metrics is kind of a suggestion on how to measure the I told that we found like two, two important metrics for di one of them is the di metrics inventory. We measure workforce leaders and resource groups, which means the majors mentorship programs are representation of the workforce or how many representation representation of representation and the leadership and stuff like that. So chaos metrics also is another matrix that you can use. One of them is at us like four sections in total and then diversity governance leadership on projects and communities that have a diversity. Typically measures the diversity of events that are conducted by conducted by the communities governance also like the presentation of people and governance and leadership and project and communities can include community safety, so you can click on the box. I can show you, I can share the link later. Yeah, anyways, these are the outcomes for the galaxy will be a project and another one is kind of a suggestion on what to do for the future action for di. So, the main concept is like how we can create an inclusive space and community. So, one of the things that we've noticed is that the things that we've conducted as our accessibility audit, which shows that we conducted an audit for the use galaxy and another one for the galaxy. So you can find the link to the other websites on the, on the right on the left. And so basically what it shows that it's very critically low, very inaccessible for other people to use. And it has like critical issues, such as color contrast, some, some aspect of the website is not really accessible to screen readers, stuff like that. So it shows that use galaxy is 40% which shows that it's very critically low and not compliant with accessibility low, those are rules. So, which makes basically the galaxy website very like not inclusive for other people. So it's not really. Not really accessible for people to use. So maybe improving that would also make people feel included in the community as well as have, give people access to the website as well. And the other one is maybe forming support groups, support groups. So that people can openly discuss about the topics that they want to discuss, they want to discuss on, which will include maybe we have some support group ideas for maybe mental and well being support groups, maybe groups focused on women. And then the DI accessibility groups, you know, neurodiversity. Those are just suggestions, you can include your own and form groups. And the best platform for the groups seems to be a matrix, because galaxy uses a lot of metrics for their crops. And the other one is forming a community. So that there would be consistency and accountability and addressing DRM actors, such as accessibility so that the community actually follows up on the accessibility of websites and other factors as well. The other one is community values, maybe having shared community values that everyone can respect and live by, could be like having a valuing openness and showing that your value openness for whoever wants to join the community. And or whoever is actually a community member. The other one is the DI metrics, maybe measuring DI on a yearly basis. It could also be maybe twice a month, twice a year or anything, just measuring DI on a yearly basis would be great. So that the community can track the progress and make improvements. And another one is the DI page, maybe having a DI page that includes DI statements could be a short statement stating that the community is very welcoming. And yeah, just a DI short statement that suggests that everyone is welcome in the community. Another one is list of support groups, we can be including support groups and the DI page so that anyone can join. And another one is the DI survey results for a transparency and progress. Another one could be the DI guidelines could be included in the DI piece as well, as well as the list of DI committees and response entities. So basically, do we have time and do we have time? Yeah, so we have time for a few questions. I think it's nice if you can ask your question and if they cannot be answered today, we can also be answered later. Yeah, please. So basically, these are like a list of questions maybe you can reflect on if we don't have time, or you can actually answer if you want. So one of them is like, what kind of support group should there be? If you think that support group should exist, then what kind of support group should there be? Should there be a DI committee? And would anyone be interested in being a committee member? Should there be shared community values? And what should there be? And how many times a year would it be? What should the DI be measured, as well as what do you think about having the DI page and what content would it have? So I don't know if you'd like to reflect on it now or by yourself or with others, you can do that. So basically, I'm done. Yeah, thanks a lot. Yeah, I'm done. Thank you for listening and if you have any questions, please. So hi everyone, this side Shivani and today we are going to discuss about my outreach project wherein we had a very big target to implement notification system in Galaxy. We'll discuss a bit about the use cases it stands, the motivation behind it, and the current status that we are present for this particular project. So since we all are aware with Galaxy workflow over here, so I would not take much time into that into highlighting the importance that how a lot of researchers, students, professors use Galaxy to run their analysis and how many users do we cater to. And we also know that a lot of like it is a very big community where which is trying to make Galaxy day every day better for its users to make it to make it better in using the to make it easier for them to provide them more good interface to provide them better results and so on. So the first motivation or the like the basic need that we need a notification system was for that. We all know that when when users or researchers run analysis and on Galaxy so it depends from analysis to analysis that it may take but either it will take some seconds to complete the analysis and it goes up to as long as days. So in these situations, we do not have an information to update the user like there are there is only limited functionality over right now to update the user that hey your analysis is completed. Similarly, if an analysis is completed then either we want to share it with other colleagues or other members of the in the group, or we want to use it for further for storage, like to present to use it further we want to store it. So right now, for all these cases, as I was saying that there is only limited functionality to notify the user when it is when the analysis is complete, either it is via browser tab notification. So with that what happens is it may if it's a very long analysis so it may happen that the user has closed the tab or has forgotten about it and there can be multiple such cases. Another option is that we do inform by an email, but that is only if the user has requested it in the workflow action. Again, continuing that only we also do not in are not able to aware inform the users that an analysis has been shared with them. So for all these particular reasons are flexible and extensible notification system would be helpful to to inform the users about any analysis that is complete, which users can share with their group members, or it can notify a group of users which have which have which have been working on the same analysis together, and so on. So these, this was the very basic motivation for it and some additional use cases to which we can extend it further is as I was discussing that sharing notification with other group members. Then, if users want to notify the admins of some request some toolbox installment request or some other requests, some issues that they're facing so they can able to, they can able to send notifications to admins regarding any particular request. Then we can also inform the users about if there is any version update there is any new Galaxy release. Currently we have a bell icon for that, but it does not come as a pop up that hey there is an update you have to update it or if the user is signing that hey I have seen this that I know that there is an update. So job and workflow completion we discussed and some other instances can be very user want to accept, very when we want if we have updated our terms of services conditions and we want the user to accept those to move forward, or if we have updated some other parameters, and then we want the user to install those particular requirements then only they would be able to continue with it. So for all such instances we can add on to this, there can be many other use cases as well to this. So, currently, as in the due to constraints of time I would not go into the entire implementation and like if we just discuss about how does the database schema currently look. We have two tables right now to keep track of the notifications that we have to keep track if the user has seen the notification. And, like, if we want to really currently we only have a track of if the user between the user and the notification, wherein if a user can have multiple notifications, but we can move forward, we can extend it further to groups and roles as well, and then we keep track of notification at group level role level and so on. So, if we are let us discuss a bit about the API part. So currently we have implemented these four routes that is API slash notifications which would create a new notification a post to this, then get to API notifications and the particular notification ID, it would provide us the content and the message in the particular notification. We also have a general get that is if we just go to API slash notifications. So that provide us say top 10 notifications right now in the system. And then we have a put to update if there is any message update in the notification. It can also be enhanced further wherein we will also keep a put to verify that a user has seen the notification that would also be like API notification slash ID. So, if we discuss a bit about on the client side. So, we have created a component for wherein a user in the master icon, we have created a bell, which displays the current pending notifications, and when the user clicks on it so we can see the content of the pending notifications. We will further want to create notifications via post as like we will want to create a view component for the post as well, where in admins can create notifications. Then users can see full text notification in the API in via the root API slash notifications slash ID. And as I was discussing earlier that users can confirm like we can keep a button or a tab or some any others icon wherein users can confirm that hey I have seen this notification and that would also be updated for us. So currently like here is the bell icon which will show the pending notifications and then we can see the pending notifications at API slash notifications route. So, in the future work, we can enhance this work a lot more and it it be like be helpful for a lot of other cases as well like as I was saying that acknowledging a notification. If a user has seen we can keep it like this that notification should be on top of everything until a user reacts to them. We can also take some feedback from the users we can keep keep either a score or any other We can provide some default options and we can ask that hey if what are the notification reactions from the user so that something if there is something that can be improved for our end. As I was discussing that we can make sure that users groups roles they they are assigned to one or more notifications. And it can all right now so the notifications are just a message text, like just a normal string, but further they can be interpreted in markdown which can contain links as well say to if they're. So, how like we were discussing about the future work I don't know how far we had completed it. I think you got to mark down. Yes. Yeah. Yes. So yeah, I think this was pretty much it like we want to. There is a lot of work that we would want to do to this in future as well. But these are some of the use cases for it. So I think we can move on to questions now thank you. Okay. So, hello, I'm so measure. I'm here to discuss the outcomes of my three months of town to church. The domain is galaxy climate to support local regional initiatives and concrete access to find the climate change. So my gratitude to my mentors and for being supported throughout the internship. I'm from India and I'm currently in the final year of the department of civil and environmental engineering. And yes, we'll move to the next slide. This slide contains the contents that I'll be covering. We have a total of 18 slides. This slide and the following discusses how the weeks of my internship have been. And what I have done be quite likely quite time frame. We'll come back to this later. Let's discuss it in detail in terms of my mile one will cover the things that I did between week one to five mile to covers week six to 10 and mile three covers the last two weeks. Okay. So this week, I've drafted a galaxy training network tutorial for the next CDS X array mapping tool. The very reason is that there are more than 150 color maps and differences act for projections, which makes choosing the perfect plot very overwhelming. The tutorial is a step by step guide on how to use along with color map and projection documentation. This is from the galaxy tutorial network site and the other ecology section as soon as you hold it past that I mean mergers. Okay. So a local use case was needed to be identified. So as to drop the potential tool notebooks, which involved the most frequent analysis done by scientists locally for the region of Mumbai in India. The second week saw the identification of use case of Mumbai. So we can explore that through this short video. I hope you can hear the sound. So we can move to the next slide now. Yeah. So, in case you missed any of the problem statements, I believe that was like what I plan. It had some audio. Okay, so these are some of the problems that the video video addressed. So we are moving to the next slide now. So following data sources, which I have used for analysis shown in a couple of slides coming next. I strongly recommend any geodata enthusiast to visit the sites and explore if not then yet. And this is something that I did in a week three. Okay. So, I used the week four to sharpen my skills. So week five began with the skimming through the code base and the GTN materials to understand how tool development takes place in galaxy. The tool that I used in around week six with the help of my mentor is a net CDS time series extractor. The purpose of the tool is reading net CDF data and extracting a time series into a CSV CSV file. Yeah, the tool also plots the time series and PNG format. The tool was built because there was no such tool which focused prominently on time series plotting. So began the drafting of notebooks using interactive notebooks. That's a tool in galaxy analysis of potential to notebooks which can be reused for the tool development. The first analysis use uses the IMD Indian meteorological department data set plotting 121 years time series of rainfall and the daily maximum and minimum temperatures for 50 years. Below is the plot of 50 years time series of daily maximum temperatures, indicating more number of days with higher maximum temperatures for the current decade. Okay. Week nine began the plotting of a mirror data set for the Albedo values over the city of Mumbai. The first plot as you can see shows the same. It indicates that the Albedo values have lower down in the current decade. And the second plot is a climatogram. The climatogram is basically a kind of a graph that's used to depict the climate of a place. The third plot is an NDVI analysis using Copernicus land data set. It's done by and the plots are high quality and clearly indicates the vegetation over the Mumbai region. The fourth analysis is the distribution of a Mumbai. The data used is harmonized words or a database. It's a very obvious, like to find the values along the source as because the regions which are white and these are the regions of ocean, the Arabian sea. Okay. And these are the links, which you can visit to find the code for the analysis. Okay. Here are the two technical blocks that I've drafted. The first block discusses galaxies climate workbench and existing tools. And the second block discusses the theoretical aspects of biomes climate and climatology. Please feel free to give a read whenever you have time. There are available in the blog section at the galaxies homepage. Okay. Finally, we are here at the most interesting part of the project. That's gal this or galaxy visit. So how do you discuss an existing use case or a problem with other people do only the people you know, help you with it. It becomes very easy with gal this to share, help and help others with their use cases. The next slide. What is the need of gal this. So, as we can read here, there are many scientists who are great at science and understand the current needs. On the other hand, there are many developers who are great at developing but lack some scientific background. There is a need of bringing the two communities to the same platform, getting help from community on certain topics. Become difficult at times to brains are better than one in some discussions, a place where everything can be found under the same is the need of our to save time. So, I'll be navigating to the site. Just a second. Okay. I'm beer with the UI because I'm going to improve it in the coming weeks. So, welcome to gal this. So, any new user that comes to gal this can choose to register if they decide to take part in any interaction in the website. Without signing in or registering, you can just view all the info with no contribution access. So, you can see I have already signed in. You can sign in using your email and password. Here you can see a profile. It's not an extensive dashboard just the some basic details of the profile. You can change your password or you can either log out. Okay. So, at first we'll go to all workflows functionality. Workflows are available at workflow hub dot you are incorporated here. Here we can search for workflows. And suppose I want to search a workflow name parks analysis. Yeah, we can find it. And then we can navigate from here. Clicking on this we are directed to workflow hub dot EU where this workflow is currently located from here, we can easily run this workflow on galaxy without any hazard. Now, coming to the heart of the site that's the country with functionality. Here we find the option of either uploading a use case, a tool notebook or a notebook. All of those three have the similar functionalities. Let's discuss a use case. At first I'll be copying some of the content for the use case. Okay. So we can add a title. We can select what topic or subtopic it falls in. We can select an image for the same. Suppose I have the title as this. And we select a topic named biology and suitably it falls under ecology section for choosing a file. We can select a test image that we have. And yeah, in this content section where we are uploading like pasting our content or writing, we have some of the formatting features like these are I think sufficient to make your text look good. And if we have any of the links for the workflow link or a history link when we are having a discussion we would invite more information. So we can have any of the links we have we can put it here we can invite anybody for the discussion. And then we click submit. Clicking on submit like create a new use case you can see here the use case is created successfully. So where can we find the use case. Actually what are use cases. It's any problem that you are working on or you are facing and you want others to help you with it. Suppose I have added this where have I added in biology and the ecology. So we'll be heading to all use cases. It's the place where ever where all of the use cases to know notebooks or two notebooks that you are adding can be seen. Okay, so I had added on the biology section for the ecology. So we are having the biology section and we can find that yeah this was the thing that I added. Apart from this, where can you find the uploaded use case. In the main site, the latest uploaded use cases can also be clearly found. Clicking on visit use case here or all use cases here. We are directed to another page. Okay. Here currently I have not uploaded any of the user images. So it's not showing. Here we can find. There is the title that I have the name and the day on which I have uploaded it the info that I had. Either we can like this or share. We can also have certain discussions. It's like, suppose we say good. We can post comment and also we can like or reply to a comment it follows two levels of hierarchy. Okay. So after all use cases we have all notebooks where this notebook come from is when we upload a notebook here. Similarly, we can we can get a notebook in the old notebook section. Or if we contribute to a tool notebook we get to a tool notebook section. Okay. So how are we filtering we are filtering using two levels of edam ontology was actually followed in the galaxy website. Okay. So the next highlight is we have an outreach section. Yeah, for now it's the info hasn't been added hasn't been added but I believe from the next time outreach section can be used to display the works of our past interns so that the ambiguity to new contributors can be reduced. I think there's one feature that's here. Whenever you are adding a new case, the number gets automatically a bit so that the user can find out how much content he or she can find at the left side. Okay. In the subscribe section, any of the user can subscribe to a bi weekly or monthly conversational kind of subscriptions like emails, and there is an all there's also an option to get feedback. If the user finds anything wrong with the site or have recommendations for the site, the user can definitely like come and let us know. Okay. So that was all about Galvez. Let's move to the next section. So what is going to be pretty much clear. The actual site and we have discussed. Moving to the next slide. I divided into five stages. The first stage involves development on the site and developing a following the development of issues. The second stage involves creating a relevant network by making connections on LinkedIn. The third is the awareness and the data collection stage where we'll be organizing webinars and asking in feedback and their interest for our platforms will improve and send out invitations and ensure smooth onboarding in the process and in the stage of four in this stage for all together consistent development in the stage five will make it a success. Yes. This fulfills the local aspect of our use case that the problem that we began with the beginning of our teaching internship. Yeah, moving to the next slide. What about reaching to various functional areas of Galaxy. This way we can fit it out potential contributors. This is there's a real gap. In the tools under the ecology section, and this needs to be looked after having a flexible but a predefined outcome and timeline the project produces the ambiguity. We can surely have a like we can surely ask for the suggestions and have some flexibility in the timeline, but we can have certain must achievable in our mind. This can really increase efficiency. Finally, the Galaxy well being mental health project is a great idea and very less people are working on it in the field. We may give it a shape of a software or a platform where people can assess the health and find remedies to. So thank you so much for being such a wonderful audience. If you have any ideas or relevant discussions feel free to connect on mail. Yeah, now I'm open to any question of feedback that you have. Thank you so much.