[Design] Do we want to be able to annotate read-only items?

[Mimi Yin]

I guess conceptually, if we allow users to add read-only items to  
different collections, which in turn "label" the items  
accordingly...then what is the difference between adding a read-only  
item to a ToRead collection in the sidebar versus:

Stamping a read-only item to show up on My Task list.

Mimi

On Apr 13, 2006, at 2:22 PM, Pieter Hartsook wrote:

> Read Only should be a status of what you're allowing others to do to
> your published information. However, If I can see something locally, I
> should be able to annotate (add information for my own personal use)
> to any item. Conceptually, I wouldn't mind if the annotations were a
> separate item that was linked to the original, as long as I am able to
> view both the original and my annotations simultaneously (different
> frames, or as overlays). Think of the UI for annotations (Postit
> Notes) in Excel for example. A Postit Note is a separate item that
> gains value by being attached to another item.
>
> Pieter
>
> On 4/13/06, Mimi Yin <mimi at osafoundation.org> wrote:
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=4729
>>
>> Right now, read-only items are non-editable for read-only sharees.
>> Do we want to be able to allow users to edit read-only items as
>> private annotations (aka outside of the sharing cloud).
>>
>> What are some use cases for this?
>>
>> e.g.
>> Private meeting notes
>> Stamp something as a Task to read and review later
>> Add more details to the Location field (address, link to a map
>> online, etc)
>>
>> Mimi
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "Design" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/design
>>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design