...
[10:40:53 CST(-0600)] <dmccallum54> but not to coop
[10:43:48 CST(-0600)] <js70> Thats fine. I don't need a label. Just wanted to make sure unicon had some visiblity on SSP. I will take them off (they are on most of mine)
[10:44:09 CST(-0600)] <dmccallum54> oh we're keeping tabs on you. oh yes 
[10:44:27 CST(-0600)] <dmccallum54> the problem is that charise is going to see those and freak out
[10:44:37 CST(-0600)] <dmccallum54> b/c she doesn't actually have coop staff working on those tickets
[10:44:38 CST(-0600)] <js70> got it.
[10:44:51 CST(-0600)] <dmccallum54> thx
[10:45:23 CST(-0600)] <js70> perfect. I hate to ask about every little detail...but the old assume ass-u-me does seem to hold true in most cases.
[10:45:34 CST(-0600)] <js70> As a heads up, I am not finding documentation for Distance Learning reports.
[10:45:59 CST(-0600)] <dmccallum54> no worries at all. would rather you just do what you think you need to do to stay organized and make progress. i dont need to be a bottleneck
[10:46:24 CST(-0600)] <js70> np. Will send an email off to Russ about the Distance Learning reports.
[10:46:29 CST(-0600)] <dmccallum54> sounds good
[10:46:36 CST(-0600)] <dmccallum54> how about to ssp-dev
[10:46:43 CST(-0600)] <js70> right.
[10:46:45 CST(-0600)] <dmccallum54> k
[10:57:45 CST(-0600)] <js70> Quick discusion on N+1, So I have created 4 methods that bring back a List of EntityStudentCountByCoachTOs through the entity daos. I then need to cycle through them to consolidate by coach (so 4 calls for all coaches). This should be pretty fast but wondering if its worth doing more like what you did and make a monster entity that is a single call.
[10:58:18 CST(-0600)] <js70> I mean just 4 dao calls to get all coaches.
[10:58:29 CST(-0600)] <js70> take it to 1 call.
[11:03:15 CST(-0600)] <dmccallum54> jim
[11:03:29 CST(-0600)] <dmccallum54> js70 as long as the # of calls is bounded, i'm just fine with it
[11:03:40 CST(-0600)] <dmccallum54> well, bounded and not, like, 300
[11:04:02 CST(-0600)] <js70> yeah its gone from n*8 to 4 calls
[11:04:09 CST(-0600)] <dmccallum54> let's move on!
[11:04:34 CST(-0600)] <js70> perfect. I'll test and check it in.
[11:06:24 CST(-0600)] <dmccallum54> awesome
[11:07:17 CST(-0600)] <js70> so about check in. As long as we mark it with SSP-tag thats all you need for handling githup releases correct? Or is there a way to tag it to the jira ticket. (You mentioned yesterday that you want to be able to do an update for just this issue.)
[11:07:49 CST(-0600)] <dmccallum54> just prefix the first line of your commit log with the jira ticket ID
[11:07:57 CST(-0600)] <dmccallum54> SSP-XXX Fixed N+1
[11:08:16 CST(-0600)] <dmccallum54> or, rather, to be properly gitish… SSP-XXX Fix N+1
[11:10:12 CST(-0600)] <dmccallum54> js70 i'm still scrambling to prep for some calls this morning… can we wait to this afternoon to chat about SSP-593?
[11:15:45 CST(-0600)] <js70> np
[11:31:53 CST(-0600)] <Patty_> tony
[11:31:57 CST(-0600)] <Patty_> are you joining the scrum?
[13:11:45 CST(-0600)] <TonyUnicon> Dan I think this is an obvious question but I think I'll ask anyway
[13:11:55 CST(-0600)] <TonyUnicon> api urls
[13:12:19 CST(-0600)] <TonyUnicon> for example
[13:12:19 CST(-0600)] Wiki Markup <TonyUnicon> person/{personId}/earlyAlert/{earlyAlertId}/response
[13:12:36 CST(-0600)] <TonyUnicon> the id placeholders
[13:12:39 CST(-0600)] Wiki Markup <TonyUnicon> like {personId}
[13:12:55 CST(-0600)] <TonyUnicon> is only necessary if that context is required for the call
[13:13:05 CST(-0600)] <TonyUnicon> correct?
[15:08:14 CST(-0600)] <Patty_> jim
[15:08:18 CST(-0600)] <Patty_> are you joining this call