Migrating namespaces from OG to DB

[armand000]

Hi!

I am a (french, sorry for the english) student using Logseq for years, and I am willing to move to Logseq DB. I imported my graph in DB and looked if everything was okay. But:

With Logseq OG, I used to take notes of my courses with a Namespaces architecture. It let me have a clear overview of the chapters with the “Hierarchy” section of any parent page, and everything was well organized:

Logseq OG ↴

But with the Logseq DB’s Namespaces, this turn into (sorry for saying that!!!) garbage because parents pages are overloaded with all the content of all the child pages.

Maybe I am missing something, but, look at the “History” page in OG versus in DB:

Logseq OG ↴ (there is content in this page, I know immediately that ÉU is a part of the history class with the page’s title, and the “Hierarchy” section let me navigate to any chapter very quickly)

Logseq DB ↴ (the content of the page seems to have disappeared, the title of the page is not clear anymore with just “ÉU” and no hierarchical context, and all the child pages are displayed in this page, making the app crash and preventing me to overview the different chapters/parts…)

Moreover, if I search for a particular page, for instance the part II of the third chapter of the United States’s history, it become very difficult to tell apart different pages:

Logseq DB ↴

Logseg OG ↴

Maybe I was on an “edge usecase” in Logseq OG so this note-taking architecture has not been considered in DB, but I wanted to know if any member of the community have been facing the same issue, and if there is a solution to it.

Huge thanks to the developpers for this app and, in advance, to the community!

[Creator]

Namespaces haven’t been implemented yet on DB version, I think they forgot about the feature since it’s not on the roadmap.

Additionally if you try to link to a namespaced page e.g. [[fruit/apple]] then that won’t work either.

[danzu]

Namespace is implemented in Logseq DB. He is using it in the example he shared.

[Creator]

I thought it obvious from posts but to clarify then: it’s only got a basic reimplementation so far compared to Logseq OG.

[armand000]

I know that I am using the Namespace’s implementation of Logseq DB. What I would like to know is if there is a path for those who used Namespaces the way I did, in DB.

= Is it possible to replicate “my workflow” in DB, or is it left behind?

[blork]

Seems left behind. Which sucks, I was also a heavy namespace user and I cannot believe smarter tags required the kneecapping of so many other pieces of my workflow.

There is the [[Library]] but it’s so frustrating and less intuitive.

[jar]

might interest some how this plugin can utilize namespaces

Discord - Group Chat That’s All Fun & Games

[armand000]

Another difference (which is, from my view, a regression): “namespaced pages” seems to no longer be linked to their parent page, at least in the graph view.

OG’s graph view:

DB’s graph view (exact same set of notes):

[jar]

could you make an issue on the github? they are refactoring the graph right now so it would be an excellent time for them to see that kind of feedback