Allow removal (requests)

adina commented

2025-05-12 07:33:47 +00:00

Owner

There are two me in the user knowledge dump. At the moment, I can't remove the second one, or request its deletion. It would be nice to be able to do that.

jsheunis commented

2025-05-12 12:17:12 +00:00

Owner

I agree. Although I'm not sure what the ideal behavior would be from the UI side, and whether it would need to be configurable based on how interaction happens with the backend.

should there be some config option that specifies whether users should be able to delete a record, vs only be able to request deletion (i.e. the record will show up until its deleted from the backend)?
in either case, should shacl-vue add some annotation to the record?
should interaction with the record change after the deletion (or deletion request), e.g. hide it if it has the relevan annotation, or make it inactive such that users cannot click on it?
in the case of a deletion request, should that be reversible in the same session?

@mih did you already have thoughts on how you'd want this to work for the inm7 user management case, or other use cases?

I agree. Although I'm not sure what the ideal behavior would be from the UI side, and whether it would need to be configurable based on how interaction happens with the backend. - should there be some config option that specifies whether users should be able to delete a record, vs only be able to request deletion (i.e. the record will show up until its deleted from the backend)? - in either case, should `shacl-vue` add some annotation to the record? - should interaction with the record change after the deletion (or deletion request), e.g. hide it if it has the relevan annotation, or make it inactive such that users cannot click on it? - in the case of a deletion request, should that be reversible in the same session? @mih did you already have thoughts on how you'd want this to work for the inm7 user management case, or other use cases?

mih commented

2025-05-12 14:00:31 +00:00

Owner

It would make sense to add dedicated support for a deletion request. It is a really common use case.

The outcome of that support should be an annotation of the record, not an actual deletion.

We could decide on a standard annotation_tag for that. The annotation_value for that should be a rationale description for the deletion.

If we make it a standard annotation_tag, it would be possible to also hide the record. But a user might also change their mind ...

It would make sense to add dedicated support for a deletion request. It is a really common use case. The outcome of that support should be an annotation of the record, not an actual deletion. We could decide on a standard `annotation_tag` for that. The `annotation_value` for that should be a rationale description for the deletion. If we make it a standard annotation_tag, it would be possible to also hide the record. But a user might also change their mind ...

jsheunis commented

2025-05-19 09:45:21 +00:00

Owner

Related: https://hub.trr379.de/q04/annotate.trr379.de-demo/issues/42

venkateshhs commented

2025-05-30 07:26:40 +00:00

Owner

Related : https://github.com/psychoinformatics-de/shacl-vue/issues/136 and https://github.com/psychoinformatics-de/shacl-vue/issues/135

Rows
Columns

Allow removal (requests) #8