Skip to content
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

Reduce reliance on using hashtag for every changeset #16

Open
RebeccaFirthy opened this issue Aug 24, 2017 · 2 comments
Open

Reduce reliance on using hashtag for every changeset #16

RebeccaFirthy opened this issue Aug 24, 2017 · 2 comments

Comments

@RebeccaFirthy
Copy link

Reason: for a lot of our corporate partners the hashtag method is a huge point of failure when it comes to tracking impact.

A fantastic solution to this would be if a mapper adds ‘#partner’, to only one changeset, could the tasking manager store that email address (or tag them as from that partner?) and each time that user maps, their impact is automatically added to Accenture totals? Ideally this could also backdate so if the mapper forgets to use their hashtag at their first few mapathons, if they use it later their previous work can be counted.

This solution would probably solve all the issues we have with impact measurement at the organisation level currently. If possible, this could integrate with MapSwipe (e.g. if they use the same username/email), so the company MapSwipe impact can also be seen on the partner page.

@dalekunce
Copy link
Member

@RebeccaFirthy this is way beyond the current capabilities of the leaderboards. This is also more appropriate for the tasking manager.

@danbjoseph
Copy link
Member

if they wanted, the company could record their employees' usernames. and that list could be used to calculate the aggregated edits of those people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants