MobileRead Forums - View Single Post - Patch: Ticket 9168 (Allow maximum number of copies (issues) per recipe)

spedinfargo · 02-25-2011, 05:21 PM

As described in this thread: https://www.mobileread.com/forums/sho...d.php?t=122336

I think a great feature for recipes would be to allow you to define at the recipe level how many copies you want to keep of a particular recipe. For daily newspapers, it might only be worthwhile to keep one or two day's copies around. For some magazines, you might want to set up a monthly download and then keep five or more around.

I've attached a patch that would achieve this. It adds a "max issues" variable to the main scheduler page and then saves it in the recipes XML file. It should be pretty non-intrusive and upgrade-friendly - if the element doesn't exist in the XML node, it will default to 0 and add that value it when the user touches the recipe. A value of 0 means no change from current functionality (i.e. it disables the new feature and keeps the maximum number of copies).

The functionality depends on the recipe title being saved as tag (I think that's enabled by default and unique) and of course the "delete news older than x days" would still be in effect (and have priority).

02-25-2011, 05:21 PM	#1
spedinfargo Groupie Posts: 155 Karma: 106422 Join Date: Nov 2010 Device: none	Patch: Ticket 9168 (Allow maximum number of copies (issues) per recipe) As described in this thread: https://www.mobileread.com/forums/sho...d.php?t=122336 I think a great feature for recipes would be to allow you to define at the recipe level how many copies you want to keep of a particular recipe. For daily newspapers, it might only be worthwhile to keep one or two day's copies around. For some magazines, you might want to set up a monthly download and then keep five or more around. I've attached a patch that would achieve this. It adds a "max issues" variable to the main scheduler page and then saves it in the recipes XML file. It should be pretty non-intrusive and upgrade-friendly - if the element doesn't exist in the XML node, it will default to 0 and add that value it when the user touches the recipe. A value of 0 means no change from current functionality (i.e. it disables the new feature and keeps the maximum number of copies). The functionality depends on the recipe title being saved as tag (I think that's enabled by default and unique) and of course the "delete news older than x days" would still be in effect (and have priority).