Preference system similar to Stremio's in lib/db

[Ivshti]

It would work like

db.findOne({  imdb_id: ...},[
   { tag: "hd", min_avail: 2 } // prefer HD torrents if they have at least 2 availability
], function(err, torrent) { /* receive torrent */ })

It must be default behaviour to prefer 720p and 1080p torrents if their availability is at least 2

[Ivshti]

@jaruba and @sammuel86 - thoughts?

[jaruba]

looks cool, but what if there is no quality tag for the torrents? will all of them simply be discarded with this query?

[jaruba]

oh, i just realized it was a dumb question. :)

[Ivshti]

LEt's still answer it - most torrents will be quality tagged, but those which aren't, simply won't be regarded as "preferred" but would still get selected if no preferred torrent is found.

[jaruba]

obviously.. 🎱

[jaruba]

I'm thinking that it would be awesome if quality-grouping was applied to the results of .db.find().

[Ivshti]

IMO this should be a separate function. Most of the code to do this stuff is the stremio add-on in the repo, using output from db.lookup + db.get (essentially a db.find, but without getting all torrents at once), getting the picked file (the file in the torrent which corresponds to the query) and deciding if it contains a preferred tag (such as hd) in the .tag array.

Let's summarize how we imagine this and merge with the simplify API issue and roll out the events API and this at the same time as 0.2 release?

IMO if we have db.findOne(query, preferred), grouping by quali won't be necessary

[Ivshti]

Actually this is implemented in the addon