SMW notes: Difference between revisions
→Hiding set data
| Line 92: | Line 92: | ||
<nowiki>{{#arraymap:{{{Eating disorders behaviors|}}}|,|x|[[Eating disorders behaviors::x|]]}}</nowiki> | <nowiki>{{#arraymap:{{{Eating disorders behaviors|}}}|,|x|[[Eating disorders behaviors::x|]]}}</nowiki> | ||
(why not just use #set?) | |||
=== Protecting #ask results === | |||
(from Markus Kr?tzsch) | |||
* make a new property "has checked" of type page, | |||
* make and a new page "main page news editor" (or whatever) and protect this | |||
page just like your main page, | |||
* add an entry <nowiki>[[has checked::some page]]</nowiki> on "main page news editor" for every | |||
page that the editor has found to be okay to make it on the main page news | |||
feed, | |||
* extend your #ask query on the main page with the condition <nowiki>[[-has | |||
checked::main page news editor]]</nowiki>. | |||
... Note that you can also have a group of editors with separate (protected) | |||
pages. You can also work with categories of editors for different topics etc. | |||
Of course, this is no longer a spam protection since categories are not | |||
protected either, but you can use another level of "has checked" to have a | |||
master editor who checks other editors to grant them trust. All of this | |||
readily works with subqueries+inverses. Applying similar methods but without | |||
actually protecting any pages maybe still be useful for managing feeds | |||
together in cases where spam is not a major issue. | |||
== Misc == | == Misc == | ||