Meeting Notes 20040625

Difference between sending an email

• And an email as an item that can be versioned.
• Emails are both an email and an item.
• So while resent emails are technically two separate emails, in Chandler, resent emails are two versions of the same item.

• [OI^?] How do we distinguish between the email wrapper and the core content of an item? What's in the wrapper? What's the item? OR Are they one in the same?
• Sidenote Rather than having a Send message stamp on the mark-up bar, there should be an Add people stamp with the option to send it out.

[Insert] Sketch out the UI for this.

Representing major and minor versions to the users Capital N v. small n versions

• Do we even need minor versions?
• If we have minor versions, can we combine them into a single ad-hoc collection with major versions.
• Proposal: View all major versions of item X (all capital N notifications) in the context of it's discussion thread with a separate link to "See all version" of this item will expand the thread to include minor versions as well.

[Insert] Sketch

Passwords and Certificates

• Waiting for engineering proposal

Need further discussion on merging Triage status with Task status

• When items are stamped as Tasks, Triage status is expanded to also include: Deferred and Delegated.
• Should we have that for all Triage status?

-- MimiYin - 25 Jun 2004

Comments

DuckySherwood - 28 Jun 2004

Mimi --

When I resend a message, frequently I want to make minor edits, so it isn't exactly the same item. I can think of two use cases right off the top of my head.

• When I add a person, frequently I want to mention what the history of the message is. "Jack -- here's the message about the fromblemeister order that I sent to Joan (CC Andy) last week."
• Sometimes I need to make a correction. "Joan, Andy -- I goofed: the order was actually placed on 23 Feb 2003, not 23 Feb 2002."

MimiYin - 28 Jun 2004

Ducky --

Yes, you're absolutely right. I think people will either edit messages to write notes for themselves or edit messages to resend them again as a new version of a collaborative document. I think because we're not really doing Annotations as a separate feature in Canoga, for now, the two use cases will be satisfied with a single user affordance. It's possible that with versioning, we won't really need to have a separate annotations feature.

• User receives email - v.1
• User edits email with annotations - v.2
• User edits email to resend - v.3

The annotations version is always preserved as a "separate version" of the same item. Instead of having to explicitly choose which feature to use: Annotation v. Resend, users simply do what they mean to do and through ad-hoc collections, maintain easy access to both "versions of an item" and "version that were actually annotations on the item."