MAP-434 - Surface Address Picker In Data Mapping

[conatus]

This allows the user to select the address picker when they map data across to a third party data source.

Description

In some situations, a postcode has ambiguous polling stations. In other implementations of this data set, the user is shown a dropdown so they can choose their specific address. We obviously can't do that when writing data across, so need to just allow CRMs to know this so they can show the user another path to find out their polling location.

See https://api.electoralcommission.org.uk/docs/endpoints/#postcode-search-results-found-3 for a situation where results are found.

See https://api.electoralcommission.org.uk/docs/endpoints/#postcode-search-address-picker-3 for a situation where a data picker is displayed.

It is useful to know this in, say, Action Network, to make decisions on what is shown in email templates. Imagining here we map over to an Action Network custom field called Polling Station Known.

{% if 'Polling Station Known' != "false" %}

Your polling station is:

{{ 'Nearest Polling Station Address' | form_value }}

Get Directions

{% else %}

Hit the link below to find your polling station:

...

{% endif %}

How Can It Be Tested?

1. Roll it out.
2. Add in the data source as required and test manually.

How Will This Be Deployed?

Usual continuous delivery process.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I've checked the spec (e.g. Figma file) and documented any divergences.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I've updated the documentation accordingly.
• Replace unused checkboxes with bullet points.

[linear]

MAP-434 Spike: Investigate adding polling stations to the map