-
Notifications
You must be signed in to change notification settings - Fork 39
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 to CSV #86
Comments
nods I was thinking the same thing. Mastodon exports e.g. following/follows as CSV, which may be a pattern to use for exporting from the activitypub.db file. |
another point in favor of CSV that just occurred to me-- if we make all fields except URL optional, and make URL the first column, we could a) reasonably detect if the first row is a header column or not and b) accept a file that was just a list of URLs using the same parser? 🤔 |
right now we make the SQLite db available for download on the admin page, but a quick export to something friendlier (CSV, JSON, etc) would probably be appreciated. CSV seems most likely to be useful to import into other things, based on experience with bookmarking/read-later/etc services.
UPDATE: re-naming this issue to specifically scope this ticket to CSV, which @PatOConnor43 has made a great start on in #118. I would consider export to other formats in their own tickets with clear naming, details of what the format is, and an explanation for the intended use case if it's not something immediately obvious like another bookmarking service.
The text was updated successfully, but these errors were encountered: