Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Photo types aren't remember in prod #60

Open
tomsaleeba opened this issue Oct 19, 2020 · 0 comments
Open

Photo types aren't remember in prod #60

tomsaleeba opened this issue Oct 19, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@tomsaleeba
Copy link
Collaborator

Steps:

  • launch app (the prod one)
  • disable sync
  • create an obs
  • edit the (local) obs
  • 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 😢 . 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.
  • run our own system that stores this data
@tomsaleeba tomsaleeba added the enhancement New feature or request label Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant