Hilmar R (u-snh)

Q: Photos - sort order ?

Mon, 21 Oct 2019 23:18:22 +0200 zuletzt bearbeitet: Wed, 23 Oct 2019 18:22:50 +0200

hi-u@snh.wsring.net

!Hubzilla Support Forum
When I'm uploading a lot of pics, that runs very well (xhr), the order in arrival at the server is always a bit ramdom. This is always normal under xhr condition. When the pics are stored in the database tables, the store order even is a bit random.
Is any logic given to present the thumbnails in the photo albums (folders) in any sort order?
Smart sort orders could be the photo name (from origin) or the exif dates (if available). The photo creation or update dates appear less usefull (see above).
Btw, have tested the files and photos access logic and the permission system is excellent. Great spirit, devs.
#photo #photoalbum #filestorage #sort #sortorder #webdav #upload

mehr anzeigen 5 Kommentare

Tue, 22 Oct 2019 04:46:27 +0200

El Dorado

mike@z.macgirvin.com

It wouldn't be difficult to add a sort by name option - if that helps your situation any. The most difficult part of that exercise would be to change the button which currently just toggles between ascending and descending creation date.

Also as I recall there's a batch size for uploading and I think it's set to upload 3 at a time. As you've noticed, the resulting order kind of depends on which of those 3 streams got the most CPU time. You can improve the chances of everything staying in order if this is set to only upload one at a time, but performance and the time it takes to upload an entire directory will probably suffer a bit.

Exif dates could be problematic for a number of reasons.

Tue, 22 Oct 2019 06:55:56 +0200

What happens if you upload using WebDAV?

Tue, 22 Oct 2019 15:45:12 +0200

Hilmar R (u-snh)

hi-u@snh.wsring.net

Thanks very for the replies.
@Mike Macgirvin

...sort by name...

The idea behind is simple: If an upload from the card of a camera is made, in most cases the pic names contain sequence numbers that reflects also the sequence in time the photos were made. When I transfer the pics from the camera card to the pc and uploading from there, the creation dates may be less usefull, because that varies depending on the software and the file system used. For own needs, filename orders playing a role, for example when archiving a lot of photos collected in folders into the cloud. To select a suitable file name scheme is the responsibility of the user. From this point of view, any logic how to order the files in the cloud store does not matter. But what matters may be the presentation. My 1st thoughts of how to do is also simple: the client site can run such; for example per jquery to reorder the dom tree. The only thing the server site has to serve is to echo the suitable meta data as well. At the moment, one of meta is yet there (the origin filename told as title in the alt of the img html).

...change the button which currently just toggles...

Cannot see the difficulty. For example (only) add a label like “Date" for that button and add a 2nd button for asc/desc labeled “Name" or so. Then delegate a click event handler to both. ... 1st thought only, too.

...Exif dates could be problematic...

very true, and a challange.

...think it's set to upload 3 at a time...

in case I understand the said well (I'm still on the surface of hubzilla and did not dig deep enough into): a) in my playground, I assume a dependency to the fastCgi controls and b) to serialize down to one (= no parallel), appears to me as no solution, because, as said, the sequence of the files from origin most is random und the user should not become enforced to select the right u/l order by herhimself. Apache and the os behind have best suitable controls to plonk up the files from the client to the server, IMO.
But slow down (myself). My ideas are far away from being urgent anyway. After one 1st thought, at least a 2nd to have is the best. When keeping such on the track of discussions, would be very well.

@Tanja
Will test dav, and also ssh, in one of the next days. But I assume similar/same results because the dav and ssh runtime environments vary even heavily. The motiv for the test is more a consistency check between the available possibilities. But will see.

Tue, 22 Oct 2019 19:12:07 +0200

Will test dav, and also ssh, in one of the next days.

Hubzilla does not have a ssh backend.

Wed, 23 Oct 2019 18:27:25 +0200

Hilmar R (u-snh)

hi-u@snh.wsring.net

Webdav: Needed some time to recognize apache dav was the wrong playground (makes me happy) and sabre is used (great).
@Tanja
My exercise was to transfer one folder via webdav (162 files, 274 MB), duration was about 10 minutes.
A 2nd folder content transfered via web ui u/l (164 files, 265 MB), duration was about 4 minutes.
The frontend for webdav was caja (a nautilus fork).
About the sort order, both exercises lead to the same result, it will be nearly impossible to influence the order a single file will successfully stored at the server (but no reason for headage

@Mario Vavti
Thanks for the tip to save my time investigating ssh.