Recurring event - 4.6.alpha4 - 'child' / 'parent' is counter-intuitive

[ken]

In 4.6.alpha4, the Manage Events lists recurring events as "parent" and "child".

While I appreciate the underlying implementation works this way, may I suggest this is counter-intuitive to end users. We think in terms of "first" and "subsequent" rather than 'parent' or 'child'.

It also doesn't fit with the editing options I get when I change a recurring event. I can edit any of the occurrences and update 'this event only', 'subsequent events', and 'all events'. An end user has no need for 'parent' or 'child' notation.

Please remove 'parent' and 'child' from the user interface.

[Deepak Srivastava]

The initial idea with the project was that parent (first) event would control the pattern. But later we figured out and implemented that the config could be changed from any event.
Also there were some feedback, to keep an indicator of initiator (parent / first) and subsequent (child).

Although agree they not really useful if pattern or updates could be made from any event, plus points are:
1. They do indicate that those events are recurring 
2. If the list of recurring events is long and parent tag helps find the first event quickly, in case user wants to change the pattern from that point again.

Not sure how to present this information in a better way, but completely fine with renaming those labels.
Probably just keep the tag for initiating event. But in that case label "first" (without subsequent) may look a bit odd.

May be Lindsey and others can jump in to share their thoughts?

[Coleman Watts]

How about a notation like:
My Event Title (1 of 3)
My Event Title (2 of 3)
My Event Title (3 of 3)

[ken]

Coleman, that's a good idea!

[Coleman Watts]

https://issues.civicrm.org/jira/browse/CRM-16323