TOPIC:

I have added new functionality to the Agenda code to allow the VPE/Agenda Creators/Website Admin to specify that the people assigned to certain roles on a meeting agenda can also edit the agenda as a whole. See below for photos of the User Interface update to support this.

Reasons for this add:
1. Currently, the system depends on text matching of specific words in role titles to determine who is the Meeting Toastmaster and thus, who can edit the agenda in addition to the VPE/Agenda Creators/Website Admin. (The Agenda Creators are those officers specified in the pop-up checklist of the Access Settings tab.) This text matching has never been very satisfactory, in my opinion, and limits what clubs can call their meeting roles. (a bad idea)

2. Currently, the system does not provide any provision for designating other meeting roles as also being able to edit the meeting agenda. For example, in my club, the General Evaluator rounds up Speech Evaluators, but because of the past limited functionality, they could not directly add the evaluators to the agenda.

With this add, clubs can determine for themselves which meeting roles can also edit the agenda as a whole, and it is more obvious which roles can edit the agenda. Some may argue that this will lead to more confusion, but I think that clubs will likely get it sorted out reliably. Additionally, since I am limiting who can designate the agenda editors for a particular meeting (only VPE/Agenda Creators/Website Admins can change) this should not be a problem.

Enjoy!

One of the reasons I am adding this now is to allow everyone to get used to this approach, as I am intending to phase out the use of asterisks (e.g., keywording), specific wording, and other klunky approaches in favor of more robust, flexible approaches in the future.

This checkbox is one of two new features that will allow me to effectively ditch the asterisks stuff in role titles moving forward.

Now, if you want to specify that someone in a meeting role can edit the agenda, then you can just specify it directly via the checkbox.

I'll give it a test and see how it goes!

I think phasing out the asterisk approach is very worthwhile. Thank you!

See below... There will still be some text matching logic in use. However, it will be moved to javascript and part of the user interface where it is more obvious. In essence, instead of hard coded text matching being in the server code, it will be in the javascript for form entry/validation... It will show up in the form of reminders and text entry helpers. This way, everyone gets the benefit of the Toastmasters aware logic, but you easily can override it and it is not longer baggage in the server code.

For example, the following below shows how the code detects when a role name contains "Toastmaster" via text match, and then shows the following pop-up up. If you click "Yes" on the pop-up, the editor checkbox gets set by the javascript. Thus, it accomplishes the same end result as the prior hard coded server code logic, but in a more flexible way... this is very much in line with my overall development philosophy.