Filter Member Overview By FIR Category: VATSIM Enhancement
Hey guys! Today, we're diving into a feature request that could seriously streamline how VATSIM-Scandinavia manages its ATC roster. It’s all about getting a better handle on controller activity and making sure we’re not losing talented folks to inactivity. So, let’s break down the problem, the proposed solution, and why this could be a game-changer.
The Problem: Deteriorating ATC Roster
So, here's the deal: Our ATC roster isn't as lively as we'd like it to be. We're seeing controllers become inactive, and it's tough to keep tabs on everyone efficiently. Now, the core issue isn't just about numbers; it's about understanding why these controllers are stepping away. Are they facing technical issues? Time constraints? Lack of motivation? Knowing the reasons is the first step in addressing the problem.
Currently, we don't have a straightforward way to monitor controller activity for specific FIRs (Flight Information Regions). We need to be able to quickly identify controllers who haven't been active in a particular FIR, reach out to them, and see if there’s anything we can do to bring them back into the fold. It’s like trying to find a needle in a haystack when all you have is a magnet that picks up everything else too.
One could argue that this should be solved in a proactive manner, but we are certainly trying to do that as well. We’re not just sitting around waiting for controllers to become inactive; we’re actively working to keep them engaged. However, having a reactive tool to identify and address inactivity is crucial for maintaining a healthy and vibrant ATC community. It’s about having a safety net to catch those who might be slipping through the cracks.
The goal here is to not only retain controllers but also to foster a supportive environment where they feel valued and motivated to stay active. Understanding the reasons behind inactivity allows us to tailor our approach, whether it’s providing additional training, offering flexible scheduling options, or simply reaching out to show that we care. This feature request is about empowering us to do just that.
Proposed Solution: FIR-Specific Filtering
Here's the idea: Let’s add a filter to the “Member Overview” section that allows us to view members per FIR. This would be a massive time-saver and would allow us to quickly identify controllers who are inactive in a specific area. Instead of sifting through a list of all members, we could simply select a FIR and see only the controllers associated with that region.
Imagine the workflow: A FIR chief could log in, select their FIR, and instantly see a list of controllers who haven’t been active in the past month. They could then reach out to those controllers, offer assistance, and try to re-engage them. This targeted approach is far more efficient than the current method of manually tracking activity across the entire network.
The key benefit here is efficiency. It’s about making the most of our limited time and resources. By focusing our efforts on specific FIRs, we can ensure that we’re addressing the areas that need the most attention. It’s also about accountability. With this filter in place, FIR chiefs can take ownership of their roster and proactively manage controller activity.
Moreover, this feature would provide valuable data for identifying trends and patterns. Are controllers in certain FIRs more likely to become inactive? Are there specific times of the year when activity drops off? By analyzing this data, we can develop targeted strategies to address the root causes of inactivity and create a more sustainable ATC community. It's about turning data into actionable insights.
Alternatives Considered
API Token
I've considered asking for an API token, but it seems that the API does not provide enough parameters to provide the data I need. While an API token would offer some level of data access, it falls short of providing the specific filtering capabilities we need. The current API doesn't expose the necessary parameters to filter members by FIR and track their activity effectively.
The limitation here is granularity. We need a tool that allows us to drill down into specific FIRs and identify inactive controllers quickly. An API token, in its current state, doesn't offer that level of precision. It would require significant development effort to extend the API and add the necessary parameters, which might not be the most efficient use of resources.
Furthermore, relying on an API token would require us to build our own interface and data processing logic. This would add complexity and overhead to the process, making it less accessible to FIR chiefs and other stakeholders who might not have the technical expertise to work with APIs. The goal is to create a tool that is easy to use and requires minimal technical knowledge.
Nagging Tech
An additional alternative is to nag tech every time I want to get this data. Yeah, not ideal, right? Constantly bothering the tech team for data extracts is not a sustainable solution. It’s inefficient, time-consuming, and puts unnecessary strain on their resources. Plus, it creates a bottleneck that prevents us from quickly addressing inactivity issues.
The problem here is scalability. As the network grows and the number of FIRs increases, the demand for data extracts will only increase. This will overwhelm the tech team and make it impossible for them to keep up with the requests. We need a self-service solution that empowers FIR chiefs to access the data they need without relying on the tech team.
Moreover, relying on manual data extracts introduces the risk of errors and inconsistencies. The data might not be up-to-date, or it might be formatted in a way that is difficult to analyze. A dedicated filtering feature within the “Member Overview” section would ensure that the data is accurate, consistent, and readily available.
Additional Context: /users and atcActivity
/users provides the data I need, but I lack the filtering to limit the data to what I actually care about. From my understanding it should be possible to create a filter based on the atcActivity table.
The /users endpoint contains valuable information about our members, including their activity levels and FIR affiliations. However, without the ability to filter this data, it’s like trying to find a specific book in a library without a card catalog. We need a way to narrow down the results and focus on the controllers who are most relevant to our needs.
The atcActivity table seems like the perfect place to start. It likely contains data on controller activity within specific FIRs. By leveraging this table, we could create a filter that allows us to quickly identify inactive controllers in a given region. This would be a relatively straightforward implementation that would provide immediate benefits.
The technical feasibility of this solution seems high. We already have the data we need; we just need to expose it in a way that is accessible and user-friendly. By adding a simple filter to the “Member Overview” section, we could empower FIR chiefs to proactively manage their rosters and ensure that our ATC community remains vibrant and engaged. It’s a small change that could have a big impact.
Conclusion
So, there you have it! A simple filter in the Member Overview section could make a huge difference in how we manage our ATC roster. It’s about efficiency, accountability, and making sure we’re not losing talented controllers to inactivity. Let’s make it happen!