carakey

**QA Fail** - a work is still fully public after tombstoning. QA process: - From my admin account, I created and reviewed a test work - work: https://staging.oregondigital.org/concern/images/pz50gw130 - ~fileset:...

QA Round 2: **QA Fail** - [ ] From admin account, I attempted to add a file to the test work, which still did not stick. **Something is broken** -...

Sure - I was almost entirely referencing the above comments about functionality.

QA round 3: Setup: - From my admin account, I deleted the previous test work for this ticket, and created and reviewed a new test work - work: https://staging.oregondigital.org/concern/images/4x51hj066 -...

QA round 4: Setup: - From my admin account, I came back to the previous test work and changed it back to active (Review --> Approve) so I could step...

Here's the TL;DR list of remaining changes to get to QA Pass (for Cara): - [x] Email message to admin: Change "The deletion request..." to "The tombstone request..." - [x]...

> @carakey Thanks for the Tl;Dr list. The layout + needs written out in that way works way better on my end. Ill go through and make sure those get...

## QA round 5: ### TL;DR list - [ ] Get rid of the second notification email; keep the one that uses the "tombstone" wording. - [ ] Remove the...

@straleyb Just to remove the `(Image)` text. I don't know any reason why it should be there. re: My Collection showing tombstoned work:  ^ The tombstoned test work is...

I am getting different results in my unaffiliated user collection from what @straleyb is seeing. Trying to reproduce: 1. As unaffiliated `cara_test` user, add a test work ([this one](https://staging.oregondigital.org/concern/documents/v692t6260?locale=en)) to...