Re: [SMW-devel] representing hierarchies in SMW
Hi, On Wed, Jan 16, 2013 at 1:47 PM, Yury Katkov wrote: > Thanks Yaron! > > That may work but it means that I'll have to add N categories for each > hierarchical library with N items in it. > Yes. That may or may not be a big deal, depending on what N is. :) > What do you think about subobjects? I don't know if I can bind > together two subobjects with a property... can I? > Yes, you could probably do that... I forgot that subobjects can be nested down any number of levels. If you can think of a way to define a subobject hierarchy that that doesn't end up looking horrible on the page, I'd be curious to see it. -Yaron > - > Yury Katkov, WikiVote > > > > On Wed, Jan 16, 2013 at 9:59 PM, Yaron Koren wrote: > > Hi, > > > > You can do that in Semantic Forms already with the "category" and > > "categories" input types. Those require the CategoryTree extension to be > > installed, and they only work with categories. However, you can create a > set > > of categories just for the sake of creating an SF input - the template > > doesn't need to add the page to the category selected; it can treat the > > selected value as just a normal property value. That would be a hack, but > > then again, categories are a very convenient way of defining hierarchies > > within MediaWiki. > > > > If there were going to be an SMW-based way of defining hierarchy, > though, I > > would think that, yes, it would require creating a separate page for each > > item. It may seem like overkill, but I can't think of another way to do > it. > > > > -Yaron > > > > On Wed, Jan 16, 2013 at 11:43 AM, Yury Katkov > > wrote: > >> > >> Hi ! > >> > >> We're trying to create a form input for semantic forms that will allow > >> users to pick the value of a field from the hierarchy (tree). For > >> example we have hierarchical list of employee key competences that are > >> structured like this: > >> > >> 1. Withstand the negative health effects > >> 1.1. Withstand the negative weather effects > >> 1.1.1 Withstand the wind > >> 1.1.2. Withstand the fire > >> 1.2. Withstand the negative psychological atmosphere > >> 1.2.1. > >> 1.2.2 > >> > >> ... and so on. > >> > >> We want to support such hierarchies and now are searching for a > >> flexible way for that. We want such hierarchies to be input from the > >> Semantic Forms and to be collapsible lists in the 'filtered' format. > >> Of course, our desire is that these objects be native to SMW, but it > >> seems unnecessary to to generate one page per hierarchy item > >> > >> Any ideas on how to better represent such trees in SMW? > >> > >> Cheers, > >> Yury Katkov, WikiVote > >> > >> > >> > -- > >> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > >> and much more. Keep your Java skills current with LearnJavaNow - > >> 200+ hours of step-by-step video tutorials by Java experts. > >> SALE $49.99 this month only -- learn more at: > >> http://p.sf.net/sfu/learnmore_122612 > >> ___ > >> Semediawiki-devel mailing list > >> Semediawiki-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > > > > > > > > > > -- > > WikiWorks · MediaWiki Consulting · http://wikiworks.com > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] representing hierarchies in SMW
Thanks Yaron! That may work but it means that I'll have to add N categories for each hierarchical library with N items in it. What do you think about subobjects? I don't know if I can bind together two subobjects with a property... can I? - Yury Katkov, WikiVote On Wed, Jan 16, 2013 at 9:59 PM, Yaron Koren wrote: > Hi, > > You can do that in Semantic Forms already with the "category" and > "categories" input types. Those require the CategoryTree extension to be > installed, and they only work with categories. However, you can create a set > of categories just for the sake of creating an SF input - the template > doesn't need to add the page to the category selected; it can treat the > selected value as just a normal property value. That would be a hack, but > then again, categories are a very convenient way of defining hierarchies > within MediaWiki. > > If there were going to be an SMW-based way of defining hierarchy, though, I > would think that, yes, it would require creating a separate page for each > item. It may seem like overkill, but I can't think of another way to do it. > > -Yaron > > On Wed, Jan 16, 2013 at 11:43 AM, Yury Katkov > wrote: >> >> Hi ! >> >> We're trying to create a form input for semantic forms that will allow >> users to pick the value of a field from the hierarchy (tree). For >> example we have hierarchical list of employee key competences that are >> structured like this: >> >> 1. Withstand the negative health effects >> 1.1. Withstand the negative weather effects >> 1.1.1 Withstand the wind >> 1.1.2. Withstand the fire >> 1.2. Withstand the negative psychological atmosphere >> 1.2.1. >> 1.2.2 >> >> ... and so on. >> >> We want to support such hierarchies and now are searching for a >> flexible way for that. We want such hierarchies to be input from the >> Semantic Forms and to be collapsible lists in the 'filtered' format. >> Of course, our desire is that these objects be native to SMW, but it >> seems unnecessary to to generate one page per hierarchy item >> >> Any ideas on how to better represent such trees in SMW? >> >> Cheers, >> Yury Katkov, WikiVote >> >> >> -- >> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery >> and much more. Keep your Java skills current with LearnJavaNow - >> 200+ hours of step-by-step video tutorials by Java experts. >> SALE $49.99 this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122612 >> ___ >> Semediawiki-devel mailing list >> Semediawiki-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] representing hierarchies in SMW
Hi, You can do that in Semantic Forms already with the "category" and "categories" input types. Those require the CategoryTree extension to be installed, and they only work with categories. However, you can create a set of categories just for the sake of creating an SF input - the template doesn't need to add the page to the category selected; it can treat the selected value as just a normal property value. That would be a hack, but then again, categories are a very convenient way of defining hierarchies within MediaWiki. If there were going to be an SMW-based way of defining hierarchy, though, I would think that, yes, it would require creating a separate page for each item. It may seem like overkill, but I can't think of another way to do it. -Yaron On Wed, Jan 16, 2013 at 11:43 AM, Yury Katkov wrote: > Hi ! > > We're trying to create a form input for semantic forms that will allow > users to pick the value of a field from the hierarchy (tree). For > example we have hierarchical list of employee key competences that are > structured like this: > > 1. Withstand the negative health effects > 1.1. Withstand the negative weather effects > 1.1.1 Withstand the wind > 1.1.2. Withstand the fire > 1.2. Withstand the negative psychological atmosphere > 1.2.1. > 1.2.2 > > ... and so on. > > We want to support such hierarchies and now are searching for a > flexible way for that. We want such hierarchies to be input from the > Semantic Forms and to be collapsible lists in the 'filtered' format. > Of course, our desire is that these objects be native to SMW, but it > seems unnecessary to to generate one page per hierarchy item > > Any ideas on how to better represent such trees in SMW? > > Cheers, > Yury Katkov, WikiVote > > > -- > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > ___ > Semediawiki-devel mailing list > Semediawiki-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/semediawiki-devel > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] representing hierarchies in SMW
Hi ! We're trying to create a form input for semantic forms that will allow users to pick the value of a field from the hierarchy (tree). For example we have hierarchical list of employee key competences that are structured like this: 1. Withstand the negative health effects 1.1. Withstand the negative weather effects 1.1.1 Withstand the wind 1.1.2. Withstand the fire 1.2. Withstand the negative psychological atmosphere 1.2.1. 1.2.2 ... and so on. We want to support such hierarchies and now are searching for a flexible way for that. We want such hierarchies to be input from the Semantic Forms and to be collapsible lists in the 'filtered' format. Of course, our desire is that these objects be native to SMW, but it seems unnecessary to to generate one page per hierarchy item Any ideas on how to better represent such trees in SMW? Cheers, Yury Katkov, WikiVote -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
[SMW-devel] Pass parsed page contents to SOLR (SMW+ Enhanced Retrieval)
Hi everyone, I am using SMW+ 1.7.1 with Enhanced Retrieval 1.7.1. This is on the one hand pushing data to the solr each time a page is created/edited and on the other hand offers a preconfigured dataimporthandler for a full import retrieved from the DB. Both results in having the raw source of a page in the fulltext. My idea is to fill the index with parsed contents, as I have a lot of query-based contents I would like to see retrievable. (There would be a problem with the up-to-dateness, but to me this seems acceptable.) I consider this possible for the part of pushing entries to the index, but have no idea how to get a solution for the full import (completely deleting and rebuilding the index from the wiki DB, see also http://wiki.apache.org/solr/DataImportHandler ). Is it possible to fetch parsed page data from the DB with SQLstore 2 or 3? Thanks for the great work (more the SMW-part than SMW+, currently ;) )! Kind regards -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
