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.
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.