Fred, The Idea behind this, comes from out music scheduling guys.
We have come to peace with the fact that the scheduler is not state of the art, like for example powergold. And we can get the most out of it with well choosen schedulercodes. But to make everything more season flavoured, these guys came up with 52 lists of music, which topped the charts in that particular week for the last 40 years. They asked me if it would be possible to tag the songs in our database. If it would be in monthly base instead of weekly, it would already improve our scheduling a lot. The real problem would be that we have many many clocks, where we would have to change the rules each week/month. And doing stuff manually calls for errors. I made the mistake of telling them it was already in the system, with the feature that the cuts can be dated. After they entered all the dates, the system could not fill the hours anymore. And i received some mad faces :) So to make things short, some "timed scheduler codes" would be a really nice feature, or even some "global rules" which affect all clocks. Makes me wonder why nobody else ever ask for this kind of feature. At the moment they enter these seasonal songs manually, which is really admirable :) Regards Peter Just in this sideline, I was thinking of another feature that might come in handy for many people. Namely a debug log for the scheduler, where 'candidate cuts' are shown, why they are picked or not picked, why/where the rules are violated etc. Now you can only see the outcome, and which rules are violated. My idea was if the machine has to make choices, it might as well log them somewhere in a text/log file. It is sometimes hard to figure out why the scheduler always picks the same cuts, with a particular rulesset. 2018-07-24 13:15 GMT+02:00 Fred Gleason <[email protected]>: > On Jul 23, 2018, at 19:00, Peter Claes <[email protected]> wrote: > > I have asked this a while ago, if it would be possible to create date > based schedule codes. > > I know you can add dates in the cut info, but then they are still > sheduled, but marked in red. > > So I was wondering i someone could help me out with a bash script. > > The idea would be that we code music by week numbers : week01 upto week52 > > > Why not use a different set of of scheduler codes for each particular set of > weeks? > > > What I would like to achieve is a bash that: > - clears the thisweek code from the DB > - calculates the weeknumber with an offset (because we schedule 10 > days ahead) with overflow for 53 and 54 being 1 and 2 > - then adds the thisweek code to all the carts carrying the weekxx > code (xx being the calculated week number) > > I would like to run this as a cronjob on a monday morning :) > > Would this be do-able ? > > > It would be very brittle going forward. The likelihood of schema changes > breaking it would be quite high. Something like this really needs to be part > of the base RD code. > > Cheers! > > > |----------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |----------------------------------------------------------------------| > | A room without books is like a body without a soul. | > | -- Cicero | > |----------------------------------------------------------------------| > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
