How to go back from logseq-db version to logseq OG

[azarmadr]

Hi, i have been experimenting with db version. But now, i want to go back to OG version.

• The db_export.edn is not importable in the OG version.
• The markdown version has some information loss, since the tags disappear from the files.

How to go back to OG from db-version?

[Harlock]

@azarmadr

But now, i want to go back to OG version.

Please explain what is wrong with the DB version. Users who are considering migrating from MD version might find this useful.

[ZenArtist]

Sad to know that going back from DB to MD version is destructive. I’m much more concerned about switching now.

[azarmadr]

I love the new tags, the properties etc.

But the db version still doesn’t feel complete.

!Disclaimer
I still haven’t perfected my PKM methods, i have been hopping from one app to another, but Logseq is the longest I’ve used.

The main issues i faced so far

• unable to import a single file.
  • all imports go into a db
  • no inter-graph communication
    • we can’t copy items from graph to another
• exporting out as noted above
• copying/exporting a block as a html is not working
• copy/cut/move is not working
  • might be my browser/pc’s fault

[LifeSMyth]

me too, I’m too dependent on using Hyperlink (local LLM) to scan my Logseq Graph. In order to make the switch to DB I need to be able to export back to MD. Maybe that is still useable, but the loss of tags in export could be an issue for me.

[CountOfCount]

Same here. The db-sync works doggy at best - moreover I won’t be able to use the db version in a corporate environment, where I am not allowed to use a non-authorizes web/internet service. The future looks bleak for me…has anyone found a way to “re-migrate” to the MD version?

[Eric_D]

I found an internal suggestion that using “Page Tags” instead of (or as well as) “Tags” to wiki-link among pages may be the way to make it reverse-compatible (DB-to-MD).

I say “MD” where you say “OG”.

Data structures for bridging Logseq-MD to Logseq-DB

I found a little hint. Property ::Page Tags Description: Provides a way for a page to associate to another page i.e. backward compatible tagging. So “Page Tags” are related to the Logseq-MD to Logseq-DB transition. Using my Gemini AI ‘Gem’, it suggests [image] [image] [image] So when round-tripping a Graph between MD and DB, “Tags” in MD convert to “Page Tags” in DB? But “Tags’“ in DB are “New Tags” with structure and inheritance, so are not exported back to MD. If you want revers…

My interest in MD-compatibility is for web and PWA (Portable Web App) compatibility. Using tablet, phone, Android etc.

demo.logseq.com is Logseq-MD using browser and local file system
test.logseq.com is Logseq-DB using browser and local file system

I appreciate the full power of DB, using the full Schema.org data structure, but it takes a lot of work setting-up and getting used to it.

It seems that full round-trip compatibility is an ambition for the developers, but a public version launch (not Beta) must be their priority. I did not get much hope from that linked thread.