Nicely done, but if you're a power user of CDFinder and you're looking for a replacement, keep on looking.
On the plus side:
- CDFinder import. Just make sure that you're running CDFinder in English (temporarily disable all languages except English in CDFinder's Get Info window) while you're exporting your catalogs, because DiskLibrary won't import localized CDFinder export files.
- Saved Searches (aka Smart Catalogs), although they're slow, at least on a PowerBook G4/1.67.
- catalogs Owner attributes
On the minus side:
- A single catalog file (Library Data.disklibrary). This may work if you intend to catalog 2 drives and 10 CDs, but I have already over 1000 CDFinder catalogs files occupying over 300 MB disk space. It will be a big pain to maintain all that data in a single file. Especially if you want to synchronize with another Mac or backup your important data regularly: each time you make a single simple change to your database the *whole* big file will change its modification date, i.e. the whole big fat file will be processed on sync/backup! (And yes, I've read about "Compacting the database (Advanced setting)" in the Help file.)
- Yet another Image Cache folder with thousands of files...
- Won't locate files in Finder with uncommon Unicode characters in their path (e.g. Central European). Is the app using AppleScript to get the location? Because that's exactly the point where AppleScript fails!
- Doesn't catalog Finder Labels, Finder Comments, Version, File Type, File Creator, doesn't correctly catalog application bundles.
- How do you *update* a catalog?
- The search should include "ANY field contains". I can't possibly always remember if a search string is contained in the file name or in the metadata or wherever.