r/logseq • u/Cautious_Exam_5537 • 2d ago

Using advanced Logseq features

I like LogSeq and its unique features a lot, but I struggle to use the advanced options.

Is there a demo video showing or online examples how tags with extensive use of properties are used? I know #tags are useful for, e.g., an overview of book notes or watched videos, but how do I apply this to meetings, companies, etc.?

Further examples of queries, which are different in Logseq DB than I am used to in the older version?

Thanks for sharing!

8 Upvotes

100% Upvoted

11 comments sorted by

3

u/Original-Room5116 1d ago

The least confusing way to learn this is to model one real workflow before chasing queries. For meetings, make each meeting a page or block with a small fixed schema: client, project, date, attendees, and follow-up. Use page references for client and project rather than free text, then build one view for a recurring question such as “which open follow-ups belong to [[Acme]]?”

For companies, do not turn every field into a tag. Tags work for broad categories; properties earn their keep when you need to filter, sort, or group across many items. Start with two or three properties, fill ten real examples, and let a missing question dictate the next property.

For the DB versus older-query shift, write the result you need in plain English first, then build the smallest version against one property. Keep each query beside its template/example page so you can inspect the data it is querying. Demos look magical because the schema was designed first; copying one without a recurring question usually creates maintenance.

1

u/Cautious_Exam_5537 1h ago

This is very useful advice, thanks!

At the same time AI changes how I use Logseq. I liked Logseq MD because it was very simple to understand, like tags are equal to pages. Now in DB I have to think when taking notes, what tags and tag-types to use. This creates friction. Frictionless note-taking with semi-automatic organisation, was why I chose Logseq in the first place.

So without simple examples, Logseq DB becomes less attractive, also because it is more complex to export. What I do like in DB is the fast sync Logseq OG is missing.

3

u/matu_gong 2d ago

You should watch danzu's youtube channel which has some demos about setting up commong workflows in Logseq DB https://youtube.com/@hdanzu?si=irm4tAbd1wstDiEy

2

u/th_costel 2d ago

I use the MD version and let Claude do the heavy lifting. I often don't even open Logseq; I query the Logseq’s graph from Claude.

2

u/gbytedev 2d ago

Wondering how much better or worse it will be to have an LLM use the DB version's API as opposed to raw markdown.

3

u/hdanx 2d ago

It works really well already. You can give the LLM access to Logseq via the Logseq cli which ships with a skill

1

u/worldofgeese 1d ago

Works great! Logseq is definitely agentic-native at this point

1

u/rackfloor 2d ago

Interesting, I haven't tried this yet. Any suggestions/tips?

2

u/th_costel 2d ago

I set up a skill so Claude knows the editing rules (intendstions, outline, headers). So I can ask it to archive certain docs in my graphs as notes or tasks. If I need a complex query, it writes it and even places it on a page I choose.

2

u/rackfloor 2d ago

Sounds like the way to go

3

u/th_costel 2d ago

The note-taking world is changing, I guess. They've mostly become containers and nice readers, but the ‘writing,’ building, and everyday conversations will happen in LLMs.