PreDB

Issue #37 new
Gfy created an issue

"check entries against a predb"

that's not a small one: we'll have to design a good predb that's based on different sources with requirements such as: same release can be pred multiple times; spam pre, delpred and then the real release; backfilling of releases with the "current" date

API support so other sources can easily push changes to us. One user can have multiple keys for each database he's pushing from. (hidden and only viewable for admins)

  • link to request system if they want to add nfo, sfv,... files too

Predb support is NOT there to remove releases in any way. It helps to filter for those that want to and can help us detect bad capitals. It'll exclude valid scene releases: e.g. Nasha.Russia.Yaytsa.Sudby.2010.RUSSiAN.720p.BluRay-DRHD that can't be found in any public pre database. I heard it's a stupid movie though.

Only make available to those that contribute in some way? Lessen the server load + get more people supporting the project.

a db that can be fixed: looking at more dbs to decide what's best etc Yeah, its so much junk in other db's

From chat: keep which info we got from which db I would keep all junk too, but label it as such (srrdbdelpre, also regular delpre) sometimes you see 2000-01-01 22:00:00 as pre date, but if we find 2000-01-02 13:33:37 from an other db, we should show that date for the srrs and instead that we pull from sources, other users should be able to push their data to us too

Priority is low. There are other people running predbs.

Comments (0)

  1. Log in to comment