modification and creation dates stripped from files uploaded through API2?

[cknd]

Someone claimed that it is impossible to supply a modification date and creation date for files uploaded through the web API and that that is the reason why for example Camera Uploads from Seadroid lose their timestamps (which is an annoying bug). Check out this issue over at Seadroid: haiwen/seadroid#91

Can someone comment whether this is true, and if so, what can be done to fix it?

[freeplant]

It is true. We will investigate the problem.

[pandiloko]

Is this issue still in the queue? I have this exact problem with iOS App and it is pretty annoying indeed. Specially since iOS app doesn't allow to sort by name descending (filenames also have date) which would be a temporary workaround.

[floco]

New seafile user here, great software. I do see the same issue. Creation date is not preserved for camera uploads on iOS. Is there anyone working on this defect already ? or this is a technical limitation ?

[despens]

The web API supporting last modified dates on upload is critical for organizations that need to migrate data into a seafile Seafile instance. If you are not starting fresh with Seafile, but have years of projects records, the last modified date is critical to preserve.

Tools like rclone are typically used for migrating data in between storage systems. For instance, an organization moving from Google Cloud or Dropbox to a self-hosted solution would use rclone to move all their files to Seafile.

(I've also posted in the community forum about this and am glad there is a technical issue opened for it already.)

[despens]

Probably an optional HTTP header with the last modified information would be a good route. Non-compatible backends (older versions of Seafile) could ignore the header, aware backends (new versions of Seafile) could use it to set the last modified time for the uploaded file.

Which parts of Seafile would need to be changed to for this to work?