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

Tagging Per Location #22

Open
luukee opened this issue May 28, 2024 · 1 comment
Open

Tagging Per Location #22

luukee opened this issue May 28, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@luukee
Copy link
Contributor

luukee commented May 28, 2024

Each location (State/Region & City) needs their own set of tags, labels sources.

Locations need to be set up per agency first. The locations collection in Firestore. Hardcoded for Austin, Texas in the Auth file.

Started Locations work in this commit: 7bafa1f

If you have a better idea please let me know, thanks!
Luke

@luukee luukee added the bug Something isn't working label Jun 13, 2024
@luukee
Copy link
Contributor Author

luukee commented Jul 12, 2024

Completed:

"Creates a tag document for a pre-existing agency if it does not exist when the agency is selected in the new report modal"

  • Makes sense. Tested and its working. Thank you.

"Creates a tag document for a pre-existing agency if it does not exist when the agency is editing their tags"

  • Cool. Tested and its working. Thanks!

Creates a tag document with default sources, topics, and labels for agencies upon creation

  • Great! @julia-elias In my testing a new document was created with a Topic map field but not the Source or Labels fields. This could have been a local dev or emulator exception, but I wanted to mention it.

In progress:

Dropdown selection in an admin user's tag view so they can select which agency to view the tags of

  • This is a great feature. Excited to see!

Testing:

  • Ensure that default tags are populated when an agency without a tags collection is trying to edit their tags
  • Creating of new tag by user to make sure that it goes to the right agency's tag collection
  • Ensuring that the right topics and sources are populated when a user is making a report

Other notes...

  • One issue we will run into with different agencies is the localId hardcoded as "Austin" in the AuthContext.jsx file (line 41).

    • Fix "Austin" hardcoded in AuthContext.jsx file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants