In my case, the nzb names of releases I'm getting dupes of are typically the exact same, except for the spacer/delimiter - but I suppose I am in the minority on that one though.hugbug wrote: ↑13 Jul 2018, 21:48It could help a little but wouldn't solve the problem because nzb names have a lot of extra words (video quality etc.). That's why nzbget have concept of dupekeys.
Indexers (the proper ones) use additional information to identify titles. They don't rely solely on nzb name, they download nfos and parse them, etc. Then provide movie identification via field imdbid.
If you can code you can try to identify titles from nzb names and build proper dupekeys by writing an RSS feed extension script. We can discuss this further if you are going to write such a script.
Unfortunately I'm not versed in coding outside of batch-scripting and some powershell.
all releases (movies in this case) are *name* (spacer/delimiter) *year* (spacer/delimiter) *everything else not necessarily needed to match to IMDB
using the OMDb API (free api, just need to provide a valid api key), could then match the name (with or without spacer/delimiter - it doesn't seem to matter for this API), and then the year, in an api request such as this: http://www.omdbapi.com/?apikey=<mykey>& ... zer&y=2014
which then returns either an xml or json, which includes the field:
Code: Select all
JSON: imdbID "tt0455944" XML: imdbID="tt0455944"
however, I have absolutely no clue how to put this all together in a script. I'm willing to try, but I'm unfamiliar with most scripting languages.
I guess I could post a request for this, if you think that's the best course of action.