...
task_id | assignee | task_type | ..other Task table columns |
|---|---|---|---|
45776 | EXPERT-2345-ty | CROP_NOMINATION_EXPERT_REVIEW |
...
Deleting a nomination
Currently we do not have a read-only view of crops. So there is no way to delete a nomination.
Should we implement the read-only view the expected behaviour would be:
changing the ‘deleted’ in nomination to true
changing the ‘nomination_id’ to NULL in the crop table.
these two things combined would mean that there is no way to see what object was nominated even though it is deleted (see Not yet implemented - immutable nominations)
if the object was re-nominated it would be assigned a new id
Question to ask yourself:
Do you want to save the nomination object as it is now? Should the nomination object be immutable (from the perspective of the creator) once submitted or should they be able to amend it mid-review?
What is the workflow that a nomination should go through for your nomination type?
Not yet implemented
Immutable nominations
If we want the record a copy of the state this could be added as a json column in the nominations table. That way if the nomination is deleted it is recoverable.
Administrative Task Types
views
...
litefarm - add new nomination point
...
user - My Nominations
...
Views
Litefarm - Being able to move the status of the nomination from admin account
Agronomist - Nominations In Your Area, Being able to move the status of the nomination
User View
My Nominations and their status'