Am 16.09.2008 um 14:49 schrieb Joen: > 1. All saved lists are public to everyone -- I suspect most of my > users would prefer to keep their collections private.
It's supposed to be used in wikis like Wikipedia where content is meant to be used by everyone. I understand that your use case with real-life comic book collections is a bit different, of course. > 2. The loading and saving of lists is a bit cumbersome, usability > wise. Who owns a list, how is it saved, why isn't it automatically > loaded when I log in? For once: A user can have lots of saved collections and might want to load different ones. There's one collection which is currently "active" (as in actively being edited), but this collection is only referenced in a cookie. Regarding the usability, there's potentially room for improvements in the future. > In the first case, I would guess that users using the list function on > pediapress and even Wikipedia when that happens (I've heard rumors > that this'll make it on to Wikipedia, congrats), would also like to be > able to keep lists private. That's also why I've added private lists > as a feature request on the wishlist (http://www.mediawiki.org/wiki/ > Extension:Collection/Wishlist). As I already noted in another mail: I think it's quite difficult to achieve this kind of access control with plain wiki pages. Not being listed in Category:Collections doesn't mean a collection is private (and as noted below, currently the category is needed). But if there's demand for such a feature, we (this includes the community :) have to think about how to implement it. > - a user wants to make a list of psychology related documents to be > printed for some background reading > - because this is a personal list of psychology material related to a > specific class the user is taking, the user doesn't expect anyone else > to want to see the list and expects any list he makes to be private > - the user registeres an account on the Wiki, surfs around and clicks > "add page" on a number of articles, and then proceeds to sort them > - the user orders the final list as a book on pediapress, and then > logs out > > In the above usecase, there is no need to save a list, and there's no > need to make the list public at all. There's no need to save a collection in order to download a PDF or get a printed book if this is what you mean. (Maybe I didn't really get the use case though :) > Actually hiding the list behind a > password might not be needed, but automatically categorizing the list > should be an option, not automatic. For now, this category is the only criteria to "detect" that the current page is a collection page. If we get a specific namespace or something like that, we could make the categorizing optional. > As for the saving -- I realize it > simply saves it as a wiki page, but in my mind the intuitive thing is > for the list to be auto-loaded when a user logs in to his/her account. The active collection -- which is stored in the session (referenced by your browser cookie) -- is "reloaded" when you come back. We *could* bind that somehow to the logged-in user, but I don't know if we really want to do that: it complicates things for the majority of users of a wiki, which usually doesn't require logins. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mwlib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mwlib?hl=en -~----------~----~----~----~------~----~------~--~---
