Open DiegoPino opened 4 months ago
Hmmm, I vote for future release (1.5.0) to give us more time for deeper testing & checking. This is a powerful potential functionality, and I think having it limited for only EAD container items--as you have said in live discussions, would be the best setup for this.
Ok good.
Will be implemented by/through #208 . Will close when code is ready
What?
When you have 100K objects in an AMI set you can't delete the way we delete. We need to enqueue the process. So we need a new Queue Worker for that, a very safe, fail safe, secure one.
Also. The "delete" action is not Nested CSVs aware right now. And ... we need a new Mode that is neither Draft/Published but is "preserve the current state".
@alliomeria for 1.4.0 (0.8.0 in this case)? or todo/future/1.5.0?