| Line 3 was replaced by line 3 |
| - ! November 2, 2004 |
| + ! Tuesday, Nov. 2, 2004 |
| At line 116 added 50 lines. |
| + *** Raja |
| + **** GOAL: EcoGrid as a standardized interface (using web and grid services) |
| + **** Grid-standardized interfaces: uniform interface to metacat, srb, digir, xanthoria; anyone can implement these interfaces; hides complexity of underlying systems |
| + **** metadata-mediated data access |
| + ***** supports multiple metadata standard, EML, Darwin Core as foci |
| + ***** computational services: pre-defined analytical services; on-the-fly analytical services |
| + **** all based on gwsdl service |
| + **** metacat and srb services implemented |
| + **** metadata: EML and darwin core |
| + **** authentication |
| + **** query sevice level 1: get/query services; web-based available |
| + **** registry services: implemented in 2 phases -- reimplemented -- list of avail services on web |
| + **** Next steps: |
| + ***** design and impl. other ecogrid services |
| + ***** extend existing services |
| + ***** more ams integration - kepler |
| + ***** more sms integration - growl (?) |
| + ***** add new services: onto servers, taxon servers, LSID server |
| + ***** user interface development |
| + ***** documentation and training |
| + ***** enable more apps and data ingestions |
| + ***** increase user collaborations |
| + *** Laura Downey |
| + **** usability |
| + ***** "the extent to which a product can be used by specified users to achieve specified goals with effictiveness, efficiency, and satisfaction in a specified context of users" |
| + ***** "an approach that incorporates direct user feedback througout the development cycle to reduce costs and create products and tools that meet user needs." |
| + **** benefits o fusability: increased productivity, sales and revenues, customer satisfaction; decrease traning and support costs, etc. |
| + **** real world example: after move.com completed the redesign of two problem features, users ability to find a home increases from 62 to 98 percent, sales lead generation to real estate agents increased 150%. |
| + **** user interface + functionality = usability |
| + ***** elegant or sophisticated internal algorithms don't make any diff inf the interface is bad ... |
| + **** software versus usability engineering: ui code 30 percent, now almost 50-60; maintainence, etc. |
| + ***** typical software program is released with 40 usability design problems; over 70% of CIO's state on of biggest problems is communicating with users |
| + **** incorporate usability in seek |
| + ***** collect demographic data |
| + ***** task analysis (interviews and observations) |
| + ***** apply good human factors and design principles |
| + ***** iterative design |
| + ***** gather user feedback and input: ind. interviews; group discussions; usability evals and testing; categorization exercises; self-reporting; satisfaction surveys |
| + **** general design principles |
| + ***** use minimalist approach but provide details on demand |
| + ***** apply consisten visual and information design (readability, coding, color, icons, metaphors, data organization) |
| + ***** apply appropriate interaction design (tasks, and user's understanding) |
| + ***** minimize memory and attention load (memory and processing information limitations) [http://www.laoairlines.com] |
| + ***** speak users' language (user terminology not geek-speak) |
| + **** providing flexibility (shortcuts, RCMs, wizards); provide status and feedback; provide meaningful error and feedback messages |
| + **** upcoming usability activities |
| + ***** seek annual meeting: general usability discussion |
| + ***** kepler - december: needs dicsussion, observation during training, group executioin of two simple scenarios |
| + ***** esa data registry -- february: individual or group usabilitiy testing on registering data |
| + ***** issues or ideas on the usability of SEEK tools then contact me: Laura L. Downey |
| At line 118 added 1 line. |
| + ! Wednesday, Nov. 3, 2004 |
| Line 120 was replaced by line 171 |
| - ! November 3, 2004 |
| + ! Thursday, Nov. 4, 2004 |
| Lines 122-124 were replaced by line 173 |
| - ! November 4, 2004 |
| - |
| - ! NOvember 5, 2004 |
| + ! Friday, Nov. 5, 2004 |
