-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to remove datasets that Harvard Dataverse Repository harvested from Swedish National Data Service #142
Comments
In the short term, just to improve the search experience for people looking for data by increasing the odds that they can find datasets, I can try to use the destroy dataset API endpoint to remove all of the harvested records at https://dataverse.harvard.edu/dataverse/SND. @djbrooke, @scolapasta would it be okay if I use the destroy datasets endpoint for this? Would that make it harder to figure out why deleting the client didn't result in those harvests being removed? |
I'm assuming it cannot be deleted or managed via normal mechanisms because it is one of the fake Nesstar-based harvested dataverses that were migrated from DVN3 years ago. I just opened an issue requesting to purge all of them (#153). It will likely require some manual API or database-level effort. |
2023/12/19: Prioritized during meeting on 2023/12/18. Added to Needs Sizing. |
2023/12/19: This issue will be superseded by: #153 |
Closing as per note about #153 |
This issue has been closed but it's still in the sprint ready column. I'll remove it. |
From the Harvard Dataverse Repository's "Manage Harvesting Clients" page, I deleted the client that was created to harvest datasets from the Swedish National Data Service. An administrator from that repository asked us to remove it. I didn't see any error message in the UI and the the client was removed from the list (at https://dataverse.harvard.edu/harvestclients.xhtml).
But so far none of the 468 datasets harvested into the collection at https://dataverse.harvard.edu/dataverse/SND have been removed.
Is there anything from the logs or database that could explain why the records haven't been removed? This is the first time I've run into this problem.
The text was updated successfully, but these errors were encountered: