[Design] Possible simplication of Communication status and Who columns

[Mimi Yin]

=====
Simplifying sorting on Who?
=====
What if we don't allow the user to sort on the WHO column? What if you
always have to specify an attribute to sort on? From:, To:, CC:, BCC:, Sent
by:, Edited by:, Updated by:, Created by:

I don't think it's valuable to be able to sort of a generic WHO attribute
anyway.

We would need additional UI for this (e.g. Who column header is a pull-down
as well), so I've been avoiding asking for this, BUT it may simplify the
sort issues around computed attributes?

=====
=====

Goals: Simplify the concept of 'perspective' in the display Items stamped as
Communications. (Not sure if this accomplishes that goal.)

Side-effect: A better way to differentiate between Communications
specifically relevant to me and Communications I receive because I'm on some
list/alias.

=====
For the first-time an Item is sent or received.
=====
=====
If you are mentioned in any of the addressing fields, i.e. From:, To:, CC:,
BCC:, Sent by:
+ Then you see the Item from the perspective of where you appear.
+ People in the From: and Sent by: fields see the Item as Outbound
+ People in the To:, CC:, BCC: fields see the Item as Inbound (does not
include lists)
+ If you are in the FROM: field as well as one of the recipient fields, TO:,
CC:, BCC:, From: wins.
+ However, if you are not in the FROM: field, but you are in the Sent by:
field and you are one of the recipient fields, the recipient field wins.

Use cases:
+ Esther sends out an invitation to the OSAF Board on Mitch's behalf. The
invitation is From: Mitch, Sent by: Esther.
--Both Mitch and Esther see the Item as Outbound.
--Both Mitch and Esther see TO OSAF Board in the Who column.

+ Mimi sends a Task on Sheila's behalf to herself to update the splashscreen
for alpha2. The task is in a shared PPD collection.
--Sheila sees the Communication as an Outbound task, TO Mimi
--Mimi sees the Communication as an Inbound task, FROM Sheila

+ Priscilla sends a task to herself, so that she will see it in her Email
client as well. She is in the FROM: field, TO: field and Sent by: field.
--Priscilla sees the task as an Outbound Communication. Priscilla sees TO
Priscilla in the Who column.

=====
If you are not mentioned in any of the addressing fields,
+ You see the Item as neither Inbound, nor Outbound
+ The Who column displays both FR and TO

Use cases:
+ c.d. sends out an invitation to the wholeoffice for the summer picnic and
CC:s Esther.
--c.d. sees the invitations as Outbound. The Who column displays: TO:
wholeoffice, CC; Esther.
--Esther sees the invitation as Inbound. The Who column displays: FR c.d.
evans
--Everyone on the wholeoffice list sees the invitation as neither Inbound
nor Outbound. The Who column displays FR: c.d. Explained in next section.

+ c.d. adds an email to the OSAF Office collection that was sent to her from
the 543 front desk, asking staff to please pre-register visitors, to the
shared OSAF Office collection.
--Staff subscribing to the OSAF Office collection sees the Communication as
neither Inbound nor Outbound.
---Staff see FR 543 front desk: TO c.d. in the Who column

+ c.d. edits the Addressing fields to Send a capital-Notification to staff
about pre-registration and Addresses the Item TO: Staff, CC: c.d.
--Staff see the Communication as neither Inbound nor Outbound because it was
sent to a list/alias.
--However, Esther sees the Communication as Inbound, because she is
enumerated as a recipient.

+ Esther sends an update to Sheila about syncing problems she's been having
on the office calendar. Mitch sees the Communications as neither Inbound nor
Outbound. Mitch sees FR Esther: TO Sheila in the Who column

=====
If a Communication Item has only been created, but not sent
=====
+ All the rules above apply, except you see the Item either as an Outbound
Draft or an Inbound Draft; which means
+ We need to create a status for Drafts of Inbound Communications

=====
For subsequent Updates to Communication Items
=====
=====
If you are mentioned in any of the addressing fields, i.e. From:, To:, CC:,
BCC:, Sent by:
+ Then you see the Item from the perspective of where you appear, IN
RELATION TO THE UPDATE. Did you sent the Update? Or did you receive the
Update?
+ People in the From: and To:, CC:, BCC: fields see the Item as an Inbound
Update and who it was UP(dated by) in the Who column
+ The person who Updated the Item sees the Item as an Oubound Update and the
TO recipients of the Item in the Who column
+ If you Updated the Item and you are in one or more of the Addressing
fields, Updated by: wins

+ If you are not specifically enumerated in any of the Addressing fields and
you neither sent the original Communication, nor sent a subsequent Update,
you see the Item as neither Inbound nor Outbound. However you do see who
UP(dated) the Item in the Who column.

Use cases
+ Brian Kirsch edits c.d.'s invitation to the summer picnic saying he's
bringing a pineapple for everyone from Hawaii.
--Brian Kirsch sees the Item as an Outbound Update TO wholeoffice.
--c.d. sees the Item as an Inbound Update, UP(dated by) Brian Kirsch.
--Everyone on the wholeoffice list sees the Item as neither Inbound nor
Outbound, but they do see that the Item has been UP(dated by) Brian Kirsch.

+ Esther updates the invitation she sent out to the OSAF Board on Mitch's
behalf.
--Esther sees the Update as an Outbound Update TO OSAF Board.
--Mitch sees it as an Inbound Update UP(dated by) Esther.

=====
If a Communication Item has been edited, but not sent as an Update
=====
+ All the rules above apply, except you see the Item either as an Outbound
Draft Update or an Inbound Draft Update

=====
For non-Communication Items
+ You see the item as neither Inbound, nor Outbound
+ If the Item is shared, the Who column displays CR (Created by) and ED
(Edited by)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20060602/bbfd9d30/attachment.htm