Tagging Per Location

[luukee]

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: https://github.com/engagingnewsproject/misinfo-dashboard/commit/7bafa1f35606d8c589c2adbb7f3de30f061947bb

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

[luukee]

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.