Draft dataset and draft collection delete: When a draft dataset/collection is deleted, the auto-refresh landing page should not show the deleted dataset

[sbarbosadataverse]

Please fill out as much of the template as you can.
Start below this comment section.
-->
What steps does it take to reproduce the issue?
Navigated to a draft dataset/collection within a subcollection, and selected to delete the dataset and next the collection.
The confirmation page is displayed, and I confirmed and when the page auto-refreshed, the dataset/colection was still showing. I had to refresh again to see the dataset/collection was deleted.

• When does this issue occur?
  during draft dataset/collection delete

• Which page(s) does it occurs on?
  dataset and collection landing page

• What happens?
  the deleted dataset/collection continues to display until user refreshes the page again

• To whom does it occur (all users, curators, superusers)?
  superuser

• What did you expect to happen?

once I select delete and confirm and the autorefresh happens, the listing would disappear and would not need to refresh again

Which version of Dataverse are you using?

most recent

Are there any open or closed issues related to this bug report?
unsyare

Screenshots:
This screen shot shows the test dataset I deleted and what is there after I confirm deletion. You see the "success" message but the dataset that was removed is still listed.

[qqmyers]

FWIW: This is probably due to the change in Solr to handle changes in batches for efficiency, which will wait for up to 1 second (by default config). If the page refreshes before then, it can still see the old index. It can probably be worked-around by reducing that 1 second time (at the cost of possibly making solr less efficient) or adding a ~1 second delay to the delete operation, or some combination.