Konzept #660
Delete foreign objects on removal from list?
| Status: | Erledigt | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Alexander Blum | % Done: | 100% | |
| Category: | - | |||
| Target version: | - |
Description
If a webuser creates a foreign object (e.g. an artist member), saves it, edits it again and removes that created entry from the list (e.g. artist member list), the foreign object gets orphaned (but might be chosen from the source list again). Should orphaned foreign objects be deleted?
Related issues
History
#1 Updated by Meik Michalke over 5 years ago
- Status changed from Neu to Vermeintlich Gelöst
- Assignee set to Alexander Blum
yes. e.g., DSGVO.
there should only be a short delay of maybe a few hours, just in case it was removed accidently.
#2 Updated by Alexander Blum over 5 years ago
- Status changed from Vermeintlich Gelöst to Erledigt
- % Done changed from 0 to 100
Result of discussion with meik: Also the history should be deleted.
#3 Updated by Alexander Blum over 5 years ago
- Related to Datenbank #661: Delete foreign objects, if they get orphaned added
#4 Updated by Alexander Blum over 4 years ago
- Project changed from repertoire to collecting_society