Group matching RSS results
Posted: February 15th, 2012, 1:32 pm
I would like to request a feature for the RSS feeds. I would like to be able to group together all results that match the same filter on an RSS feed. This would only have to be grouped for matches in the current, latest rss feed. These grouped results would then be sent to the queue as a single download.
This would be very useful for automatically downloading things that are spread across multiple posts, with rar files separated from par files for example. This could then fail post-processing (if one of the rar files needed repair) even though the par files are already in the queue. Additionally, this feature could prevent your queue and history from cluttering up, because you would only have a single entry for every thing you download.
So the feature would work roughly like this. You'd have an additional switch option available, labeled as something like "Group matching RSS results". Now let's say your RSS feed has a filter named "test". When the latest RSS feed is retrieved, let's say it contains the following posts:
- test.rar (generally containing all rar files and a single par2 file)
- test.par2 (generally containing all par2 files)
- test.nfo (generally containing an nfo file and an srr file)
Now, when this is matched against the filters, you would normally get 3 separate entries in your queue, one for each RSS entry. But since all these RSS entries would have been matched against the "test" filter, they would be grouped together as a single entry, named after the first matched RSS entry (or something else). You then have a single entry in your queue, and later in your history, representing this download. You can also perform all post-processing correctly and run post-processing scripts on all available data at once.
Note that the next time the RSS feed is retrieved and checked, all information about previously matching entries can be forgotten.
Of course, there is still the matter of multiple filters matching (like with "Requires" filters). Here you could choose to either match the entire set of matched filters or, probably the more simple solution, just to check the last matched filter and group on that.
I hope this feature makes it into this already excellent program. It would really clean up my queue and history and, more importantly, make my post-processing scripts work correctly when the data is spread over multiple posts.
This would be very useful for automatically downloading things that are spread across multiple posts, with rar files separated from par files for example. This could then fail post-processing (if one of the rar files needed repair) even though the par files are already in the queue. Additionally, this feature could prevent your queue and history from cluttering up, because you would only have a single entry for every thing you download.
So the feature would work roughly like this. You'd have an additional switch option available, labeled as something like "Group matching RSS results". Now let's say your RSS feed has a filter named "test". When the latest RSS feed is retrieved, let's say it contains the following posts:
- test.rar (generally containing all rar files and a single par2 file)
- test.par2 (generally containing all par2 files)
- test.nfo (generally containing an nfo file and an srr file)
Now, when this is matched against the filters, you would normally get 3 separate entries in your queue, one for each RSS entry. But since all these RSS entries would have been matched against the "test" filter, they would be grouped together as a single entry, named after the first matched RSS entry (or something else). You then have a single entry in your queue, and later in your history, representing this download. You can also perform all post-processing correctly and run post-processing scripts on all available data at once.
Note that the next time the RSS feed is retrieved and checked, all information about previously matching entries can be forgotten.
Of course, there is still the matter of multiple filters matching (like with "Requires" filters). Here you could choose to either match the entire set of matched filters or, probably the more simple solution, just to check the last matched filter and group on that.
I hope this feature makes it into this already excellent program. It would really clean up my queue and history and, more importantly, make my post-processing scripts work correctly when the data is spread over multiple posts.