Hi Anca, Pardon me if it's already on your roadmap (there isn't one published yet, right?): * As far as I understand, the groups are used to categorize the feeds input & listing. I'd like to see something like 'favorites' or 'workbook', where a user would store an article (or even own documents) he did find interesting from the feed listing or on the web. Beside keeping your personal things together, it might be interesting to see what other people are interested in. Maybe you could realize that as an extension to the user space/profile. * Feeds are not working if the website itself needs authentication (I guess that's a really hard one or indeed unsolveable) * The search field needs a click on the 'OK'-button, 'Enter' is not working If it's not already on your roadmap and you can use the input, I'd be happy to create JIRA's. Cheers, Squirrel PS: I like this 'Watch' more and more...has a lot of potential...especially in bigger projects... On Sun, Jun 29, 2008 at 5:09 AM, <[email protected]> wrote:

...

Hi,

First time I tried 'XWiki Watch' (standalone JAR). I like the idea very much.

Hi Squirrel,

thanks for your interest in XWiki Watch.

...

Is it planned to support manual added pages too? The use-case would be,

if

...

someone finds a specific article, which other team members could maybe use too. So instead adding the whole RSS (if even one is available) you would just add the specific link to the article and comment it, group it, tag and flag it...

Yes, we have this idea too and it's in the features list for the next versions, along with other content improvement methods.

...

Cheers, Squirrel

PS: Could you maybe add a link to the actual Watch space, too (on the first page of the installation and on the sidebar)?

Will do.

Happy coding, Anca Luca

...

I tried the whole time to click at the 'Watch' menu entry at the top, but this isn't 'XWiki Watch' but the default watch from XWiki, I figured...*g* _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

On Sun, Jun 29, 2008 at 5:15 PM, Guillaume Lerouge <[email protected]> wrote: Hi Guillaume,

* As far as I understand, the groups are used to categorize the feeds input

...

& listing. I'd like to see something like 'favorites' or 'workbook', where a user would store an article (or even own documents) he did find interesting from the feed listing or on the web. Beside keeping your personal things together, it might be interesting to see what other people are interested in. Maybe you could realize that as an extension to the user space/profile.

The "star" option already lets you mark the articles you really like... If an user wants to keep some specific articles to himself, he can also go to that article page on the wiki (they're hard to find right now, but give a look at the what's new page of your wiki and you'll see what I mean) and use the watch feature (that is, the bookmark / favorite one) to keep track of the article for himself.

The reason we're having the same star applying to everyone right now into the reader is that they're supposed to reflect the community's collective wisdom over a number of articles. The collaborative part of the reader means that everyone gets to see the same content : boring articles can be deleted by one person, meaning that other people won't have to even skim through them while starred ones can be exported for others to enjoy.

But overall XWatch is meant as a collaboration tool, which is why most stuff is shared between all the users instead of having individual, personal watchlists. There are 2 populations meant to use the tool though :

- Information filterers : they read the article, flag and delete them, tag them... - Informaiton consumers : they can subscribe to the Press Review for a specific tag for instance

Ok, thanks for your detailed answer. I guess I can follow the idea. I didn't mean to replace the current functionality, but to enrich it. Let's think about an IT BU within a company. Let's say 30 people. While they have a general topic in common, everybody has a special topic to follow. Different responsibilities, different technologies and so forth. So while general feed information is ok for everybody, there might be articles, which are only interesting for the DB guys or even only for the last COBOL guy, so he would take the article and 'archive' it under his user within the Watch-app. It's still there, it's still collaborative, in my opinion it's even more collaborative because it's enriched with the additional information 'who uses this information', so you would actually know too, who to ask (maybe more important in bigger teams than 30 people...but maybe other parts from the company have some BA's and they could faster target the knowing guy). So, while you 'remove' it from the general view, you add it to the user/group or special branch of the department. Or if it's not comming from the feed, but from an web article or an own ressource/file he would probably not add it to the general pot, but either to his own (or his group or special branch) 'space' or if the DB guy finds an interesting article which might interests the COBOL guy, he can pass it to him directly but nevertheless transparent to the whole community/company. Personally, this is highly valuable to me. If I know this guy reads this and this I might take a look into it (or not). It's like open-up your bookmarks plus what you're reading and this in an already filtered quality. So you have the general and the individual (+ the own added) stuff you would share with everybody...

...

* Feeds are not working if the website itself needs authentication (I guess that's a really hard one or indeed unsolveable)

* The search field needs a click on the 'OK'-button, 'Enter' is not working

If it's not already on your roadmap and you can use the input, I'd be happy to create JIRA's.

Please do. Thanks for the kind words as well :-)

Guillaume

I'll do that, but probably tomorrow... Cheers, Squirrel