Event Management

Issue #71 resolved
Ryan Parry created an issue

I would like to propose the ability to manage events better in the future please. The Senior Staff and EC should be able to post, edit, and delete an event regardless of who posted it ie: a former EC no longer with the ARTCC.

The old site, before the forum upgrade, allowed the EC and Senior Staff to manage an event regardless of who posted it. Now if an EC posts an event then vacates the position, we have no way to go in and update the event with a banner, changed information, anything, and we have to send an email to VATUSA and wait for them to either make the change for us, or delete the post so we can repost it. In addition to that, events are posted in the forums under the user account of whoever created it. If that person is to find themselves in a sticky situation, or becomes an unsavory person they are representing the ARTCC when they shouldn't be.

Comments (3)

  1. Daniel Hawton

    I can grant senior staff moderation access to the events forum so they'd be able to edit and delete posts assuming the VATUSA leadership is okay with that. I'm not sure I'd trust ECs with that same access though and there is no forum method of dissociating posts from the original author to a fictitious entity.

    The old forums handled the events completely differently. But it was a paid forum software to which the staff did not have a key to upgrade it, so it was left unupdated since 2004. There were a large number of severe security fixes since then, and it was requested upon my appointment to upgrade and replace the forums. That brought with it a complete change in how events were handled. To meet the requests of the leadership is the reason the events moved into forum posts like they are now.

    I'll discuss and enable moderation approval with the leadership when I get home from work.

  2. Daniel Hawton

    Just adding: users who are not in the "EC" group cannot edit or delete their own posts. They must be in the "EC" group to edit or delete their own posts.

  3. Log in to comment