Meeting Notes 2.9.

Agenda

  • How membership categories / reservation rights are created and how they affect round statistics
  • How booking rules are configured and what types of restrictions can be defined in the tee sheet
  • How green fee pricing is configured and how prices can be adjusted based on the booking time
  • How the booking process works from the player’s and admin’s perspectives
  • Tee sheet functionality: editing, copying and closing tee times, and adding comments


Memberships and Statistics

  • The number of categories can be reduced by combining categories that have similar booking rights.
  • Round statistics are based on categories, so when defining categories, it is worth considering how detailed the data needs to be for each category.
  • Future AI development will make it possible to use even more streamlined categories, as other data such as tags and roles can also be used for reporting and statistics.


Booking Rules

  • A “view only” feature is required in the booking view, allowing players to see the entire season but only make bookings up to 7 days in advance. There is currently a workaround for this, but the rule could be made more straightforward.
  • Restricted times / peak-time rules are currently defined in minutes. This needs to be changed so that the setting can be configured in days, hours and minutes.
  • 10-round cards (overseas members) work automatically. Making a booking reduces the number of remaining rounds by one, and the round is restored if the booking is cancelled.
  • The seasonal limit for guests (6 rounds at a discounted price) is currently not working. This could be addressed in the future using AMS.
  • The system does not currently support dynamic / demand-based pricing, but prices can be adjusted manually on an hourly basis. Dynamic pricing is, however, being considered for future development.
  • The number of simultaneous bookings needs to be configured so that competition entries are not included in this limit.


England Golf API

  • The API makes it possible to search for players by their home club and name when making a booking.
  • This enables booking logic similar to the one currently used in Finland.
  • This reduces the creation of duplicate player records and makes features such as handicap restrictions easier to implement.
  • In addition to this logic, players could also be allowed to make bookings using only a name and email address. At the moment, this functionality is available to admins only.


Payments

  • When making a booking, the player can choose whether to pay online immediately or pay at the club.
  • In the next meeting, we will demonstrate how unpaid bookings are displayed at the till (POS).


Tee Sheet

  • Admins can switch between the customer view and the admin view.
  • Players only have access to the customer view.
  • Fulwell requested colour coding so that the admin and customer views are visually distinct and the current view is easier to identify.
  • The basic functionality is clear, and moving / copying tee times is straightforward.
  • Tee times are automatically blocked for competitions, but development of the competition integration is otherwise still ongoing.
  • A separate report can be used to monitor the number of rounds played within a specific time period. The report can be broken down by player name or, for example, the reservation right / membership category used.
  • Mass communication to players within a specific time period and deleting tee times can be done from the same view.
  • Fulwell requested a banner in the booking view where an informational message relating to a specific day could be added and edited.
  • Scott will provide Miikka with more details about the booking requirements for “Knockouts”.


Next Steps

  • Miikka will update the article created on cms.ukgolfdemo.fi with instructions relating to the topics covered in the meeting.
  • Miikka will discuss the ongoing development work with Lasse (Head of Development) and whether any of the developments could be demonstrated in the next meeting.
  • The next agenda will cover the POS system and ongoing development work. The agenda can still be refined further.
  • Scott will get back to Casimir regarding the list he sent concerning the Levy development.