[10:53:50] Afternoon! Does anyone know if you can set a semantic property based on the results of a query? [12:54:05] Person: yes, you can. [14:17:27] I'm being optimistic, but does anyone know why printing out an array inside a table template would break the table template? [14:26:16] I keep getting a warning saying some part of my query isn't understood. [14:26:41] It's a query with a template format, the template calls on a second template which has #arraydefine and #arrayprint in [16:24:17] I claim victory over my own failure to understand SMW! [19:52:37] Good [22:31:16] If I have an Event form that creates an Event, and I add in a link to other types of page to create an event (autopopulating a field in Event), is there a way in the Event form to link that event to other pages but have the semantic information written into the other pages rather than Events? [22:32:42] the only way I can think of is using an array and a template to pass parameters through {{#autoedit}} but that seems like it's probably complicated to the point that there should be an easier way [22:33:27] and even then Autoedit might replace the content of the property rather than add to it [22:35:00] the reason being I'd rather declare in the Person and Theme pages, the relevant events, rather than store that information in the Events page [23:11:48] the channel log link doesn't work for me [23:25:54] Person: yes, it needs to be fixed; change "petrb" in the URL to "wm-bot". [23:26:23] Thanks Yaron [23:27:09] Hmm, still not seeing it [23:27:27] You get a 404? [23:28:04] aye [23:28:33] nm now I seem to get a list of text files [23:28:38] Alright. [23:28:42] thank you [23:29:02] can you field a couple of Semantic Forms questions? [23:29:07] Speaking of the log, I just checked it and saw your question about creating events, but I don't understand it. [23:29:10] Yes, sure. [23:29:26] I'll try to explain myself better [23:30:43] I have an information hierarchy, with Person at the top, Organisation in the middle, and Event at the bottom. The idea is a Person page has semantic markup for the Organisations and Events they are involved with. Organisations show involved Persons through a query, but declare the Events they are involved with. Events should show involved Persons and Organisations only through queries. Events are just the targets of markup [23:31:17] For ease of wiki users, though, I would like Person and Organisation pages to be able to create Event pages with a #forminput included in the Person and Organisation templates. [23:31:54] The obvious next step is to allow the form then to add other Persons and Organisations involved with the Event, rather than making the user update each Person and Organisation page separately [23:33:15] But I'm not sure of the best way to make an Event form called from Person Page A, also add the Event to Person Page B. I might be able to replace the contents of the semantic markup in Person Page B using #autoedit in an array or something but that seems like a bad solution [23:33:37] Failing that I just change my information flow and make Events responsible for the people and organisations but that makes querying things more complex [23:34:09] Why not just have people manually add that kind of info the event page? [23:35:17] (to the event) [23:36:03] Because if I do a query for all Persons, then showing all the Events they are at is easy if the information is in the Persons page. If it's in the Events page, I have to nest queries. Which I can do, but I was hoping to have a hierarchy whereby the most important things (arbitrarily starting with people) contain information about the lesser things, and the lesser things derive their information only [23:36:26] I don't want a Person declaring an Event and an Event declaring a Person because I want just the single source of truth [23:36:44] It might be that just moving the details to Event is far easier [23:36:54] Yes, sure - I would think it makes sense to only have events declare their attendees. [23:37:06] Do you really need to nest queries, though? [23:37:21] I did to show all the people in an Organisation [23:37:46] on a page that had an #ask query for all Organisations and then each result showed all members [23:38:34] Ah, right. [23:38:56] I'll change the structure. [23:39:32] Wait, can't you do something like "{{#ask:[[Category:Organisations]] |?Year started |?Country |?-Is member of}}"? [23:39:46] Probably, if I'd realised that was possible. [23:39:54] I forget know if you can print out inverse queries. [23:40:01] * Person facepalms. [23:40:06] I'll try it. [23:40:51] Second question, I have tried to implement Semantic Forms to declare the page name of an uploaded file (to avoid File:IMG1234.png type names) by including the form in a Person page, and then making it File:Personpagename, but it seems to still upload the file into File:1234.png and also make a page called File:Personpagename which isn't actually a File page [23:41:21] That's.... not good. [23:41:31] Are you using "default filename="? [23:41:36] Is what I want possible with Semantic Forms? Or is it just to assign semantic properties to File:1234.png [23:42:08] | {{{field|Image field|uploadable|property=Image name|default name={{SUBPAGENAME}}|mandatory }}} (Required) [23:42:24] It's "default filename". [23:45:35] Thanks! [23:48:05] Note that the "default filename" doesn't work great - if you set the name to end in, say, "png", and someone uploads a file in a different format, the whole thing will fail. [23:48:31] I wish I knew how to fix this problem. [23:48:53] Ah [23:49:02] Okay, I can't constrain the type [23:49:27] I'll just provide an easy link to File:Upload [23:49:54] It's a shame, making the name of a file come from the page it was uploaded from would be very useful [23:50:31] Anyhow, it's an awesome extension, thanks for creating and updating it. Its power far exceeds my grasp of computing heh [23:54:24] ?-Is member of works fine.