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
This would be on an admin page where a user could select an image collection an optionally a label, and the result would be
deleting all annotations for that image collection (optionally just the ones with the given label) from the db
deleting all ROIs that are "orphaned" by this process (e.g., delete the ROI record from the db, but don't delete the image on disk)
The user req driving this is that a user may want to work temporarily and then clean up their work after they export what they need. Or for instance there's a huge category, the user sorts selected ROIs out of it, then they want to delete that category. Mostly to not clutter up the UI with work that's been completed, but also to keep the database smaller and thereby improve performance.
The text was updated successfully, but these errors were encountered:
@joefutrelle What if they try to delete either a collection or a label that was done by someone else? E.g, I add the collection, and annotate a few things. Heidi goes in and does some as well. Can I still delete the collection or labels, even though some of them would be Heidi's?
This is intended to be a "big hammer" and so a user with privileges to do this (basically anyone who can annotate) will be able to perform these operations regardless of who had worked on that collection/label.
Got it. I think it requires a confirmation message (obviously), but with other project we included some of the details of what was being removed. E.g, something like:
Along with your XXX annotations, there are XXX annotations from other users that will also be deleted. Are you sure you want to delete this image collection?
This would be on an admin page where a user could select an image collection an optionally a label, and the result would be
The user req driving this is that a user may want to work temporarily and then clean up their work after they export what they need. Or for instance there's a huge category, the user sorts selected ROIs out of it, then they want to delete that category. Mostly to not clutter up the UI with work that's been completed, but also to keep the database smaller and thereby improve performance.
The text was updated successfully, but these errors were encountered: