Feasibility Review: wins form entry edit feature

[ExperimentsInHonesty]

Overview

Users would like the opportunity to be able to edit their wins after it is submitted so that they can have more control over their submitted info. For this issue, as a developer, we will determine

1. the feasibility of allowing users to edit their wins submissions, and
2. then how to identify a changed win on the spreadsheet so that its status is switched to Display:False and then a new issue is opened in the repo notifying project managers to re-review.

Details

Currently, we already have a spreadsheet with existing data from Wins form submissions by users. From Wins form research conducted by UX Researcher Vivian, it was determined that users would like the ability to edit their Wins entries after submitting them. Thus, we (developers) need to determine the feasibility of allowing editing after submission.

Action Items

• Read about the Wins page in the wiki
• In order to understand how our Wins form and response spreadsheet are set up, you can request "Viewer" access to the "Wins-form", "Wins-form (Responses)", and the Apps Script associated with the "Wins-form (Responses)" files in the "HfLA website Admin" Google Drive from a Merge Team member or Tech Lead. See Meet the Team wiki page for their contact info.
  • Then, you need to re-create the "Wins-form" and "Wins-form (Responses)" within your own Google Drive, including copying and pasting any Google Apps Script into your own Google Drive.
  • You will also need to set up your own Personal Access Token to use with the Google Apps Script in your own Google Drive. (Note: Personal Access Tokens are like passwords, so be very careful with them.)
    • Request 1Password account (from Bonnie at team meeting or through your lead, or via Admin slack channel by referencing this issue as a link), so that you can store your own personal access tokens for this project in your private vault.
  • Test out how allowing users to edit their submissions will work in your own Google Drive and GitHub
• Determine the feasibility of allowing editing after a Wins form submission. As a starting point for your feasibility assessment, consider the following questions:
  • If editing is enabled, how would we determine if an entry was edited by the user in order to re-review their edits before it is updated on the site?
  • What happens when editing is enabled and someone edits their submission? Does it change the timestamp on the form? Does it have some other indication it was changed?
  • Is there a way to check the spreadsheet with Google AppScript that a submission was edited by the user? For example, can the status for the entry be switched to Display:False?
  • Can a new issue be opened in the repo notifying project manager(s) to re-review a Wins submission? How would they know which Wins submission to re-review?
  • Be sure to include anything else you find as part of your assessment/research
• Write up a feasibility report in a Google Doc in the "HackforLA.org website" Google Drive and add a link to it in the Resources/Instructions section below
• Go over your feasibility report with the tech lead(s) and PM(s), including possibly demoing what happens when a user edits their submission. Also, discuss with tech lead(s) and PM(s) what the next steps are.
• Merge Team member or Tech Lead: After closing this issue, if the assignee is not a member of Merge Team nor a Tech Lead, please remove the assignee's access to the "Wins-form" and "Wins-form (Responses)" files in the "HfLA website Admin" Google Drive.

Resources/Instructions

• Tracked in issue Add editing feature for win submission form #3143
• Meet the Team wiki page
• Wins webpage
• Wins wiki page
• Link to feasibility report: [INSERT LINK TO FEASIBILITY REPORT HERE]

[github-actions]

Hi @ExperimentsInHonesty.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Size, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[JessicaLucindaCheng]

Temporarily putting what I wrote in the issue above here because I can't seem to save my edits in the top post.

Edit: This was copied to the top and saved successfully.

Overview

Users would like the opportunity to be able to edit their wins after it is submitted so that they can have more control over their submitted info. For this issue, as a developer, we will determine the feasibility of allowing users to edit their wins submissions.

Details

Currently, we already have a spreadsheet with existing data from Wins form submissions by users. From Wins form research conducted by UX Researcher Vivian, it was determined that users would like the ability to edit their Wins entries after submitting them. Thus, we (developers) need to determine the feasibility of allowing editing after submission.

Action Items

• Read the Wins page in the wiki
• Determine the feasibility of allowing editing after a Wins form submission. As a starting point for your feasibility assessment, consider the following questions:
  • If editing is enabled, how would we determine if an entry was edited by the user in order to re-review their edits before it is updated on the site?
  • What happens when editing is enabled and someone edits their submission? Does it change the timestamp on the form? Does it have some other indication it was changed?
  • Is there a way to check the spreadsheet with Google AppScript that a submission was edited by the user?
  • Be sure to include anything else you find as part of your assessment/research
• In order to understand how our Wins form and response spreadsheet are set up, you can request "Contributor" access to the "Wins-form" and "Wins-form (Responses)" files in the "HfLA website Admin" Google Drive from a Merge Team member or Tech Lead. See Meet the Team wiki page for their contact info.
  • Then, you need to re-create the "Wins-form" and "Wins-form (Responses)" within your own Google Drive, including copying and pasting any Google Apps Script into your own Google Drive.
  • You will also need to set up your own Personal Access Token to use with the Google Apps Script in your own Google Drive. (Note: Personal Access Tokens are like passwords, so be very careful with them.)
  • Test out how allowing users to edit their submissions will work in your own Google Drive and GitHub
• Write up a feasibility report in a Google Doc in the "HackforLA.org website" Google Drive and add a link to it in the Resources/Instructions section below
• Go over your feasibility report with the tech lead(s) and PM(s), including possibly demoing what happens when a user edits their submission. Also, discuss with tech lead(s) and PM(s) what the next steps are.
• Merge Team member or Tech Lead: After closing this issue, if the assignee is not a member of Merge Team nor a Tech Lead, please remove the assignee's access to the "Wins-form" and "Wins-form (Responses)" files in the "HfLA website Admin" Google Drive.

Resources/Instructions

• Tracked in issue Add editing feature for win submission form #3143
• Meet the Team wiki page
• Wins webpage
• Wins wiki page
• Link to feasibility report: [INSERT LINK TO FEASIBILITY REPORT HERE]