Opened 12 years ago

Closed 8 years ago

#5251 closed Patch - Feature (Won't Fix)

Add watched status as weighted input to Time/Priority auto expire

Reported by: Nick French <naf@…> Owned by: cpinkham
Priority: minor Milestone: unknown
Component: MythTV - Scheduling Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: yes

Description

This patch extends the concept of the "Weighted Time/Priority?" auto-expire method to include a recording's watched status as an input into the weighting algorithm.

The renamed Weighted Time/Priority/Watched? method takes a configurable number of days to take away from already watched programs when ranking them for auto-expiry. This parallels the existing # of days weight to add to higher-priority programs (although watched is boolean, but this can be offset by using a larger watched weight).

Having a weight for watched programs allows a mix of expiring ancient unwatched programs before new watched programs (that your spouse watched without you) while at the same time expiring old watched programs before new unwatched ones.

Setting the max watched weight achieves a similar effect to the current 'watched before unwatched" flag, so no functionality is lost for anyone who prefers the existing method.

Attachments (2)

watch-weight-expire.diff (3.8 KB) - added by Nick French <naf@…> 12 years ago.
Patch adding watched status as autoexpire weight
watch-weight-expire_v2.diff (4.0 KB) - added by naf@… 9 years ago.

Download all attachments as: .zip

Change History (8)

Changed 12 years ago by Nick French <naf@…>

Attachment: watch-weight-expire.diff added

Patch adding watched status as autoexpire weight

comment:1 Changed 10 years ago by stuartm

Component: mythtvMythTV - Scheduling

comment:2 Changed 9 years ago by databubble

As of 25614, this patch no longer applies.... although it worked on builds a month or so ago.

I've personally found it very useful for over a year... I much prefer items I've watched to be expired over items I haven't watched. I don't believe this is particularly intrustive.

Is there any chance it can be cleaned up and committed?

comment:3 Changed 9 years ago by robertm

Ticket locked: set

Please direct discussion to discussion lists. Ticket locked.

comment:4 Changed 9 years ago by robertm

Owner: changed from Isaac Richards to gigem
Status: newassigned

comment:5 Changed 9 years ago by robertm

Owner: changed from gigem to cpinkham

whoops

Changed 9 years ago by naf@…

Attachment: watch-weight-expire_v2.diff added

comment:6 Changed 8 years ago by stuartm

Resolution: Won't Fix
Status: assignedclosed
Type: enhancementPatch - Feature

There comes a time when a feature patch has been ignored for so long that it's unlikely to ever get the attention it deserves. I'm closing this as 'Won't Fix' because there seems to be no interest in this feature among the devs. If I'm wrong one of them will accept the ticket, re-open and make a commitment to get this in for 0.26.

Note: See TracTickets for help on using tickets.