dpla-takedown

To remove items from an Elasticsearch index via a takedown request, you provide explicit IDs or criteria like hub and institution. The system coordinates pre-flight verification, search-before-delete, and post-deletion confirmation to ensure safe deletion from S3 and Elasticsearch.

Yes, you can delete records from S3 and Elasticsearch using hub, institution, or collection criteria. The takedown process generates an item ID list from these criteria, allowing batch handling and staged deletion without needing explicit individual IDs.

Safeguards preventing accidental data loss during a batch takedown include mandatory pre-flight verification, search-before-delete operations, safety prompts, and explicit user confirmations. Post-action verification also ensures no collateral data loss occurs.

The best way to process takedown requests for a live search index and master dataset is using a staged deletion workflow. This approach coordinates S3 master dataset exports and Elasticsearch operations with strict pre-flight checks and post-deletion confirmation.

Yes, explicit user confirmation is required before deleting items from the live site. The takedown workflow enforces strict safeguards and safety prompts to ensure deliberate action and prevent unintended removal of DPLA items.