Bug 237806 - Rename using database entries
Summary: Rename using database entries
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-metadata (show other bugs)
Version: 1.2.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-16 11:42 UTC by Michal Thoma
Modified: 2022-02-01 06:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 2.3.0
Sentry Crash Report:


Attachments
New rename option (43.72 KB, image/png)
2010-05-19 21:21 UTC, Andi Clemens
Details
Multiline comments (203.23 KB, image/png)
2010-05-19 21:39 UTC, Andi Clemens
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Thoma 2010-05-16 11:42:01 UTC
Version:           1.2 (using KDE 4.4.2)
OS:                Linux
Installed from:    Ubuntu Packages

Right now digiKam has pretty cool renaming capabilities though yesterday when doing extensive piece of works I discovered some limitations.

We have now ability to rename file using file metadata. This is good, but we first need to write metadata to files. This metadata renaming function fails to work when we don't write descriptions etc. to to files.

So I think there should be another option in rename - Database. Where we would be able to select - Digikam description, digikam rating, digikam keywords etc. And that would work regardless of what is written in metadata of the original files.
Comment 1 Andi Clemens 2010-05-19 21:21:53 UTC
Created attachment 43739 [details]
New rename option

I started to implement something, right now it is very limited (to be precise, only one keyword exists :-))

I'm not quite sure which database values I want to display here and how to present them to the user. Need to evaluate this first...
Comment 2 Andi Clemens 2010-05-19 21:39:07 UTC
Created attachment 43740 [details]
Multiline comments

Multiline comments are cleaned up to match a single line, otherwise newline characters mess up the filename.
Comment 3 Michal Thoma 2010-05-20 14:08:07 UTC
From my point of view, the Comment is most important.

There after the copyright data, like author etc.

I would like also to see the possibility to somehow include keywords though here it's get really confusing as there could be multiple keywords and multiple hierarchies...

My working scenario for which I like to have keywords renaming is as follows:

I have couple of images in various albums and I'm making some selection for purpose. For example I need to select some images of Mountains, Rivers and Monuments. So i create following keyword structure: My Tags > Selections > Selection #1 > Mountains | Rivers | Monuments

I select the images and tag that with respective keywords.

Then I export all images to new album out of archive (like ~/Images/Selection/Selecion #1/*) and I like to rename the images according to keywords with following pattern [db:all_descendants_of_keyword:"Selection_#1"]_###.ext so the result will be something like Mountains_001.tif, Rivers_001.tif etc.

Is it possible?
Comment 4 Michal Thoma 2010-05-20 14:29:03 UTC
Little bit more thinking I feel that there should these possibilities for keywords renaming:

-All keywords (option - separator) - unsorted list of all selected keywords with selectable sparator.

-All descendants of given keyword (options - separator) - keywords sorted by level, divided by separator. If separator is slash "/" it should result in recreating of directory structure according to tags - which is in fact very desirable and useful function unfortunately still missing in digiKam.

-First or second or third... descendant of given keyword ...

I feel these are most useful possibilites - the others are:

-All top level keywords
-All bottom level keywords 
-All parent keywords
etc.

Though I don't find much practical use for these.
Comment 5 Andi Clemens 2010-05-22 16:30:26 UTC
Sure this should be possible... Right now I only added the most common values in SVN trunk, like comments, author, aperture etc... the rest needs to be analyzed a little bit more. Keywords can, as you already mentioned, really mess up the filename if they are too deeply nested. Need to check what I can do.
Comment 6 Andi Clemens 2011-10-27 16:17:57 UTC
I guess I will close this bugreport now, since the primary goal has been fixed.

Michal,
please open a new bugreport for adding keywords to file renaming, if this is still a needed feature.