-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restrict stats/rankings to "real" users #741
Comments
Such information can now be added to the DB (TravelMapping/DataProcessing#71) and it's time to think about how to use it on the front end. Where should the "unranked" users be listed and not? Thread here: https://forum.travelmapping.net/index.php?topic=6309.msg34907#msg34907 |
Yes, for sure, once the implementation is finalized. |
This is now live on the main site, so this issue is closing. Open new issues for feature requests or bug reports related to web front end display of data affected by unranked users. |
Discussion so far in TravelMapping/DataProcessing#71
Idea: by introducing a convention that non-"real" users (like the a3.list which are my travels in my current car only) have a specific pattern, such lists could be processed normally and stats and maps viewed when that user is selected, but those users would not count as travelers for stats and rankings. And can this all be done on the web front end by updating SQL queries in various places?
The text was updated successfully, but these errors were encountered: