Venue Registry

Each venue is registered with name, address, and GPS coordinates that anchor it on the public map. The profile layer adds photos, descriptions, capacity figures, and amenities that render on venue detail pages, while a separate court inventory lists every playing surface with its number, terrain type, indoor/outdoor classification, and lighting status. Ownership is modelled through a club_id reference so that operations like opening hours, bookings, and homologation always resolve back to a responsible OrgNode within the tenant.

Discovery is built on two cooperating endpoints. The directory search filters by location, capacity, and facility attributes for structured queries from federation portals, and the map-based finder runs a Haversine-based geo-search against lat/lng/radius parameters so the public app can stream nearby boulodromes as the user pans the map. Both views share the same accessibility schema, exposing wheelchair access, parking, toilet facilities, and hearing-loop availability so that players with accessibility needs can pre-qualify a venue before travelling.

Opening hours are managed as structured weekly schedules with override windows, which the venue feed broadcasts to player apps and which the booking system consults when computing available slots. Contact details (phone, email, website) are stored on the venue record itself, while social links live in a dedicated channel feature to avoid duplicating identities across federation tooling.

Ratings and reviews close the loop: visitors leave star ratings and short reviews, which surface aggregated scores on the directory and finder. Moderation hooks let club administrators flag inappropriate content, and review counts feed into ranking heuristics so well-run venues bubble up in nearby searches. Every change to a venue record is auditable through Craft Easy's standard audit trail, and the registry is the read-down source for downstream subsystems including Court Management, Booking, and Homologation.