Overview

This page details the expectations for integrating email attachments into Chandler for 0.5. This work will be stage over the next couple of releases with most of the work occurring in the services layer for 0.5. The approach will be to see how far we get in 0.5 and have none or minimal UI (at the discretion of development) to enable testing of the attachment functionality that is working at the end of 0.5. We are not attempting to do anything innovative with attachment in Chandler.

Assumptions

• Minimal engineering UI for 0.5, whatever is necessary to help test the phases attachments functionality.
• Brian will be supporting as many of the MIME types as possible in the service layer (he estimates around 90%)
• Only the presence of an attachment that is a "document" type will be visible to the user in 0.5.
• Any UI for handling other MIME types will be moved to post 0.5. Need to sit down with Mimi and plan what scenarios we want to handle in the UI for these other types. Will add this to the requirements for 0.6.

Workflows and Use Cases

Use Case #1: Add an email attachment

• There will be no Chandler UI to add an attachment for 0.5.

Use Case #2: Remove an attachment

Supporting this use case is not a requirement for 0.5.

Use Case #3: Indicating that an attachment is present, in the detail and summary views

• The will be a visual indicator in the detail view listing the attachments if any are present. You will not be able to click on the attachment.
• The use case for testing this is to send an email with an attachment (ie: word doc) from another email client to our Chandler email.

Use Case #4: Opening an attachment

Supporting this use case is not a requirement for 0.5.

Issues List

• Need to remember to add attachment colum in the summary table view for 0.6.

Status

• Sent out for review 11/11/04.

-- SheilaMooney - 11 Nov 2004