search

kghalamb / AirStage

0 stars 0 forks source link

Product ideas Gibson Hooper #5

Open gibsonhooper25 opened 11 months ago

gibsonhooper25 commented 11 months ago
  1. POST request booking, for performers and venues. This would be somewhat of a layer above the current booking endpoints, where a performer or venue submits a booking request with all the current information of a booking: performer_id, venue_id, time_start, time_end. Before the actual booking is inserted into the bookings table, the entity that did not book the performance (i.e. the venue, if the performer was the one that booked) has a chance to reject or accept the request. For example, they may reject the request if they were looking for a more popular performer to fill that time slot. Only if both entities accept the booking request is it entered into the bookings table.
  2. POST review performer or venue - after a booking has been completed (the performance happened), allow the venue and performer to leave reviews or ratings for each other. This data can be stored as attributes within the Users table, like an average rating out of 10. It can be used in venue search filtering, maybe a venue wants to search for the top 10 rated performers, or a performer wants a certain venue to be filtered out of their search results when they call the /catalog/venues/ endpoint.