From: Jani P. <jpa...@ik...> - 2009-11-18 04:40:25
|
Greetings, So I've got a large bunch of SMW pages tagged with [[Place::X]], and it's common that multiple pages have the same Place tag. It's easy enough to get a list of all places... {{#ask: [[Place:+]] | mainlabel=- | ? Place | sort = Place | format = broadtable }} ...but how do I get a listing of _unique_ Places, without duplication? Cheers, -j. |
From: Dan B. <dan...@gm...> - 2009-11-18 11:00:10
|
2009/11/18 Jani Patokallio <jpa...@ik...>: > Greetings, > > So I've got a large bunch of SMW pages tagged with [[Place::X]], and it's > common that multiple pages have the same Place tag. It's easy enough to > get a list of all places... > > {{#ask: [[Place:+]] > | mainlabel=- > | ? Place > | sort = Place > | format = broadtable > }} > > ...but how do I get a listing of _unique_ Places, without duplication? Good question! If SMW had a FAQ, I bet that would be one! It would be convenient if SRF had a 'unique' results format, but in any case you can use sask to get the unique list: http://www.mediawiki.org/wiki/Extension:SemanticQueryFormTool I think the query you want is as simple as {{#sask: ?Place}}, but I haven't played with sask yet... What I really miss is the equivalent of "SELECT Place, COUNT(*) FROM bunch GROUP BY Place"... does anyone know if sask supports that? Cheers, Dan. > > Cheers, > -j. > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Günther Z. <zeh...@mo...> - 2009-11-18 11:51:43
|
Hi, > > ...but how do I get a listing of _unique_ Places, > without duplication? I don't think SQFT can do this yet (although it might be easy to implement as filter) although it might already be possible with the below mentioned addfrequency parameter and a filter - I'll have to check if the frequencies are added before or after the filtering is done. > I think the query you want is as simple as {{#sask: > ?Place}}, but I haven't played with sask yet... In principle yes but that would return the default dropdown form element and if you want the result in a different format the 'return' parameter (and maybe others) have to be added to specify the desired format. > What I really miss is the equivalent of "SELECT Place, > COUNT(*) FROM bunch GROUP BY Place"... does anyone know > if sask supports that? The sad point is that I had to look it up myself on the doc page as I haven't had much time to do anything with the SQFT extension in the last months. The good news is that I actually did implement 'frequency' parameters when I added the google statistics which should be doing what you want: * addfrequency = (determines frequency of each property value and displays it with the result) * addfrequencypercent = (determines frequency of each property value and displays frequency percentage with the result) o if no value is given, the frequency number is shown in brackets after the property value (this default display can be changed by setting the global variable $sqftgFrequencyString). o if a value is given, it is used for the display of the frequency number ('$$$' can be used as placeholder for the number in the display string) o frequency mode is automatically switched on with special return formats (googlepie, googlepiepercent, googlebar, googlebarpercent) I even did make a special example page for these parameters: http://mbw.molgen.mpg.de/wiki/Help:Sask/Frequency_examples Cheers, Gu --- On Wed, 11/18/09, Dan Bolser <dan...@gm...> wrote: > From: Dan Bolser <dan...@gm...> > Subject: Re: [Semediawiki-user] Removing duplicate properties from search > To: "Jani Patokallio" <jpa...@ik...> > Cc: sem...@li... > Date: Wednesday, November 18, 2009, 11:59 AM > 2009/11/18 Jani Patokallio <jpa...@ik...>: > > Greetings, > > > > So I've got a large bunch of SMW pages tagged with > [[Place::X]], and it's > > common that multiple pages have the same Place tag. > It's easy enough to > > get a list of all places... > > > > {{#ask: [[Place:+]] > > | mainlabel=- > > | ? Place > > | sort = Place > > | format = broadtable > > }} > > > > ...but how do I get a listing of _unique_ Places, > without duplication? > > Good question! If SMW had a FAQ, I bet that would be one! > > It would be convenient if SRF had a 'unique' results > format, but in > any case you can use sask to get the unique list: > > http://www.mediawiki.org/wiki/Extension:SemanticQueryFormTool > > > I think the query you want is as simple as {{#sask: > ?Place}}, but I > haven't played with sask yet... > > What I really miss is the equivalent of "SELECT Place, > COUNT(*) FROM > bunch GROUP BY Place"... does anyone know if sask supports > that? > > Cheers, > Dan. > > > > > > Cheers, > > -j. > > > > > > > > > ------------------------------------------------------------------------------ > > Let Crystal Reports handle the reporting - Free > Crystal Reports 2008 30-Day > > trial. Simplify your report design, integration and > deployment - and focus on > > what you do best, core application coding. Discover > what's new with > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal > Reports 2008 30-Day > trial. Simplify your report design, integration and > deployment - and focus on > what you do best, core application coding. Discover what's > new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Günther Z. <zeh...@mo...> - 2009-11-18 12:39:00
|
Hi, well it works to combine a simple filter with the addfrequency parameters to select only those values which occur once (or any specific number of times): {{#sask: ?Chromosome Name | return=ol | addfrequency=}} gives 1. X (2188) 2. UNKN (1036) 3. 3R (5158) 4. 3L (4236) 5. 2R (7164) 6. 2L (6108) ---- {{#sask: ?Chromosome Name | return=ol | addfrequency=|filter=(2188)}} gives: 1. X (2188) so using 'filter=(1)' should show only unique values. (the filter could be made specific by using a value for the addfilter parameter and changing the filter text accordingly, if the default way should clash with the property values) Cheers, Gu BTW I'll upload a new version of SQFT very soon as I have in the meantime sorted out some more bugs. --- On Wed, 11/18/09, Günther Zehetner <zeh...@mo...> wrote: > From: Günther Zehetner <zeh...@mo...> > Subject: Re: [Semediawiki-user] Removing duplicate properties from search > To: "Jani Patokallio" <jpa...@ik...>, "Dan Bolser" <dan...@gm...> > Cc: sem...@li... > Date: Wednesday, November 18, 2009, 12:51 PM > Hi, > > > > ...but how do I get a listing of _unique_ > Places, > > without duplication? > > I don't think SQFT can do this yet (although it might be > easy to implement as filter) although it might already be > possible with the below mentioned addfrequency parameter and > a filter - I'll have to check if the frequencies are added > before or after the filtering is done. > > > I think the query you want is as simple as {{#sask: > > ?Place}}, but I haven't played with sask yet... > > In principle yes but that would return the default dropdown > form element and if you want the result in a different > format the 'return' parameter (and maybe others) have to be > added to specify the desired format. > > > What I really miss is the equivalent of "SELECT > Place, > > COUNT(*) FROM bunch GROUP BY Place"... does anyone > know > > if sask supports that? > > The sad point is that I had to look it up myself on the doc > page as I haven't had much time to do anything with the SQFT > extension in the last months. > > The good news is that I actually did implement 'frequency' > parameters when I added the google statistics which should > be doing what you want: > > * addfrequency = (determines frequency of each > property value and displays it with the result) > * addfrequencypercent = (determines frequency of each > property value and displays frequency percentage with the > result) > o if no value is given, the frequency number is shown in > brackets after the property value (this default display can > be changed by setting the global variable > $sqftgFrequencyString). > o if a value is given, it is used for the display of the > frequency number ('$$$' can be used as placeholder for the > number in the display string) > o frequency mode is automatically switched on with special > return formats (googlepie, googlepiepercent, googlebar, > googlebarpercent) > > I even did make a special example page for these > parameters: > http://mbw.molgen.mpg.de/wiki/Help:Sask/Frequency_examples > > Cheers, > Gu > > --- On Wed, 11/18/09, Dan Bolser <dan...@gm...> > wrote: > > > From: Dan Bolser <dan...@gm...> > > Subject: Re: [Semediawiki-user] Removing duplicate > properties from search > > To: "Jani Patokallio" <jpa...@ik...> > > Cc: sem...@li... > > Date: Wednesday, November 18, 2009, 11:59 AM > > 2009/11/18 Jani Patokallio <jpa...@ik...>: > > > Greetings, > > > > > > So I've got a large bunch of SMW pages tagged > with > > [[Place::X]], and it's > > > common that multiple pages have the same Place > tag. > > It's easy enough to > > > get a list of all places... > > > > > > {{#ask: [[Place:+]] > > > | mainlabel=- > > > | ? Place > > > | sort = Place > > > | format = broadtable > > > }} > > > > > > ...but how do I get a listing of _unique_ > Places, > > without duplication? > > > > Good question! If SMW had a FAQ, I bet that would be > one! > > > > It would be convenient if SRF had a 'unique' results > > format, but in > > any case you can use sask to get the unique list: > > > > http://www.mediawiki.org/wiki/Extension:SemanticQueryFormTool > > > > > > I think the query you want is as simple as {{#sask: > > ?Place}}, but I > > haven't played with sask yet... > > > > What I really miss is the equivalent of "SELECT > Place, > > COUNT(*) FROM > > bunch GROUP BY Place"... does anyone know if sask > supports > > that? > > > > Cheers, > > Dan. > > > > > > > > > > Cheers, > > > -j. > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Let Crystal Reports handle the reporting - Free > > Crystal Reports 2008 30-Day > > > trial. Simplify your report design, integration > and > > deployment - and focus on > > > what you do best, core application coding. > Discover > > what's new with > > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > > _______________________________________________ > > > Semediawiki-user mailing list > > > Sem...@li... > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > ------------------------------------------------------------------------------ > > Let Crystal Reports handle the reporting - Free > Crystal > > Reports 2008 30-Day > > trial. Simplify your report design, integration and > > deployment - and focus on > > what you do best, core application coding. Discover > what's > > new with > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal > Reports 2008 30-Day > trial. Simplify your report design, integration and > deployment - and focus on > what you do best, core application coding. Discover what's > new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Günther Z. <zeh...@mo...> - 2009-11-18 13:25:44
|
Well I realised that at the moment with this method the frequency is always shown after the value. That's not good if one just wants to filter out e.g. unique values but not show the frequency. I therefore added a 'hidefrequency' parameter which allows to use the frequencies for filtering (and sorting) but removes them again before displaying. {{#sask: ?Chromosome Name | return=ol | addfrequency=|filter=(2188)|hidefrequency=}} gives: 1. X Obviously only working from next SQFT version. This sentence in my last mail: (the filter could be made specific by using a value for the addfilter parameter and changing the filter text accordingly, if the default way should clash with the property values) should of course read (the filter could be made specific by using a value for the addfrequency parameter and changing the filter text accordingly, if the default way should clash with the property values) i.e. {{#sask: ?Chromosome Name | return=ol | addfrequency=###$$$###|filter=###2188###|hidefrequency=}} Gu --- On Wed, 11/18/09, Günther Zehetner <zeh...@mo...> wrote: > From: Günther Zehetner <zeh...@mo...> > Subject: Re: [Semediawiki-user] Removing duplicate properties from search > To: "Jani Patokallio" <jpa...@ik...>, "Dan Bolser" <dan...@gm...> > Cc: sem...@li... > Date: Wednesday, November 18, 2009, 1:12 PM > Hi, > > well it works to combine a simple filter with the > addfrequency parameters to select only those values which > occur once (or any specific number of times): > > {{#sask: ?Chromosome Name | return=ol | addfrequency=}} > gives > 1. X (2188) > 2. UNKN (1036) > 3. 3R (5158) > 4. 3L (4236) > 5. 2R (7164) > 6. 2L (6108) > > ---- > {{#sask: ?Chromosome Name | return=ol | > addfrequency=|filter=(2188)}} > gives: > 1. X (2188) > > so using 'filter=(1)' should show only unique values. > > (the filter could be made specific by using a value for the > addfilter parameter and changing the filter text > accordingly, if the default way should clash with the > property values) > > Cheers, > Gu > > BTW I'll upload a new version of SQFT very soon as I have > in the meantime sorted out some more bugs. > > --- On Wed, 11/18/09, Günther Zehetner <zeh...@mo...> > wrote: > > > From: Günther Zehetner <zeh...@mo...> > > Subject: Re: [Semediawiki-user] Removing duplicate > properties from search > > To: "Jani Patokallio" <jpa...@ik...>, > "Dan Bolser" <dan...@gm...> > > Cc: sem...@li... > > Date: Wednesday, November 18, 2009, 12:51 PM > > Hi, > > > > > > ...but how do I get a listing of _unique_ > > Places, > > > without duplication? > > > > I don't think SQFT can do this yet (although it might > be > > easy to implement as filter) although it might already > be > > possible with the below mentioned addfrequency > parameter and > > a filter - I'll have to check if the frequencies are > added > > before or after the filtering is done. > > > > > I think the query you want is as simple as > {{#sask: > > > ?Place}}, but I haven't played with sask yet... > > > > In principle yes but that would return the default > dropdown > > form element and if you want the result in a > different > > format the 'return' parameter (and maybe others) have > to be > > added to specify the desired format. > > > > > What I really miss is the equivalent of "SELECT > > Place, > > > COUNT(*) FROM bunch GROUP BY Place"... does > anyone > > know > > > if sask supports that? > > > > The sad point is that I had to look it up myself on > the doc > > page as I haven't had much time to do anything with > the SQFT > > extension in the last months. > > > > The good news is that I actually did implement > 'frequency' > > parameters when I added the google statistics which > should > > be doing what you want: > > > > * addfrequency = (determines frequency of each > > property value and displays it with the result) > > * addfrequencypercent = (determines frequency of each > > property value and displays frequency percentage with > the > > result) > > o if no value is given, the frequency number is shown > in > > brackets after the property value (this default > display can > > be changed by setting the global variable > > $sqftgFrequencyString). > > o if a value is given, it is used for the display of > the > > frequency number ('$$$' can be used as placeholder for > the > > number in the display string) > > o frequency mode is automatically switched on with > special > > return formats (googlepie, googlepiepercent, > googlebar, > > googlebarpercent) > > > > I even did make a special example page for these > > parameters: > > http://mbw.molgen.mpg.de/wiki/Help:Sask/Frequency_examples > > > > Cheers, > > Gu > > > > --- On Wed, 11/18/09, Dan Bolser <dan...@gm...> > > wrote: > > > > > From: Dan Bolser <dan...@gm...> > > > Subject: Re: [Semediawiki-user] Removing > duplicate > > properties from search > > > To: "Jani Patokallio" <jpa...@ik...> > > > Cc: sem...@li... > > > Date: Wednesday, November 18, 2009, 11:59 AM > > > 2009/11/18 Jani Patokallio <jpa...@ik...>: > > > > Greetings, > > > > > > > > So I've got a large bunch of SMW pages > tagged > > with > > > [[Place::X]], and it's > > > > common that multiple pages have the same > Place > > tag. > > > It's easy enough to > > > > get a list of all places... > > > > > > > > {{#ask: [[Place:+]] > > > > | mainlabel=- > > > > | ? Place > > > > | sort = Place > > > > | format = broadtable > > > > }} > > > > > > > > ...but how do I get a listing of _unique_ > > Places, > > > without duplication? > > > > > > Good question! If SMW had a FAQ, I bet that would > be > > one! > > > > > > It would be convenient if SRF had a 'unique' > results > > > format, but in > > > any case you can use sask to get the unique > list: > > > > > > http://www.mediawiki.org/wiki/Extension:SemanticQueryFormTool > > > > > > > > > I think the query you want is as simple as > {{#sask: > > > ?Place}}, but I > > > haven't played with sask yet... > > > > > > What I really miss is the equivalent of "SELECT > > Place, > > > COUNT(*) FROM > > > bunch GROUP BY Place"... does anyone know if > sask > > supports > > > that? > > > > > > Cheers, > > > Dan. > > > > > > > > > > > > > > Cheers, > > > > -j. > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > Let Crystal Reports handle the reporting - > Free > > > Crystal Reports 2008 30-Day > > > > trial. Simplify your report design, > integration > > and > > > deployment - and focus on > > > > what you do best, core application coding. > > Discover > > > what's new with > > > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > > > > _______________________________________________ > > > > Semediawiki-user mailing list > > > > Sem...@li... > > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Let Crystal Reports handle the reporting - Free > > Crystal > > > Reports 2008 30-Day > > > trial. Simplify your report design, integration > and > > > deployment - and focus on > > > what you do best, core application coding. > Discover > > what's > > > new with > > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > > _______________________________________________ > > > Semediawiki-user mailing list > > > Sem...@li... > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Let Crystal Reports handle the reporting - Free > Crystal > > Reports 2008 30-Day > > trial. Simplify your report design, integration and > > deployment - and focus on > > what you do best, core application coding. Discover > what's > > new with > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal > Reports 2008 30-Day > trial. Simplify your report design, integration and > deployment - and focus on > what you do best, core application coding. Discover what's > new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Jani P. <jpa...@ik...> - 2009-11-18 15:24:24
|
Dan Bolser wrote: > Good question! If SMW had a FAQ, I bet that would be one! > I'd be delighted to add it to Help:Displaying information, but for unexplained reasons the SMW wiki doesn't appear to allow anon edits or account creation... > It would be convenient if SRF had a 'unique' results format, but in > any case you can use sask to get the unique list: > http://www.mediawiki.org/wiki/Extension:SemanticQueryFormTool > Thanks! Will take a look. > What I really miss is the equivalent of "SELECT Place, COUNT(*) FROM > bunch GROUP BY Place"... does anyone know if sask supports that? > Coincidentally enough, here's my present identi.ca status, written about 1 hr before I saw your response: <http://identi.ca/jpatokal> "jpatokal is exploring the weird world of semantic !mediawiki. screw inline #ask syntax, i want an sql parser for this sucker..." Seriously, has anyone tried building an SQL engine for SMW, perhaps even by exposing and simplifying the actual SQL used internally by SMW? Given that most SMW queries boil down to relational operators, it would seem to be very well suited to the task and would also lower the bar of entry for us developer types. Cheers, -jani |
From: Dan B. <dan...@gm...> - 2009-11-18 11:51:12
|
2009/11/18 Jani Patokallio <jpa...@ik...>: > Dan Bolser wrote: >> Good question! If SMW had a FAQ, I bet that would be one! >> > > I'd be delighted to add it to Help:Displaying information, but for > unexplained reasons the SMW wiki doesn't appear to allow anon edits or > account creation... Yeah, that needs to be fixed. Perhaps using the 'FlaggedRevs' extension will help deal with the previous issue that lead to the manual getting too many inconsistent and informal edits: http://www.mediawiki.org/wiki/Flaggedrevs >> It would be convenient if SRF had a 'unique' results format, but in >> any case you can use sask to get the unique list: >> http://www.mediawiki.org/wiki/Extension:SemanticQueryFormTool >> > > Thanks! Will take a look. > >> What I really miss is the equivalent of "SELECT Place, COUNT(*) FROM >> bunch GROUP BY Place"... does anyone know if sask supports that? >> > > Coincidentally enough, here's my present identi.ca status, written about > 1 hr before I saw your response: > <http://identi.ca/jpatokal> > "jpatokal is exploring the weird world of semantic !mediawiki. screw > inline #ask syntax, i want an sql parser for this sucker..." > > Seriously, has anyone tried building an SQL engine for SMW, perhaps even > by exposing and simplifying the actual SQL used internally by SMW? > Given that most SMW queries boil down to relational operators, it would > seem to be very well suited to the task and would also lower the bar of > entry for us developer types. Yeah, at one point I wrote up the SMW -> SQL (ish) mapping here: http://seqanswers.com/wiki/Semantic_MediaWiki/Overview I think the problem with exposing SQL is that people worry about handing over powerful (expensive) queries to the general public, however, I'm not sure if SPARQL is any 'safer' in that respect (it's just less well known). You should be able to write SPARQL queries directly here: http://seqanswers.com/wiki/Special:Ask But I don't know enough about the language to be able to tell you if grouping is supported! Dan. > Cheers, > -jani > > |
From: Franz M. <fra...@la...> - 2010-10-24 17:50:04
|
I had a similar problem: Contents of wiki: "Event"-pages with property "hasParticipant" "Person"-pages On each "Person"-page I wanted to create a list of participants who took part in the same events as the relative person without duplicates. I used the Extension SQFTlight (sask): {{#sask: [[hasParticipant::{{PAGENAME}}]] |link= |format=list |?hasParticipant }} The Output is correct, but looks a bit ugly because the blanks between first name and last name of the persons are replaced underscores. Example-Output: John_Smith, Cho_Chang and Harry_Potter -- View this message in context: http://old.nabble.com/Removing-duplicate-properties-from-search-tp26402948p30042340.html Sent from the Semantic Mediawiki - User mailing list archive at Nabble.com. |
From: Günther Z. <zeh...@mo...> - 2010-10-25 10:13:34
|
Just to clarify 'SQFTlight' is the name of the latest public version of my 'SemanaticQueryFormTool' (SQFT) extension. Its general functions are identical to the previous SQFT but SQFTlight is smaller as it contains less code only used for my own projects. Unfortunately I didn't have the time to announce that yet. Yes the underscores in internal links look quite ugly. I changed that for the next version so that in the link text the underscores are replaced by spaces (unless a parameter is given to prevent it). Gu --- On Sun, 10/24/10, Franz Meier <fra...@la...> wrote: > From: Franz Meier <fra...@la...> > Subject: Re: [Semediawiki-user] Re moving duplicate properties from search > To: sem...@li... > Date: Sunday, October 24, 2010, 7:49 PM > > I had a similar problem: > > > Contents of wiki: > > "Event"-pages with property "hasParticipant" > "Person"-pages > > On each "Person"-page I wanted to create a list of > participants who took > part in the same events as the relative person without > duplicates. > > > I used the Extension SQFTlight (sask): > > {{#sask: [[hasParticipant::{{PAGENAME}}]] > |link= > |format=list > |?hasParticipant > }} > > The Output is correct, but looks a bit ugly because the > blanks between first > name and last name of the persons are replaced > underscores. > > Example-Output: John_Smith, Cho_Chang and Harry_Potter > -- > View this message in context: http://old.nabble.com/Removing-duplicate-properties-from-search-tp26402948p30042340.html > Sent from the Semantic Mediawiki - User mailing list > archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Nokia and AT&T present the 2010 Calling All > Innovators-North America contest > Create new apps & games for the Nokia N8 for consumers > in U.S. and Canada > $10 million total in prizes - $4M cash, 500 devices, nearly > $6M in marketing > Develop with Nokia Qt SDK, Web Runtime, or Java and Publish > to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Franz M. <fra...@la...> - 2010-11-21 12:23:38
|
Franz Meier wrote: > > Contents of wiki: > > "Event"-pages with property "hasParticipant" > "Person"-pages > > On each "Person"-page I wanted to create a list of participants who took > part in the same events as the relative person without duplicates. > > > I used the Extension SQFTlight (sask): > > {{#sask: [[hasParticipant::{{PAGENAME}}]] > |link= > |format=list > |?hasParticipant > }} > > The Output is correct, but looks a bit ugly because the blanks between > first name and last name of the persons are replaced underscores. > > Example-Output: John_Smith, Cho_Chang and Harry_Potter > I was wrong about the output. It is not correct because with this query, every Participant is listed on every person-page. I think that is because #sask ignores/does not understand the part [[hasParcipant::{{PAGENAME}}]] I did not recognize this first because I testet the query on a small testwiki. So #sask can output unique results, but it can not output only those pages which have a property with a given value and #ask can not output unique results, but can output only those pages which have a property with a given value...? Can anybody think of a solution for this problem? Or will ask get a "-unique" parameter soon? -- View this message in context: http://old.nabble.com/Removing-duplicate-properties-from-search-tp26402948p30271085.html Sent from the Semantic Mediawiki - User mailing list archive at Nabble.com. |
From: Jack D. P. <jac...@ps...> - 2010-11-21 18:52:48
|
It took me several hours to figure this out, so I thought I would document it in case someone else runs across it. If you use the Create Class for SF, you may get undesireable code generated in the template if you intend to use commas in your "Allows values" of your properties. In this example, I tried to define an allowed value of property "Constituency Type" to be "Columbia, District" When the template is generated, it will default to a generated: (in template): {{#arraymap:{{{Constituency Type|}}}|,|x|[[Constituency Type::x]]}} (in form): {{{field|Constituency Type}}} Since there is a comma in the acceptable value "Columbia, District", it will actually try to evaluate the property tag as "Columbia" and "District" rather than "Columbia, District". To correct this, you can do one of two things (depending on what you're doing): 1. Edit and change the default delimiter (if you are allowing multiple selections for this property): ex (in template): {{#arraymap:{{{Constituency Type|}}}|xyzzy|x|[[Constituency Type::x]]}} ex (in form): {{{field|Constituency Type|delimiter=xyzzy}}} 2. If you are using radiobuttons (I was) and you are only returning one value, eliminate the multiple selections: ex (in template): [[Constituency Type::{{{Constituency Type|}}}]] ex (in form): {{{field|Constituency Type|input type=radiobutton}}} ---------------------------- Property:Constituency Type This is a property of type [[Has type::String]]. The allowed values for this property are: * [[Allows value::Columbia, District]] ---------------------------- |
From: Dan B. <dan...@gm...> - 2010-11-22 10:08:46
|
On 21 November 2010 18:23, Jack D. Pond <jac...@ps...> wrote: > It took me several hours to figure this out, so I thought I would document > it in case someone else runs across it. > > If you use the Create Class for SF, you may get undesireable code generated > in the template if you intend to use commas in your "Allows values" of your > properties. > > In this example, I tried to define an allowed value of property > "Constituency Type" to be "Columbia, District" > > When the template is generated, it will default to a generated: > > (in template): {{#arraymap:{{{Constituency Type|}}}|,|x|[[Constituency > Type::x]]}} > (in form): {{{field|Constituency Type}}} > > Since there is a comma in the acceptable value "Columbia, District", it will > actually try to evaluate the property tag as "Columbia" and "District" > rather than "Columbia, District". > > To correct this, you can do one of two things (depending on what you're > doing): > > 1. Edit and change the default delimiter (if you are allowing multiple > selections for this property): > ex (in template): {{#arraymap:{{{Constituency > Type|}}}|xyzzy|x|[[Constituency Type::x]]}} > ex (in form): {{{field|Constituency Type|delimiter=xyzzy}}} Have you tried that in a form? Looks ugly! When I allow multiple values for a property and individual values may contain commas, I would tend to use: Template: {{#arraymap: {{{my prop|}}} | ; | x | [[my prop::x]] }} Form: {{{field | my prop | delimiter=; }}} > 2. If you are using radiobuttons (I was) and you are only returning one > value, eliminate the multiple selections: > ex (in template): [[Constituency Type::{{{Constituency Type|}}}]] > ex (in form): {{{field|Constituency Type|input type=radiobutton}}} In this case you only want one value per-property per-page, so it seems like a bug in the "Create a class" special page if it generates an #arraymap for the property assignment... Unless you accidentally clicked the 'List of values?' checkbox? Good to know commas aren't show stoppers in property values! Dan. > ---------------------------- > Property:Constituency Type > > This is a property of type [[Has type::String]]. > > The allowed values for this property are: > * [[Allows value::Columbia, District]] > > ---------------------------- > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Jack D. P. <jac...@ps...> - 2010-11-22 15:27:50
|
Dan, You're absolutely right, I just used xyzzy to make it visually very apparent. ";" (or any other unused character and/or sequence in the "Allowed") is a better choice. Regarding the second, I agree it might be a bug, but since it occurs so infrequently, I'm not sure it's worth fixing. If it were to be fixed, I think requiring the user to escape the character (e.g., "\,") might be a good solution. Jack D. Pond "Get it right, get it quick, get it out, and get it over. Your problem won't improve with age." - Warren Buffett > -----Original Message----- > From: Dan Bolser [mailto:dan...@gm...] > Sent: Monday, November 22, 2010 5:09 AM > To: Jack D. Pond > Cc: sem...@li... > Subject: Re: [Semediawiki-user] Comma in Property "Allows > Values" may not properly store or query using Generated Semantic Forms > > On 21 November 2010 18:23, Jack D. Pond <jac...@ps...> wrote: . . . > Have you tried that in a form? Looks ugly! When I allow > multiple values for a property and individual values may > contain commas, I would tend to use: > > Template: {{#arraymap: {{{my prop|}}} | ; | x | [[my prop::x]] }} > Form: {{{field | my prop | delimiter=; }}} > > . . . > > In this case you only want one value per-property per-page, > so it seems like a bug in the "Create a class" special page > if it generates an #arraymap for the property assignment... > Unless you accidentally clicked the 'List of values?' checkbox? > > > Good to know commas aren't show stoppers in property values! > > Dan. > |