RDAdmin>Groups>Auto Expire cuts xxx days after creation

[AaronJowitt]

This is addition and complementary to existing AUTO PURGE. Essential -esp for VT's.

Hi Fred

On 12/09/15 02:30, Frederick Gleason wrote:

On Sep 10, 2015, at 09:05 56, Aaron Jowitt Aaron.Jowitt@rebelfm.com.au wrote:

How do we 'auto expire' VT's that have externally scheduled (Music Master) cart numbers, so we can recycle the cart numbers, and ensure (which is essential) that 'old' VT's can not air when the cart numbers are recycled ~6 weeks later

If this functionality does not exist, our suggestion is to add a default "AUTO EXPIRE" ( + dd:hh:mm) to RDAdmin>Groups settings. This would be used in addition to existing AUTO PURGE feature ifor the Groups. It would add + dd:hh:mm to the current date/time to any cut that is part of that group (irrespective of hows its created - VTer, RDimport, RDCatch, RDLibrary etc). This would allow VT's to auto 'end date' xx days after recording, and then later, auto purge xx days later. Very useful for things other than VT's. Eg street reports, Outside Broadcast X's, Interviews, Beach reports, traffic reports etc. We have this functionality already, which is administered on a per-group basis. I think all that remains would be the ability to specify a default expiration date for when a VT is created.

Cheers!

Yes agreed. How do you see the functionality being implemented?

Current Group functionality is;

[Optionally] "Purge expired cuts after xx days"

To clarify, I suggest; to be added to this window (presumably just above purge carts) would be;

[Optionally] "Expire cuts after xx days, xx hours, xx minutes"

This extends usefulness well beyond VT's to other events, in other groups. Behavior would be, whenever an audio cuts audio file is first created (by any method), RD sets an initial cut Air Date/Time - End value based on values of those Group settings. Naturally, once the cut is created and that initial value set, the user can later change those Air Date/Time Start/End settings in the normal way if ever required.

i.e. if set to "Expire cuts after 5 days, 1 hour" and "Purge expired cuts after 10 days", when a VT (or news report, phone cross - whatever) is recorded that belongs to that group, RD would set an initial Air Date/Time End value to expire the cut 5d1h from that point. The cut would then purge ~15d from that point (being ~10d after the cut expired).

Is that how you see it working?

Have a great weekend.

Cheers

Aaron

[ElvishArtisan]

Cut expiration (as opposed to purge) is currently set on a per-cut basis. To extend this to a per-group attribute as well is to generate a mare's nest of question about how those two settings should interact. How about just the ability to set a default expiration at some time interval after creation or update of the cut audio?

[AaronJowitt]

| Cut expiration (as opposed to purge) is currently set on a per-cut basis. To extend this to a per-group attribute as well is to generate a mare's nest of question about how those two settings should interact.

Yes there would be quite a few cut vs group interaction questions. Most logical I can think of is;

Library>Cut info>Air/Date Time can be set to ENABLED/DISABLED/GROUP DEFAULT. If a Group expiry attribute is set, then RD automatically sets the cut initially to GROUP DEFAULT only when the cut is created/replaced. The expiry date set by RD could either be a'static expiry date 'that remains unchanged by RD (if the cut audio does not change), or, it could be a fluid value that changes based on the cut age and any further change to group expiry attribute value.

After the cut exists, the user could then (optionally) change Library>Cut info>Air/Date Time from GROUP DEFAULT to ENABLED/DISABLED. Automated import processes (RDImport etc) would also 'over ride' the group default (by setting date to ENABLED) if a cut expiry date is specified.

| How about just the ability to set a default expiration at some time interval after creation or update of the cut audio?

So when a cut is created/updated, there is the option for it to auto set Library>Cut info>Air/Date Time to ENABLED and set the expiry date to 'now + the predetermined time interval'? Yes, I think that achieves the same thing. But if it is not 'Group' based, how do you determine which (new or existing) carts/cuts that should apply to?