From BARBEE.E.TEASLEY@x400gw.ameritech.com Fri Aug 2 16:38:22 1996 Return-Path: Received: from mailer.oclc.org (mailer.dev.oclc.org) by fssun09.dev.oclc.org (4.1/SMI-4.1) id AA12101; Fri, 2 Aug 96 16:38:22 EDT Received: from mail.cis.ohio-state.edu by mailer.oclc.org (5.0/SMI-4.1) id AA17538; Fri, 2 Aug 1996 16:38:21 +0500 Received: from ACM.ORG (ACM.ORG [192.135.174.1]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id QAA01507 for ; Fri, 2 Aug 1996 16:15:44 -0400 From: BARBEE.E.TEASLEY@x400gw.ameritech.com Received: from alpha.xerox.com ("port 4050"@alpha.Xerox.COM) by ACM.ORG (PMDF V5.0-6 #10219) id <01I7SZGFOGF2004R3V@ACM.ORG> for perlman@ACM.ORG; Fri, 02 Aug 1996 15:15:31 -0500 (CDT) Received: from Revere.Parc.Xerox.xns by alpha.xerox.com via XNS id <15550(4) >; Fri, 02 Aug 1996 13:14:36 -0700 (PDT) Received: from portal2.ameritech.com ([198.186.232.49]) by alpha.xerox.com with SMTP id <16379(5)>; Fri, 02 Aug 1996 13:14:11 -0700 (PDT) Received: by portal2.ameritech.com id AA03578 (InterLock SMTP Gateway 3.0 for perlman.chi@xerox.com); Fri, 02 Aug 1996 16:13:18 -0400 Received: by portal2.ameritech.com (Internal Mail Agent-2); Fri, 02 Aug 1996 16:13:18 -0400 Received: by portal2.ameritech.com (Internal Mail Agent-1); Fri, 02 Aug 1996 16:13:18 -0400 Date: Fri, 02 Aug 1996 13:10:45 -0700 (PDT) Subject: comments on To-Do list To: perlman.chi@xerox.com, raggavab@cis.ohio-state.edu Message-Id: Content-Transfer-Encoding: 7BIT X-Ns-Transport-Id: 0800207424C500DE7293 Content-Length: 1910 Status: RO Srinivas - Got a chance to look at the ToDo list. Looks like a good start. And I'm impressed that it's got real data in it already! It's also really helpful to have a first try that we can look at. Makes it easier to see what might work in the long run, and what may not work. Here are my comments so far: 1. I like the light, 3-D boxes around the entries. It makes them easy to keep separate 2. I'm one of those people who gets annoyed if a I have to scroll just to see what there is to be seen (ie, what a page contains). Thus, having to use the left-right scroll right off bothered me. Here's a suggestion. A lot of the information in each record (to-do item) is detail, and may not be the first thing people want to see. What if we pick the top 3-5 fields that we think people will most often want to see, hide the rest of the information, and provide a "show me more" button beside each entry. When the user presses the 'show me more', the rest of the details of the record come up. The most relevant fields are probably Action Item, Owner, Status and Next Due Date. These are probably the ones people will want to sort by, too. 3. Thinking about sorting, we need to decide what the initial (default) order is. I would think primary sort would be Status (done/not done), so that all the Done items fall to the bottom. [Or maybe move Done items off to a history file] Secondary default sort would be due date. 4. Small item: human factors research says reading words written in all capitals is harder than mixed caps and lowercase. Let's make the Column captions mixed case and bold. The members link and Action Items links should also be mixed case. 5. The first graphic (leftmost) would not load for me. The second and third were so small as to be almost unreadable. Let's save graphics for a possible add-on, and just eliminate them for now. thanks for getting going on this - Barbee From perlman@mailer Wed Aug 7 10:25:23 1996 Return-Path: Received: from mailer.oclc.org (mailer.dev.oclc.org) by fssun09.dev.oclc.org (4.1/SMI-4.1) id AA09287; Wed, 7 Aug 96 10:25:23 EDT Received: from mail.cis.ohio-state.edu by mailer.oclc.org (5.0/SMI-4.1) id AA21451; Wed, 7 Aug 1996 10:25:22 +0500 Received: from ACM.ORG (ACM.ORG [192.135.174.1]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id KAA13208 for ; Wed, 7 Aug 1996 10:25:07 -0400 Received: from alpha.xerox.com ("port 1191"@alpha.Xerox.COM) by ACM.ORG (PMDF V5.0-6 #10219) id <01I7ZMOL4PJK0014CI@ACM.ORG> for perlman@ACM.ORG; Wed, 07 Aug 1996 09:25:00 -0500 (CDT) Received: from Clayvin.Parc.Xerox.xns by alpha.xerox.com via XNS id <15650(6) >; Wed, 07 Aug 1996 07:24:18 -0700 (PDT) Received: from fssun09.dev.oclc.org ([132.174.19.10]) by alpha.xerox.com with SMTP id <15623(9)>; Wed, 07 Aug 1996 07:23:27 -0700 (PDT) Received: from dev1.NISDEV (dev1.dev.oclc.org) by fssun09.dev.oclc.org (4.1/SMI-4.1) id AA09005; Wed, 07 Aug 1996 10:23:16 -0400 (EDT) Received: by dev1.NISDEV (SMI-8.6/SMI-SVR4) id KAA13701; Wed, 07 Aug 1996 10:23:16 -0400 Date: Wed, 07 Aug 1996 07:23:16 -0700 (PDT) From: perlman@fssun09.dev.oclc.org (Gary PERLMAN) Subject: Re: comments on To-Do list In-Reply-To: " from \"BARBEE.E.TEASLEY@x400gw.ameritech.com\" at Aug 2, 96 01:10:45 pmo" To: BARBEE.E.TEASLEY@x400gw.ameritech.com Cc: perlman.chi@xerox.com, raghavan@cis.ohio-state.edu, infodir_sigchi@ACM.ORG, clore@ACM.ORG Message-Id: <199608071423.KAA13701@dev1.NISDEV> Mime-Version: 1.0 X-Mailer: ELM [version 2.4 PL23beta3] Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Ns-Transport-Id: 0800207424C500DEBABB Content-Length: 2637 Status: O Good, it sounds like progress is being made, and that Srini is gathering feedback right away (albeit frm a small sample). Sounds like we should get an ACM account for Srini. Scott Robertson, the SIGCHI Information Director, should request that Michael Clore, ACM system guru, create an account for on turing.acm.org (DEC Ultrix) for Srinivas Raghavan (username raghavan, sigchi group). Srini will work with Michael Clore to get help/info about CGI setup, databases available, etc. SIGCHI files are kept in /acminfo/1/sigs/sigchi, but I don't know about CGI BIN locations. Here are some ideas: We don't have a reqs doc yet for the SIGCHI EC intranet, so perhaps one could be created in HTML by Srini with input from Barbee, Me, Scott, etc. Minimally, I think we want to see 1. an online to-do list editable from forms password protected sorting options detailed views etc. 2. an online contact list editable from forms password protected some info only abvailable to some users 3. a way to generate the SIGCHI officer's page and others (e.g., the contact page for the SIGCHI Bulletin) from the online contact page I think a reqs doc might be organized around the tasks a user might want to accomplish: 1. web-browse to-do list for "my" tasks (perlman or all) 2. web-form change/add to-do list item (delete would be privileged) 3. web-form change "my" contact information 4. web-form browse detailed contact information by EEC people only 5. generate sigchi/officers.html (by VC-Comms only, or automatically) Here are some details: I propose that the SIGCHI EC/EEC intranet be set up in /acminfo/1/sigs/sigchi/ec, with permissions to access only via a secure interface with passwords. Ideally, the passwords would be coordinated with the ACM access system, currently in use for the online SIGCHI Bulletin. (See: http://www.acm.org/sigchi/bulletin/) Initially, we could live with an unadvertized URL, but eventually, there might be sensitive information on the pages, maybe sooner than we might expect. We might need a sigchi-ec group on the ACM machine. > 4. Small item: human factors research says reading words written in all > capitals is harder than mixed caps and lowercase. Let's make the Column > captions mixed case and bold. The members link and Action Items links > should also be mixed case. Smith & Mosier sez allcaps are okay for labels: 2 Data Display 2.1 Text 2.1/6 Conventional Use of Mixed Case Display continuous text conventionally in mixed upper and lower case. Exception: An item intended to attract the user's attention, such as a label or title, might be displayed in upper case.