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 resource_cnt column to c_system_use tables #31

Open
gotdan opened this issue May 24, 2024 · 4 comments
Open

Add resource_cnt column to c_system_use tables #31

gotdan opened this issue May 24, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@gotdan
Copy link

gotdan commented May 24, 2024

It seems like these values are mostly interesting in the context of the total resource count in that category, status and year.

@mikix
Copy link
Contributor

mikix commented May 28, 2024

This and #32 seem like yet another cube vs aggregate issue. A CUBE provides that info automatically.

But you could also get it by summing up the aggregate rows, right?

@gotdan
Copy link
Author

gotdan commented May 28, 2024

I think that's only true if a terminology element is populated in all resources though. If I want to get a sense of how many Encounters I can find with a particular coding, I think the total number of Encounters would be the more useful denominator, not the total number of Encounters with a coding populated.

@mikix
Copy link
Contributor

mikix commented May 28, 2024

The rows with cumulus__none for the systems field will tell you the count of Encounters without any terminology element populated (as well as Encounters with the element populated but no actual system filled in).

So you should still be able to sum up to get the total.

@gotdan
Copy link
Author

gotdan commented May 28, 2024

Ah, cool, in that case agree that summing in a query in the presentation layer could be a workaround.

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
None yet
Development

No branches or pull requests

2 participants