Implement ProfilePictureUpload Command object

[cspath1]

This command will be used to upload a new profile picture for a User. It will need a data class (called Request) that has the following parameters:

• User Id
• Multipart File

The command should check that the user id refers to a valid user record. If this validation fails, we should respond with a HashMultimap<ErrorTag, String> as a failure data type

Otherwise, it should check to see if the user already has a profile picture uploaded, and if so, it should call a separate S3 service to delete this image. It should then call an S3 upload service to upload the new image. If the image is uploaded successfully, the ProfilePicture record associated with the User should be retrieved and updated. A boolean marked true should be returned as the success data type.

If the aforementioned image upload is not successful, we should respond with the errors the S3 upload service returned.

[TUllery]

Since the image must be approved by an admin, we should not delete the previous image until the approval has occurred. This would mean we need a pending image indicator along with current image indicator. Does this mean there should be a table with ID and images where the ID is a foreign key into the User table? This would allow the User table to have a current ID, a pending ID for the images. When the Admin is approving the pending image, it would be nice to be able to see the current image. Logging should indicate which user the image is associated with as they are added. Todd Ullery Planetarium Director York Learning Center Planetarium York County Astronomical Society www. <http://www.ycas.org>astroyork.com

…

On Tue, Sep 18, 2018 at 9:47 PM Cody Spath ***@***.***> wrote: This command will be used to upload a new profile picture for a User. It will need a data class (called Request) that has the following parameters: - User Id - Multipart File The command should check that the user id refers to a valid user record. If this validation fails, we should respond with a HashMultimap<ErrorTag, String> as a failure data type Otherwise, it should check to see if the user already has a profile picture uploaded, and if so, it should call a separate S3 service to delete this image. It should then call an S3 upload service to upload the new image. If the image is uploaded successfully, the ProfilePicture record associated with the User should be retrieved and updated. A boolean marked true should be returned as the success data type. If the aforementioned image upload is not successful, we should respond with the errors the S3 upload service returned. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#37>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGG65LYdfI5MKMf3UF_2r96g16Ig9IiAks5ucaIagaJpZM4WvQyL> .

[cspath1]

Since the image must be approved by an admin, we should not delete the previous image until the approval has occurred. This would mean we need a pending image indicator along with current image indicator. Does this mean there should be a table with ID and images where the ID is a foreign key into the User table? This would allow the User table to have a current ID, a pending ID for the images. When the Admin is approving the pending image, it would be nice to be able to see the current image. Logging should indicate which user the image is associated with as they are added. Todd Ullery Planetarium Director York Learning Center Planetarium York County Astronomical Society www. http://www.ycas.orgastroyork.com
…
On Tue, Sep 18, 2018 at 9:47 PM Cody Spath @.***> wrote: This command will be used to upload a new profile picture for a User. It will need a data class (called Request) that has the following parameters: - User Id - Multipart File The command should check that the user id refers to a valid user record. If this validation fails, we should respond with a HashMultimap<ErrorTag, String> as a failure data type Otherwise, it should check to see if the user already has a profile picture uploaded, and if so, it should call a separate S3 service to delete this image. It should then call an S3 upload service to upload the new image. If the image is uploaded successfully, the ProfilePicture record associated with the User should be retrieved and updated. A boolean marked true should be returned as the success data type. If the aforementioned image upload is not successful, we should respond with the errors the S3 upload service returned. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#37>, or mute the thread https://github.com/notifications/unsubscribe-auth/AGG65LYdfI5MKMf3UF_2r96g16Ig9IiAks5ucaIagaJpZM4WvQyL .

I have few ideas. The one I'm thinking would work best would be to have an enum of (Pending, Active) in the ProfilePicture table. Then what we could do is, when a user uploads a new photo, it will delete any pending photos (since the new image will be replacing it). Then, after the new image is (ideally) approved by an admin, we will delete the image with the Active enum type, then change the new image to be the active one.

Then, when the admin goes to approve (or disprove) an image, we can portray them side-by-side.

As far as logging goes, that will definitely be possible.