...
[13:16:43 CDT(-0500)] <cwaymire> cool. thanks.
[14:37:31 CDT(-0500)] <cwaymire_> EricDalquist: as an update. I found why it wasn't updating the child's parent key column.
[14:37:38 CDT(-0500)] <EricDalquist> oh?
[14:37:40 CDT(-0500)] <EricDalquist> what was going on
[14:38:02 CDT(-0500)] <cwaymire_> the definition of the set on the parent was flagged as inverse=true so the child owned the relationship
[14:38:25 CDT(-0500)] <EricDalquist> ah
[14:38:28 CDT(-0500)] <EricDalquist> yeah that would do it
[15:12:30 CDT(-0500)] <cwaymire_> able to successfully export the announcements data to xml and re-import it
[15:12:41 CDT(-0500)] <cwaymire_> using the maven lifecycle hook
[15:13:44 CDT(-0500)] <jwennmacher> good job.
[15:49:13 CDT(-0500)] <cwaymire_> isn't the Concurrent user aggregator supposed to aggregate on unique logins?
[15:49:36 CDT(-0500)] <EricDalquist> no
[15:49:40 CDT(-0500)] <EricDalquist> it watches all events
[15:49:44 CDT(-0500)] <cwaymire_> ahhh
[15:49:57 CDT(-0500)] <EricDalquist> and tracks "active" users by those it has seen an event from in that interval
[15:50:05 CDT(-0500)] <EricDalquist> and it isn't actually by user
[15:50:08 CDT(-0500)] <EricDalquist> it is by event session id
[15:50:13 CDT(-0500)] <cwaymire_> ahh ok
[15:50:22 CDT(-0500)] <EricDalquist> so if you login once
[15:50:31 CDT(-0500)] <EricDalquist> but stay active in the portal clicking around
[15:50:36 CDT(-0500)] <EricDalquist> you will be "active" for a long time
[15:52:13 CDT(-0500)] <cwaymire_> its been requested to modify the Portal Activity portlet to take into account unique logins for the totals so i'll have to modify it a bit.
[15:52:41 CDT(-0500)] <EricDalquist> yeah concurrent user aggregator won't get you that data
[15:52:48 CDT(-0500)] <EricDalquist> you'd have to look at unique logins
[15:52:57 CDT(-0500)] <cwaymire_> yep