<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>You might want to take a look at Shotwell too. It allows you to group pictures in an album despite the files location (folders).</div><div><br></div><div>I believe it does not write anything to files metadata either but instead keeps all the information in its database but I am not 100% sure about that.</div><div><br></div><div><br></div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: BensonBear <benson.bear@gmail.com> </div><div>Date: 2017-09-21 9:08 AM (GMT-07:00) </div><div>To: digikam-users@kde.org </div><div>Subject: Re: Displaying photos without segregating by album </div><div><br></div></div>"Oh, I guess in your case photos from each camera have different extension<br>e.g. some are DNG, some are CR2, some are PEF etc. If you group by type then<br>each raw format is probably grouped together. "Flat" cancels that<br>grouping."<br><br>No, I don't have any fancy cameras, they are mostly just phones and do not<br>shoot raw, all the files are jpeg or some movie format. It is not the<br>formats being grouped together, but the cameras, because I have each camera<br>in a folder, which then becomes an album.<br><br>"You might want to read DAM section of the digikam handbook. There are some<br>good practices mentioned there including advantages of the DNG format,<br>recommended folder structure, etc. "<br><br>Thanks, I looked in there and it is useful, but I do not want any semantic<br>(including time) information encoded in the external folder structure and<br>then forcefully applied by digikam to "albums". I would prefer to have all<br>of this kind of information specifiable in the program. For example if one<br>uses time to define the folders, that unnaturally divides up events that<br>cross over the borders of one's time divisions. The only thing preventing me<br>from putting everything in one directory is the unwieldy size of it. So I<br>already decided to use one directory per camera, which is *fairly* natural,<br>keeps directories fairly small (and can use arbitrary subdirectories, as one<br>of my cameras already does) and doesn't impose any real semantics outside<br>of the program, but then the problem I initially specified arose. However,<br>"flat" view fixes that just fine.<br><br><br><br><br><br>--<br>Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html<br></body></html>