In this presentation I will focus a good bit of time on how I provide support and "training" for our editors along with some of the things I do to make editing easier for them. I have always thought I would rather something be harder on my end if it makes it easier for our editors, and I hope to showcase that mindset. I will also talk about how I organize our permissions using groups and such.
6. How I educate
Tutorials
Written
Video
User Manual
User Support
7. Tutorials
Use both written and video to make learning easier
for different learning styles
Tutorials are short and to the point
Easier for users to use over and over
Easier to update when needed
Mostly cover topics that are specific to our website
8. User Manual
Basically the same as the tutorials with a few
differences
Text Only. Users can print this out and keep it near
so it is readily available
Not updated as regularly as Tutorials, but procedures
usually do not change that dramatically
Have received good feedback on this method
9. User Support
This is the hardest with a department of one
Most user support is handled through email/phone
If Tutorials are up to date, it is simple to direct most
user support inquiries to a specific Tutorial
Last resort is to schedule a meeting, however it is
not a bad idea to check in with editors every now
and then
12. Permssions
Control what editors can see/edit
Place users into groups and give appropriate
access by group
This makes it easy to give appropriate permissions to
new editors as well as take permissions away
Giving permissions by individual user
Necessary in some situations, slightly more difficult
to set up
13. Workflows
Control content through approval process
Great idea for student groups, or approval of news
articles, announcements and events.
Can seem too restrictive to Faculty
