Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Edit, Add, Delete Local Units with Validation and Reversion Mechanism #2318

Open
samshara opened this issue Nov 21, 2024 · 0 comments
Assignees
Labels
DFS DFS implements/leads the implementation

Comments

@samshara
Copy link
Member

samshara commented Nov 21, 2024

Create APIs to enable the following tasks

  1. Editing Workflow

    • Lock Edited Entries
      • Lock Local Unit entries upon submission to prevent further edits during validation.
      • Store editor information (user ID) and submission timestamps.
    • Validation Workflow
      • Implement a validation status field (Validated, Not validated, Pending edits validation).
      • After an edit, set the validation status field to Pending edits validation.
      • Add API endpoints for validators to approve or reject changes.
      • Record validator actions, comments, and timestamps.
      • Notify the editor, copying the validator.
    • Reversion Mechanism
      • Provide backend functionality to revert edits to the last validated state.
      • Record reversion actions and validator comments.
      • Notify the editor, copying the validator.
    • Notification System
      • Trigger email notifications to the NS Focal Point (Local Validator) upon submission.
      • Implement escalation logic to notify the Regional Validator if no response is received within 14 days.
      • Escalate further to the Global Validator after an additional 14 days if required.
  2. Addition Workflow

    • Lock New Entries
      • Lock newly added Local Unit entries upon submission.
      • Record creator information (user ID) and submission timestamps.
    • Validation Workflow
      • Add new entries with a default status of Not validated.
      • Extend API endpoints to validate or reject new entries.
      • Capture validator actions, comments, and timestamps.
      • Notify the editor, copying the validator.
    • Notification System
      • Trigger and escalate notifications for validation as in the editing workflow.
  3. Deletion Workflow

    • Mark Entries as Deprecated
      • Upon deletion request, mark the entry as Deprecated in the database instead of hard deletion.
      • Record the deletion reason(Non-existent, Incorrectly Added, Security Concerns, Other), additional comments, and the user's information.
      • Notify the validator.
    • Reversion Mechanism
      • Provide validators with functionality to revert deletions.
      • Restore the entry's previous state.
      • Notify the editor, copying the validator.
    • Notification System
      • Notify the NS Focal Point
      • Escalate notifications to the Regional and Global Validators using the same escalation logic.
@samshara samshara changed the title Implement validation and reversion workflows for validation, edits, additions, and deletions Implement Edit, Add, Delete Local Units with Validation and Reversion Mechanism Nov 21, 2024
@samshara samshara transferred this issue from IFRCGo/go-web-app Nov 21, 2024
@samshara samshara added the DFS DFS implements/leads the implementation label Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DFS DFS implements/leads the implementation
Projects
None yet
Development

No branches or pull requests

3 participants