From: Yaron K. <ya...@gm...> - 2010-04-21 14:21:21
|
Well, opinion definitely seems mixed on this issue... Remco - having SMW be able to query more than one version would be nice, but is probably a long way off - that was actually the main subject of the original FlaggedRevs discussion. Robert - it's good to know that FlaggedRevs has in fact been used successfully. The documentation does seem a little weak, but I don't know if that's the main issue: even with good documentation, you still have database modifications, extra user groups, etc. In my view, the problem is that the creators of FlaggedRevs decided to support not just version "validation", but also version comments and reviews. Version validation seems to be very useful and fairly simple to implement, while comments and reviews seem only marginally useful and complex to implement. It's possible that if they had split up the functionality into two different extensions, none of this would be an issue. Neill - Ah, so your system involves creating a separate wiki page, making all the changes there, then copying the approved contents back. That would work, but it seems quite a bit more complicated than simply being able to approve a certain version of the page; and it might not be practical for any wiki that has more than, say, 10 people working on it. Hala - It's nice to see that DSMW finally has a demo; it looks interesting. For this case, what you describe as a "public wiki" sounds like it would be publicly-readable, but only editable by a few administrators. It's certainly a possible solution, but it doesn't seem ideal for this case. -Yaron On Wed, Apr 21, 2010 at 6:36 AM, Hala Skaf <sk...@lo...> wrote: > Hi Yaron, > > You can realize the scenario you mention by using our extension DSMW > (Distributed Semantic MediaWiki http://dsmw.org) of Semantic MediaWiki. > DSMW allows to deploy the validation processes as follows > > You need two SMW called SMW1 and SMW2 installed with the DSMW extension. > > Let say SMW1 is a public wiki, so it contains only validated data. SMW1 is > a private one, it contains data that need to be validated. > After the validation of data at SMW1 by an administrator for example, > validated data can be pushed to SMW1... > > I am not sure it is easier than FlaggedRevs extension but it is a possible > solution.. > > > Best wishes, > > > On Tue, Apr 20, 2010 at 6:29 PM, Yaron Koren <ya...@gm...> wrote: > >> Hi everyone, >> >> I sent an email about two months ago [1] to the SMW developers mailing >> list >> about having SMW work with the FlaggedRevs extension. [2] FlaggedRevs, for >> those who don't know about it, lets administrators "validate" certain >> versions of an article as being of high quality - and then when regular >> users see that page on the wiki, what they'll see is the latest validated >> version, not necessarily the latest version. The idea was to have SMW, if >> FlaggedRevs is installed, save data not when a page is saved, but when >> it's >> validated - so that queries will only display data that's been approved. >> It's a straightforward way to do quality control on one's data. >> >> It seemed like a good idea, and that was the general consensus of the >> discussion on the mailing list. However, afterwards, when I actually went >> to >> try to install FlaggedRevs on one of my wikis, I realized that the >> extension >> is quite complex. The main issue seems to be that it allows for comments >> and >> "reviews" of each page, in addition to the validation. To that end, it >> requires additions to the database; it allows for an arbitrary set of >> attributes for each page (like 'accuracy' and 'tone'), each with an >> arbitrary number of levels; it defines four new user rights and three new >> user groups; and it defines a bunch of new special pages. Since then I've >> gone back a few times to that documentation, but I haven't been able to >> bring myself to actually try installing it - it just seems too complex. >> The >> one positive aspect of it is that I think now I understand better the >> total >> confusion that some people feel when they first see SMW (or sometimes >> Semantic Forms, for that matter :) ). >> >> My sense is that there has to be a much simpler way to do this. >> FlaggedRevs >> is clearly an "industrial-strength" solution, appropriate for use on >> Wikipedia and other major sites. But for smaller-scale wikis, a much >> simpler >> extension might be the better option. Really such an extension only needs >> to >> accomplish three things: >> >> 1) provide a way for administrators to set one version of a page as >> "stable". >> 2) display the stable version of a page for normal users when they view it >> through its main URL. >> 3) provide a hook for SMW to use. :) >> >> I don't know if it makes sense to create a new extension just for this >> functionality, or if so, who can/should create it, but I wanted to "throw >> the idea out there". Though - has anyone successfully installed and/or >> used >> FlaggedRevs on their wiki? Is it more usable than it looks? >> >> [1] >> >> http://www.mail-archive.com/sem...@li.../msg01882.html >> [2] http://www.mediawiki.org/wiki/Extension:FlaggedRevs >> >> -Yaron >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > > > > -- > Hala Skaf-Molli > Maître de Conférences > Université Henri Poincaré, Nancy1 > LORIA > INRIA Nancy-Grand Est > www.loria.fr/~skaf > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |