[00:16:48] (PS1) Yaron Koren: Various spacing improvements [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109017 [00:17:31] (CR) Yaron Koren: [C: 2 V: 1] Various spacing improvements [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109017 (owner: Yaron Koren) [00:17:33] (Merged) jenkins-bot: Various spacing improvements [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109017 (owner: Yaron Koren) [00:49:58] (PS1) Yaron Koren: Made parsing of "page name=" parameter more robust [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109027 [00:51:22] (CR) Yaron Koren: [C: 2 V: 1] Made parsing of "page name=" parameter more robust [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109027 (owner: Yaron Koren) [00:51:24] (Merged) jenkins-bot: Made parsing of "page name=" parameter more robust [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109027 (owner: Yaron Koren) [16:21:03] (PS1) Siebrand: Correct Title::getInterwiki method name case on call [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109101 [16:22:16] (CR) Yaron Koren: [C: 2 V: 1] Correct Title::getInterwiki method name case on call [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109101 (owner: Siebrand) [16:22:18] (Merged) jenkins-bot: Correct Title::getInterwiki method name case on call [extensions/SemanticForms] - https://gerrit.wikimedia.org/r/109101 (owner: Siebrand) [16:48:01] I have a page with subobjects. The subobjects have multiple of the same property. Those properties have two parts, an quantity and a name. Is there any semantic way to separate those, or should I just stick to "ingredient=2x apple" and parse that into "2" and "apple" with string functions later when I am dealing with the ingredient properties? [16:48:58] sparr: they should ideally be separate parameters to #subobject. [16:49:34] I could do quantity1=2 | ingredient1=apple | quantity2=3 | ingredient2=pear [16:49:39] but that seems even harder to deal with [16:49:40] Oh... I get it. [16:50:04] You're talking about storing a three-dimensional table of information in one page, in other words. :) [16:50:30] well, I'd like to think of the ingredient as a tuple rather than another very-sparse dimension [16:50:38] if I moved every subobject to its own page, then I could use subobjects for the ingredients [16:50:40] I would strongly recommend bringing that down to two dimensions, i.e. having only one recipe per page. [16:50:46] Right, exactly. [16:51:01] that means a lot of extra pages :( [16:51:09] How many? [16:51:20] in the immediate case... a few hundred. [16:51:29] That's not so bad. [16:51:35] I'm planning ahead [16:51:43] a future implementation of this same solution might have thousands of recipes [16:52:08] Well, however many it is, I think that's the only reasonable solution. [16:52:46] ...other than potentially using External Data, and storing all that "recipe" information in CSV files, then extracting it using #store_external_table. [16:53:26] It might be worth looking into that - it depends on how exactly you're planning to use and display all that data. [16:54:08] http://olywiki.asciiking.com/wiki/index.php/Item:Worker [16:54:28] ignore the flat presentation, there will be theming and templating later. right now I'm working more on functionality [17:53:03] (CR) Parent5446: [C: 2 V: 2] Call Linker methods statically [extensions/SolrStore] - https://gerrit.wikimedia.org/r/106932 (owner: Siebrand) [19:28:13] sparr: why not have pages for recipies, pages for ingredients, and have relations represend the amount? [19:28:44] Applepie ---contains 1--> apple [19:29:05] still not extremely elegant, but the bigger the database, the smaller the overhead [19:30:02] there'd be a set of relations that are piecewise, a set that are by teaspoon, a set that are by grams etc. [19:32:16] make all the relations in a set a subproperty of a generic property: [Property:Contains 1] [[subproperty of::Contains pieces]] [21:05:07] Saruman: one page per recipe is the direction I'm trending [21:05:26] although I can already see another situation where I'm going to want one MORE level of depth :( [21:08:45] the recipe metaphor only goes so far. this is actually for a video game where you use things to make other things [21:08:48] or upgrade units into other units [21:08:50] http://olywiki.asciiking.com/wiki/index.php/Item:Sailor [21:10:48] if I move each "recipe" onto its own page then I can use a subobject for each ingredient, and specify quantity and ingredient and even ingredient-specific notes [21:48:23] yes [21:48:32] think well about your information model, and you'll pull it of [21:48:36] off [22:17:12] I have a lot of subobjects that I want to turn into their own pages. Is there any easy/fast/automated way to do that? My naive solution is going to be to export all the existing pages, do some text manipulation voodoo to the xml file, then re-import it. [22:17:18] sorry if that's a repeat, flaky connection here