Skip to content
This repository has been archived by the owner on Jan 28, 2020. It is now read-only.

Put party as organisation on popit candidacy memberships? #78

Closed
tfgg opened this issue Nov 30, 2014 · 2 comments
Closed

Put party as organisation on popit candidacy memberships? #78

tfgg opened this issue Nov 30, 2014 · 2 comments

Comments

@tfgg
Copy link
Collaborator

tfgg commented Nov 30, 2014

Currently candidacy memberships don't have a party associated with them and you instead have to iterate through other memberships and match them by the timespan. I was discussing with @mhl whether it made sense in the Popolo format for the organization on the candidacy membership to be set to the party.

@jpmckinney
Copy link

A discussion started recently about this on the Poplus list (unfortunately it's threaded under "Introductions" despite the change in subject). The main issue is this one: popolo-project/popolo-spec#90

The emerging consensus is to use Membership's onBehalfOf property to refer to the party.

@mhl
Copy link
Contributor

mhl commented Oct 13, 2015

I'm closing this as it's superseded by #502 - we'll do this migration to using on_behalf_of after the PopIt -> django-popolo migration.

@mhl mhl closed this as completed Oct 13, 2015
@mhl mhl removed the 1 - Contender label Oct 13, 2015
mhl pushed a commit that referenced this issue May 3, 2017
Because SOPNs often have the name in LAST first form people sometimes
add candidates like this so include some guidance in the label that we
prefer First Last.

Fixes #78
mhl pushed a commit that referenced this issue May 3, 2017
Add text to the name label in the add candidate field that we would
like the name to be in First Last form and not LAST First as it often
appears in official documents.

For #78
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants