Spike: Snowflake Exploration
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 7
- Avg merge
- 15h 49m
- Merged PRs (30d)
- 57
Description
#### Description:
Look into Camis' prod data to explore how the site works. Note: team highlights that this work will most likely take months to dig through.
#### Acceptance Criteria:
- [x] gain access to Snowflake
- [x] document helpful pieces
- [ ] determine whether we want to export the data
- [ ] develop ETL process
#### Development Checklist:
- [ ] ...
- [ ] ...
- [ ] ...
#### Dependencies
- Blocked by
- Blocking
**Relevant documentation as reference**
**Definition of Ready**
- [ ] Acceptance criteria are included
- [ ] Wireframes are included (if applicable)
- [ ] Design / Solution is accepted by Product Owner (if applicable)
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)
**Definition of Done**
- In progress:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] UI meets accessibility requirements
- [ ] Unit tests are written
- [ ] Work is traceable in GitHub
- [ ] PR linked to ticket number
- [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
- Code review:
- [ ] Code is peer reviewed and has passed CI/CD tests
- QA:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Code is potentially shippable to the production environment
- [ ] Functional features have been tested and passed by QA
- [ ] UI components tested by designer
- [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
- PO Review:
- [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
- [ ] Reviewed and approved by Product Owner
#### Notes:
-
-
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the existing Snowflake access and documented helpful pieces, then clarify whether data export is wanted and what the ETL process must cover. Done means the export decision is recorded and an agreed ETL process is developed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- data-engineering, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100