EPIC: Destinations — manage, tag and measure the places you've been and dream of (backend/web) #1209

Closed
opened 2026-10-17 11:07:55 +00:00 by spikerj · 1 comment
Owner

The profile's Travel tab stores a destination as nothing more than an ISO code in one of six string lists on UserProfile.Travel, and shows them as one flat, unsorted row of flag chips. Past ~40 places it is unusable, and there is nowhere to put a tag, a star, a note, or a link to a hike, a photo, or a seed collected there.

This epic adds a real per-destination record and a /destinations page where a member can dream (wishlist) and record reality (visited) in one place, manage destinations in depth (tags, favorites, notes, first visit), and see what the rest of the site already knows about each place: explorations, photos, seed varieties collected, trails verified, and km hiked / biked / run / walked per country and state.

Locked decisions (2026-10-17):

  • New top-level /destinations page (table + grid, search, sort, filters sidebar, favorites, tags, "Favorite regions" and "All tags" rollups) plus /destinations/:code detail. The profile Travel tab keeps the map and summary counts, caps its chip row and links to the page.
  • Status stays on the profile. Visited-via-SpikerSoft / visited-externally / wishlist / parent-approved are still derived from the six TravelProfile lists, so the map, sponsor cards, dashboard places widget, rewards facts and ExplorationTravelSync are untouched. A new owner-scoped destinations collection holds only metadata (Favorite, Tags, Notes, FirstVisitedOn), unique on (OwnerKeycloakUserId, Code).
  • Stats are joins, not new tracking. Explorations are keyed by country + regions already; seed varieties carry Provenance.DestinationCode; trail verifications carry RegionCode. Recorded routes and photographs get a nullable CountryCode / RegionCode stamped from GPS through the existing offline IRegionResolver at upload time, plus an idempotent backfill. No coordinates in logs; stats are owner-only (parent-for-child like explorations).
  • Continents: neither repo has continent data. A static ISO 3166 table (alpha-2, alpha-3, continent) is added on both sides, following UN M49 (Central America and the Caribbean roll into North America). Sub-regions are a follow-up.
  • Tags are free-form with an i18n starter set suggested in the picker (same model as photo gallery tags). Limits: 20 tags per destination, 32 chars each, case-insensitive dedupe.
  • Climbing is deferred to its own issue: there is no per-user climb log (climbing is a read-only public crag catalog). The stats DTO leaves room for routesClimbed.
  • Page code lives in the app project (projects/spikersoft/src/app/_components/destinations/, route module routes.destinations.ts like routes.mapping.ts) because it needs TravelStateService / ProfileService, which boundaries lint keeps out of feature libraries. Shared continent data goes in @spikersoft/domain-geo.

Order: backend-A → (backend-B ∥ angular-D) → angular-E.


Child issues (per-repo, auto-close on merge)

This epic is complete when every box below is checked. Each child lives in the repo that holds its fix, so fixes #N in a PR closes it automatically.

Backend

Web

Follow-ups (not children): per-user climb log feeding routesClimbed; Central America / Caribbean sub-regions; whether deleting an exploration should un-mark a visit.

The profile's Travel tab stores a destination as nothing more than an ISO code in one of six string lists on `UserProfile.Travel`, and shows them as one flat, unsorted row of flag chips. Past ~40 places it is unusable, and there is nowhere to put a tag, a star, a note, or a link to a hike, a photo, or a seed collected there. This epic adds a real per-destination record and a `/destinations` page where a member can **dream** (wishlist) and **record reality** (visited) in one place, manage destinations in depth (tags, favorites, notes, first visit), and see what the rest of the site already knows about each place: explorations, photos, seed varieties collected, trails verified, and km hiked / biked / run / walked per country and state. **Locked decisions (2026-10-17):** - **New top-level `/destinations` page** (table + grid, search, sort, filters sidebar, favorites, tags, "Favorite regions" and "All tags" rollups) plus `/destinations/:code` detail. The profile Travel tab keeps the map and summary counts, caps its chip row and links to the page. - **Status stays on the profile.** Visited-via-SpikerSoft / visited-externally / wishlist / parent-approved are still derived from the six `TravelProfile` lists, so the map, sponsor cards, dashboard places widget, rewards facts and `ExplorationTravelSync` are untouched. A new owner-scoped `destinations` collection holds only metadata (`Favorite`, `Tags`, `Notes`, `FirstVisitedOn`), unique on `(OwnerKeycloakUserId, Code)`. - **Stats are joins, not new tracking.** Explorations are keyed by country + regions already; seed varieties carry `Provenance.DestinationCode`; trail verifications carry `RegionCode`. Recorded routes and photographs get a nullable `CountryCode` / `RegionCode` stamped from GPS through the existing offline `IRegionResolver` at upload time, plus an idempotent backfill. No coordinates in logs; stats are owner-only (parent-for-child like explorations). - **Continents:** neither repo has continent data. A static ISO 3166 table (alpha-2, alpha-3, continent) is added on both sides, following UN M49 (Central America and the Caribbean roll into North America). Sub-regions are a follow-up. - **Tags are free-form** with an i18n starter set suggested in the picker (same model as photo gallery tags). Limits: 20 tags per destination, 32 chars each, case-insensitive dedupe. - **Climbing is deferred** to its own issue: there is no per-user climb log (climbing is a read-only public crag catalog). The stats DTO leaves room for `routesClimbed`. - Page code lives in the app project (`projects/spikersoft/src/app/_components/destinations/`, route module `routes.destinations.ts` like `routes.mapping.ts`) because it needs `TravelStateService` / `ProfileService`, which boundaries lint keeps out of feature libraries. Shared continent data goes in `@spikersoft/domain-geo`. Order: backend-A → (backend-B ∥ angular-D) → angular-E. -------- ## Child issues (per-repo, auto-close on merge) This epic is complete when every box below is checked. Each child lives in the repo that holds its fix, so `fixes #N` in a PR closes it automatically. **Backend** - [x] spikerj/spikersoft-backend#1469 — A: destinations collection, ISO/continent table, `api/destinations` mine + PUT - [x] spikerj/spikersoft-backend#1470 — B: stamp routes/photos with country + region, backfill, per-destination stats **Web** - [x] spikerj/spikersoft-angular#1663 — D: `/destinations` page (table, grid, search, filters, tags, favorites) - [x] spikerj/spikersoft-angular#1664 — E: `/destinations/:code` detail + site-wide stats per destination **Follow-ups (not children):** per-user climb log feeding `routesClimbed`; Central America / Caribbean sub-regions; whether deleting an exploration should un-mark a visit.
spikerj added the enhancementepic labels 2026-10-17 11:07:55 +00:00
Author
Owner

All four children merged on 2026-10-17: backend slices A + B landed as one PR (spikerj/spikersoft-backend#1472), the Angular slices D + E landed on the CSS audit code branch (spikerj/spikersoft-angular#1661). The follow-ups named above are filed separately: per-user climb log (spikerj/spikersoft-backend#1483), Central America / Caribbean sub-regions (spikerj/spikersoft-backend#1484), and whether deleting an exploration un-marks a visit (spikerj/spikersoft-backend#1485). Closing the epic.

All four children merged on 2026-10-17: backend slices A + B landed as one PR (spikerj/spikersoft-backend#1472), the Angular slices D + E landed on the CSS audit code branch (spikerj/spikersoft-angular#1661). The follow-ups named above are filed separately: per-user climb log (spikerj/spikersoft-backend#1483), Central America / Caribbean sub-regions (spikerj/spikersoft-backend#1484), and whether deleting an exploration un-marks a visit (spikerj/spikersoft-backend#1485). Closing the epic.
Sign in to join this conversation.