[Documentation] Document the examiner cycle management process

[karntrehan]

We should document the entire cycle management process:

• [x] 1. Invalidating existing examiners
• [x] 2. Adding examiners
• [ ] 3. Creating cycle - Data required
• [ ] 4. Randomizer setup
• [ ] 5. Testing cycle setup

[Ajay-Maury]

Added script and docs which contains:-

• Parsing and validating CSV file
• Invalidating existing examiners
• Creating new users on fusion auth from CSV data
• Creating or updating examiners from CSV data
• Mapping them to the latest assessment cycle
• Logging errors

[charanpreet-s]

@Ajay-Maury dependent on data from PM for the cycle

[charanpreet-s]

@Ajay-Maury to add curl for the api for reset schools-cycle mapping

invalidate-examiner-assessments API

curl --location '{{baseUrl}}/admin/assessment-cycle/<cycle_id>/invalidate-examiner-assessments' \
--header 'Authorization: Bearer <admin_token>' \
--header 'Content-Type: application/json' \
--data '{
    "udises":  ["<list of udise to invalidate result>"],
    "reset_all": true,
    "delete_all": false,
    "mentor_id": "000"
}'

• reset_all : invalidates all assessments of the given mentor and udise, deletes udise cycle mapping, and recreate the udise cycle mapping with random students

  • delete_all : invalidates all assessments of the given mentor, delete udise cycle mapping and udise and remove the examiner from the assessment cycle

[charanpreet-s]

@Ajay-Maury to add user journey diagram

[karntrehan]

Biblography added. User flow diagram pending. @karntrehan to take a crack at this for now.

[karntrehan]

Raw: https://drive.google.com/file/d/1dtlBK7rctww31NjxS-uVg22gYxNnenax/view?usp=sharing

[karntrehan]

v2 of diagram with anomaly detection flow added:

[VargishChauhan]

Completed the document.