Skip to main content

Surveys

Surveys pull responses from an external provider, map the provider's fields to MLH's own questions, and process the responses. Manage them under https://core.mlhtools.com/resources/surveys and related resources.

How the pieces fit together​

  1. A survey connects to an external provider and is mapped.
  2. Each provider field becomes a survey field, which an operator maps to a survey question (a reusable, canonical question).
  3. Members' answers come in as survey responses.
  4. Survey value mappings translate a provider's answer values into MLH's internal values.

Surveys​

  • Title and Admin (the owner).
  • Provider type: typeform, qualtrics, or dev.
  • URL: the provider survey URL.
  • Polling enabled and Polling period: whether and how often MLH polls the provider.
  • Status: pending, mapped, or failed.

Actions: Map survey (set up the field mapping) and Reprocess responses.

Survey fields​

Each field from the provider:

  • Title and Provider field ID.
  • Field type (from the provider).
  • Handle as: capture, ignore, or user lookup.
  • Lookup strategy (when handling as user lookup): email or user ID.
  • Survey question: the canonical question this field maps to.

Actions: Assign question, Handle as capture, Handle as ignore.

Survey questions​

A survey question is a reusable question template (just a Title) that many survey fields across different surveys can map to.

Survey responses​

A survey response is one member's submission:

  • Provider response ID and User.
  • Answers and Payload (raw data).
  • Status: pending, processing, completed, or failed.
  • Error log and Processed at.

Action: Process responses.

Survey value mappings​

A survey value mapping maps a provider value to an MLH internal value.

  • Provider value / Provider label and Internal value.
  • Status: discovered or mapped. Set it to mapped to translate the provider value to the internal value.