Skip to main content
Inspiring
May 26, 2011

P: Date Created Field is not accepting correct date?

  • May 26, 2011
  • 11 replies
  • 639 views

In the IPTC field Date Created...I enter 1906-01-01 and hit return....the field is now populated w/ 2042-02-6. Lightroom says that the metadata has been saved with the original file, but when I look at the image in Bridge (or one that has been exported from LR...) I get the correct date that I entered (1906-01-01).

How can I get Lightroom to display the Date Created that is imbedded w/in the file?

btw I'm using MacOS 10.6.7 & LR 3.4.1.....thanks!

This topic has been closed for replies.

11 replies

Participating Frequently
September 29, 2011
Still is the case when exporting in the 3.5 official release. Dates in file names are still buggy...
Participating Frequently
August 24, 2011
I just tried it out in 3.5 RC and it looks to have been corrected in the metadata panel inside Lightroom, but the error still occurs when I export the file with the year in the file name, just as before...
Participating Frequently
August 24, 2011
great to hear! thanks!
johnrellis
Legend
August 24, 2011
The release notes say this is fixed in 3.5RC:

http://blogs.adobe.com/lightroomjournal/
Participating Frequently
July 4, 2011
Thank you all very much! I look forward to future updates of LR.
Participating Frequently
July 3, 2011
I'm having a strange metadata/date issue when exporting images. I have images in my LR catalog going back to 1885 and they're all dated accordingly in the metadata. When I export to the hard drive I like to have the filenames be YYYYMMDD, followed by the file name. What's weird is that all the dates before about 1934 totally get screwed up. A photo from 1890, for example, is exported with a date of 2026. 1932 becomes 2068. My iPad will sort them with the oldest ones at the end of the total library, and the Finder obviously sorts them by year and puts the batch from 1885 to 1934 at the end.

This came up in Lightroom 3 and has never seemed to resolve itself. Worked just fine in LR 2 and 1.

Any thoughts? It has been driving me crazy for a while but seems to just be a bug.

David__B
Adobe Employee
Adobe Employee
May 27, 2011
I reported the issue to the LR developers and it sounds like they've already isolated the cause. Its slated to be fixed although I can't say specifically when. Thanks again for letting us know and the group input.
Inspiring
May 26, 2011
Thanks David...Since I can still output to the proper data, I'm not going to sweat it. I'm using that field to date code a bunch of family images from the early 20th century. It seems to me that it only affects pre-1933 dates as well.

Best, Adam
johnrellis
Legend
May 26, 2011
See this thread for the likely cause of the bug:

http://forums.adobe.com/message/37029...
Geoff the kiwi
Community Expert
Community Expert
May 26, 2011
Thanks David, I had an idea it is a Mac OS thing as I can reproduce it as well with 10.5 but think it comes from inside the OS and the way MacOS deals with dates but what I have no idea!