Group libraries in client: four simple UI suggestions for improvement
1. All group libraries are expanded by default in the client. No idea why; all collapsed seems to be a better default option.
Proposal: all group libraries collapsed (but visible under the main node) by default, unless a different state has been saved (see #3) in which case use that state.
2. What makes #1 worse is that there is no easy way to collapse all group libraries at once. Using the left arrow key multiple times in the end collapses all groups under the main node "Group libraries", but if you then use the right arrow to expand one level (expecting it to work like the collections in My Library), everything's expanded again!
Proposal: make this work as the Collections work (and as most file managers in general work)
3. It would be much nicer if the client would remember the collapsed/expanded state of group libraries. One reason is that if I'm a member of ten groups and I work with one, I don't want to scroll don the whole list in search of that one. Another reason is the issues with expanding/collapsing part of the tree mentioned above.
Proposal: remember the state of the tree across sessions in the client.
4. Ordering. There is no visible principle according to which groups are sorted currently. It appears to be the order in which they were added, which makes very little sense to the user. Of course alphabetic ordering would also make little sense.
Proposal: make reordering (by dragging) possible.
Proposal: all group libraries collapsed (but visible under the main node) by default, unless a different state has been saved (see #3) in which case use that state.
2. What makes #1 worse is that there is no easy way to collapse all group libraries at once. Using the left arrow key multiple times in the end collapses all groups under the main node "Group libraries", but if you then use the right arrow to expand one level (expecting it to work like the collections in My Library), everything's expanded again!
Proposal: make this work as the Collections work (and as most file managers in general work)
3. It would be much nicer if the client would remember the collapsed/expanded state of group libraries. One reason is that if I'm a member of ten groups and I work with one, I don't want to scroll don the whole list in search of that one. Another reason is the issues with expanding/collapsing part of the tree mentioned above.
Proposal: remember the state of the tree across sessions in the client.
4. Ordering. There is no visible principle according to which groups are sorted currently. It appears to be the order in which they were added, which makes very little sense to the user. Of course alphabetic ordering would also make little sense.
Proposal: make reordering (by dragging) possible.
This discussion has been closed.
So I would amend my proposal #3 as follows: remember the state of the tree during sessions and across sessions in the client.
https://www.zotero.org/trac/changeset/9950
Still, manual reordering would be preferable I think. But alphabetic ordering a good start.