dpgabot/validate-digitalpublicgoods

validate-digitalpublicgoods's Issues

Record time to complete a review

Currently the form records the timestamp at the end of the submission here.

In addition to the current timestamping, we would like to record the time difference between the moment that the user starts reviewing the first question to the time they submit, (recorded as a Time_end - Time_start in milliseconds) and added as an additional field to the submission. We will later use this additional data point to filter out those submissions where the user quickly browsed the entirety of the form arbitrarily clicking yes or no without thoughtfully analyzing each question.

Link to SDG Goals

For every mention on relevance to the individual SDG, link to the SDG website to provide enough information to assess that relevance. Consider display additional information on SDG indicators

Update "Almost Done" to "Done" in final screen

Once the submission has been completed, update the "Almost Done" to "Done" title page.

Track projects already reviewed by user, and prevent double submissions

Require one meaningful comment

Require at least one "meaningful comment" before the submission is processed to filter out submissions that don't add value.

The very basic and minimum implementation for this feature would be to check whether there is at least one non-empty comment field in the entire form, and prevent the user from submitting the form unless that requirement is met. The "non-empty" can be further enhanced with additional checks. We are open to suggestions on how to implement the requirement to be "meaningful".

Add timestamp and author fields to submission

Add two additional fields to the JSON field that document the timestamp and author of the submission

Add optional SKIP button

In addition to Yes, No buttons, add a Skip button for users who are not confident answering certain questions.

Add confidence slider

Add a required slider (1 through 5) for users to say their degree of confidence in their responses.

Submitting PR when validating DPG trying to retrieve reference to 'master' instead of 'main'

Hi @lacabra !
I'm an Outreachy applicant and noticed there were a few other applicants having issues when trying to submit their review of a DPG. One of the other applicants noted that this was to do with the process trying to find the master branch, which has now been renamed to main across the projects.
DPGAlliance/publicgoods-candidates#178 (comment)

Have come across a similar issue before, so wanted to check where this could be coming from.

I'm not sure if the production .env file has been updated, but the template still references master as the NEXT_PUBLIC_GITHUB_MAIN which is used as the main const in components/openpr.js https://github.com/lacabra/validate-digitalpublicgoods/blob/main/.env.local.example
https://github.com/lacabra/validate-digitalpublicgoods/blob/main/components/openpr.js

Add optional comment box for every response

Provide an optional opportunity for reviewers to comment on why they agree or disagree in their review

Bullet points for longer description of documentation question

Displaying the description text in the documentation question as a bullet list will improve readability

Add an project overview/details to every question

Add GitHub actions to enforce code style

As a continuation of the work started in #14, configure the CI through GitHub Actions to enforce the code style upon committing files to the repo.

Randomize display of potential projects

Address the issue that users may default to selecting the first project that is displayed. Thus, randomize the order in which these get displayed.

Display summary of responses before submission

User could have second thoughts about how s/he responded to one of the questions especially after a second glance at what the user entered earlier prompting the user to want to update their response. If the user is able to see the entire summary of answers provided, then the user can probably revisit and change. So the summary page just allows you to confirm your answers before final submission, similar to job application systems which permits to verify your answers are accurate before final submission.

Cc: @nathanbaleeta

Add optional feedback box at the end of each submission

Integrate an opportunity to provide feedback to the process at the end of each submission.