[digikam] [Bug 367700] It should be possible to search for more, if not all metadata fields.

[Glenn Washburn]

https://bugs.kde.org/show_bug.cgi?id=367700

Glenn Washburn <development at efficientek.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |development at efficientek.com

--- Comment #1 from Glenn Washburn <development at efficientek.com> ---
I'm running into an issue on 5.4 that this feature request would resolve as
well.  I'd like to search all images that have the GPano XMP namespace, but
there is currently no predefined search area for this (nor do I think there
should be).

bug 180268

I think a first iteration of this should create a new search section called
"Metadata".  In that section there should initially be one horizontal line of a
select box and a text input box.  The select box would contain a selectable
list of all metadata fields contained in every image known to the database. 
The text input box would be the corresponding value being search for.  Further
iterations can add search operators and value type selection.

Just below the metadata search fields should be a button labeled "Add search
field" or something like that.  Pressing the button would add another metadata
search field as an AND clause in the query.  Further iterations may choose to
add the ability to modify the AND to an OR or add other boolean logic
operations.

As I understand it the search currently can only search over data in the
database.  Not all (actually most) of the image metadata is not stored in the
database.  So this issue depends on a as of yet non-existant bug to change the
schema and import all image metadata.  I don't think the importing should be
too difficult since DK already gets and displays the metadata info in the
metadata tabs.  As a side note, the maintenance mode which syncs image metadata
to database should be taken into account as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.