Post
by silhouette » 12 Dec 2018, 20:27
Changes to make the script universal in terms of list source, RSS feed formatting, filtering and custom post processing-
Please bare with me while the explanation is long, I don’t think that it would require changing more than 5% of the code.
This script could easily be adjusted to strip id's from any html page containing a list of relevant id's- Not only IMDB ID’s.
Step 1. Accommodate any website with levant id’s in the page source.
Step 2. Match relevant items in different RSS feeds
Option 2.a Current method
Option 2.b Flexible method
Step 1. Accommodate any website with levant id’s in the page source.
I would the run a slightly adapted version of the current script. I would adapt the line, and string identification. currently used for the nzb feed, to make the script adaptable to any html page containing relevant id's . It wouldn't matter if that is rage id's or imdb'id's as long as the nzb feed contains the same id's.
If we include the ‘tt’ part of the id, the script would become more robust to use for other types, as for instane tv-rage.
Field.1: a comma separated list of urls containing a list of items.
Field.2: user optional: comma separated list of categories or another parameter which would be assigned to results from the corresponding lists above.
Field.3: comma separated lists of corresponding start string
Field.4: comma separated list of corresponding end strings
Field 3. and 4 would also be used for identifying the relevant lines.
By making the above adaptations any nzb feed containing relevant id's could be paired with any and multiple web pages containing wanted id's.
Step 2. Match relevant items in different RSS feeds
There are two ways to identify the item's from the nzb feed, containing the id's identified above.
Either way it should be possible to assign a category or parameter to the item, based on the source of the ID, and the list in field 2.
Solution 2.a
Current (inflexible) method of pairing the identified ID’s with the NZB feed.
To accommodate multiple feeds with different formatting, We would need three more fields. The downside of using this method, is that it wouldn't be possible to mix and match for instance tv-rage and imdb id’s
RSS Feedname as set in RSS
Field.RSS.Name
To isolate the relevant ID, we would need two more fields to define the Corresponding Start and End strings;
Field.RSS.Start
Field.RSS.End
It would be great, if we could set a category or another parameter for each item to carry over the source of the ID:
Solution 2.b
Flexible method that would make it possible to identify any type of ID for each item in the nzb feed.
The flexible solution would be to inspect each item in the nzb feed for each of the id's identified in source lists, and assign the corresponding user defined Categories in the process. This option would be very flexible as we could search for any form of id without out any concern for how the nzb feed is formatted as long as the ID is present.
The point of assigning categories based on the source, is that it would be possible to maintain separate lists, for items that would require additional filters. For example one list could be for items should have the string ‘MULTI’ in the title. Another list could be items which have no special requirements.
While it might sound a tat tedious it is really rather simple. It is my impression that it would only require small adjustments to the original script to achieve this enormous flexibility. Support for different html lists, support for any nzb feed, which contain the relevant ID’s regardless of formatting, and source information, which might be relevant for defining filters or post processing.