-
Notifications
You must be signed in to change notification settings - Fork 35
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
Add Logseq to import tools #2
Comments
If you look at the first pull request, it already adds rudimentary support for importing Logseq. The goal of making this repository open source is to enable the user community to build out support for the tools that they want. Feel free to test the code in PR #1 and submit PRs to improve it, or specific feature requests/bug reports to the author, etc. |
@houshuang fully understood. i think one of the dilemmas users face is not wanting to pollute their KB. early access != beta testers. |
like this isn't reasonable for any casual user expecting the content to import: i'm not complaining "someone should have done better!!!" i'm just saying this isn't yet a tool people can use to migrate from logseq to tana. not everyone is an engineer and can just dive in to scratch their own itches. @davidjaggi's request remains valid and eventually enough engineers who care about this can make it a reality. |
@houshuang having thought about this for a few hours I'll offer a different lens in the form of a question: Can you please advise how a user could test importing their Logseq data, to help you test, in a quarantined KB that does not pollute their primary? Thank you! |
@jkmaxwell Well every single import happens in a separate workspace, which you can remove afterwards, so that should not be a problem. Feel free to look at the Roam import video in the help center for how this looks. It would be the same with Logseq or Obsidian data. |
I appreciate your interest and enthusiasm. I totally agree that the list above is not reasonable for any casual user, and Tana has never said that we offer well supported Logseq support. We'd love to support lot's of products' data, but we don't have the capacity to support anything other than Roam yet, so we made this open source collaboration. Once Obsidian and Logseq are mature enough, we'll include them directly in the Tana interface and support them with help center docs etc, then they will be ready for casual users. Currently it's only for people very happy with experimentation. |
As a frequent Logseq user, I have all of my notes stored in Logseq. A good import solution into Tana will be vital to make the switch as smooth as possible.
The text was updated successfully, but these errors were encountered: