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

Add temporary ability to verify resources #446

Closed
vontell opened this issue Jun 18, 2024 · 1 comment · Fixed by #458
Closed

Add temporary ability to verify resources #446

vontell opened this issue Jun 18, 2024 · 1 comment · Fixed by #458
Assignees
Labels
Version 2 Features to be developed for Version 2.0 of the PHLASK App

Comments

@vontell
Copy link
Contributor

vontell commented Jun 18, 2024

In order to have a successful v2 launch of PHLask, we need to make sure that resources on the platform are verified. Currently, each resource in our database has a verified field, which is set to false by default.

We would like a way to easily mark resources as verified. Rather than building out a dashboard for admins (which we will do eventually), we will implement a feature within the app that allows us to mark a resource as verified or as not valid (and therefore deleted). The idea is that team members can go check various resources in person (or in streetview) and easily mark the resource as verified.

The below screenshots show a proposed design / flow for how this would work. Here are the main ideas:

  • A tag showing "VERIFIED" or "UNVERIFIED" is added to the detailed view of a resource. In the images below, I found that the bottom right of the image header of the resource is a good spot.
  • When that tag is clicked, a dialog pops up. An admin can enter a password (which we will provide to PHLask members) and then choose whether this should be marked as verified or deleted.
  • Based on what the user chooses, a call to firebase is made - either to delete that resource, or update its verified field to true.

image

Note that this feature may be removed soon after the launch, as we build out more official verification tools.

@vontell vontell added the Version 2 Features to be developed for Version 2.0 of the PHLASK App label Jun 18, 2024
@vontell vontell self-assigned this Jun 23, 2024
@vontell
Copy link
Contributor Author

vontell commented Jun 23, 2024

This is implemented in #458

@tomporvaz tomporvaz linked a pull request Jun 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Version 2 Features to be developed for Version 2.0 of the PHLASK App
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant