comanage-dev - [comanage-dev] Cascading Delete Through History Records
Subject: COmanage Developers List
List archive
- From: Benn Oshrin <>
- To: comanage-dev <>
- Subject: [comanage-dev] Cascading Delete Through History Records
- Date: Tue, 14 Jan 2014 17:41:48 -0500
Ordinarily, we want to discourage people from deleting people and other entities, but let's assume an admin decides to delete a person. Let's further assume that the person to be deleted caused history records to be created. For this to be interesting, they would have to be history records for another person.
As a concrete example, let's say a CO Admin X has been told to "remove all records related to COU Admin Y". COU Admin Y enrolled CO Person Z, and therefore there are history records for CO Person Z saying that they were added by COU Admin Y. What should we do with those records?
(1) Delete them
(2) Change their "actor" to "Deleted CO Person"
(3) Reassign them to someone else... who?
(4) ?
-Benn-
- [comanage-dev] Cascading Delete Through History Records, Benn Oshrin, 01/14/2014
Archive powered by MHonArc 2.6.16.