Let's say someone deletes a property (by deleting its vocabulary or whatever). Any property-type prompt that's assigned to that property will no longer function. We need to set either an onDelete="CASCADE" or an onDelete="SET NULL" on the prompt's property annotation.
CASCADE is risky because all text assigned to that prompt will also be deleted. (This is the same for item property text, if that's any consolation.) If our goal is to preserve collecting inputs at all costs, even when something so drastic as deleting a property happens, we should SET NULL and change the prompt type from "property" to "input" (i.e. "Supplementary") on some delete event.
Let's say someone deletes a property (by deleting its vocabulary or whatever). Any property-type prompt that's assigned to that property will no longer function. We need to set either an
onDelete="CASCADE"or anonDelete="SET NULL"on the prompt's property annotation.CASCADEis risky because all text assigned to that prompt will also be deleted. (This is the same for item property text, if that's any consolation.) If our goal is to preserve collecting inputs at all costs, even when something so drastic as deleting a property happens, we shouldSET NULLand change the prompt type from "property" to "input" (i.e. "Supplementary") on some delete event.