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

Transaction enrichment should handle the initial backfill as a special case #1549

Open
zachgoll opened this issue Dec 16, 2024 · 0 comments
Open
Labels
💻 Self Hosted only Issues pertaining to self-hosted versions of Maybe 3️⃣ Low priority Contributions accepted, but Maybe team will not be working on this in the near term

Comments

@zachgoll
Copy link
Collaborator

Currently, transaction enrichment via Synth will loop through all user transaction entries and attempt to auto-assign categories, clean up the name on the transaction, and assign a merchant.

Since many users have thousands of transactions that need to be backfilled, we should give the user more control over which transactions will be enriched (and consume Synth credits). Currently, new self hosted instances will have data enrichment turned off by default, but no controls around what data will be synced when this is turned on:

CleanShot 2024-12-16 at 11 01 33

@zachgoll zachgoll added the 💻 Self Hosted only Issues pertaining to self-hosted versions of Maybe label Dec 20, 2024
@zachgoll zachgoll added 3️⃣ Low priority Contributions accepted, but Maybe team will not be working on this in the near term and removed 💡 Improvement labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 Self Hosted only Issues pertaining to self-hosted versions of Maybe 3️⃣ Low priority Contributions accepted, but Maybe team will not be working on this in the near term
Projects
None yet
Development

No branches or pull requests

1 participant