How do I propose a change to export function to add images to library upon export

Processing
1

I am not sure where to propose a change to the export function for Darktable. What I would like to see is the option to add or not add the exported image to the Darktable library upon export. This would be a useful feature to improve the digital asset management capabilities of Darktable. I appreciate that a developer would have to see value in such a suggestion to invest their time in changing the code.

2

In the bug tracker on github.

Sounds doable in lua. I thought it existed already but couldn’t find it.

3

Is the bug tracker the most suitable place as it is not a bug but a suggestion for a new feature. It would be nice if it was just a tick box in the export module.

I have become really impressed with how Darktable has matured as a digital asset management tool over the last few versions.

4

Yes, I did not say it to waste your time.

1 Like
5
6

Thanks for the the link to GitHub. I have posted my request and it is now up to the developers to see or not see merit in this suggestion.

7

Bear in mind that storing exported images to the DB will likely increase the DB size by a few orders of magnitude. I just checked my library.db, and it averages about 13 KB per image. Checking the size of my JPEGs, they tend to be in the range of 10-14 MB. It may be a useful option for you, but be aware of the side effects.

8

The actual image size would not be adding to the database size. What I am proposing is that the database knows the image exists and we can see it in our library. So I guess 13kb per image would be added. I don’t feel that would stretch computer resources too much. Thanks for reading my post and making constructive comments. I have made a request for this feature on GitHub and the developers can decide it has merit or not.

9

So in short, you propose an option to import the image file just after it is generated through the export module?

Just a few points that come to mind:

  • I rarely export to the directory where I have my raw file. So that means I wouldn’t see the exported image next to the original anyway.
  • And iirc, dt switches to the import directory. As I often export to different directories from one “raw” directory, that would break the flow of the work (having to switch back to the original folder after every export)
  • Sometimes I redo edits, and want to overwrite an export. That should be taken into account as well (implementation detail, but still)
10

@rvietor I have suggested a tick box in the export module so that it is only selected by those that would benefit from the feature. I have seen this feature in other programs and it was very helpful. It would also let me see that I have successfully exported the image as well. I don’t see any issue with wanting to overwrite a previous export. But it is up to the developers to see merit or not in my suggestion that I have placed on GitHub.

11

Well, in that case I won’t bother you with comments here, the more since I’m not a dt dev.

12

@rvietor I did appreciate you taking the time to read my post and offer constructive comments. I just know it is easy for me as a user to propose something that I want and expect the developers to magically do my bidding. The developers get bombarded with request and they have to decide what is worth their time. But I feel it is important that users can post suggestions and requests and others can comment in a constructive way.

Previously, I only used Darktable as a development tool and recently I have seen value in it as a tool to import and copy images from my SD cards and place them suitably into a folder structure. That is why I would like to have the edited Tiff images included in the library automatically. If I export a JPG to post on the internet or something else then I don’t need that added to my library. Hence the suggestion of a tick box.

13

This is not what you are asking for but could work …I use a little syntax with the variables when I export. Basically it will create the current image folder name automatically to a new root folder called Photoedits . So I have a mirrored folder structure for edits.

You can the create a collection to work with that or easily update that recursively to your library. The thing I use it for is to have that mirrored folder structure separate with clean folders with only the edited files so I can view or share the without clutter from xmp files or any other files…

It’s just a string in the export syntax box and saved as a preset…I’m sure you could actually use the same method to have it saved in the source folder if you desired…

EDIT:. This got me to thinking that I might be able to use a command line switch and have a separate library for my exports in the mirrored folders. Just to keep things separate and also he have to he option to separate them. Not sure I will but you could.