* not only: annotations that were aimed at the group
* also: annotations that are public (of which the group is a member :)
The logic here is that an author should not have to write something twice (once for the public, once for the group) if he/she wishes it to be seen by a group.
Please, is there another logic?
(I wonder, has experience shown that group views of public annotations can become cluttered?)
> The logic here is that an author should not have to write something > twice (once for the public, once for the group) if he/she wishes it > to be seen by a group
… and the author should not have to write something (one thing) publicly three times for it to be seen by two public groups
… and so on, for however many groups have bookmarked that page.
There's a tension here: the _more popular_ a page becomes, the _more likely_ it is to be bookmarked by multiple groups, but the social (Diigo) aspect of publicly sharing with groups becomes _less easy_ .
a. I share a page with two groups, both of which are public. I am the first person to do so.
b. Later, to the bookmark, I add a tag and a public comment.
c. The intention of the public comment is for the note to be seen by all individuals and groups who might be interested in the page.
d. Later, I realise that neither group is aware of my tag; neither group is aware of my comment.
In the test/example above (which I am not referencing) I worked with just two groups.
In _reality_ I work with many more groups. A public view currently totals fifteen projects for my own centre, and to that number I add project proposals (few of which are expressed publicly), then to that greater number I add the collaborative projects/proposals of the second centre with which our building is shared. Across these mixes I add group tag dictionaries, which include (are not limited to) the six themes expressed by our centre plus the four areas expressed by one of the two universities. Et cetera.
We can't have a single group for the entire building (with scores of projects and scores of dictionary entries) _and_ expect tagging or other current Diigo mechanisms to keep group noise to a reasonable level. Some separation of groups is logical, desirable.
Assuming six themes for each centre within the building, maybe twelve Diigo groups.
Next: I share a page with seven of the groups. (Knowing what our themes are, will be, this multiple is realistic.)
A month or so later, I have some thoughts and express them publicly.
I wish to:
* express myself once (not eight times) * certainly, not unwittingly lose the tags that the many members of the seven groups have applied.
PS I do have thoughts (more workflow/brainstorm related, less software UI related) on how my groups' use cases may be catered for, but I'll not inflict them on Diigo Community until more of what's under the hood of Diigo is understood.
Some graphical representations should certainly minimise the risk of losses such as the one in comment #3 above, but I'm not pushing Diigo. I see them busy with *nice* things :)
PPS my face looks less than happy in that cartoon. I'm not quite that bad in real life, and I do have a life beyond bug reporting. Ha ha. Time for me to update my profile :))
> At (for example) http://groups.diigo.com/Diigo_HQ/bookmark when I click > 'Expand All' I expect to see > > * not only: annotations that were aimed at the group > > * also: annotations that are public (of which the group is a > member :) > > The logic here is that an author should not have to write > something twice (once for the public, once for the group) if > he/she wishes it to be seen by a group.
At (for example) http://groups.diigo.com/Diigo_HQ/bookmark when I click 'Expand All' I expect to see
* not only: annotations that were aimed at the group
* also: annotations that are public (of which the group is a member :)
The logic here is that an author should not have to write something twice (once for the public, once for the group) if he/she wishes it to be seen by a group.
Please, is there another logic?
(I wonder, has experience shown that group views of public annotations can become cluttered?)
Best regards
Graham
Postscript: completed my unfinished sentences
> twice (once for the public, once for the group) if he/she wishes it
> to be seen by a group
… and the author should not have to write something (one thing) publicly three times for it to be seen by two public groups
… and so on, for however many groups have bookmarked that page.
There's a tension here: the _more popular_ a page becomes, the _more likely_ it is to be bookmarked by multiple groups, but the social (Diigo) aspect of publicly sharing with groups becomes _less easy_ .
= Example 1 =
Neither
http://groups.diigo.com/search?group_name=Web2&what=280slides.com
nor
http://groups.diigo.com/search?group_name=web2tools&what=280slides.com
see the public comment that I have made at
http://about.diigo.com/about/http%3A%2F%2F280slides.com%2F
1. edit my bookmark for 280slides.com
2. overtype 'no_tag'
3. enter two tags
4. share to one group
5. share to another group
= Problem =
The groups' views have lost the tags of the people who previously shared the page
- designdivide and LouCypher (Zoolcar9) sorry; I really didn't imagine this loss!
With reference to http://groups.diigo.com/Diigo_HQ/forum/topic/diigo-expressions-share-to-and-add-to-are-debatably-misleading-the-actual-results-are-more-like-duplicate-triplicate-8754#4
a. I share a page with two groups, both of which are public. I am the first person to do so.
b. Later, to the bookmark, I add a tag and a public comment.
c. The intention of the public comment is for the note to be seen by all individuals and groups who might be interested in the page.
d. Later, I realise that neither group is aware of my tag; neither group is aware of my comment.
In the test/example above (which I am not referencing) I worked with just two groups.
In _reality_ I work with many more groups. A public view currently totals fifteen projects for my own centre, and to that number I add project proposals (few of which are expressed publicly), then to that greater number I add the collaborative projects/proposals of the second centre with which our building is shared. Across these mixes I add group tag dictionaries, which include (are not limited to) the six themes expressed by our centre plus the four areas expressed by one of the two universities. Et cetera.
We can't have a single group for the entire building (with scores of projects and scores of dictionary entries) _and_ expect tagging or other current Diigo mechanisms to keep group noise to a reasonable level. Some separation of groups is logical, desirable.
Assuming six themes for each centre within the building, maybe twelve Diigo groups.
Next: I share a page with seven of the groups. (Knowing what our themes are, will be, this multiple is realistic.)
A month or so later, I have some thoughts and express them publicly.
I wish to:
* express myself once (not eight times)
* certainly, not unwittingly lose the tags that the many members of the seven groups have applied.
Some graphical representations should certainly minimise the risk of losses such as the one in comment #3 above, but I'm not pushing Diigo. I see them busy with *nice* things :)
PPS my face looks less than happy in that cartoon. I'm not quite that bad in real life, and I do have a life beyond bug reporting. Ha ha. Time for me to update my profile :))
> At (for example) http://groups.diigo.com/Diigo_HQ/bookmark when I click
> 'Expand All' I expect to see
>
> * not only: annotations that were aimed at the group
>
> * also: annotations that are public (of which the group is a
> member :)
>
> The logic here is that an author should not have to write
> something twice (once for the public, once for the group) if
> he/she wishes it to be seen by a group.
Note to self: review this topic alongside
workflow: all annotations: public, private and group comments and notes
Group meta views include public comments.
Hindrance
The route from your groups to Diigo Meta is given only after you sign out from Diigo.
Considerations
Care to not confuse the viewer with a mixture of group + public content, especially if the group is private.