Menu

Support Image Review: Preserve Decision Outcomes and Notify Uploaders Across Migrations
📰

Support Image Review: Preserve Decision Outcomes and Notify Uploaders Across Migrations

DEV Community: go·CaspianHayes3586·9 days ago
#fPRf0xiK
#devtogo#devto#dev#decision#review
Reading 0:00
15s threshold

An approved support image can produce several crops; a rejected image still needs an answer. That constraint determines the design before any crop service enters the picture. TL;DR: queue the image review, record the moderator and reason, then publish or reject and notify the uploader in both outcomes. Keep that decision and its notification obligation in application-owned storage so replacing a media vendor doesn't replace your moderation history.

For a bounded production design exercise, I'd start with a customer support attachment destined for 1:1 and 16:9 views, then ask what happens if a moderator rejects it just before a vendor migration. This is a hypothetical incident review, not a report of an observed outage. Can the replacement worker discover that the uploader still needs a rejection notice without asking the previous image service what happened?

Ask what paged.

A dashboard showing completed transformations would not answer that question. Neither would a count of approved images.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.