From: Debra Goldentyer (goldenty@haas.berkeley.edu)
Date: Fri Aug 23 2002 - 12:26:25 PDT
I like the idea of a "publish" flag (is that possible?) or some sort of
after-the-fact alert thing. If the majority of the pages are ok and in
compliance, it seems less "police-y" and all around easiest for everyone.
You can look at the flags and triage from there.
D.
At 12:30 PM 8/23/2002 -0800, Sara Leavitt wrote:
>Hi Anna,
>
>Perhaps you can design a set of web forms to handle your time-critical
>information with restrictions on the type of data allowed (e.g., no phone
>numbers, no links) or even better -- if you know ahead of time what kinds
>of info gets changed, use drop-down menus, radio buttons, check boxes to
>select pre-formatted info for inclusion.
>
>For other pages, a solution might be to include a "publish" flag that
>get's turned on by responsible parties after review.
>
>-Sara
>
>At 11:04 AM -0700 8/23/02, Anna Maurer wrote:
>>Hi all,
>>
>>I'm running into a situation I'm having a hard time resolving, so some
>>other points of view would be very helpful.
>>
>>Currently, I'm a one-person web shop, and the only one with access rights
>>to the webserver. I'm trying to figure out the best situation to allow
>>certain key individuals to post to the website, without compromising
>>security. Privacy issues and protecting the University's image are also
>>factors. Purchasing a CMS is not possible, so I have to develop it
>>myself. I have ASP, MySQL, and Visual Interdev at my disposal, as well as
>>a real need.
>>
>>I've narrowed down the procedure to a SSL encrypted, password-protected,
>>web front end to a backend database. The individuals would be able to
>>update the content, but not touch the template or navigation structure.
>>My sticking point is the review period between the data getting updated,
>>and actually posting to the website.
>>
>>The issue is the individuals who would be posting. I've got a wide
>>variety. Some are just as fanatical as I about web privacy and security.
>>Most aren't aware of university policies and would happily post
>>endorsements and links to commercial sites. Some would pass the task onto
>>student assistants. And then there are those that - every year - I have
>>to re-train in the fact that I will not allow personal information, such
>>as home numbers, to be posted on the web without a signed letter of
>>consent from the individual involved.
>>
>>The final monkey wrench is that some items could wait for me to review
>>them, but others need to be posted immediately.
>>
>>SO - is anyone in a similar situation? Advice and recommendations are
>>welcome. I'm leaning towards setting up a notification system so I know
>>when and what someone does. It wouldn't prevent inappropriate material
>>being posted, but at least it wouldn't be up for long, which is still too
>>long for me. Or I could approve any submissions before they get posted,
>>but that interferes with the "Pools Closed Saturday" post submitted at
>>6am on Saturday.
>>
>>Regards,
>>
>>Anna
>>
>>**************************
>>Anna Maurer
>>Web Developer
>>UC Berkeley
>>Athletics and Rec Sports
>>2301 Bancroft Way #4420
>>Berkeley, CA 94720-4420
>>
>>-----------------------------------------------------------------------
>>The following was automatically added to this message by the list server:
>>
>>Webnet information is available at <URL:http://webnet.berkeley.edu/>.
>
>-----------------------------------------------------------------------
>The following was automatically added to this message by the list server:
>
>Webnet information is available at <URL:http://webnet.berkeley.edu/>.
_______________________________
Debra Goldentyer
Web Editor
University of California, Berkeley, Haas School of Business
510-643-3847 / goldenty@haas.berkeley.edu
http://haas.berkeley.edu/
-----------------------------------------------------------------------
The following was automatically added to this message by the list server:
Webnet information is available at <URL:http://webnet.berkeley.edu/>.
This archive was generated by hypermail 2b29 : Fri Aug 23 2002 - 12:43:06 PDT