edward_allen_2426703's profile

195 Messages

 • 

3.6K Points

Sat, Jun 11, 2011 2:34 PM

24

Lightroom: Auto Import to folders organized by date

The Auto Import feature could be really useful but it does not allow users to handle files in the same way as the "standard" import routine within Lightroom, and this makes is problematic to use.For example:I use a Canon 7D which auto imports images into the "final destination" folder, then when I open Lr I can run the Standard import routine to apply metadata & presets etc. The cataloguing structure I use is a main folder named 2011, and each new batch of images goes into a separate folder named automatically by the date the image was shot, which makes things really easy.Auto Import does not appear to allow me to replicate this simple and effective workflow, and it would be really useful if it did.Any suggestions welcomethanks for your interest

Responses

Champion

 • 

1.4K Messages

 • 

24.5K Points

3 y ago

@Ralf Bruechmann,

Yes, it is. 

This particular feature request has accumulated 19 votes over the past 7 years.  How do we know that? - because all of the threads requesting the same feature have been accumulated and counted as a group (see the top of the page).  If instead there were 19 disparate posts scattered across 7 years, would Adobe have any easy way to determine the strength of support for a particular feature.?

Whether it is a Problem which links to a bug, a Question that links to an answer, or an Idea that links to a Feature Request, aggregating them makes it easier for customers to find definitive answers.  If you are searching for "Auto-Import Folder Organization?" would you rather find a single thread that contains the whole of subject including Votes for, comments made by Adobe Staff, and potential workarounds, or would you rather search and find a dozen or more posts that might contain no answers, or only partial answers? 

Adobe's system for tracking issues and requests works best when a single bug, feature request, or point of user confusion tracks to a single source of customer-supplied information.  That way, when it is fixed, implemented, or answered, everyone on the thread receives the answer.  Let's say for this thread, that 19 people have asked and that another 25 (following) are interested in the answer. Let's also say that Adobe implements the features, with a single post to this aggregated thread, they can notify everyone of the implementation-regardless of how long ago they made the post.

The length of time a thread has been active (or in this case inactive) matters less than the total and continued support of a request.  A chorus is always louder than a single voice. 


 

29 Messages

 • 

592 Points

Okay - it makes sense from a categorizing point of view, but:

why does nobody work on a solution ?
As this feature is allready implemented for "normal" imports it shouldn't be difficult to implement this for auto-imports, too ...

3 Messages

 • 

146 Points

What would we need to do to get this feature request to the top of the pile? I reckon that many users would appreciate it once they knew about it and this minor implementation was made to make it more usable

1 Message

 • 

64 Points

Love this idea. Can we get it some love, please?

35 Messages

 • 

560 Points

On the issue of feature requests and bugs....

Had a quick chat with a friend with decades years of experience in UX. The challenge from their experience is summed up by discovering that forward looking companies don't typically look backwards. Old bugs aren't on the table.

There's a challenge here because the user community eventually loses motivation to report. Some people don't know how to report. Or, you find a work around, you just cope with it, you decide not to do that, you move to another product.

Fundamentally, there needs to be an internal champion who is prepared to take on the challenge and own the problem. In the ideal case, they have enough product experience that they could be seen as a subject matter expert for the product. 

They all use a voting / count system to figure out whether to pay any attention to an issue/bug. So to paraphrase, every vote counts, you need to  vote.  

This forum is the place to be the squeaky wheel.

But don't squeak just to vent, you need to articulate the problem in repeatable steps, what is the observed outcome, what did you expect to happen and what is the (business/design) impact?

Use a numbered list to define the steps you went through.

Developers need specific scenarios and use cases to test. They need to find bugs in a methodical repeatable way. They need enough detail to find the edge cases.

There's also the challenge where the end user and the internal developer don't use the same terminology....

(edited)