Serious File Import / Renaming Problem for Professional Photographer

Question

I'm a professional photographer who imports thousands of photos from several CF cards from several photographers using several different brands of cameras. I recently came across the following problem.
CASE #1: If you import a CR2 and a NEF file into the same directory, both with the same capture time, in two different import processes, and rename them at the time of import to the capture time of HHMMSS, then you end up with two files in the same directory with the same filename and different extensions. This is a big problem. It's common to have two photographers shooting with two different camera brands at big events. When this renaming issue happens, and those filenames remain the same, only a single XMP file is ever written. Additionally, only a single JPG can be generated from the RAW file; one will overwrite the other.
CASE #2: If you import a CR2 and a NEF file into the same directory, both with the same capture time, in a single import process from a local drive, and set the import to rename the files at the time of import to the capture time of HHMMSS, then you end up with an error message that states that neither file can be renamed. I haven't hit this in my environment but I uncovered it in my testing for this issue.
CASE #3: If you rename a CR2 and a NEF file in the same directory, both with the same capture time but with different file names, and set the Library > Rename Photos... process to use the capture time of HHMMSS, then the files will be renamed properly, except one of the files will automatically have a “-1” appended to it (prior to the differing extension). This is the way I think it should work for both CASE #1 and CASE #2.
I only just now discovered this problem. I'm not sure it was present on previous releases but if so, I'm scared to think of how many files were never exported as JPGs to my customers. In the last event that I processed, I discovered 20 photos (40 files) that were shown to exhibit this problem.
How do I get this addressed by Adobe? I don't want to use the Rename function after every muliple card import just to work around this problem!

Answer 1

RobGreerPhotography wrote:
It sure does feel like you're trolling here. Given the fact  that I successfully manage over 100,000 client images annually and I've been  successfully following this naming convention for the last six years, I  think I know a little bit about how I need to go about manaing my own  files. File naming is key component of my DAM and my office automation.  Until you've walked in my shoes for a few years, you can't speak to the  best way to run my business or my file management. Well, you can, but  you'd probably be wrong.
My comments were definitely not "trolling", unless you mean I had a hook in the water looking for a bite. In which case: success!
You may have all the reason in the world to think your way is the best, but the more you explain it, the less I am convinced. Even pros have to reconsider less ideal workflows. In fact, it is often pros that insist on sticking to old busted workflows that were crafted around earlier, less capable tools.
And, yes, depending primarily on a filename created at import (before you have even looked at the images) for the core of your DAM workflow is, well, not DAM. Your blunt, and yet strangely constricted, file-naming pattern is obviously not really helping you, and yet your first response is to blame the tool. There is a famous platitude in there somewhere.
There is a lot of good advice else-thread. You should at least heed some of it. Because the /combined/ experience here will always exceed personal experience.
You have been given a lot of good workarounds for your situation, and gentle advice to consider how image metadata can be used post-import in a more nuanced manner, as well as a place to raise a feature request.
It isn't trolling to point out that none of this seems to satisfy you, and it appears to be because some folks are not immediately agreeing whole-heartedly with you.  But you are welcome to take what you want, if anything, from my comments.