Bug 183425

Yes that's a feature.
It's not clear from the UI if it's AND or OR. In the tags filter sidebar this can be adjusted via context menu
Marking as wish to add UI option (along the same line as right sidebar filter; share settings??) in the future. Not 0.10.0, for technical reasons as well.

Hello:

Digikam version 1.0.0-beta1 with KDE 4.3.00, Ubuntu Jaunty.Search related:

Advanced search with 1 search group and "Meet all of the following conditions":

Return pictures with 2 or more tags give the "OR" condition and not the "AND" condition. 

In other words:
The result is all the pictures with OR [tag1] OR [tag2] instead of all the
pictures that have [tag1] AND [tag2].

If this is a feature, it is misleading. 
There is no easy way to select pictures with [tag1] AND [tag2]...
OTOH it is easy to select "All pictures with tag1 OR tag2" by making another search group.

Hope that this can be resolved. Selecting pictures by help of multiple tags is crucial.

Created attachment 37200 [details]
Use field operator for tagid in-tree search

This patch uses the field operator for the selected tag ids, which means that the Match All / Match Any choice is applied to the selected tags.

I dont feel this intuitive, the Match All / Match Any should apply for connecting the fields in different lines, and tags is one single field (think of parentheses). Compare this to albums: Here, there is no sense at all in a "Match All" connection. And if the albums combo box always uses Match Any and the tags combo box adheres to the settings it's not coherent
 For me, to make this intuitive, inside the tags combo box need to be a separate option.

Nadav, Paul,

Do you see Marcel comment #3 ?

Gilles Caulier

Hi Gilles :-)

I saw Marcel's comment.

To me, what seems intuitive is...
Clicking a TAG from a listbox and then it shows on a textbox list of TAGS with a tiny sign in front of it ( plus/minus sign ) and a tiny "X" sign at the end of the TAG. 

clicking the TAG switches between + (AND) and - (NOT) and clicking the "X" removes the TAG.

Not sure what to do about the OR option.

Example:
+FLOWERS(x) +ECO(x) -BLUE(x)

There's still a lot which can be improved here.

This is clearly a bug.  The fact that the search options for a search group say "Meet All of the following conditions" means it should do just that, and all selected tags and all selected albums should be combined with AND.  Any other behavior is clearly a bug.  If one wants OR, there are other options to do that, either using "Meet Any..." or using additional search groups.  Am I missing something here?!

P.S.  It would be nice if the left-hand tags pane allowed one to select multiple tags simultaneously -- combining them with AND -- by using Ctrl-MouseClick.  This is a feature in many treeview widgets in many frameworks and would be very useful.  Same with left-hand album pane, to select multiple albums.

....Aaaaahhhhh...  I am missing something here...  I see the problem with tags vs albums, and with AND vs OR.  I think intuitively one expects albums to be combined with OR because another interpretation doesn't make sense.  But when the search group says "Meet All of the following conditions" and you select multiple tags, one expects the tags to be combined with AND.  At least, that's what I would consider to be intuitive, and that's what I would vote for.

To comment #8 : Multiple selection of tag is already implemented through this GSoC 2013 project :

http://community.kde.org/Digikam/GSoC2013#digiKam_Tag_Manager

Gilles Caulier

When the search group says "Meet All of the following conditions", the checkboxes allowing one to select multiple albums shouldn't even exist.  The album pull-down should only allow one selection.

C Doe,

What's the status of this file using last digiKam 4.2.0 ?

Gilles Caulier

I'm still using 3.x under Ubuntu Trusty.  Not sure if I can install 4.x

C Doe, Nadav, Paul,

This file still valid using digiKam 4.10.0 ?

Gilles Caulier

New digiKam 4.11.0 is available with official PKG installer for OSX.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

What was the final decision on whether this is a bug or a feature, and if a bug, what to do about it?

C Doe,

The question is : problem still reproducible with recent release ?

Gilles Caulier

The problem is still reproducible in digiKam 3.5.0 on Ubuntu.  Haven't been able to test the most recent release.

This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release ?

It available at this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier

Created attachment 104891 [details]
Draft for applicable operations on chosen tags in extended search

For tags, the user can select if the images to find must be in all the chosen tags or at least in one.

The patch will be uploaded here: https://bugs.kde.org/show_bug.cgi?id=353331

Git commit 660782be8137d8448ef10e5e944a2dd213d781cc by Mario Frank.
Committed on 11/04/2017 at 17:27.
Pushed by mfrank into branch 'master'.

Added an overall improvement of fuzzy, duplicates and extended search.
1) Users can now restrict the results of fuzzy image/drop/sketch search to be in specific albums.
2) Users can now select both tags and albums in duplicates search and restrict the set of images in which duplicates are searched with logical operations (in selected albums or/and tags, in selected albums but not tags and vice versa and only in
selected objects of current tab)
3) In extended search, the tags selection can also be restricted such that images must be either tagged with at least one of or with all selected tags.
Related: bug 353331, bug 300565

M  +7    -1    NEWS
M  +31   -3    app/utils/searchmodificationhelper.cpp
M  +11   -0    app/utils/searchmodificationhelper.h
A  +307  -0    libs/album/albumselectioncomponent.cpp     [License: UNKNOWN]  *
A  +121  -0    libs/album/albumselectioncomponent.h     [License: GPL (v2+)]
M  +248  -173  libs/album/albumselectors.cpp
M  +34   -19   libs/album/albumselectors.h
M  +7    -0    libs/database/coredb/coredbsearchxml.cpp
M  +1    -0    libs/database/coredb/coredbsearchxml.h
M  +1    -0    libs/database/dbjobs/dbjob.cpp
M  +11   -0    libs/database/dbjobs/dbjobinfo.cpp
M  +4    -0    libs/database/dbjobs/dbjobinfo.h
M  +119  -30   libs/database/haar/haariface.cpp
M  +30   -8    libs/database/haar/haariface.h
M  +32   -10   libs/database/item/imagelister.cpp
M  +44   -0    libs/database/item/imagequerybuilder.cpp
M  +6    -4    libs/settings/applicationsettings.cpp
M  +3    -0    libs/settings/applicationsettings.h
M  +11   -0    libs/settings/applicationsettings_miscs.cpp
M  +1    -0    libs/settings/applicationsettings_p.cpp
M  +2    -0    libs/settings/applicationsettings_p.h
M  +1    -1    utilities/facemanagement/facescandialog.cpp
M  +69   -22   utilities/fuzzysearch/findduplicatesview.cpp
M  +83   -21   utilities/fuzzysearch/fuzzysearchview.cpp
M  +1    -0    utilities/fuzzysearch/fuzzysearchview.h
M  +6    -1    utilities/maintenance/duplicatesfinder.cpp
M  +1    -1    utilities/maintenance/duplicatesfinder.h
M  +4    -4    utilities/maintenance/maintenancedlg.cpp
M  +2    -1    utilities/maintenance/maintenancemngr.cpp
M  +72   -27   utilities/searchwindow/searchfields.cpp
M  +18   -4    utilities/searchwindow/searchfields.h

The files marked with a * at the end have a non valid license. Please read: http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page.


https://commits.kde.org/digikam/660782be8137d8448ef10e5e944a2dd213d781cc