-
-
Notifications
You must be signed in to change notification settings - Fork 8
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Export Data #63
Comments
Yes. Unfortunately it is easier currently with the resources we have to run the export manually but we could potentially have it run on a scheduled cron job and email a link to the user. |
Hi! How does one run the export manually? I don't really want automated
exports, I just want one whenever I need one.
…On Fri, 24 Jan 2025, 12:48 Dr. Matt Lee, ***@***.***> wrote:
Yes. Unfortunately it is easier currently with the resources we have to
run the export manually but we could potentially have it run on a scheduled
cron job and email a link to the user.
—
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARAPQPJD2PNT25QJTPPLYRD2MHSKRAVCNFSM6AAAAABVY3T2DOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJRG43DQOJSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Email support and we run it and email the files back to you ASAP. |
I see, thank you! I'll be sure to email support when I need these csvs. That said, it would be less pressure on the support team if the user could just... download it from their account panel. |
It takes longer to run than it would be desirable to run automatically without slowing down the service for everyone. Running it as needed doesn't give us that issue. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
It would be nice if the user could easily export their listening data (CSV, JSON, anything of the sort) when they are logged into their user.
The text was updated successfully, but these errors were encountered: