Sync Molnix appraisals and appraisers

[szabozoltan69]

Refers to #2633 and to #2732

[arunissun]

@szabozoltan69
In api/management/commands/sync_molnix_appraisals.py, please check the block around lines 559-615. It looks like for appraisal in appraisals: starts correctly, but the actual normalize_appraisal(...) write logic and the nested appraiser handling are outside that loop, so the code appears to process only the last appraisal on each page and only that last appraisal’s appraisers. The ticket expects one row per appraisal and the full child set from appraisal.appraisers[], so could you please verify the indentation/control flow,
let me know if I am missing something

[szabozoltan69]

...please check the block around lines 559-615

Good one, @arunissun – I fixed the loop indentation and pushed the change.

[arunissun]

@szabozoltan69
Please could you confirm whether duplicate rrms_event_participation rows on rerun are expected by design? In sync_molnix_appraisals.py, the event participation records are written with create(), and the uniqueness constraint was removed in migration 0095_molnix_appraisal_appraised_person_and_event_participation_constraint.py. So if the sync is run again on the same source data, it looks like the same (event_id, person_id, role) participation row could be inserted again instead of being updated or skipped. If that behavior is intentional, then this point is fine from my side or I am missing anything ,

no more issues identified and you can merge the PR

[szabozoltan69]

@arunissun You were right about duplicates. I solved it via this commit: "Update RRMS event participation to upsert and log create/update counts".