The IRC channel is #sakai on the freenode network, you can join using a web client at http://webchat.freenode.net/?channels=sakai and you can view the complete logs at http://sakai.iriscouch.com/irc/_design/viewer/index.html
13:22 <nicolaas> simong's pull request has been merged 16:06 <duffy> am lonely on the call. was our stand up cancelled? (have not yet reviewed email if there was an announcement) 16:07 <zacht> I won’t be on the call today duffy, but I expect other people would be. 16:08 <duffy> zacht: got it. at present I'm thinking not as we're 10 minutes in and I've already given my update to myself 18:19 <GitHub23> [nakamura] lancespeelmon pushed 3 new commits to 1.4.2: http://git.io/GTuakg 18:19 <GitHub23> [nakamura/1.4.2] NOJIRA merge sakai/master/bundles/basiclti into 1.4.2 branch - Lance Speelmon 18:19 <GitHub23> [nakamura/1.4.2] KERN-3165 CLEVirtualToolDataProvider component is no longer configurable via /system/console - Lance Speelmon 18:19 <GitHub23> [nakamura/1.4.2] Merge pull request #996 from lancespeelmon/142 - Lance Speelmon 19:22 <GitHub135> [nakamura] lancespeelmon pushed 3 new commits to master: http://git.io/gpSKJQ 19:22 <GitHub135> [nakamura/master] KERN-3159 Promote nyu-force-migration to core - Lance Speelmon 19:22 <GitHub135> [nakamura/master] KERN-3159 Added authz logic to only allow admins to access endpoint; reformat code. - Lance Speelmon 19:22 <GitHub135> [nakamura/master] Merge pull request #1002 from lancespeelmon/kern-3159 - Lance Speelmon 23:39 <duffy> can anyone suggest who on this channel might be a suitable pooled-content guru? I have a question about the row/column document model and how it is managed via the REST API 23:40 <duffy> I am willing to accept "guy willing to make up plausible stuff" as a stand in for "guru" :) 23:40 <thecarlhall> duffy, I can guess as good as the rest of them :) 23:40 <duffy> thecarlhall, sweet :) 23:40 <thecarlhall> duffy, "managed via rest": the whole document is submitted at once 23:41 <duffy> thecarlhall: I'm looking at KERN-3166. timestamp does not update when a document is editted 23:41 <duffy> thecarlhall: I have surmised that mods to content elements touch their _lastModified datestamp, but nothing is trickling that change up to the parent document 23:42 <thecarlhall> duffy, sounds right 23:42 <thecarlhall> duffy, since everything is treated as a tree of independent nodes, there would need to be a follow up call to update the parent/containing document 23:43 <duffy> there is a call being made within a /system/batch call that attempts to POST to the parent document with a param 'sakai:forceupdate = true" 23:43 <duffy> but I can't find an endpoint that does anything with that 23:43 <thecarlhall> duffy, what's the batch call endpoint? 23:43 <thecarlhall> for ^^ 23:43 <thecarlhall> just to the parent doc itself? 23:43 <duffy> yup 23:43 <thecarlhall> hm, that should update the timestamp 23:43 <duffy> that's what I thought 23:44 <duffy> but when I grep for forceupdate in bundles/ I get squate 23:44 <duffy> -e 23:44 <thecarlhall> it's probably just there to act as a touch command 23:44 <duffy> got it 23:44 <thecarlhall> safe, unused value type thing 23:45 <duffy> cool, I'll trace through that call and see where it ends up. I was concerned an endpoint had disappeared 23:45 <duffy> thx 23:46 <thecarlhall> it'll most likely end up in the default post servlet with no explicit handler 23:50 <duffy> thecarlhall: correct sir, on all counts :) 23:51 <duffy> thecarlhall: so that trick only works once. once the param "sakai:forceupdate" is set to true on the document node… setting it again does not actually modify the node. 23:51 <thecarlhall> duffy, ah! so it should be something like "myVar=<random anything>" 23:51 <ixmati> random anything is my middle name 23:51 <thecarlhall> :) _______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
