41 lines
1.5 KiB
Plaintext
41 lines
1.5 KiB
Plaintext
## DB
|
|
|
|
Need to think about...
|
|
file (image) -> has X faces, Y matches
|
|
X == Y (optim: dont scan again)
|
|
say X-Y == 1, then to optimise, we need to only check the missing
|
|
face... at the moment, the DB structure is not that clever...
|
|
(file_refimg_link --> file_refimg_link needs a face_num?)
|
|
|
|
### BACKEND
|
|
*** Need to use thread-safe sessions per Thread, half-assed version did not work
|
|
|
|
Future:
|
|
Admin
|
|
-> reset face_flag
|
|
|
|
AI
|
|
-> rescan <dir> for <person> --> can do this on new image only
|
|
(optimised to only scan has_unidentified_face)... BUT if you change
|
|
thresholds on AI, or we get a new/better one some day, then it can
|
|
all images with faces, or if we 'reset face_flag' rescan all images
|
|
|
|
Admin
|
|
-> delete old jobs / auto delete jobs older than ???
|
|
|
|
### UI
|
|
|
|
### AI
|
|
* allow for threshold/settings to be tweaked from the GUI
|
|
- it would be good to then say, just run the scanner against this image or maybe this DIR, to see how it IDs ppl
|
|
|
|
|
|
### SORTER
|
|
* duplicate files - this sql finds them:
|
|
select d1.path_prefix, e1.name, f1.hash from entry e1, file f1, dir d1, entry_dir_link edl1, entry e2, file f2 where e1.id = f1.eid and e2.id = f2.eid and d1.eid = edl1.dir_eid and edl1.entry_id = e1.id and f1.hash = f2.hash and e1.name != e2.name
|
|
|
|
* date stuff
|
|
* exif processing?
|
|
* location stuff - test a new photo from my camera out
|
|
-- image is in dir, need to look at exifread output
|