New leaderboard page (aka "partner page")

[dgquail]

Ticket to track partner pages setup within Tasking Manager

[dgquail]

Hello Emilio!
We have a question about how to obtain the current projects of each partner (carousel component). We suppose that we should obtain a list with the ids of those projects to invoke the summary and tasks endpoints, but we cannot find how to obtain that list of current projects

Thanks!

[ramyaragupathy]

@emi420 - for now we can simply let the partnerships team populate project IDs for each partner without running actual validation for existence of projects. Like agreed we can have the second phase of the project to build the association between partners.

[emi420]

Ok @ramyaragupathy @dgquail , we'll need to add:

• A new column to the database schema named current_projects or something similar for a list of project IDs.
• A new field in the partner add/edit form for the ids
• Update the partner's endpoint

And then we'll use those ids in the frontend for the carousel.

[dgquail]

@emi420 @ramyaragupathy ok, let's go with an additional attribute to the model that contains a string of project ids separated by commas. It's OK?

[CristianAmici]

We've introduced the "Current Project" section, we offer a slider display highlighting each active project. Furthermore, there's a zoom-enabled map focusing on the project's layer, granting users the ability to navigate and zoom in and out effortlessly. We've retained the same buttons and functionalities from the previous page for consistency.

[CristianAmici]

In this section, we present activity using three charts. We have employed the same bar components used in the projects section to create the list of participants, maintaining the link and previous functionality.

[CristianAmici]

Hi! This is the resources section, and we would need to know if the resource buttons are partner-specific and how to dynamically retrieve that information for each partner.

[dgquail]

@emi420 @ramyaragupathy Cristian left a question for you

[ramyaragupathy]

We've introduced the "Current Project" section, we offer a slider display highlighting each active project. Furthermore, there's a zoom-enabled map focusing on the project's layer

looks great!

we would need to know if the resource buttons are partner-specific
yes theses are partner specific and there could be different set of resources for each partner. @nicolelaine could you please confirm the usage of resources section?

cc @emi420

[ramyaragupathy]

Here are all the partners that have added custom links:

• Accenture
• JPMC
• AIG
• HoganLavells
• Salesforce
• MMC
• Morgan Stanley

I think for now it will be good to restrict this field to 5 items and each item should allow for:

• custom link
• text that refers to the link

@emi420 @nicolelaine - please share your thoughts.

[emi420]

@CristianAmici The partners table has a field for "Other links" , max 5, it's called website_links in the DB schema and in the DTO:

#6346 (comment)
#6346 (comment)

CC @ramyaragupathy @nicolelaine @dgquail @lotjulieta

[dgquail]

@emi420
ahh ok There was a mailto, that's why we thought it was other data. No problem, then we display the buttons based on that partner attribute

[nicolelaine]

@ramyaragupathy Yes, these resources are partner specific. I think 5 sounds like a good number.

[nicolelaine]

We've introduced the "Current Project" section, we offer a slider display highlighting each active project. Furthermore, there's a zoom-enabled map focusing on the project's layer, granting users the ability to navigate and zoom in and out effortlessly. We've retained the same buttons and functionalities from the previous page for consistency.

@CristianAmici Is it possible to also see the progress bar on each project on the page?

So, for example, how you can see that this project is currently 88% complete?

[CristianAmici]

@nicolelaine Hi! I forgot the percentage line that was supposed to go inside each slide. Yes, we implemented it and left the information as the project component takes it from a hover (ProjectProgressBar), as the information of the 3 fields comes from the API: "percentMapped", "percentValidated", "percentBadImagery", we implemented that bar that has the 3 colors for them. It seemed to us the most appropriate, but tell us if it's okay this way, and thanks for reminding me.