Issues on survey

1. Nomadic use access of Chandler information from multiple machines -
   • prevelance
     • Faculty
     • Administrative staff
     • Students
     • Departments
   • method/style of access
     • Is a a web UI necessary for deployment?
       • would read-only access be sufficient for initial deployment?
     • If someone were to provide a Nebula-style web access to Chandler calendar data only, would that be sufficient to deploy?
     • Would you deploy Chandler on lab machines if no private data persists on disk after session?
2. on-line accessible persistance
   • prevelance of private availability
     • private machine on-line and accessible 24/7
       • Faculty
       • Administrative staff
       • Students
       • Departments
   • prevelance of public availability
     • privately managed _private machine accessible on-line 24/7
     • publically managed, e.g. private storage/ftp/web page space on IT supported machine
3. Proof of scalability from the start
   • based on poor Meeting Maker experience
4. Trial deployment
   • Would you be willing to try Chandler in a decentralized 'workgroup' environment?
   • Would you require Chandler to be tested in a central server configuration?
5. Corporate Time interoperability
   • is interoperability, Chandler is a client to Corporate Time server, a show stopper
   • would Chandler as a CAP client be sufficient assuming Corporate Time will migrate to support CAP protocols

1. What are needs for kiosk-style usage of Chandler?
   • Does this need to be a 1.0 feature?
2. What would the web interface of Chandler be like?
   • What subset of features are critical to a web interface
     • Basic email access?
     • Basic read only calendar access?
3. How can we ensure that both centralized and decentralized requirements work seamlessly?
4. What kind of administrative and reporting requirements are there?
5. How do we migrate a user's existing data to Chandler [parcel specific data e.g. email will be dealt with at the parcel level]
   • Which email programs are the most used so that we can write converters?
6. What deployments and features should come first?
   • informal - just let interested users download
     • administration/ staff
     • faculty
     • students
   • formal
     • departmental
     • other work group
     • students