Project

General

Profile

Feature #8670

Allow for Setting tags and metadata on import

Added by Richard Wonka almost 6 years ago. Updated over 4 years ago.

Status:
Triaged
Priority:
Low
Assignee:
-
Category:
Lighttable
Target version:
Start date:
Due date:
% Done:

20%

Affected Version:
System:
bitness:
64-bit
hardware architecture:
amd64/x86

Description

When importing, I would like to be able to set some tags and metadata to all images in this import (film roll?)

e.g.: I am importing a shoot for a certain client at a certain location, so I want to add <jobname>, <client>, <location> to all images in this film roll. - It would make life easy to set all this and be done before hitting [import].

It would also be good to be able to set some defaults in this in the settings dialogue. e.g. creator, publisher, copyright ...

History

#1 Updated by James C. McPherson over 5 years ago

This is possible with current master, I expect it to be part of 1.0.4.

#2 Updated by Richard Wonka over 5 years ago

Very cool. Now the only problem is that this option is not visible during import from camera, but only during import from a folder.

#3 Updated by Simon Spannagel over 5 years ago

  • % Done changed from 0 to 10
  • Status changed from New to Confirmed
  • Target version changed from --- to Candidate for next minor release
  • Category set to Lighttable
  • Tracker changed from Bug to Feature

#4 Updated by Richard Wonka over 5 years ago

Will it be possible to set tags and metadata in the import dialogue also when importing from camera/card?

I would like to not only set the defaults for this in the preferences, but also to override them for a specific import. (e.g. location related stuff or which job this import is for, etc...)

#5 Updated by Richard Wonka over 5 years ago

This is now working nicely when importing folders.

The values set there then overwrite the defaults in the preferences, it seems. Is this expected behaviour?

It would now be nice to be able to set these tags also when importing from camera.

#6 Updated by Tobias Ellinghaus over 5 years ago

  • % Done changed from 10 to 20
  • Status changed from Confirmed to Triaged

Yes, that's intended behavior.

Using these settings when importing from camera shouldn't be hard to add, maybe someone wants to add it?

#7 Updated by Richard Wonka over 5 years ago

Tobias Ellinghaus wrote:

Yes, that's intended behavior.

Ah, okay.

Using these settings when importing from camera shouldn't be hard to add, maybe someone wants to add it?

The tags set are used when importing from camera, but - different from folder import - I can not overwrite/change them when importing from camera. essentially, my request is just about adding the same input fields that are present in folder import to the camera import dialogue.

As for overwriting the settings with every import, I would like to suggest to make it possible to set the default values for these tags in the preferences and then the possibility to override the default during import without changing the default values. So the next time I run an import, the tags are again set to what I put into the preferences (which is likely what I want to use most of the time) and I then get to add/change what applies for this particular import.

That way I can for example add a default set of tags to every import and add stuff that only applies this once without having to remove these one-off tags on the next import.

#8 Updated by Jérémy Rosen over 5 years ago

Lua will be able to do that, does it make sense to clutter the UI or would a specific script for your need be enough ?

#9 Updated by Richard Wonka over 5 years ago

Well, the functionality is there already, it has just been omitted in one of the import dialogues.

#10 Updated by Tobias Ellinghaus over 4 years ago

  • Status changed from Triaged to Fixed
  • % Done changed from 20 to 100

Since import from camera got removed this feature request is obsolete now.

#11 Updated by Richard Wonka over 4 years ago

Import is back. Issue de-obsolitised?

#12 Updated by Tobias Ellinghaus over 4 years ago

  • % Done changed from 100 to 20
  • Status changed from Fixed to Triaged
  • Target version changed from Candidate for next minor release to Future

Probably. What a mess. :)

Also available in: Atom PDF