[digikam] [Bug 150531] SCHEMA : add album password-protect feature

J-o-h-n- bugzilla_noreply at kde.org
Thu Feb 2 08:09:08 GMT 2017


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

J-o-h-n- <forgivenbyjc at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |forgivenbyjc at gmail.com

--- Comment #21 from J-o-h-n- <forgivenbyjc at gmail.com> ---
This is a complex request.  Though one which probably requires more
consideration.  Yes, it is true this feature could be used to hide embarrassing
nudes or compromising situations.  There are other situations which could also
need to be restricted from view.  Confidential information like financial,
contact, security camera locations, security vulnerabilities, corporate and
government intelligence.  This feature could also be used to speed navigation
when dealing with large collections by being able to hide albums and individual
photos.  Also ex-girlfriends or recently deceased avoidance.

There have been several approaches mentioned.  1> Changing permission or
encryption, 2> using 'hidden' tag, 3> using internal flag, and 4> add to filter
options.

Changing permissions or encryption (1) would require a large addition to the
code to implement in any effective way.  Too this approach would cause multiple
issues accessing the photos outside of digiKam.

Creating a special 'hidden' tag (2) and creating an internal flag (3)
approaches both require adding sub-routines (functions, programs, whatever) to
the code to control access to those photos.  With the internal flag (3)
approach, there would be the added sub-routines to maintain those flags.  In
either case, the database must be able to query with the ability to exclude
specific criteria.

This leads me to think the adding filter options (4) would be the best
approach. The most simple implementation would be to add to the filter tags the
ability to exclude (NOT include) tags.  Current tag filter ability is '+tag1
AND +tag2' (intersection) and '+tag1 OR +tag2' (union).  By adding exclude (NOT
include) tag filter option, this will add the ability for
'-tag1' (absolute complement)
'+tag1 AND -tag2' (relative complement)
'-tag1 AND -tag2' (complement of intersection)
'-tag1 OR -tag2' (complement of union)
In a future version, adding sub-expressions can be explored.  ie '+tag1 AND (
-tag2 OR -tag3 )' and '+tag1 OR ( -tag2 AND -tag3 )'
Though adding an exclude filter option (4) does not specifically address hiding
photos, doing so could be achieved using filter logic.  This approach could
later be expanded so a special hidden tag (2) or an internal flag (3) could be
used to control access to hidden photos.  Using this intermediary step (4) has
the added benefit of making the filter more robust.

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


More information about the Digikam-devel mailing list