Impossible to mark attendance for recurring event stream

[dantefromhell]

I created a never ending recurring event that represents a weekly meetup within a space.

While I can mark my attendance for individual events, it is not possible to mark my attendance for the whole series.

[yurabakhtin]

@luke- I don't think it is possible with current database structure and code, because for attending status we use the table calendar_entry_participant where we have to know calendar_entry_id, i.e. each recurrence calendar entry should be created in DB before user can be attended. A separate calendar entry is created automatically only when user clicks on the date cell:

[luke-]

@yurabakhtin Ok, let's discuss some improvement possibilities here at a later time to possibly support this.

[dantefromhell]

I'm wondering if I can participate in the design thinking of this? But I struggle to find the documentation for the current mechanic & data model for recurring events.

[yurabakhtin]

@luke- We can try this:

• Add new buttons like [Attend All] [Maybe All] [Decline All] for recurrence event, locate them above or under the buttons [Attend] [Maybe] [Decline], or we should think how to make the UI better.
• Add new column like recurrenced in the DB table calendar_entry_participant
• When click on a new button [xxxxxx All] we fill the column with state 1 that will means all recurrenced/child events will have the same participant state. And for optimization we can clear all child event records from the table calendar_entry_participant if they were added before, or we may keep them for case when the button [xxxxxx All] will be clicked second time so user will have the participant states per each separate event as before the button [xxxxxx All] clicking.
• Also after click on the button [xxxxxx All] all single buttons [xxxxxx] should be disabled/grayed.

---

Another UI:

• Add new checkbox [x] Use this participation for all recurrence events, put it above or under or on the right the buttons.
• On click the checkbox update new column recurrenced in the DB table calendar_entry_participant to value 1 for parent event. For child events do same as I have written above.

---

Of course SQL queries will be more complex with this structure and I am not sure how it will be possible to implement the filter by "I'm attending" but we can try.

[dantefromhell]

A random thought that came to mind reading @yurabakhtin proposal.

I frequently have situations where I want to be able to decline one (or a more) specific dates of a series. E.g. when marking my calendar for vacation, I decline team meetings I will be unable to participate.

Also after click on the button [xxxxxx All] all single buttons [xxxxxx] should be disabled/grayed.

IMO conflicts with the scenario above. Would it be possible to:

• Disable/ grey out 'accept' button if the whole series is marked as attending
• Disable/ grey out 'decline' button if the whole series is marked as declined

I guesstimate the UI piece is rather flexible to implement this - the question I am curious about is if the DB schema allows this.