Secondary review: retired images tier

[nathanielrindlaub]

I think the simplest solution to the need for a secondary, "expert" review tier may be to implement a concept of "retiring" an image, which would be a special action only Project Managers could take & would apply to entire Images, rather than individual objects. I imagine you'd want to display retired state in the images table as well as enable filtering by retired / not retired status.

Project Managers could then use their own discretion to decide what images they thought ought to be retired (if any) for their own use-case. For SCI Biosec., Juli might create a View that's all reviewed images with rodents in them that are not retired, and use that as her queue of new images she needs to perform a final pass on and retire them (confirmed rodents & not rats).

I think it would be fairly straight forward to implement. On the backend, we'd need to:

• [ ] Add a "retired" field to Image schema
• [ ] Add mutation revolvers for "retire image" and "un-retire image"
• [ ] Add filter capabilities for filtering both "retired" images and "not-retired" images
• [ ] Add to get stats payload (?)

On the frontend, we'd need to:

• [ ] Display retired status in Image table and somehow in Loupe panel
• [ ] Add controls for retiring an image (add menu items to context menu(s) too where appropriate) - but only expose them to Project Managers
• [ ] Add filter controls in filter panel

[nathanielrindlaub]

Think about whether we need this now or will #138 suffice.

[nathanielrindlaub]

I think #138 will solve for this in a more flexible way. Closing out.