note that the types of the photos are remembered (they stay under their headers)
cancel the edit
enable sync
wait for the obs to upload
once uploaded, edit the (remote) obs
Expected:
The photo types are still remembered. If you uploaded a "whole plant" photo, it would show up under that header when you edit the obs.
Actual:
The types are lost. In dev and beta it worked but that's because the iNat instance was serving up the photos and kept the filenames we gave it. In prod, I think there's an S3 bucket serving the photos and it creates its own filenames.
Notes:
This doesn't actually break anything as all the photos still show up under the "other" header and they can still be deleted. It's just that the user experience isn't as nice as I designed it to be :cry: . As far as how to resolve this, here's some ideas:
patch iNat to allow storing a photo type (or a field for arbitrary data)
use an obs field to store data about photo types. This has obvious downsides.
Steps:
Expected: The photo types are still remembered. If you uploaded a "whole plant" photo, it would show up under that header when you edit the obs.
Actual: The types are lost. In dev and beta it worked but that's because the iNat instance was serving up the photos and kept the filenames we gave it. In prod, I think there's an S3 bucket serving the photos and it creates its own filenames.
Notes: This doesn't actually break anything as all the photos still show up under the "other" header and they can still be deleted. It's just that the user experience isn't as nice as I designed it to be :cry: . As far as how to resolve this, here's some ideas: