There have, from time to time, been other similar threads (about using DT to index photos). The concensus, which I (as an amateur photographer) think is right, is that it is better to use applications which are designed specifically for photographers.
For what it’s worth, when I used Windows (fortunately now many years ago) I used iMatch and found it excellent in every respect. Since using a Mac it’s taken me a long time to find anything comparable but recently I’ve been using Photo Mechanic Plus—not cheap but very good indeed.
I know I’ve not really answered your specific questions about how DT might fare as a catalogue for photos but I do think an application designed for that use is a better bet. That said, there’s nothing to match the flexibility of DT for handling quantities of disparate documents. It is a superb application with unsurpassed support here.
It is not optimized for handling image metadata (exif), does not read natively all the exotic file formats, nor is it particularly fit at batch generation of thumbnails/previews, nor provides conversion and export tools.
I have not much use for EXIF data, this was one of my biggest complains about IMatch.
The creation and modification dates could be valuable, but not much more.
IMatch versions after 3.x took hours or days to import a myriad of EXIF data from all images and converting a database from 3.x to 5.x (or whatever version that was), was a near impossible task … at least when your database was great and used several, partly exchangeable disks.
I used it mostly to sort images and used tags to find images.
The same would be possible with DT … with groups and tags, also ratings would be possible
Also, DT previews / thumbnails seems to work fine with both JPG and NEF files and I don’t need other formats.
In case you can already see e.g. keywords of your photos in finder then you can see them as tag in DT.
You are not able the see exif data! I checked this a few min. ago.
There are 2 very useful programs in Mac app store:
Photostatistica - analyses several 1000 photos rapidly by ISO, aperture, time…and generates helpful diagrams. I recently analysed a selection of appr. 100k of my photos.
ApolloOne - a picture browser which renders really fast and has a high render quality. The app needs/generates no database. It shows exif, iptc, xmp and renders gps data on map (if available). Keywords if are visible and editable. You can batch rename…and much much more.
I bought both app, so I can’t see the price any more, as far as I remember each was about 20 € or below. Test period is available.
Well it depends on what you use the images for. I initially got DEVONthink as an image reference system before it became something bigger.
I store images and short video clips for concept references and use the tagging system and custom metadata to provide more utilities for them. Sounds like what you use them for too.
My image reference group in my reference database is about 8gb with over 3000 images and video clips and growing. All imported. So far so good.
Still far from your projected hundreds of gigabytes, so I’m not sure what the limit is. If I remember correctly mentioned somewhere in this forum it’s the number of words that affects the performance, not the size of database. Perhaps someone from the team can shed some light?
Some other functions you may find useful if you use it like I do:
Annotations on the image. Creates an external file that has bidirectional link
URL to link back to the original site where the reference comes from
DEVONthink’s url scheme to link to other documents and vice versa (all back links are indicated)
I don’t really do much with the images.
This is about 3 TB of NEF and JPG files from my former photography.
I use an Image database mostly to find and rate images, that’s all.
This way, I can easily find the best from any given shooting to send them out or make prints from them.
Also, I would tag them for being selected and cropped to find any relevant subsets.
And finally, I am trying to strip the amount down to upload more of my local content to OneDrive … an image database can greatly help in such an effort.
From what you wrote, I could try to index images with DT …