Event Approval Problem
Our workflow is this: librarians create events. Managers approve events. Admins publish the events. The problem lies in the approval process: Everything that's approved/ready to post goes to one big list. We host hundreds of events, so if we could filter by manager or building, that would be a huge enhancement. Another shortcoming is that the Admins have no way of knowing if the managers have approved their events. A three-step process for (1) creating; (2) approving (with a checkmark or something); and (3) publishing events would also be an enormous improvement.
Julianne Smith
shared this idea
-
Kasey Blankenship
commented
Because drafts do not hold rooms, the workaround suggested to us was to leave events in the pending approval stage if they are still drafts by clicking "Submit" instead of "Publish." We now have a long list of pending events that include both drafts and events ready to be reviewed for the calendar. It would be helpful to our staff to be able to "un-approve" events if they are accidentally published instead of submitted.
To clarify, we use the approvals to signal to our admin that events are ready to be reviewed for publishing. 1) Librarians schedule/submit their events and 2) publish them when they are ready for the public calendar, 3) the admin makes sure all i's are dotted and t's are crossed, and then 4) publishes the event. If the event has 0 approvals, the admin assumes the event is still a draft and leaves it alone. When the event has 1 approval, the admin reviews and publishes. If a librarian accidentally publishes a draft, there doesn't appear to be a way to unpublish from the pending approval stage, which means we now have a few draft events with 1 approval just cluttering the workflow. Instead of having the admin approve and unpublish or make the event private, which takes us back to our original issue with drafts, it would be helpful for our librarians to be able to "take back" the approval.