[06:55:32] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#654 (regression-tests - 7f8e809 : mwjames): The build failed. [06:55:32] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/commit/7f8e809b8a06 [06:55:32] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17258850 [07:10:47] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#658 (regression-tests - 8b3087d : mwjames): The build is still failing. [07:10:47] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/7f8e809b8a06...8b3087d7f341 [07:10:47] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17259302 [07:18:34] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#658 (regression-tests - 8b3087d : mwjames): The build is still failing. [07:18:34] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/7f8e809b8a06...8b3087d7f341 [07:18:34] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17259302 [07:23:07] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#660 (tests - 585beb2 : mwjames): The build failed. [07:23:07] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/commit/585beb273a47 [07:23:08] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17259583 [07:23:27] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#658 (regression-tests - 8b3087d : mwjames): The build is still failing. [07:23:27] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/7f8e809b8a06...8b3087d7f341 [07:23:28] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17259302 [07:27:49] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#663 (regression-tests - 668aab4 : mwjames): The build is still failing. [07:27:49] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/8b3087d7f341...668aab478a63 [07:27:49] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17259702 [12:32:12] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#670 (regression-tests - 69ad376 : mwjames): The build was broken. [12:32:12] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/020d8696706d...69ad376bd98b [12:32:13] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17272713 [12:34:20] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#670 (regression-tests - 69ad376 : mwjames): The build was broken. [12:34:20] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/020d8696706d...69ad376bd98b [12:34:20] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17272713 [12:45:50] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#670 (regression-tests - 69ad376 : mwjames): The build was broken. [12:45:50] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/020d8696706d...69ad376bd98b [12:45:50] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17272713 [13:45:42] [travis-ci] SemanticMediaWiki/SemanticMediaWiki#674 (regression-tests - 26cb32b : mwjames): The build is still failing. [13:45:42] [travis-ci] Change view : https://github.com/SemanticMediaWiki/SemanticMediaWiki/compare/249bf07357c7...26cb32b9520d [13:45:42] [travis-ci] Build details : http://travis-ci.org/SemanticMediaWiki/SemanticMediaWiki/builds/17276111 [16:37:53] I have a category of pages with names. Each page's subject matter also has a numerical ID associated with it. Any time the page is linked to, I'd like the editor to be able to insert just the number or the name and get a link with text of "Name [number]". My current solution to this is to use a template with a large switch statement listing all the pages and IDs. Is there a better way? [16:37:59] http://olywiki.asciiking.com/wiki/index.php?title=Template:ID&action=edit [16:38:46] this becomes a problem when I try to refer to those pages in SMW properties. I can just make it a String property and feed it to that template when I need to display it, but that seems like I'd be giving up some of the functionality that the Page property type might provide. [16:44:30] sparr: how would someone link to a page? [16:45:13] right now I can do {{ID|1}} or {{ID|gold}} or {{ID|GoLdS}} to get a link to the Gold page with a text of however I spelled/capitalized/pluralized it in my template parameter [16:46:27] I see, okay. Well, sure, you could use #show for that, I assume. [16:46:36] someone in #mediawiki has put me on to the idea of moving the data out of the template and into SMW objects. one page per item, with the name(s) of the item and its ID as properties, then replace the template contents with a SMW query of that data [16:47:19] that's a nicer organization, but still doesn't address my problem with how to represent that in a property [16:47:27] I thought the data was already outside of the template... [16:47:38] Isn't each ID a semantic property on its own page? [16:47:43] not yet [16:47:56] should be, will be, just didn't occur to me since I made that template before starting to use SMW [16:48:07] I see, okay. [16:48:37] so, let's say I've done that [16:48:43] I've moved all that data out to a page for each item [16:48:59] and I've modified the ID template to query that data [16:49:20] so the ID template continues providing the same functionality that it has now [16:49:48] now, I've got some other set of semantic properties on some other pages, and one of those properties is "ingredient", which will refer to an item [16:50:49] two questions arise [16:51:12] first, is it possible to write my queries in such a way that I could specify ingredients by name or plural name or number? [16:52:11] second, once I've done [[ingredient::gold]], how can I, if at all, make sure that that always displays the same way that {{ID|gold}} would? [17:00:10] sparr: no, you should have the logic for determining what kind of value it is happen before the queries happen. [17:04:34] ok, how might I do that? [17:05:39] page "Swordsman" is going to have a few properties. one will be [[ID::20]], others might be [[alternate-spelling::swordsmen]] [[alternate-spelling::swordsmans]] [17:05:42] I don't know... I'm guess there's some way to determine if something is a number... [17:06:00] Ah, at that point it becomes tricky. [17:06:09] given one of those four strings (counting "20" as a string), I can write a query that will find that page [17:06:17] For alternate spelllings, you can do redirects. [17:06:28] that query is what I'll replace my existing ID template with [17:07:06] I don't know - this seems tricky. [17:07:08] but my concern is when I refer to one of those things on another page, as a property [17:07:16] I know, tricky is my middle name :) [17:07:26] Maybe the logic should indeed use #show. [17:08:01] I think I'll table this until I've got some real examples [17:08:17] I'll make all the item pages, and reimplement my ID template, and then make some examples to illustrate the situation [17:17:38] thanks for all the feedback and help [19:53:14] Is there a way to specify that a certain Page-type property will always be in a specific namespace? [19:53:44] that is, I'd like to say [[foo::bar]] and configure Property:foo such that it links to somenamespace:bar instead of just to bar [20:30:05] What does enableSemantics actually do? I've got a couple of test sites I'm running and I'm trying to decide if I should be using their actual site names, or the names of the sites their mirrored from. [21:03:58] Rosencrantz: it should use the current site domain. [21:04:07] Ok, thanks. [21:06:44] I'm using a template that adds a lot of SMW properties to a page. However, I'm stuck when I need two copies of the same property, since I can't pass a template two of the same named parameter. Help? [21:07:44] What do you mean by two copies? [21:08:26] [[ingredient::rice]] [[ingredient::water]] [21:10:23] Okay, two values. Can't you just call the same template twice? [21:10:50] right now the idea is a single "monolithic" template with a bunch of different parameters [21:11:21] {{Recipe|cook_time=4 hours|difficulty=easy|ingredient=rice|ingredient=water...}} [21:11:34] I'm trying to comprehend alternative approaches [21:12:04] more generally, I want to understand how I can make SMW properties and templates for layout get along, in general [21:15:59] Well, I would recommend using forms, but I'm biased. [21:16:22] I actually want to try that, but how is it relevant to this concern? [21:16:52] forms make it easier to enter data, but they don't change how it ends up on the pages, right? to make the form I need to solve the problem first, so I know what ot make the form output [21:18:08] Well, that's true, but having the form there can also make it easier to standardize the template and page structure. [21:20:16] oh, sure [21:20:26] in this particular case new pages will get created very very rarely [21:20:31] possibly never [21:20:40] so I'm concentrating more on the implementation side of the problem [21:21:30] I just can't grasp all the different ways to accomplish this, and which would be ideal [21:22:11] if I give up on templating then I can just write each page with the appropriate properties, but that risks inconsistency in the presentation of those pages [21:22:38] if I wrap the data in a template to make it present consistently, then I run into problems with multiple properties and some annoyances regarding pipes [21:23:12] Well, it's not perfect, but you can do ingredients = water, rice [21:23:20] and then use #arramap [21:23:20] You might want to use subobjects for that, by the way. [21:23:23] one thought is to put all the data in properties on the page, and then have a parameter-less template that queries the SMW properties of the current page to decide what to display [21:23:47] Or if you want to include quantities, Ingredients = water, 2 cups; rice, 1 cup; .... [21:24:15] And then you can have an array map inside an array map. [21:24:57] Although at that point I'd do what Yaron suggested and use subobjects [21:24:58] I'm faking #arraymap with #replace right now on another set of pages, and that's very hacky. However, Semantic Forms seems like it will do a lot of things I need. [21:28:47] using subobjects seems orthogonal to the question at hand [21:30:42] Well, to me it makes the most sense if you're dealing with ingredients and their associated quantities [21:30:49] oh, sure [21:30:56] I will very likely use subobjects [21:31:00] Otherwise, I'd do #arraymap as is. [21:31:08] err #arraymap + property [21:31:12] err... [21:31:19] I have to do the arraymap either way [21:31:25] Hmm, good point. [21:32:01] the core problem is how to represent multiple values that are going to end up as unique-but-with-the-same-name-or-type-or-identifier-or-whatever bits of data [21:32:05] in a template [21:32:31] once the data is given to the template and broken out (somehow, probably #arraymap), I can put it in properties or subobjects or whatever else I want. [21:32:33] I thought we nailed that part already. [21:32:46] | Ingredients = Water, rice, .... [21:33:04] Or am i missing something.. [21:38:55] that's an option [21:39:08] but that gets annoyingly tricky if I want to include quantities and other metadata [21:39:20] and requires me to install yet another extension :( [21:39:49] another option is that I could ditch the template and put the properties or subobjects directly onto the pages in question. this increases maintenance cost a little [21:40:48] What version of SMW are you running? Subobjects gets included after… 1.8 I think? [21:40:52] 1.8 [21:41:23] the craziest solution I've come up with so far, which addresses all of my concerns but will be the hardest to implement, is to use on-page properties/subobjects AND a template [21:42:05] the properties and subobjects on the page would be hidden. the template would have no parameters, it would use SMW queries to look up all that hidden info on the including page. [21:42:35] Oh, so you're using the template for display as well then? [21:42:44] Hmmmmm [21:42:57] the template's primary purpose is for display [21:43:17] I'm going to have a thousand of these pages, and I'd like them to look the same. And I'd like to be able to re-arrange them by editing that template [21:43:17] Makes sense I suppose, put it all in one. [21:43:36] the crazy solution is the direction I'm leaning right now; I just hoped there was a better answer :) [21:43:37] I'm doing the same thing, but just with a list of names. [21:44:19] I just list it out the way it's entered in the template, and then break it up into properties inside the template. [21:44:44] I guess it sort of depends on how you want to display it [21:45:47] If you find a way to break up the ingredient+quantity syntax, you can just tack on the #arraymaps at the end. [21:45:57] Not quite sure how the display works with subobjects [23:04:24] sorry, didn't mean to go offline so suddenly [23:38:51] different question! [23:39:01] is there a way to specify a default namespace for a Page property? [23:39:24] I'd like to be able to do [[item name::wood]] and have that link to [[Item:wood]] instead of just [[wood]] [23:44:45] why doesn't this page show anything for the query that's looking for the subobject? http://olywiki.asciiking.com/wiki/index.php?title=Item:Wood&action=edit [23:45:44] my Special:Properties does not list any of the collection properties I'm trying to use in the subobject