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

Find verifiers for reports in novel NACE categories #174

Closed
alexanderzatko opened this issue Nov 12, 2022 · 1 comment
Closed

Find verifiers for reports in novel NACE categories #174

alexanderzatko opened this issue Nov 12, 2022 · 1 comment

Comments

@alexanderzatko
Copy link
Owner

alexanderzatko commented Nov 12, 2022

If a work report is filed in a NACE category that has fewer than 2 (or 3) experts, the work report will not get currently verified.
In this case, Rovas should send verification requests to selected users to voluntarily verify such reports.

The user profile will gain new fields:
Voluntary verification

  1. undecided (default)
  2. I will try to verify any reports
  3. I am unwilling to verify reports from outside of the areas I work

Refused to verify report
the node ID the user declined to verify (to avoid asking them again to verify the same report in the future)

The work report will gain a new field:
Verification reward of type decimal (default will be 0)

Workflow

  1. Rovas detects that the just filed report can't be verified, due to lack of experts,
  2. Rovas sends an email to the report author, to set a reward to potential verifiers of the report. The email lists the reward amount value (1/3, or 1/2 of the offered amount),
  3. the mail recipient clicks a link that will open a simplified work report editing form with just the field to set the reward, possibly with couple of other pieces of info
  4. If the user sets a reward amount

The verifier selection criteria

  • The Voluntary verification of a user has value 1 or 2
  • has filed work reports,
  • does not have negative compliance, nor Merit score,
  • is randomly selected from the set

verification workflow

  1. CRON that skans unverified reports will check that the report has no verifiers because there are no experts
  2. the CRON process checks that the report has a reward set
  3. a verifier is found and an invitation is sent
  4. verifier declines verification of the report - mark that node ID into the user profile, to prevent them from being asked to verify the same rejected report again.
  5. verifier verifies the report (report not verified yet) - mark that node ID into the user profile, to prevent them from being asked to verify the same rejected report again.
  6. report gets approved or rejected - clean entry for this report ID from the Refused to verify report field in all user profiles
  7. create AURs for all of the verifiers
@alexanderzatko
Copy link
Owner Author

Implemented in a different way, but completed. Here are the pieces touched by this update:

content type
work-report
update computed field field_work_report_buttons
verification-slot

new/edited views
top_compliant_users
find_slot_for_verifiaction
report_slots

new/edited rules
rules_ask_user_to_verify_report
rules_create_verify_slot
rules_find_verification_slips
rules_send_email
change TO email

							rules_verifiability
							rules_create_work_report
							rules_find_verifier
							rules_verify_work_report
							rules_process_outstanding_verifications
							rules_delete_voluntary_verification_slips

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant