apply a moderator's decision to a pending person-edit suggestion - same permission as moderating a poem correction (Auth policies: ganjoor:modify)

correction review result

review note

suggestion id

the person this suggestion proposes changes for

date

suggester's user id

suggested name

suggested description

suggested wikipedia url

suggested birth year in lunar hijri

suggested death year in lunar hijri

suggested ValidBirthDate

suggested ValidDeathDate

suggested birth location id

suggested death location id

suggested family tree caption

only meaningful alongside a non-null SuggestedFamilyTreeCaption. Normally, ModeratePersonEditSuggestionAsync rejects approving a caption when another person in the same connected kinship component already carries one (two separate "family tree" list entries would otherwise open to the exact same graph). Set this to true only when a second, distinct caption on the very same tree is genuinely intended (e.g. two commonly used alternate names for the same dynasty/family) to approve it anyway.

suggested other names (GanjoorRelatedPerson.Aliases) separated by «،». null = this suggestion says nothing about them (aliases stay as they are); the contributor's form is pre-filled with the current aliases, so emptying the box entirely is also read as "no change" - removing every alias is a moderator-only action (Admin/MergePeople)

how editorially prominent a GanjoorRelatedPerson is treated as - purely a display/sizing hint (see GanjoorRelatedPerson.Importance, GanjoorPersonGraphNode.Importance and peoplegraph.js's nodeRadius()), never used to filter, rank or otherwise affect query results. New values can be appended safely later (stored as int).

a GanjoorRelatedPerson's gender - used only by the family-tree chart (familytree.js's buildLayout()) to break ties when a child has two recorded parents and both happen to have their own recorded ancestors (so neither side can be preferred on "continues a documented lineage" grounds alone): the father is preferred as the tree's spine parent, matching conventional patrilineal genealogy-chart practice, with the mother then drawn attached beside him. Never used to filter, rank or otherwise affect query results. New values can be appended safely later (stored as int).

true if this suggestion is actually a request to delete the person outright, not to change their fields - when true, every Suggested* field above is ignored on approval (they still carry whatever the contributor's pre-filled form happened to hold) and ModeratePersonEditSuggestionAsync removes the person and every relation/affiliation/tag reference to them instead. Kept on this same entity rather than a separate one so the existing suggest/review UI and permissions are reused as-is.

what a GanjoorPersonEditSuggestion asks for (deleting a person is the SuggestedForDeletion flag of an Edit suggestion)

Merge: the person that stays (PersonId is the duplicate that is merged into it and deleted). Deliberately no foreign key, so it never blocks deleting a person.

Split: first poem (inclusive) of the part that belongs to the new person

Split: first couplet (inclusive) of SplitFromPoemId that belongs to the new person

Split: last poem (inclusive) of the part that belongs to the new person; null = up to the end of the book

Split: last couplet (inclusive) of SplitToPoemId; null = the whole poem

Split: name of the new person (empty = same name)

Split: description of the new person

Merge/Split: report of what the approved operation did

suggester's note to the moderator

reviewed

correction review result

review date

review note

reviewer's user id