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

Per-event ConCat reports #2

Open
glitchfur opened this issue Jul 14, 2024 · 0 comments
Open

Per-event ConCat reports #2

glitchfur opened this issue Jul 14, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@glitchfur
Copy link
Member

Currently, Tracker will use the CONCAT_BASE_URI environment variable to determine which ConCat instance to use when running reports that rely on it (specifically the Volunteer Applications and Application Department Summary reports). However, there is not a way to specify different ConCat instances for different events within Tracker. The same ConCat data will be pulled regardless of event chosen.

For example, ConCat typically archives previous year data for conventions by making it available at a subdomain (such as 2023.reg.example.com). Ideally, when having distinct con years as different "events" in Tracker, they should be able to pull reporting data from that year's ConCat URL rather than the current one.

The ConCat environment variables, including client ID and secret, should then only be used for logging into Tracker. Each event in Tracker should separately store a ConCat base URL, client ID and secret in the database to ensure it's pulling data from the correct source.

@glitchfur glitchfur added the enhancement New feature or request label Jul 14, 2024
@Gawdl3y Gawdl3y moved this to On Deck in Tracker planning Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: On Deck
Development

No branches or pull requests

2 participants