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

Add field for participant in Submission #1586

Merged
merged 3 commits into from
Sep 5, 2020

Conversation

tienne-B
Copy link
Member

@tienne-B tienne-B commented Aug 14, 2020

This commit adds a new field to Submission models as a Person foreign key. This field is then populated when using private URLs as an alternative to IP addresses (although still collected).

With this, ballots can be more easily distinguished from which adjudicator had submitted the ballot. This is added to the "other ballots" list. It can also be used to find which team member submitted feedback, although not shown in any template.

Fixes #683

This commit adds a new field to Submission models as a Person foreign
key. This field is then populated when using private URLs as an
alternative to IP addresses (although still collected).

With this, ballots can be more easily distinguished from which
adjudicator had submitted the ballot. This is added to the "other
ballots" list. It can also be used to find which team member submitted
feedback, although not shown in any template.
@tienne-B tienne-B force-pushed the db/submitter-person branch from 5a788da to 6216166 Compare August 14, 2020 13:19
@philipbelesky
Copy link
Member

This looks good to me!

@czlee czlee self-requested a review September 5, 2020 00:36
Copy link
Member

@czlee czlee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

Do we also want to modify the subtext in the results entry table?
image image

Relevant line is line 173 here:

return {
'ballot_id': self.id,
'debate_id': self.debate.id,
'submitter': self.submitter.username if self.submitter else self.ip_address,
'admin_link': reverse_tournament(admin_url, tournament, kwargs={'pk': self.id}),
'assistant_link': reverse_tournament(assistant_url, tournament, kwargs={'pk': self.id}),

but I don't know if there are knock-on effects from changing the serializer, and also it occurs to me that with usernames, participant names and IP addresses all as legitimate things to appear there, we might want to a clean unambiguous visual way to tell between them at a glance.

@czlee czlee merged commit ec9cd73 into TabbycatDebate:develop Sep 5, 2020
@tienne-B tienne-B deleted the db/submitter-person branch September 5, 2020 01:09
@tienne-B
Copy link
Member Author

tienne-B commented Sep 5, 2020

Good point, the subtext should also be changed. I don't think we'd need to differentiate between IPs and participants/users as name formats are different. Even between participants and users, usernames are not normally the owner's full name. To distinguish if we have to, we could add a subtle indication or link to their record page.

@czlee
Copy link
Member

czlee commented Sep 5, 2020

I agree, it'll be obvious most of the time, but I thought some tournaments might use just first names or something (for participant names), so something subtle might be nice 🙂 e.g. a different colour or something, then once we're there we may as well also just distinguish three-way.

@tienne-B
Copy link
Member Author

tienne-B commented Sep 5, 2020

Got a comment a few days ago that keeping track of who submitted (participants) was important in preventing non-chairs from submitting ballots (asked that we keep IPs from checkins to cross-reference)

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

Successfully merging this pull request may close these issues.

Public ballot submissions should save which adjudicator's link was used
3 participants