Skip to content

Phase 2: Organizers can map arbitrary CSV columns to the attendee badge contract #130

Closed

Description

@svg153

Part of #128. Depends on #129 and domain contracts from #104.

Problem

Real attendee exports use different header names. Assuming fixed columns such as name,company,title would make the importer brittle and event-provider-specific.

Approach

Define a normalized attendee/badge input contract with required/optional fields, then add an explicit column-mapping step. Offer conservative header suggestions but require visible confirmation when ambiguity exists.

Acceptance criteria

  • The normalized attendee contract clearly distinguishes required and optional fields.
  • Every detected source header can be mapped, ignored or remapped without editing the CSV.
  • Common names such as full_name, name, company_name, organization, position, github_username may be suggested but suggestions remain visible and reversible.
  • Two source columns cannot silently overwrite the same single-value target field.
  • Required unmapped fields block progression with an actionable message.
  • Mapping state is scoped to the current import/session and does not persist attendee row values.
  • Tests cover an expected GHSpain-like CSV and a deliberately differently named CSV.
  • npm run lint, npm run build, and targeted UI tests pass.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestphaseGSD phase issue from the coherence pass

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions