TOPIC:

Club 1027647 Huntingdonshire Speakers Club

Help! My agendas are broken. The speech evaluators are now listed incorrectly and refuse to be corrected!!

We have four evaluators, labelled Speech *Evaluator #1* to Speech *Evaluator #4*

The sign up option was allowed on the first four instances (1-4).

The second set, which members cannot sign up for (for obvious reasons) were also labelled the same way. This allowed the agenda to put the signees names in that place on the agenda.

The second set has changed and is now labelled Speech *Evaluator #5* to Speech *Evaluator #8*

I cannot change Speech *Evaluator #5* to Speech *Evaluator #1* as it does not save when I press Save. The same goes for Speech *Evaluator #6* to Speech *Evaluator #8*

In addition, on some agendas the first four are now called Speech *Evaluator #1* but when I edit the agenda they appear correctly and I am able to save the agenda again, then they remain.

I tried creating a new agenda template from an older meeting where roles appear correctly. This was created and had the same problem I have described above.

I tried to create a test agenda and made the roles Speech *Evaluator #1* to Speech *Evaluator #4* as sign-up roles, then made Speech *Evaluator #1* again and it got changed to Speech *Evaluator #5* therefore I declare this problem a bug and need your help, please.

Turn off the auto renumbering.

It was working, so something has changed and broken it.

We make use of the reporting so it needs to be clear how this needs to be configured to work correctly and if it doesn't work, it needs to be fixed today.

Yes a change was made, an auto numbering feature was added. Clubs that use the #1,#2,#1,#2 for more than once a role will have issues, turn off the auto numbering.

I have made some updates to this feature to (hopefully) allow it to work well for more complex agendas.

In addition to supporting multiple occurrences of a numbered role or multiple "keyworded" occurrences of a numbered role (e.g., *Evaluator #1* Gives their Evaluation), it should also be able to handle more complex agenda items where it contains both a the keyworded numbered role and a reference to a numbered role in a different agenda item.

For example,
*Evaluator #1* Gives their Evaluation of Speaker #1

The askerisks make this agenda item tied to the role "Evaluator #1". However, the additional reference to "Speaker #1" should also get renumbered if you were to reorder the Speakers. For example, if you moved the current Speaker #1 to the Speaker #2 slot, you should find that the Speaker #1 reference in this agenda item also gets updated.

This is an example of what I am referring to as a "complex" agenda item for this feature... multiple numbered roles referenced in a single agenda item.

For future reference, you should always consider trying out the renumbering on a copy of your agendas that you really do not care about. I have tried to make this feature handle a number of edge use cases that I never expected to support, but for every feature I come up with to support a variety of use cases, somebody always seems to find a way to break my code. It is a good thing I like an intellectual challenge.

Remember, you are not obligated to use this feature... you can shut it off if it is not working as you expect.

Thanks for the follow up..
I think that our club's agenda is complex because we had the benefit of a real geek editing it. Now that she's moved I hate to mess with it and move things a round. ....I'm no geek. Just a nerd.

Thanks for looking at this, Steve. It is quite a complex use-case scenario. Maybe we should be able to declare anything we want auto-numbered in the same way as repeating roles? Also, can we have the option to choose whether it modifies published agendas as the biggest problem I thought I had was that they had all changed, however they corrected themselves after I corrected the first one - it wasn't intuitive and there was a moment where I felt quite put-out (you can blame our hot summer for that!)

Are these being stored in arrays so you can use the index number for auto-numbering? Will multi-dimensional arrays be a good fit for this?

Thanks again for your help!

Darren.

I am not going to spend any more time on this. (Not supporting any more complex / edge use cases.)
Auto-renumbering works across multiple roles (one in relationship to the others), so it has to be all or nothing.

If you don't like the way it works, shut the feature off and don't use it.

You can combine the use of askerisks and role numbering for repeated numbered roles.

Locking this and moving on. If anyone feels strongly that further improvements are warranted (I don't) post an improvement suggestion in that forum section so that others can post in support of it.