Can only certain pages (along with their properties, tags and Aliases etc.) be exported from one graph and imported to another graph in database version?
Say you are multilingual and you are planning a trip to a foreign country. You create one page with that country’s name in your native language and you create another page as alias in English. After gathering the information about that country, you realize that you created the notes in the wrong graph and now you want to move them to the correct graph, but only these two pages (the main page and the alias). Can this be done in LogseqDB?
Since Logseq DB is getting closer and closer to a release, I really want to know if we will be able to transfer pages from one graph to another.
If you make a complex template that has links to other pages/nodes which have their own content (tags, properties, descriptions, assets etc), you would want to be able to share it with your coworkers and friend as is, with the structure it has in the original graph.
Up to now, the export function only exports the one page (ignoring the linked pages and everything else). And even worse, when you try to import it to another graph, it only allows to create a new graph with only that page’s content. What is the purpose of exporting single pages if you cannot import a single page to another graph?
This is a deal breaker, and it’s making me think if Logseq DB is a viable option for me .
good news is that there are going to be multiple ways to possibly achieve your goals here
for the template share- the public roadmap has an upcoming project specifically for a “template share” to make sharing templates cleaner and easier
for generic page share with properties- the team just finished a markdown mirror and is currently finishing a Two-way sync between Markdown and db
graph. in theory, this means you would be able to share your actual pages with relevant properties as simple as dropping the files locally
last note is that the export functions have undergone more maturation to capture more on export- i’m not sure if it would capture the issue you’re interested in or not, but if there are gaps- people reporting issues only help us get better together!
I don’t know what markdown mirror means, but if the team is working one features like this then it would be great. I check the nightly builds from time to time, but I haven’t seen anything close to this, hence the question above. So for now we just wait and see. Thanks for the reply.
And there is also an experimental feature of having 2 way sync: right now if you edit your DB graph it will be reflected to the MD graph. What this new feature would do is add the reverse: you would be able to edit your MD pages and these changes would be synced back to the DB version of your graph. You can watch it here and this is the PR for it
Oh, markdown mirror is not what I need. I don’t want to share my entire graph with others. I want to be able to export and import individual pages (along with all their properties, links, assets etc) in unrelated DB graphs.
But the problem is that, currently, when you try to import a single page it creates a new graph. I want to be able to import a few pages in an existing graph. And since we are moving away from MD, why use it in the DB version since EDN is used as a base? I am a bit confused.
.