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

Why Exif fields are not editable? #6

Open
simobrazz opened this issue Jan 17, 2020 · 2 comments
Open

Why Exif fields are not editable? #6

simobrazz opened this issue Jan 17, 2020 · 2 comments
Labels
docs enhancement New feature or request

Comments

@simobrazz
Copy link

I would like to make exif fields editable so I can see and modify them on edit forms, why is that not possible?

@escaped
Copy link
Owner

escaped commented Jan 17, 2020

That's a good question. For me, the extracted EXIF information of a file is not mutable as it should reflect the information about the file itself.

Furthermore, what happens if you have changed the EXIF information? Should it be written back to the file (currently not supported)? What happens if you decide on uploading a new file? What should happen to the changes?
In general, I don't think we can say whether we could keep them or should overwrite them as the requirements for applications differ. If the EXIFField would be editable, your changes would be overwritten by the current implementation when a new file is assigned to the field.

Maybe making it configurable would be an option, but I have to think about the downsides and implications of that approach. But I would be open for other suggestions as well.

For now, as a workaround, I would suggest to add a new JSONField() to the model and copy all EXIF information to the new field once they are available.

@escaped escaped added enhancement New feature or request question Further information is requested labels Oct 2, 2020
@escaped escaped added docs and removed question Further information is requested labels Jan 11, 2021
@escaped
Copy link
Owner

escaped commented Jan 11, 2021

For now, we should add a section to the documentation, which describes the issue, the reason for the implementation and maybe a suggestion to work around this limition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants