elodie

Pasting my own answer from [0]: --- For myself and my family, I wrote my own tool [1] that runs everyday on an "input folder". A quick google on "github photo organizer" shows a lot of others having done the same :) It organizes all traversed photos by date (extracted from exif or from filename), and puts them in a "failed" folder if it can't parse the date. If any photos get the same name, they are either deduped because they are exact duplicates, or are marked as conflicts (e.g. A.jpg and A_conflict1.jpg) if they are different. Last time I used it for a large input it took 3h for 200GB, though I suspect network latency was the main bottleneck. It's around 300 lines of python - verify the code for yourself if you want to use it! You probably also need to fork it if you don't intend to run it on a Synology NAS. However, as I mentioned las

I moved my photos to Synology 5 years ago and have never looked back. I did some very thorough research into a number of options including iCloud, Dropbox, Google Drive, etc. and they all had some really odd behavior which kept me from using them (i.e. getting select photos into iCloud Photos was impossible - it was every photo taken or nothing ... and don't get me started on iCloud Drive's incompatibility with iCloud Photos). Right now I'm using DS File from Synology to transfer photos to my NAS and from there there's a script [1] that organizes it into a destination folder which is then synced to Dropbox and Google Photos simultaneously. So I get to use Google Photos as my primary photo viewer but it's just essentially a cached copy of my library (which I could trash and restore at any point). I have a series of blog posts [2] about my

For myself and my family, I wrote my own tool [1] that runs everyday on an "input folder". A quick google on "github photo organizer" shows a lot of others having done the same :) It organizes all traversed photos by date (extracted from exif or from filename), and puts them in a "failed" folder if it can't parse the date. If any photos get the same name, they are either deduped because they are exact duplicates, or are marked as conflicts (e.g. A.jpg and A_conflict1.jpg) if they are different. Last time I used it for a large input it took 3h for 200GB, though I suspect network latency was the main bottleneck. It's around 300 lines of python - verify the code for yourself if you want to use it! You probably also need to fork it if you don't intend to run it on a Synology NAS. However, as I mentioned last time I pitched this, elodie [2] mi