|
The TEC-T subcommittees includeT
Each subcommittee is charged with
- developing requirements that meet Dartmouth’s need for collaboration and social software tools and services and
- evaluating available systems to see which features they offer that meet these needs.
The subcommittees in turn will offer their suggestions to the TEC-T project team who will make recommendations to the Council on Computing.
Timetable for Evaluation Process
|
Due Date
|
Milestones
|
|
March 31, 2009
|
Develop Subcommittee Charters
|
|
April 30, 2009
|
Complete Subcommittee Work
|
|
May 8, 2009
|
Subcommittee Deliver Reports
|
|
May 22, 2009
|
Share Proposal with Stakeholders
|
|
May 31, 2009
|
Present Proposal to Council on Computing
|
|
June 15, 2009
|
Reach/Communicate Solution Decision
|
Testing and Evaluation
Subcomittee Charter (PDF document) - 4/29/09
The testing and evaluation subcommittee is evaluating the potential replacements for BlitzMail and Oracle Calender across a number of platforms and browsers. The variables we tested:
Communications
Subcomittee Charter (PDF document) - 4/29/09
Technical
Subcomittee Charter (PDF document) - 4/29/09
The Technical Subcommittee will identify the technical challenges involved in migrating to a new email and
calendering system, and propose solutions. Some of the technological considerations they are examining on prospective systems include:
1. Migrate all mail, using
-
IMAP import tool, built into server, or
-
External IMAP to IMAP copying tool, or
-
Users can manually copy messages if needed
2. Migrate personal & group mailing lists, including
3. Migrate calendar appointments
-
Users can export/import calendars by themselves if needed, or
-
A program to migrate calendars system-wide (if available)
4. Existing Dartmouth.edu, alumni Dartmouth.org addresses continue to work (including nickname support)
5. Dartmouth name/password login credentials continue to work
6. Ability to automate account creation/removal/maintenance
7. Search Dartmouth directory for email addresses, including searching by nickname
- Plug in tool to enable searching external directories
8. Search external (DHMC) directory for email addresses, including searching by nickname
9. Administrative interface for changing passwords, creating groups, etc.
10. Capability to respond to mailbox snapshot requests
Top of page
Security and Privacy
Subcomittee Charter (PDF document) - 4/29/09
Reference and Background Checks
Subcommittee Charter (PDF document) - 4/29/09
The reference and background check subcommittee is calling several institutions to ask about their experiences moving to and using hosted email and calendar solutions. Some of the questions we asked:
Background
- How many users do you have?
- What system(s) were you using?
- What motivated you to change?
Decision Process
- What systems did you look at when considering a new email system?
- What factors were the final deciding factors?
- What schools did you contact as references and what were their comments?
General
- What do you provide for email services for Alumni?
- How are you handling student accounts when they graduate?
- Did you do any branding with your new email system?
Features
- Are you using an IM feature in the email system?
- Are you using calendaring functions in your new email system?
- Are you using IMAP features or POP features?
- What features are used most often and by whom?
- If you have students on a different system from faculty and staff how do you handle collaboration between the two groups?
Transition
- Did you migrate existing email onto the new system?
- If so, was the migration performed by central administrators or by individual users?
- If so, what problems did you encounter?
- Did you migrate existing calendar data onto the new system?
- If yes, was the migration performed centrally or by end-users? How did it go?
- What types of training did you provide?
- What is the most common question you received during the transition?
- Have you conducted a post Go-Live survey?
- If so, what did you learn?
- Where there any surprises?
- If you went through this process again, what would you do differently?
- What advice would you give to us as we move forward?
Infrastructure
- What are you using for a directory system with email?
- How are passwords changed?
- What is the policy for changing passwords?
- What is your end-user support model for email?
- What is your administrative model for managing the email system?
Vendor
- How is the quality of support provided by the vendor? Examples of good or bad responses?
- What is the uptime?
Top of page
|
