334 asks that botanists be able to edit image properties, but it is not clear whether the Django admin interface is the proper place for this function, because I am not sure how image curation will work going forward. Currently, information about each photograph — what plant it shows, and what part of the plant — is embedded in its filename, and images are uploaded to S3 through file-system-level operations that are then followed by a nightly import step that re-scans the images in S3 and rebuilds a database table recording which images are available for which plants.

@jnga and @jrrickerson and @sidkoul should be asked for their input on whether the current “filesystem → database” direction makes sense going forward, or whether it should be discarded like all of the other import scripts that will stop running, and if the running Django app should become how images get added to S3 and removed from S3 from now on. There are complications either way.

newfs / gobotany-app

Botanists need a procedure for adding, removing, editing photos #370