photoprism VS exiftool-vendored.js

Photoprism does indeed have features that are added under a subscription. All of the functionality is the same, subscribing just adds customization to your interface, and it allows unlimited reverse geocoding (otherwise, it is rate-limited, according to the documentation). There is a limit to the maximum resolution as well. No reason why you can't use the product for free, however.

Was looking at an old thread on this, https://photoprism.app/features was a suggestion you haven't gotten in this thread yet.

I started using Photoprism instead a couple years ago and have been quite happy with it so far. I'd recommend looking into that project. Their roadmap is here. Memories like you asked is in there, but I doubt it's coming anytime soon as it seems they have other priorities and a very small team.

* They have the community version/premium model. Differentiators of premium (from https://photoprism.app/features):

PhotoPrism has a bunch of photo management features, but it's self-hosted so you'd have to run it yourself at home or on a VPS.

Is Photoprism in the ballpark of what they might be looking for? They have a demo that you could try searching for the metadata you'd plan to use.

Have you seen Photoprism? It does some of the things you're saying. Organization is in a dated hierarchy, then you search from there. As far as editing, I guess you could try mounting the WebDAV and importing that to your library. Could probably also network mount the /originals/ directory from the NAS and then simply import the sidecar files generated. Apparently, multiple users feature is coming soon, until then the admin account could be used like a shared account.

You could put something like Minio (https://min.io/) for syncing via S3 and Photoprism (https://photoprism.app/features) for sharing / tagging on the VPS. Look into Docker to ease the pain of hosting / configuring services on a server. The downside is that you still have to manage the VPS, plus pay for the hosting and the domain name. The upshot is that this adheres to "freedom" and keeps your home network secure.

Know that although ExifTool is written in perl, you can run it in "batch mode" which makes it quite fast--only a couple of ms to parse a file. I've written an open source library to manage the subprocesses for you if you're using node.js (and I also wrote the ruby variant ages ago):

https://github.com/photostructure/exiftool-vendored.js

The frontend is in Vue. Both the FE and BE are in TypeScript.

Parallelism is provided by https://github.com/photostructure/batch-cluster.js/

Metadata reads and writes are via https://github.com/photostructure/exiftool-vendored.js/

My more nerdier blog posts are tagged here: https://photostructure.com/tags/coding/

if you're looking into doing stuff with EXIF, there's a really good library that's also typed: https://github.com/photostructure/exiftool-vendored.js

I needed a good Node wrapper for ExifTool and wrote https://github.com/photostructure/exiftool-vendored.js

When I saw how slow it is to fork child processes in Windows, I then realized I wanted to run ExifTool in "stay-open" mode, which meant I needed to manage 1 or more long-lived child processes that communicate via stdin/stdout, so I wrote https://github.com/photostructure/batch-cluster.js

I also really missed scala's `lazy` operator, so I built that (and several other small, helpful functions/classes) that I documented here: https://photostructure.com/coding/uncertain-lazy-forgetful-a...