As a CIF administrator, I want to have access to specific project metabase views/questions, so that I don't have to repeat a large amount of join statements #1826
Due to the relational nature of the CIF database, aggregating CIF data can be quite cumbersome and lead to a large amount of join statements, which can lead to errors and confusion.
For example, linking a payment to the stream requires 5 or 6 relational hops that translate into joins in a metabase query.
This would be alleviated by creating ad-hoc views (or metabase questions) that aggregate some of that data already, especially in the case of 1..1 relationships.
What would go in those views is still TBD
Development Checklist:
[ ] Gather information from CIF about what data would be most helpful to be flattened into single views
[ ] Create SQL questions in metabase that flatten the above data into single views
[ ] Check that the SQL questions can be queried and joined on without issue
[ ] If there are issues, determine whether views coded directly in the database would work better
[ ] Meets the DOD
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)
·Definition of Done (Note: If any of these points are not applicable, mark N/A)
[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
Description:
Due to the relational nature of the CIF database, aggregating CIF data can be quite cumbersome and lead to a large amount of join statements, which can lead to errors and confusion. For example, linking a payment to the stream requires 5 or 6 relational hops that translate into joins in a metabase query.
This would be alleviated by creating ad-hoc views (or metabase questions) that aggregate some of that data already, especially in the case of 1..1 relationships.
What would go in those views is still TBD
Development Checklist:
Definition of Ready (Note: If any of these points are not applicable, mark N/A)
·Definition of Done (Note: If any of these points are not applicable, mark N/A)
Notes:
-