 So relationships, so let's start with the relationships. So here we are going to talk mainly about the two domains of relationships that are relationship between TI's and also they supported by Andrew since the beginning, but also from this current version, the two five, we are also supporting relationship between events and TI's. Events that can be part of a tracker program or can be just a program that is a single event without registration, okay? Just an event program. However, relationships between TI's and events, sorry, and events are not supported, okay? So we can have the events in the left side of relationship and the TI's in the right side, but the opposite, it is not supported yet. It will be supported in the coming versions, but it's not supported yet. Also, we don't support enrollments. You know that also in, as part of the access to definition for relationships, you can select the enrollment as part of the relationship as well, so the enrollments are not supported yet. But in front of that, there are no constraints with the programs, with your units, so within tracking the type, meaning that you can build in a relationship between TI's that belong to different programs, between TI's that has a different tracker TT type or TI's that belong to, with that enroll in different units. There are no problems at all, okay? There are no constraints. So basically, if you go through the, if you open a TI and you have a relationship type for a program in which the TI is enrolled, if you have a relationship type defined in that program, so you can like, you will see like a new button over here in the menu, okay? So this button, this icon represents relationships. So the relationships are being listed like this, is a list of the TI's as well, and you can navigate through them as well, okay? So you can move, in this case Pablo, you can select if you click on Pablo, so you will like go to the next screen, that basically is the enrollment that Pablo has in this particular program with some data, some attributes of Pablo, okay? And then of course you can open that TI as well, okay? Let me see if now I am a bit more lucky with my mobile, hopefully yes, okay? So if I open a TI here, okay? Okay, so I click in on the relationship button, okay? And I can see my those two TI's, two relationships that Victor has here, okay? If I click on any of these, we will redirect to this TI with enrollment of Pablo in this particular program, COVID-19 control registration and follow up, okay? And I can see, I can navigate to Pablo as well. And the same, so you can go to Pablo, to this TI, the icon of relationships over here. So I can see that Pablo is also related to Victor, okay? So it's the way that we used to navigate the TI. If we can also remove any relationship clicking on this on this bottom, and then it will remove all those also in the server and synchronizing with the server. So how we can define this? So basically, you know, this is the same from the version 233 in which we need to define the, we need to go to relationship type here in the configuration. So in this case, basically I have created a relationship that this is one has been in contact with. So if I open this one, it has a name, I mark this as Bay Directional, this means that you can navigate both parts of the relationship. So from the left side, you can go to the right or from the right, you can go to the left, okay? And this is the text that you will actually appear in the Android application this person has been in contact with. So now if I'm going to my Android application, I can see that this is the label that is appearing on this particular relationship here. This person has been contact, okay? We need to define like both parts of the relations in the left hand, that the left side from constraint and the right side to constraint. And here is what we said before that we have like three different options that TI's enrollment and even the program or program stage. Again, enrollments are not supported yet. It will be soon, but not yet. And we have track identity instances. And in the left, we could select the track identity instance and the events in program or program stage, okay? While in the right, it only can be track identity things. That's we know that we don't support enrollment some in the right side of the relationship we don't support the events, okay? But then there, as I said, there are no constraints. You can, well, right now in the server you only have one track identity type that is person, but we have different ones which you can select any of them here. So this can be two different track identity types if you want. And the same with the programs. We are called, we are like in this case we are defining one relationship type between TI's that belong to the same program but I can select any of the programs here. There are links, so it's a quite powerful mechanism, okay? Okay, you save it and then whenever you synchronize again you will see that the relationship bottom in the whenever you open up TI. Okay, so let me go back to my presentation. Okay, as important because sometimes when in the implementation people are asking us the relationship doesn't work and many times it's because they forgot the sharing settings. I normally forgot the sharing settings too. So everything has a sharing settings in the access too as you know and traditionally type is not an exception. So you need to be sure that you are like also sharing the sharing the relationship with your user groups or your users, okay, for metadata and data. That's important always to remind, to keep in mind. The way that we create relationships is quite straightforward so you can, you can navigate for instance, let me go to Jaime and then you can navigate, you can click on this button. Okay, so you click here on the plus has been in contact with. Okay, and then as I said, as the relationship can belong to different programs, so then you need to select the programs that you want to, here you need to select the program that you want to use for creating the relationships. In this case, we are only using the COVID-19 contract registration and follow-up. So I click on this one and I can like then I'll just click this one. So now I can create the relationship with anyone, with any people, any TIs that I want there, okay. So in this case, I select Pablo. So we can also show the relationships in a map. So if I'm going to another application again, click on the relationships and now we can see this button over here. Okay, so this shows me the relationship that we have between the different TIs. Okay, now. However, I think it's, so in this case, Victor has to, the TIs selected, Victor Garcia has two relationships, Juan Pena Andres, with Pablo. Okay, but also now you can see, when we are listing the TIs, you can see also the relationships in with the full TIs list in a map, that I think is pretty cool. So let me go back then to my list and I'm going to, again, I'm going to select the TIs that has been enrolled last month, okay. Now I'm clicking on the map, okay. So now if in my layer, this will be opening, okay, here we go. So now as we have relationship types in our mobile application, so we see that we have this option here has been in contact with this layer, is part of the, is a relationship. Okay, so if I click on this one, click on apply, this will probably, you will see the results hopefully in more than 10 seconds. I have already done that. Okay, so then you can see how all the TIs are being related with each other in the application. Okay, so one more thing regarding relationships. As I said before, you can specify, you don't need to be like constrained by a program or a track entity type. In fact, in some places that we have, we are like using also areas as the person was asking to us, like what is the difference between a point and an area? When can we use one or the other? So in this case, for instance, this is an example, so that we are like collecting COVID cases, but also we are collecting areas like geographic areas of interest, right? So it was defined like a particular area at TI, which has, which feature type is a kind of polygon. And in the other hand of the relationship, we have a point at TI, which feature type is point, and then how this will be rendered in a map. So this is the way how it looks like. So basically, we can see in a map also areas and also the TIs that belong or are related to a particular area. And both will be like, will be showing up both geographics, that one for the areas and other for the coordinates at RGPS points together. Okay. I don't know if there is any question about this, or we can go to the exercise, but I also have to remind you that the words of the day to day is data, okay? Therefore what to use to put data. Is there any question or should I go to the exercise? Okay, so I'm about to exercise now then. So it's very simple. Basically in the previous session, you had to create like three cases. Okay, and here we are going to play with those three cases that you have created. The objective of the session is how to define relationship types to render it in Android, that we have already seen the theoretical part, and then how you can add relationship between the TIs, okay, and then how you can render those relationships as a list or in a map. So what you need to do is that as I said, you have already created three cases in the previous session. So you need to connect those two cases with relationship, okay? So it will be in this program again, we are always working now today on this particular program, under this particular program. So you need to create two relationships, okay? So you have created three TIs and you have to create two relationships, and let's suppose that one case is in this case, okay? Then you have to visualize your relationships in a map, and then synchronize your relationship with the servers as well, okay? And the submission basically here is like, you need to submit one screenshot of the map showing the relationship that has been created, that you have created in the Android application. Let me know if something is not clear. Jose, there are two questions, sounds like that I think we can take here. Okay. In this session, one is from Arif Azad Khan saying, I would like to capture GeoPoint for an organization unit village. Is there any process to capture the point through Android? I think what I understand is that you can capture a GeoPoint if you create the data element or an attribute of type coordinate. But that value will not be the coordinate of the org unit. So if the question is if you can assign coordinates to org units in the app, the answer is no, you cannot. You can assign coordinates to attribute or data elements, the identity instances or enrollments for events. Is that correct, Jose? Yeah. You can put a data element like we put now origin and then we add a list of org units. If you don't want org units, but you want to coordinate, then you can also put it there. Let us know if that doesn't answer the question. And then there is another one that I don't really understand. It's from Channada. So maybe Channada, you can explain us better. The question is, how to generate tracker has relationship in event report? That's the question, Jose. I don't know if you... How to generate tracker has relationship in event report. Channada, maybe you can give us Channada. Or in Channada. If you can give us more details, maybe in your questions or here, if you want to unmute. Let's see if you can... I mean, okay, thank you. If we can show tracker data in event report. Yes, you can show it. Tracker data in event report, okay. You can... Yeah, but in the... So if your question is event report in the server, right? So you define the event report in the server. So you want to know maybe if you can filter in event report based on relationships. Like I want to see the track entity instances that have one relationship. Can you... I'm going to unmute, I think we need to listen to this question. I mean, in the event report, what the data program indicators... I don't remember now what are the functions. You can unmute, Channada, if you want to explain the process. Hi, I'm Channera from Cambodia. By the way, usually the visa line on the map is very helpful that we can visual the direction and relation with the tracker person to another person. Like the mother has the children or the children from the mother like that. And by the way, we want to generate the event report on the server, web server on DHA2 that able to see, for example, like the code of the children and where is the pattern code that link with the children. So we can see on the event report, possible can see like that. I don't think so in the server side. You can visualize, I mean, the same way that we are visualizing the TI is in the map, you also have the possibility of visualizing the relationships in the map. But in the event reports, what you can do is use program indicators. And now I know that there is a function. But I have to say that I've never tested in the last two years or one year. Now basically it counts the number of relationships that the TI may have. I think then you can have these results in the event report. But probably it's not what you are asking for. But as far as you know, it's the only thing that we can do with the event report. I know that the Oslo team is working, the analytics team is working in improving the relationship capability for analysis in the next versions. But so far I only think that you can visualize relationships in the server in the map or basic counts in the event report. I don't know if I have answered your question.