Skip to content

Enhancement: Updating Verification Request schema and adapting parameters in Verification Request form #1960

@lucaslobatob

Description

@lucaslobatob

Background Information

  • We need to update the Verification Request schema with the receptionChannel, reportType, and impactArea parameters.
  • The impactArea params needs Wikidata to generate the report topics.
  • Update the Verification Request form.

How

Updating schemas

These are the schemas of the new parameters that we must add to the schema of a verification request

receptionChannel - (defined by some function that identifies the channel)
@Prop({
required: true,
enum: ["site", "instagram", "whatsapp"],
})
receptionChannel: string;

reportType
@Prop({
required: true,
enum: ContentModelEnum // Speech, Image, Debate, Unattributed
})
reportType: ContentModelEnum

impactArea - (wikidata filtered topics)
@Prop({
required: false,
enum: ["saude", "politica", "meio-ambiente", "direitos-humanos"],
})
impactArea: string;

severity - (initially does not require)
export enum Severity {
LOW = "low",
MEDIUM = "medium",
HIGH = "high",
CRITICAL = "critical"
}

@Prop({
required: false,
enum: Severity,
})
severity: Severity;

Adaptation of parameters in the verification request form

Among the four new parameters, only two were included in the verification request creation form

visual example:
Image

Expected Behavior

The intention is that we can create new verifications requests with new parameters defined in the database and in the creation form, maintaining the old design for this first version

Sub-issues

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions