<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>384396</bug_id>
          
          <creation_ts>2017-09-05 20:10:47 +0000</creation_ts>
          <short_desc>Display faces sorted by similarity (pre-grouped) instead of album/time/..</short_desc>
          <delta_ts>2020-09-12 05:26:16 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>2</classification_id>
          <classification>Applications</classification>
          <product>digikam</product>
          <component>Faces-Workflow</component>
          <version>5.6.0</version>
          <rep_platform>Other</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>0</everconfirmed>
          <reporter name="Jens">jens-bugs.kde.org</reporter>
          <assigned_to name="Digikam Developers">digikam-bugs-null</assigned_to>
          <cc>caulier.gilles</cc>
    
    <cc>daniel-other+kdebug</cc>
    
    <cc>iwannaberich</cc>
    
    <cc>jmzd3an</cc>
    
    <cc>kartikx2000</cc>
    
    <cc>metzpinguin</cc>
    
    <cc>nicofo</cc>
    
    <cc>Niyaz.Batyrshin</cc>
    
    <cc>pouchard.alain</cc>
    
    <cc>stefan.mueller.83</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin>7.2.0</cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>1</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1699195</commentid>
    <comment_count>0</comment_count>
    <who name="Jens">jens-bugs.kde.org</who>
    <bug_when>2017-09-05 20:10:47 +0000</bug_when>
    <thetext>When detecting faces, there are often a high number of similar images (and identical faces in different images).
I would like an option where the newly processed images with &quot;unknown&quot; and &quot;unconfirmed&quot; faces are *already* grouped by face so that confirming a face (or creating a new one) is much quicker. 
Correcting such a detection can then be achieved by moving a face from one group to the other.

Note: I do not want the *images* to be grouped, but the *faces*. This means that images with multiple people on them will of course appear in multiple face groups.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1738962</commentid>
    <comment_count>1</comment_count>
    <who name="Jens">jens-bugs.kde.org</who>
    <bug_when>2018-03-18 20:50:37 +0000</bug_when>
    <thetext>Does this wish have a chance of implementation?
I think it is quite useful and many other image management apps implement it (e.g. Apple iPhoto / Photos). When I look for people in images, I don&apos;t want to care about files or images, just *people*.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1738965</commentid>
    <comment_count>2</comment_count>
    <who name="Simon">freisim93</who>
    <bug_when>2018-03-18 20:52:55 +0000</bug_when>
    <thetext>*** Bug 392024 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1752927</commentid>
    <comment_count>3</comment_count>
    <who name="Jmz D3an">jmzd3an</who>
    <bug_when>2018-05-16 14:10:12 +0000</bug_when>
    <thetext>This would be very helpful when dealing with huge amounts of faces.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1834541</commentid>
    <comment_count>4</comment_count>
    <who name="">stefan.mueller.83</who>
    <bug_when>2019-01-27 19:39:48 +0000</bug_when>
    <thetext>I agree.  I regard this a very urgent feature, since if you have a high number of faces, without having a possibility of sorting and filtering, it becomes messy and fiddly what drives me crazy.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1864161</commentid>
    <comment_count>5</comment_count>
    <who name="Jens">jens-bugs.kde.org</who>
    <bug_when>2019-06-19 21:26:27 +0000</bug_when>
    <thetext>Can we please revisit this feature request?
It would help enormously when assigning face tags, even if face recognition is not (yet) perfect.
Thanks!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1864259</commentid>
    <comment_count>6</comment_count>
    <who name="MarcP">iwannaberich</who>
    <bug_when>2019-06-20 10:52:22 +0000</bug_when>
    <thetext>In theory, this was proposed as part of the improvements for the GSoC 2019 in the Faces Management workflow improvements project. However, it was included as one of the last things to do (see point 4 at https://docs.google.com/document/d/1EPACR_JgZ5BWfbuqOP_Xlyd_cldEIKSd7n4TTgZ495Q/edit ), so I don&apos;t know if that option will be ready this summer.

I agree that it is important, and all other software dealing with picture recognition has this feature.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1868770</commentid>
    <comment_count>7</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2019-07-14 13:44:21 +0000</bug_when>
    <thetext>*** Bug 409788 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1894100</commentid>
    <comment_count>8</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2019-11-30 10:27:54 +0000</bug_when>
    <thetext>*** Bug 414653 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1898075</commentid>
    <comment_count>9</comment_count>
    <who name="">caulier.gilles</who>
    <bug_when>2019-12-23 15:21:29 +0000</bug_when>
    <thetext>7.0.0-beta1 is out with new Face Recognition algorithm based on Deep
Learning/Neural Network API from OpenCV

https://download.kde.org/unstable/digikam/

Please test and give us a feedback

Thanks in advance
Gilles Caulier</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1900476</commentid>
    <comment_count>10</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2020-01-04 20:55:43 +0000</bug_when>
    <thetext>*** Bug 415878 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1908732</commentid>
    <comment_count>11</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2020-02-10 16:52:45 +0000</bug_when>
    <thetext>*** Bug 417390 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1908756</commentid>
    <comment_count>12</comment_count>
    <who name="Jens">jens-bugs.kde.org</who>
    <bug_when>2020-02-10 19:20:36 +0000</bug_when>
    <thetext>I looked at 7.0.0beta2.
It seems the new engine better separates unconfirmed and confirmed faces, and also displays unconfirmed faces with the respective people&apos;s tag (and a prominent border). Right? However, I cannot find a way to show *only* unconfirmed faces (they are sprinkled between confirmed faces, of which there are many), and I cannot find a way to say &quot;This is a face, but it&apos;s not *this* one&quot; to remove a face from the &quot;Unconfirmed&quot; group of faces, but keep the tag.

So far, I also cannot see unknown faces, or images in general, being groupable by similarity. Yet. Is this feature hidden somewhere?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1908758</commentid>
    <comment_count>13</comment_count>
    <who name="MarcP">iwannaberich</who>
    <bug_when>2020-02-10 19:37:27 +0000</bug_when>
    <thetext>No, showing only unconfirmed faces for a person (there&apos;s current bug report for that), or automatically grouping unconfirmed faces for similarity (this bug report) are features that have not been yet implemented. And rejecting a suggestion still deletes the face region instead of sending that face back to the &quot;Unknown&quot; category (this is bug 384485)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1908763</commentid>
    <comment_count>14</comment_count>
    <who name="MarcP">iwannaberich</who>
    <bug_when>2020-02-10 20:09:14 +0000</bug_when>
    <thetext>(I have opened a feature request for the hide/show confirmed faces, so it is registered in the bugtracking system. It is bug 417399)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1917027</commentid>
    <comment_count>15</comment_count>
    <who name="Kartik">kartikx2000</who>
    <bug_when>2020-03-19 17:51:57 +0000</bug_when>
    <thetext>Hello all, I would like to work on this bug. 

I noticed that Google Photos resolves this in a very efficient manner, it does not show you the entire &quot;Unknown&quot; Collection, instead only individual collections of people that are currently unknown, but the algorithm has concluded to be the same.

Maybe this is something we can incorporate into DigiKam? I was thinking of creating a hierarchy within the Unknown tag, where each sub-tag will display face-tags of people that are similar (or the same).

The user could reject if the person is not the same as the rest, in which case the person would move into the misc. unknown tag. 

There are a few issues to this, firstly I&apos;m not sure whether it&apos;s ideal to create a hierarchy within the unknown tag, furthermore, I&apos;m not sure what I&apos;d name these subtags.

I&apos;d be grateful for any suggestions regarding this.

Thanks 
Kartik</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1917028</commentid>
    <comment_count>16</comment_count>
    <who name="MarcP">iwannaberich</who>
    <bug_when>2020-03-19 18:00:40 +0000</bug_when>
    <thetext>Hi Kartik. This is quite ambitious! 

Since digikam can already &quot;group&quot; pictures, why not just grouping them by similarity inside Unknown/Unconfirmed, without creating subtags? When the user enters Unknown/Unconfirmed, they will see all the groups (the groups with the most people could be showed first), and then they could enter a name (or confirm the suggestion). The user could also expand or collapse a particular group to see the containing pictures.

Although I believe that the &quot;group&quot; option is disabled for faces.

Another issue will be obtaining the similarity value. I guess that every new face that is detected should be compared with the rest of the faces in the Unknown/Unconfirmed categories and, if the similarity is superior to 0.95 (for instance), then add that face to the group.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1917031</commentid>
    <comment_count>17</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2020-03-19 19:07:09 +0000</bug_when>
    <thetext>The digiKam Icon View knows categories. I would find it better if the person name is the category and thus the people are grouped. That would be much clearer.

Maik</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1932134</commentid>
    <comment_count>18</comment_count>
    <who name="Maik Qualmann">metzpinguin</who>
    <bug_when>2020-05-23 15:51:50 +0000</bug_when>
    <thetext>*** Bug 421985 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1941503</commentid>
    <comment_count>19</comment_count>
    <who name="Kartik">kartikx2000</who>
    <bug_when>2020-07-03 08:02:24 +0000</bug_when>
    <thetext>(In reply to Maik Qualmann from comment #17)
&gt; The digiKam Icon View knows categories. I would find it better if the person
&gt; name is the category and thus the people are grouped. That would be much
&gt; clearer.

I do like this idea. However, I don&apos;t think this would work for images with multiple faces. When categorizing items (faces in our case) the ItemInfo is passed to the various sorting functions. Different faces (in the same image) share the same ItemInfo. Even if I store face suggestions in each ItemInfo, given an ItemInfo it&apos;s tough to know which face called it.

I&apos;ll have to think of a work-around for this. Maybe I could store a Map of Face Regions to Suggested Faces, and somehow pass Face Regions to the categorizing algorithm as well?

Kartik</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1941724</commentid>
    <comment_count>20</comment_count>
    <who name="Kartik">kartikx2000</who>
    <bug_when>2020-07-04 12:54:18 +0000</bug_when>
    <thetext>Just to update, storing maps of tag regions to suggested names is definitely feasible. I&apos;ll go forward with this approach to implement categorization based on Suggested Names. This will lead to categorization of similar looking faces together.

Kartik</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1941732</commentid>
    <comment_count>21</comment_count>
      <attachid>129889</attachid>
    <who name="">pouchard.alain</who>
    <bug_when>2020-07-04 14:31:52 +0000</bug_when>
    <thetext>Created attachment 129889
attachment-25234-0.html

Hello Thank you very much, as soon as there is an online version I will 
test. See you again and again thank you

Le 04/07/2020 à 14:54, Kartik a écrit :
&gt; Just to update, storing maps of tag regions to suggested names is definitely
&gt; feasible. I&apos;ll go forward with this approach to implement categorization based
&gt; on Suggested Names. This will lead to categorization of similar looking faces
&gt; together.
&gt;
&gt; Kartik</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1947935</commentid>
    <comment_count>22</comment_count>
    <who name="Kartik">kartikx2000</who>
    <bug_when>2020-08-01 18:02:29 +0000</bug_when>
    <thetext>Gilles, this bug report may be closed now.
Here&apos;s the new Feature in case anyone&apos;s interested to see: https://imgur.com/a/CKVopzi</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1956882</commentid>
    <comment_count>23</comment_count>
    <who name="">caulier.gilles</who>
    <bug_when>2020-09-12 05:26:16 +0000</bug_when>
    <thetext>Fixed with #384396</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>129889</attachid>
            <date>2020-07-04 14:31:52 +0000</date>
            <delta_ts>2020-07-04 14:31:52 +0000</delta_ts>
            <desc>attachment-25234-0.html</desc>
            <filename>attachment-25234-0.html</filename>
            <type>text/html</type>
            <size>1535</size>
            <attacher>pouchard.alain</attacher>
            
              <data encoding="base64">PGh0bWw+CiAgPGhlYWQ+CiAgICA8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRl
bnQ9InRleHQvaHRtbDsgY2hhcnNldD1VVEYtOCI+CiAgPC9oZWFkPgogIDxib2R5PgogICAgPHBy
ZSBjbGFzcz0idHctZGF0YS10ZXh0IHR3LXRleHQtbGFyZ2UgWGNWTjVkIHR3LXRhIiBkYXRhLXBs
YWNlaG9sZGVyPSJUcmFkdWN0aW9uIiBpZD0idHctdGFyZ2V0LXRleHQiIGRpcj0ibHRyIiBzdHls
ZT0idW5pY29kZS1iaWRpOiBpc29sYXRlOyBmb250LXNpemU6IDI4cHg7IGxpbmUtaGVpZ2h0OiAz
NnB4OyBiYWNrZ3JvdW5kLWNvbG9yOiByZ2IoMjQ4LCAyNDksIDI1MCk7IGJvcmRlcjogbm9uZTsg
cGFkZGluZzogMnB4IDAuMTRlbSAycHggMHB4OyBwb3NpdGlvbjogcmVsYXRpdmU7IG1hcmdpbjog
LTJweCAwcHg7IHJlc2l6ZTogbm9uZTsgZm9udC1mYW1pbHk6IGluaGVyaXQ7IG92ZXJmbG93OiBo
aWRkZW47IHRleHQtYWxpZ246IGxlZnQ7IHdpZHRoOiAyNzdweDsgd2hpdGUtc3BhY2U6IHByZS13
cmFwOyBvdmVyZmxvdy13cmFwOiBicmVhay13b3JkOyBjb2xvcjogcmdiKDM0LCAzNCwgMzQpOyBm
b250LXN0eWxlOiBub3JtYWw7IGZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1hbDsgZm9udC12
YXJpYW50LWNhcHM6IG5vcm1hbDsgZm9udC13ZWlnaHQ6IDQwMDsgbGV0dGVyLXNwYWNpbmc6IG5v
cm1hbDsgb3JwaGFuczogMjsgdGV4dC1pbmRlbnQ6IDBweDsgdGV4dC10cmFuc2Zvcm06IG5vbmU7
IHdpZG93czogMjsgd29yZC1zcGFjaW5nOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6
IDBweDsgdGV4dC1kZWNvcmF0aW9uLXN0eWxlOiBpbml0aWFsOyB0ZXh0LWRlY29yYXRpb24tY29s
b3I6IGluaXRpYWw7Ij48c3BhbiBsYW5nPSJlbiI+SGVsbG8KVGhhbmsgeW91IHZlcnkgbXVjaCwg
YXMgc29vbiBhcyB0aGVyZSBpcyBhbiBvbmxpbmUgdmVyc2lvbiBJIHdpbGwgdGVzdC4KU2VlIHlv
dSBhZ2FpbiBhbmQgYWdhaW4gdGhhbmsgeW91Cgo8L3NwYW4+PC9wcmU+CiAgICA8ZGl2IGNsYXNz
PSJtb3otY2l0ZS1wcmVmaXgiPkxlIDA0LzA3LzIwMjAgw6AgMTQ6NTQsIEthcnRpayBhIMOpY3Jp
dMKgOjxicj4KICAgIDwvZGl2PgogICAgPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIKICAgICAgY2l0
ZT0ibWlkOmJ1Zy0zODQzOTYtMjIxOTE4LUd4bG54ck90OVRAaHR0cC5idWdzLmtkZS5vcmclMkYi
PgogICAgICA8cHJlIGNsYXNzPSJtb3otcXVvdGUtcHJlIiB3cmFwPSIiPkp1c3QgdG8gdXBkYXRl
LCBzdG9yaW5nIG1hcHMgb2YgdGFnIHJlZ2lvbnMgdG8gc3VnZ2VzdGVkIG5hbWVzIGlzIGRlZmlu
aXRlbHkKZmVhc2libGUuIEknbGwgZ28gZm9yd2FyZCB3aXRoIHRoaXMgYXBwcm9hY2ggdG8gaW1w
bGVtZW50IGNhdGVnb3JpemF0aW9uIGJhc2VkCm9uIFN1Z2dlc3RlZCBOYW1lcy4gVGhpcyB3aWxs
IGxlYWQgdG8gY2F0ZWdvcml6YXRpb24gb2Ygc2ltaWxhciBsb29raW5nIGZhY2VzCnRvZ2V0aGVy
LgoKS2FydGlrCjwvcHJlPgogICAgPC9ibG9ja3F1b3RlPgogIDwvYm9keT4KPC9odG1sPgo=
</data>

          </attachment>
      

    </bug>

</bugzilla>