Prioritize participants in visualization | Case in Uruguay

[raulsperoni]

Hey! I'm glad to share that we are using pol.is in an ongoing referendum campaign in Uruguay. The site is luc.com.uy .

As you can see, the visualization is becoming crowded. We would like to limit the number of participants in the graph, but also prioritize or fix some of them. For example in the event that some public person or politician participates, we would like her or him to appear always.

Can you think of a way of doing this?

Thank you!!

[colinmegill]

Congratulations on what looks like a successful deployment and conversation! We'd love to know more about the case study as it wraps up and would invite you to submit open data afterwards along with a report.

We have had this feature in moderation view previously. It didn't get a lot of use! Your use case is the exact reason we did build it there in the first place, however: to ensure public persons would be displayed. I'm not sure the best way to implement this now (the old one listed potentially thousands of people in a list, not particularly useful) so it would seem to me that it's like a "search" and then "pin".

[patcon]

Re: http://luc.com.uy case study.

Just linking up some notes from a Polis User Group open call that @raulsperoni was able to join: https://hackmd.io/@patcon/conversa-calls/https%3A%2F%2Fhackmd.io%2F%40patcon%2Fr17N55C19

Nice to meet you, Raúl!

[raulsperoni]

hey nice to meet you too!

[patcon]

Here's a ticket to track the re-introduction of this feature: #458

(feel free to +1 or leave additional thoughts there :) )

And here's a ticket that shows how it used to look, since it's hard to deploy a working version of the app from that point in the codebase (before we all put in some time to get docker working smoothly): #129 (comment)

[raulsperoni]

That looks good! I think this could be a thing of defining priorities (I see a priority field in the viz that I don't understand), for example taking into account the number of followers, or if it is verified for Twitter users. And then being able to define a max number of participants to show in the viz. I've been trying to find someplace in the code to do both things (just to make my viz nicer), prioritize and limit the array, but no luck yet

.

[patcon]

Re: understanding "priority". I re-posted a link to a session that was run about the math code, and I believe that might shed some light on the terms: #1282 (reply in thread)

[patcon]

But also, I think you're discussing some ideas that might make good feature requests, so pls do feel welcome to open new issues if you don't find them already existing!

[metasoarous]

Hey @raulsperoni.

As @patcon pointed out, we are tracking this issue on #458, and you're welcome to submit a PR for that if you have the bandwidth.

If you just want to get something working for now, as pointed out in that issue, this was something we actually used to have support for, and so the database/server/participant-view infrastructure for it should already mostly exist (just not the admin view). So you could always root around in the participants and/or participants_extended tables to sus out how to trigger this, and do so manually with a handful of SQL commands.

[raulsperoni]

That's perfect, thank you! I will poke around

[patcon]

Ah, chris got me thinking: the server should still allow api calls that do this. Trying to look back around the time of #458 to see API call it was running. Seems it's happening here. You can maybe even deal with this in the browser console with a big loop 🤷 (maybe a TERRRIBLE idea):

Feature/show participant

https://github.com/pol-is/polisClientAdmin/blob/c92115a295179984b25b41c69af20468b099eb54/src/actions/index.js#L1535-L1541

Hide participant

https://github.com/pol-is/polisClientAdmin/blob/c92115a295179984b25b41c69af20468b099eb54/src/actions/index.js#L1495-L1501

PS, found this great commit name while searching 😄 a27b8b0 @colinmegill @mbjorkegren. ah those were the days *looks out beyond the treeline, wistfully*

[raulsperoni]

huge find! thank you!