uPortal IRC Logs-2011-12-30
[13:06:27 CST(-0600)] <EricDalquist> anyone around?
[13:08:02 CST(-0600)] * athena waves
[13:08:32 CST(-0600)] <EricDalquist> hi, so term/quarter stuff
[13:08:44 CST(-0600)] <athena> yes!
[13:08:59 CST(-0600)] <EricDalquist> so the date and time dimensions will be populated as they are used
[13:09:16 CST(-0600)] <EricDalquist> so what I need is a way to say for Date X what is the current term and what is the current quarter
[13:09:24 CST(-0600)] <athena> so what configures the aggregation jobs themselves? is that just code?
[13:09:51 CST(-0600)] <EricDalquist> so the way I'm planning it right now is that there is a schedule task that runs once/minute
[13:10:19 CST(-0600)] <EricDalquist> and it is autowired with a collection of IPortalEventAggregator instances
[13:10:42 CST(-0600)] <athena> ah ok
[13:10:51 CST(-0600)] <EricDalquist> when it runs it queries for all un-aggregated events and calls IPortalEventAggregator.aggregateEvent on each aggregator for each event
[13:11:02 CST(-0600)] <athena> i'm wondering if the quarter configs should be stored in the db
[13:11:16 CST(-0600)] <athena> since if it's a file / spring config, you'd have to recompile / redeploy to update the registrations
[13:11:28 CST(-0600)] <EricDalquist> so when this process is running various places will be asking DateDimensionDao.getDateDimensionForDate(date)
[13:11:35 CST(-0600)] <EricDalquist> yeah
[13:12:05 CST(-0600)] <athena> brb - whining dog
[13:12:08 CST(-0600)] <EricDalquist>
[13:22:37 CST(-0600)] <athena> sorry about that
[13:22:49 CST(-0600)] <athena> so . . . database-configured?
[13:22:58 CST(-0600)] <EricDalquist> yeah
[13:23:00 CST(-0600)] <EricDalquist> that seems reasonable