Skip to content

Conversation

erikbsa
Copy link
Member

@erikbsa erikbsa commented Oct 13, 2026

Summary

  • Add PostgreSQL migrations for venues and external source IDs
  • Add GraphQL venue types and read queries
  • Add a validated, repeatable seed script for normalized Geoapify data
  • Document VM development database setup and venue import steps

Notes

  • The seed data file is empty and must be populated with verified venue records
  • Image, description, price level, rating, and review count are not included in this version
  • The migration and seed import must be run against tapfinder_dev

@erikbsa erikbsa requested a review from a team as a code owner October 13, 2026 16:14
@andss andss self-assigned this Oct 13, 2026
Copy link
Member

@andss andss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved as a foundation for the venue database and Geoapify import. The schema and source mapping give us a good starting point, and rerunning the import preserves existing venue IDs.

As agreed, I’ll take over the remaining work in a separate PR:

  • Improve validation of coordinates, opening hours and website URLs, with tests.
  • Adapt our Geoapify export to the seed format.
  • Add the remaining Venue fields (priceLevel, rating, reviewCount, description and imageUrl) and store the original source data.

I’ll complete the validation and format adaptation before the first import into the server database. The additional fields will be introduced through a new migration that preserves existing records and IDs.

@andss andss merged commit 8e715e4 into main Oct 13, 2026
1 check passed
@andss andss deleted the feat/venue-database-and-geoapify-seed branch October 13, 2026 19:29
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants