From: Jonathan D. G. <jon...@ha...> - 2009-01-27 19:07:03
|
Anyone know if there any way to eliminate transcluded pages from an #ask result? Thanks, Jon |
From: Jonathan D. G. <jon...@ha...> - 2009-01-28 15:28:21
|
All, Greetings. Let me broaden the questions and see if anyone has any suggestions. I have an #ask query running against /now individual/ data pages as per the many fine suggestions in the lengthy thread from last week. However, users really need (and like) to see various combinations of these individual data pages aggregated. So I created some user-friendly "aggregation pages" by transcluding related combinations of data pages. The #ask query does a beautiful job of bringing together a table of property values from the data pages, however it also includes (duplicate) entries from the "aggregation pages" -- again /users really like and want these pages/. So I have been trying to eliminate these "aggregation pages" from the #ask query results. I have tried things like assigning a unique property [[Subject::B]] value in the template for the aggregation pages and excluding that value in the query (see below), but that does not work as the aggregation pages have both properties and the query seems to operate like an 'or'. {{#ask: [[Subject::A]] [[Subject::!B]] | ?Property1=Property1Label | ?Property2=Property2Label . . . }} Thank you for reading this far. If anyone has any suggestions on how to query "around" transcluded pages, I would be most appreciative. Thanks again. Jon Jonathan D. Greene wrote: > Anyone know if there any way to eliminate transcluded pages from an #ask > result? > > Thanks, > > Jon > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > |
From: <zeh...@mo...> - 2009-01-28 16:13:07
|
Hi, if I understand that correctly I'm using something similar. I have data on sub-pages (Page/A, Page/B ... Page/Z) which are transcluded onto the main page Page. In order to not get results from the main page and the sub-pages I added the Page page to the category MainPage and add to all queries {{#ask:[[Category:MainPage]] ...}} Basically I do not 'eliminate these "aggregation pages" from the #ask query results' but rather 'eliminate all other pages except the "aggregation page" from the query results'. Maybe this helps. Cheers, Gu Quoting "Jonathan D. Greene" <jon...@ha...>: > All, > > Greetings. Let me broaden the questions and see if anyone has any > suggestions. > > I have an #ask query running against /now individual/ data pages as per > the many fine suggestions in the lengthy thread from last week. > > However, users really need (and like) to see various combinations of > these individual data pages aggregated. > > So I created some user-friendly "aggregation pages" by transcluding > related combinations of data pages. > > The #ask query does a beautiful job of bringing together a table of > property values from the data pages, however it also includes > (duplicate) entries from the "aggregation pages" -- again /users really > like and want these pages/. > > So I have been trying to eliminate these "aggregation pages" from the > #ask query results. > > I have tried things like assigning a unique property [[Subject::B]] > value in the template for the aggregation pages and excluding that value > in the query (see below), but that does not work as the aggregation > pages have both properties and the query seems to operate like an 'or'. > > {{#ask: [[Subject::A]] [[Subject::!B]] > | ?Property1=Property1Label > | ?Property2=Property2Label > . . . > }} > > Thank you for reading this far. > > If anyone has any suggestions on how to query "around" transcluded > pages, I would be most appreciative. > > Thanks again. > > Jon > > > > > > > Jonathan D. Greene wrote: > > Anyone know if there any way to eliminate transcluded pages from an #ask > > result? > > > > Thanks, > > > > Jon > > > > > > > ------------------------------------------------------------------------------ > > This SF.net email is sponsored by: > > SourcForge Community > > SourceForge wants to tell your story. > > http://p.sf.net/sfu/sf-spreadtheword > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: Jonathan D. G. <jon...@ha...> - 2009-01-28 16:38:13
|
Gu, Thank you for your reply. I started off with a similar approach. I found that when a given property is set to the same value twice (which is how the aggregation pages are interpreted) two thing happened, (1) Multiple sets of data were presented in a single row of the #ask query result table, and (2) The second value is omitted from the #ask query result; it was that issue that took me down the path of creating multiple data pages Do you see these same results? zeh...@mo... wrote: > Hi, > > if I understand that correctly I'm using something similar. I have data on > sub-pages (Page/A, Page/B ... Page/Z) which are transcluded onto the main page > Page. In order to not get results from the main page and the sub-pages I added > the Page page to the category MainPage and add to all queries > {{#ask:[[Category:MainPage]] ...}} > > Basically I do not 'eliminate these "aggregation pages" from the #ask query > results' but rather 'eliminate all other pages except the "aggregation page" > from the query results'. > > Maybe this helps. > > Cheers, > Gu > > Quoting "Jonathan D. Greene" <jon...@ha...>: > > |
From: <zeh...@mo...> - 2009-01-28 17:24:52
|
>From the logic of my data it isn't possible to have the same property with the same value more than once on the sub-pages of a Page. So I have no experience with that scenario, sorry. Gu Quoting "Jonathan D. Greene" <jon...@ha...>: > Gu, > > Thank you for your reply. I started off with a similar approach. I found > that when a given property is set to the same value twice (which is how > the aggregation pages are interpreted) two thing happened, (1) Multiple > sets of data were presented in a single row of the #ask query result > table, and (2) The second value is omitted from the #ask query result; > it was that issue that took me down the path of creating multiple data pages > > Do you see these same results? > > > > > > > > zeh...@mo... wrote: > > Hi, > > > > if I understand that correctly I'm using something similar. I have data on > > sub-pages (Page/A, Page/B ... Page/Z) which are transcluded onto the main > page > > Page. In order to not get results from the main page and the sub-pages I > added > > the Page page to the category MainPage and add to all queries > > {{#ask:[[Category:MainPage]] ...}} > > > > Basically I do not 'eliminate these "aggregation pages" from the #ask > query > > results' but rather 'eliminate all other pages except the "aggregation > page" > > from the query results'. > > > > Maybe this helps. > > > > Cheers, > > Gu > > > > Quoting "Jonathan D. Greene" <jon...@ha...>: > > > > > > > |