JPEG + Raw Seperated during Import

Question

Hi!
I'm just starting out with Lightroom and ran into a problem.  Something makes me think it might be a bug, but not sure so I thought I'd ask.  When I imported files (did the copy) into LR, I created a folder structure based upon Year\Date\<original filename>.  These folders contain JPG + raw files (NEF).  Initially, I had a setting wrong on my camera that just started the filenames at 0 when I deleted all the pics from the card.  So, basically, I have dsc_0001.jpg, dsc_0001.jpg, and then another set of duplicates for the next day. 
When I imported it into Lightroom, it worked fine because of the folder structure.  However, I started reading that using dates for pictures isn't the greatest thing.  OK, so, I deleted everything and re-imported based on events.  So, I did...
Event\<filename>
This worked well until I ran into my duplicates.  Lightroom adds a -2, -3, etc to the find of the file name.  So heres a snapshot of the directory...
====cut====
-rw-r--r--  1 1000  1000   9889900 Jul 10 14:16 DSC_0071-2.JPG
-rw-r--r--  1 1000  1000  25936077 Jul  8 10:00 DSC_0071-2.NEF
-rw-r--r--@ 1 1000  1000      4135 Jul 10 14:16 DSC_0071-2.xmp
-rw-r--r--  1 1000  1000   8011250 Jul 10 14:07 DSC_0071.JPG
-rw-r--r--  1 1000  1000  23624762 Jul  7 15:16 DSC_0071.NEF
-rw-r--r--@ 1 1000  1000      4132 Jul 10 14:07 DSC_0071.xmp
====cut====
Now in Lightroom, it will show the duplicate JPG and NEF files because of the rename.  The "Treat jpeg files next to raw files as seperate photos" is not checked, but I think Lightroom is getting confused after the rename.  If I do a regular folder structure of "Year\Date" so it doesn't rename the files, everything works as expected.
I even tried to rename the file (in Lightroom) with the date-sequence number, but had the same results.
Is there a trick to get it to import both files, but treat them as a single photo after the rename because of a duplicate filename?

Answer 1

wiz562 wrote:
I started reading that using dates for pictures isn't the greatest thing.
If you are talking about including capture date in folder and/or filename, I think it's a pretty great thing.
wiz562 wrote:
So, I did...
Event\<filename>
This worked well until I ran into my duplicates.  Lightroom adds a -2, -3, etc to the find of the file name.
This is just my opinion, but I've found photo life to be a whole lot simpler by making sure all filenames in catalog are unique. It's not a requirement, but you're encountering one of those occasions when you'd not have the problem if filenaming convention assured uniqueness.
So, consider a filenaming convention like:
{date-time}_{camera-id}_{camera-file-number}.{ext}
I realize this makes for long filenames (and I've been trying to lobby Adobe for the support needed for shorter (shortest) unique filenaming which also assures alphabetic order same as date-time order, but so far to no avail), but has the advantages:
* alphabetic order same as date-time order.
* all filenames are unique
* "sequence number" associates image to original in-camera number, in case that should come in handy.
* it's informative.
* you never have to change naming when exporting (although you can if you want).
* you can determine which source photo based on exported filename alone.
I do:
{date}_{photographer-id}_{time}_{camera-id}_{camera-file-number}.{ext}
So things are naturally organized how I want upon export or when viewing in OS..., even when multiple photographers shoot with multiple cameras.
Anyway, "Events" may be best handled as collections and/or collection sets (and/or keywords...) instead of folders, which would be another way to solve your problem.
PS - If you're more of a minimalist, consider shortest unique naming convention (if tip needed, do tell...).
Rob