Feature Request: Meeting Effective Dates

[jeboal]

There are meetings that are 1-time, or only for a limited time (like outdoor meetings from months xxx-yyy, or meetings only during a conference) that it would be excellent to list in the guide during their time in effect and have them automatically appear "Closed" when they are not meeting.

Proposed possible solution:
Add optional fields:
Start Date Field: Start_DateTime
Expiration Date field: End_DateTime

A) The meeting would not show in the guide until the user's local date/time would be between Start_DateTime and End_DateTime, if these fields exist.

B) The meeting would show as "Closed" if < 60? days past the End_DateTime

Thinking that making these fields optional would make the feature backward compatible with existing data, and the TSMLUI would only act on these fields if they existed.

[joshreisner]

thanks @jeboal this is a timely topic, i've been thinking about this lately for meetings that are temporarily closed over the holidays. this also happens for seasonal meetings like you said, or when there is a natural disaster or some other issue

i have moved this to the spec discussions since this will need to be cross-application and not special for TSML UI. we'll need to discuss this with GSO and have them not only agree but i think we need wait for them to actually implement support for it in Meeting Guide before we move forward in other applications, otherwise users could see meetings and not know they're inactive

rather than "Closed" which has special program meaning we'd label these meetings "inactive" -- but this could be a mechanism to officially deprecate the Location Temporarily Closed meeting type

i might call these fields active_on and inactive_after and they could take an optional date YYYY-MM-DD

some use cases:

• let's say we have a Monday 9am-10am meeting that is set to have its first meeting on the first of January. in this case active_on could be 2024-01-01 and if it's added to the schedule today (Dec 23) it would appear as Inactive from now until 10am on December 25, thereafter it would look like a normal weekly meeting
• let's say we have a Monday 9am meeting which has been meeting for years but is going to be suspended for Christmas and New Year's Day, in this case active_on could be 2024-01-08 and inactive_after could be 2024-12-18
• in the case of the meeting closed on Christmas and New Years, there could be some flexibility in the dates. for example, if it were active_on could be 2024-01-02 and inactive_after could be 2024-12-24 and it would have the same effect as the bullet point above
• let's say that we have a group of summer meetings at different times of the week but they all run from June-August. each of these meetings could have active_on of 2024-06-01 and inactive_after of 2024-08-31
• might be cool if the year above were optional, that way the meetings would not have to be updated every year
• let's say we have a meeting that is having its last meeting ever at the end of the year. we could say inactive_after on 2023-12-31 and it could remain on the schedule for some period of time with an Inactive label - i would say 30 days would be better than 60 but perhaps that could be up to the application. as an inactive meeting you should not be able to get directions, share, or add it to calendar

[onemooresam]

Hi @joshreisner - has there been any movement on this? A district is asking to manually note a meeting is not happening due to inclement weather or other timely reason, but to also have that status change automatically reversed at a set date. Further, being able to provide the reason for the temporary change is desired.

[joshreisner]

thanks @onemooresam seems reasonable

we haven't made any headway on this yet. we have talked about it a bit internally and with GSO - i'll let you know if something happens with this