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

Update analytics documentation #2130

Closed
4 tasks done
acouch opened this issue Sep 17, 2024 · 7 comments · Fixed by #3562 or #3598
Closed
4 tasks done

Update analytics documentation #2130

acouch opened this issue Sep 17, 2024 · 7 comments · Fixed by #3562 or #3598
Assignees

Comments

@acouch
Copy link
Collaborator

acouch commented Sep 17, 2024


Migrated from navapbc#131
Originally created by @acouch on Tue, 02 Jul 2024 14:29:08 GMT


Summary

The current analytics readme and docs focuses on the previous version of the tool. It should be rewritten to reflect the recent changes.

It should highlight the fact that we have moved to capturing analytics in a postgres analytics database that will house our future analytics data and that we will use Metabase as a analyses and dashboard tool. It should highlight that system is architected so that the analytics work that will be part of the project can be run locally, though it is housed in AWS.

Acceptance criteria

  • README.md should be updated.
    • The introduction should reflect the goals and structure noted above. Bonus points if it can link to the architecture diagram and if a separate diagram can be created to show the metabase -> analytics database <- ECS python service.
    • The directory structure should be updated or removed
    • An "Data Pipeline Service" section should be written that explains the python portion
    • A sub-section of "Data Pipeline" should include "Current Data" section that describes the current data and its structure
    • Using the tool should be renamed "Using the Slack Tool" or something, and a "Local Development" section be written with quick instructions to start the tool and run github report, ie 1. start the containers make start 1a. setup the github login or token 2. export the current datamake sprint-data-export && make issue-data-export 3. import the data make sprint-db-data-import and 4. view the data in metabase ie go to localhost:3100
  • Technical Overview should be updated. The "Key Technologies" section could be updated to reflect that this is just the "Data pipeline service" part of the analytics. The "Orchestration" section should be be updated to include correct links https://github.com/navapbc/simpler-grants-gov/blob/main/documentation/analytics/technical-overview.md#orchestration
  • development.md should be updated to focus on the steps that were created for the README.md . Create two sections, "Analytics Data Pipeline" and "Slack Integration Tool". The first section could link to the readme install steps or expand on them. Copy/paste the items from usage.md to here, but use the make commands instead of the local poetry. The Github token thing might need to be included. Setting up the tool locally could be moved under that latter setting so it is clear it is just for the slack integration piece. make setup doesn't exist AFIACT so should be removed.
  • usage.md, should be updated so that the new stuff is removed and moved to 'development.md' and the file is renamed to "Usage of Slack Integration"
@acouch
Copy link
Collaborator Author

acouch commented Sep 17, 2024


Migrated from navapbc#131 (comment)
Originally created by @margaretspring on Thu, 18 Jul 2024 20:04:22 GMT


@aplybeah - Not sure if it's bc I'm checking this out from the Project view side of things, but it's sorta tricky to tease out what I should be reviewing as new content. It'd be great if you could point to or include links... for example When I tried to check out the README.md - The history doesn't indicate any changes. Another example, when I tried to check out the Technical Overview & the Orchestration updates - the 1st link went to a 404 error. Is there possibly a draft version that I'm supposed to look at & guidance is provided in the PR version opposed to the Project view of the issue?

@mxk0 mxk0 added the analytics label Oct 6, 2024
@mxk0 mxk0 moved this from Icebox to Todo in Simpler.Grants.gov Product Backlog Nov 11, 2024
@mxk0 mxk0 changed the title [Task]: Update analytics documentation to reflect metabase and analytics database and deemphasize slack and metric calculation Update analytics documentation to reflect metabase and analytics database and deemphasize slack and metric calculation Nov 11, 2024
@mdragon
Copy link
Collaborator

mdragon commented Jan 3, 2025

I checked in with Billy and he thought this would land well in some of their Analytics improvement work so I've pushed it over to their Epic and will remove it from the Nava Sprint.

@DavidDudas-Intuitial DavidDudas-Intuitial self-assigned this Jan 10, 2025
@DavidDudas-Intuitial DavidDudas-Intuitial changed the title Update analytics documentation to reflect metabase and analytics database and deemphasize slack and metric calculation Update analytics documentation Jan 10, 2025
@DavidDudas-Intuitial
Copy link
Collaborator

Image

@DavidDudas-Intuitial
Copy link
Collaborator

Image

@DavidDudas-Intuitial
Copy link
Collaborator

Image

@DavidDudas-Intuitial
Copy link
Collaborator

Image

@DavidDudas-Intuitial
Copy link
Collaborator

Follow up PR: #3598

DavidDudas-Intuitial added a commit that referenced this issue Jan 22, 2025
## Summary
Fixes #2130

### Time to review: __2 mins__

## Changes proposed
> What was added, updated, or removed in this PR.

A few minor additions to the analytics documentation, as requested in
the comments on PR #3562

## Context for reviewers
> Testing instructions, background context, more in-depth details of the
implementation, and anything else you'd like to call out or ask
reviewers. Explain how the changes were verified.

## Additional information
> Screenshots, GIF demos, code examples or output to help show the
changes working as expected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
4 participants