Id like to see support for a real RDMBS (oracle, postgres, mysql, db2, etc) for the image catalog. I have 3 laptops that share a common repository of a little over 100K files. I use ACDSee personally, but I would love it if I could convince the wife to do so also (she uses Elements; we have no reason to standardize on an app as there is no easy way to share ratings, categories, etc).
This DB would store:
- ratings
- categories
- keywords
- exif
- iptc
- possibly thumbnails (get rid of that damned ripcache)
- md5sums <-- so if I move a file to another location outside of ACDSee, it can quickly generate a new checksum for this file and compare it to ones that already exist in the DB, then ask me if I want to apply meta data from the file that is already in the DB. Oh god, would this rock.
<u>Use case</u>
My wife and I share a common image repository: G:\Grahics\Pictures (mounted from a unix server); inside of which, directories go by date and description; eg:
2005
- 2005-12-25 - Gift Giving <-- contains image thumbnails
- cr2 <-- original canon raw files marked read only
- dng <-- converted cr2 -> dng files; these get editted
- 2005-12-25 - Christmas Parade
- 2005-12-26 - Night time sleigh ride with family
2006
- 2006-01-01 - The bender
- 2006-01-01 - Legion shoot
I use ACDSee, she uses Elements. We use separate programs because there is no real benefit to using a single one because we can't share ratings and categories so we do it all manually through thumbs, filenames and text files and folder names and we aren't willing to copy our sync our db's because there is no reason to.
As an aside, I'd also like to see better integration with other features like Duplicate Finder. An 'Exact Duplicate' finder action would be simple: Catalogue the images in the first pass and add an md5sum, then, to find duplicates all you need to do is:
SQL> select filename, md5sum from (select md5sum, count(*) from image_data where (path like '%some path string%' or path like '%some path string%') group by md5sum having count(*) > 1);
In oracle, this can be done in a second.. instead of waiting 20 mins for ACDSee to chug through it's temporary db of files. </forums.acdsystems.com/style_emoticons/<#EMO_DIR#>/sad.gif" style="vertical-align:middle" emoid=":(" border="0" alt="sad.gif" />
So I understand that this would see limited use, but there are a number of photography companies out there that would kill for a feature like this; but I know that most of your users wouldn't use it. Perhaps there needs to be an 'Enterprise Edition'?
The reason that I don't like the NAS based DB file is because it is too easy for a single file to be corrupted and accessing a huge file over the network (even using gig-e) would be performance restrictive. No, it makes more sense to have something running on a server that serves up the information to the client application. And rather that reinventing the wheel, it also makes more sense to just use existing systems... postgres, oracle, mysql, etc [my preference is in that order]. MS Access support would be a waste as it is nothing more than another version of the ACDSee DB; file based and slow.
Take care,
Dave.
PS - I know that most users wouldn't use this so this will likely fall upon deaf ears but I have to ask anyways. </forums.acdsystems.com/style_emoticons/<#EMO_DIR#>/smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />
Posted On June 11, 2006 - 05:36 AM (3 years ago) (
Permalink to this post)
New Content Since Last Visit
No New Content Since Last Visit
