Hi Thomas,
hmm some of your requirements are already on our todo-list, but some of the adaptions would require some extensive code changes and custom development. (Even more if these changes should not change the current behavior / system of Matukio for our normal customers. Just "customizing / hardcoding" the needed changes into Matukio would probably be a lot easier then to adapt it for everyone, but we are willing to give it a try without bringing that into account).
For a quote we need some more details, so we maybe should have a chat or phone call
Let me outline a basic list of changes needed:
We publish an event (Autom. email to all our societies), our societies log in and register some of their members (editable, confirmation email to society)
The automatic emails would require some custom coding (Do you have a fixed list of email addresses, or are they already there as Joomla users? (that would make the this and other things much more easy)), we have a option inbuilt to notify (fixed) email addresses about a new event creation including event details, but it's primary thought for administrators to watch there organizers - this sounds more Matukio needs to send some sort of automatic newsletter (We have already manual options for this). It is easily possible for organizers / joomla administrators (backend and frontend) to add / edit bookings (e.g members) to Matukio events, if you don't want them to also have the ability to edit / change all bookings etc., we would also need to change some code so they can't change all bookings but just theirs - custom booking confirmation emails (with an easy HTML template system) are already inbuilt.
at day X before event system sends reminder email to societies
That is also going to need some changes, because we need a cronjob for this. PHP is normally not designend to execute timebased jobs (e.g. looking every hour / day in the database and when Day X is there -> send an email). I already have this feature on my TODO-List for a later version.
at registration deadline the system decides whether the event takes place or not (based on amount of participants; system sends cancellation email to societies & info on upcoming events, system sends confirmation/reminder email to administrator)
This one is the most complicated part, because that requires some extensive changes and custom development.
and system sends invoice to societies (depending on how much participants).
Matukio already has an inbuilt invoice generation (PDF based on an easy to customize HTML-Template), but it is currently designed to generate invoices per booking - We would need to change that to generate invoices per society.
Kind regards,
Yves