-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow professor to modify other profile attributes #60
Comments
Should we let them set titles? Seems like that could be abused. Well, probably not, but... |
Yes. Allow them to modify: name, title, email, office, phone. Do not allow them to edit their kangaroo webpage. Add a user editable personal webpage link. Many faculty have requested the ability add additional labeled blocks to their calendar (regular meetings, off campus times, etc). if a faculty is current "inactive", we should drop back to an inactive page with little to no information. we should only show a limited teaching history: probably only the current semester and the previous major (FA, SP) semester. We need to order teaching history in reverse chronological order (fall 2012 before summer 2012 before spring 2012 before janterm 2012). Thanks! I am working on getting IT to create us reports. Bill Edgette thinks he can run these in a cron job and push them into a share volume and we can avoid most of the page scraping. He has asked for a detailed specification for each report and is requiring that I go through the normal IT project request process (hoops). On Sep 4, 2012, at 9:46 PM, Phillip Cohen wrote: Should we let them set titles? Seems like that could be abused. Well, probably not, but... — |
That's great, the report will be a big help. With cron, we might even be I can help with the specification of the report, but I'll need a few (I'm assuming this is a good approach? The alternative is to ask them to do On Wednesday, September 5, 2012, Michael Higgs wrote:
|
professor name
professor title
professor office
professor email
what else?
The text was updated successfully, but these errors were encountered: