You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are ~14 Dandisets with test in the title on the production server, and some have published versions. Should we contact the owners to request the removal of those Dandisets?
Ah yes, to clarify the entire query has both test and real datasets. It's mainly the top of the sorted query that are test datasets.
Once we have approval, I think that admins can delete the Dandisets. I'll need to check with the Kitware team on how we will handle deleting published Dandisets.
Jake mentioned that only Dandisets with draft versions can be deleted. So for some of these Dandisets will need discuss further with the Engineering Core.
The restriction on deleting Dandisets is an API design feature. We can bypass it if we need to perform this type of cleanup. That is, it would be a "meta operation" rather than something we would do through the system itself. (As such, we need to be extremely careful before we do anything like that.)
There are ~14 Dandisets with
test
in the title on the production server, and some have published versions. Should we contact the owners to request the removal of those Dandisets?cc @bendichter
The text was updated successfully, but these errors were encountered: