You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: