[chandler-users] [d/f] Assorted Usage Notes

[Mimi Yin]

Hi Andre,

The Update button is meant to actively ping both Chandler and non- 
Chandler users when you've made significant changes.

Both Chandler and non-Chandler users receive the Update in their email.
Chandler subscribers see the updated item pop to the top of the NOW  
section.

The original intent was that only Chandler subscribers listed in the  
Addressing fields would see the updated item pop to the top of their  
NOW section. However, we decided to punt that behavior for Preview.  
So right now,

1. All subscribers see Updates, even if they're not listed in the  
Addressing fields.
2. Both edited and updated items pop to the to top of the NOW section  
for subscribers.

As a result, for Preview, there's not really a big difference for  
other subscribers. But the intent is to provide a way for people to  
either make 'silent' edits that don't alert subscribers versus  
broadcast 'Updates' that go to both non-Chandler users and actively  
alert Chandler subscribers.

Does that make more sense?

I imagine you will not be the only one who is misled by the Update  
button, so this is good information to come by now. I will add this  
to the list of things we should endeavor to explain in the release  
notes.


Mimi

On Jun 25, 2007, at 2:42 PM, Andre Mueninghoff wrote:

> I like that better, 'Notify'. However, in the user behavior  
> department,
> I'm realizing that I have been clicking the Update button in part,
> because it appears at all. Changing the label to Notify may not reduce
> that initial impulse. Even though I trust the sync to Cosmo/Hub,
> clicking the Update button evokes Done or Commit. Is Update/Notify
> perhaps really intended for propagating changes to non-Chandler users?
> If so, maybe the label or tool-tip could clarify/amplify that intended
> purpose. If I'm missing the point, I apologize. Wanted to give you my
> candid impulse response without peeking first at the spec.
>
> Please let me know if you have any questions.
> Thanks, Andre
>
>
> Mimi Yin wrote:
>> Hi Andre,
>>
>> Currently, if you don't hit Update, your changes are sent to the  
>> server
>> and all subscribers will see them without receiving an email. Perhaps
>> renaming Update to something like 'Notify' would make that clearer?
>>
>> Mimi
>>
>> On Jun 22, 2007, at 8:45 PM, Andre Mueninghoff wrote:
>>
>>> - It seems to me there would be value in a counterpart to the "Apply
>>> Changes" functionality, that is, a "Send Changes" function that  
>>> would
>>> permit the selective sending of field-level changes, or minimally, a
>>> Don't Send Updates option at the item level. (I think this may well
>>> have been covered in the specs and on the lists, but I have not read
>>> all of the traffic, so sending this anyway.)
>>
>