Logseq - Collecting Blocks in Tables

[@LAWRENCESYSTEMS]

Thank you! Your videos have been really helpful for learning LogSeq.

[@toolsontech]

That's always the best thing to hear, enjoy Logseq!

[@pjpw2320]

Hi Bas, thank you for your down to earth and easy to follow videos on using Logseq. I am interested in your thoughts on best practice options for printing Logseq content for presentation purposes or even just for informal use.

[@toolsontech]

Haven't got a good solution for printing documents, having a way to export to proper PDF is still on my wishlist. Once I do figure out a good solution (or probably plugin) I will definitely make a video about it.

[@ABCtarou95]

I wish Logseq has the function to automatically add some default properties set by the users when some tags are applied, just like the way "supertag" on Tana works. Otherwise adding the same properties again and again whenever I apply some specific tags is just too time consuming. Of course I know there are some add-ons to do similar things on Logseq and I tried, and result was not good...

[@toolsontech]

Not good enough at all, agree fully with this and know work is getting done but just wish it was here already

[@edjwise]

I dream of an offline Tana... LogSeq needs views and something like supertags.

[@voldefox]

@@edjwise if I'm not wrong, the future database version system of Logseq will allow this, right?

[@indigoverly5897]

Hello, I followed your steps but the ingredients property does not show up in the table. I'm using 0.10.2 W10.

[@toolsontech]

Hey, that's a bit hard to debug remote, but if you're on the Logseq Discord then feel free to ping me and I would be happy to have a look together.

[@syedabdullah-jk6oe]

Good work Indeed. Could you please make a short tutorial on citation manager plugin used in Logseq? Your efforts would be highly appreciated.

[@andypassion5787]

Hi! But are we able to group results in table view by... (for example by Ingredients)?

[@toolsontech]

It might be possible with the right query, but it would require some debugging. I usually just modify the query to include what I want to work around it. Would be awesome to have better grouping options.

[@JustinSCampbell]

Great video Bas. I feel that I could be using properties a lot more than what I'm currently doing. I wish they would improve string properties. Each property should be treated separately.

[@toolsontech]

Agreed, really looking forward to the work being done there. The mockups from Logseq on what they are working towards look amazing.

[@JustinSCampbell]

To be fair, 2 years ago, I was just hoping OneNote would add tags and improve how tasks are handled. Logseq is pretty amazing. @@toolsontech

[@AR-ym4zh]

​@toolsontech I'm very excited for the page properties overhaul. I currently have a rudimentary "type" system, and wanna take it further. That's pretty much all that is missing from Logseq for me (besides some occasional stability issues).

[@toolsontech]

For sure, the properties getting an upgrade would be a huge deal on the usability and keeping data structures clean. Spend too much team cleaning up properties because I added the wrong entries or made the options too detailed

[@blake-ow9mv]

Is there any way to make notion like tables here in logseq

[@toolsontech]

We can only make basic tables and they are hard to edit right now, really hoping that once the db branch is released they will improve and get multiple formats like calendar, kanban and editable tables. But for now it only gives me an overview.

[@blender_tom]

Thank you for I was looking for this to add in any subscriptions I get. Next step for me to figure how how to add all the values, so I can estimate how much I'm paying monthly.

[@RodrigoKormann]

Is there another way to do tables? Because using # or [[ ]] it would mess with the purpose of my #s and [[ ]] already created. I use #s as tags so I can find the subjects I need. If I use that to create tables it would mess my list of tags (and plugin I use for it). Thank you so much for the content! Have a great week!

[@toolsontech]

Well, it is if you want to generate tables because you need some way to mark those lines, ideally those tags would already match your workflow but if it's not the case then you can build tables by hand using markdown table markup. If you do want to filter and you already have a system I would try and build the table using the existing tags you have and modify the query for example to combine some tags to get to the same result. The final way would be to make it a subblock of something that is tagged elsewhere, but once you get to that it might just be easier to make a tag and see if the plugin u use has a ignore setting so you can hide it.

[@RodrigoKormann]

@@toolsontech Thank you for your time! :)

[@RodrigoKormann]

@@toolsontech I was looking for something like a sheet (ex.: Google Sheet). Where you can have a table and you just put entries there without having to create a page for every entry. But I think this is a different concept that doesn't exist in LogSeq. Correct me if I'm wrong. (I'm a newbie).

[@toolsontech]

@@RodrigoKormann Sadly no, would love that function since I often have data in tables that I quickly want to edit. I hope it will come with the DB version. My current workaround is to shift click the pages and load a stack in the sidebar and edit the notes there but it's very clunky. And welcome to the rabbithole that is Logseq (and pkm, not sure if starting with that as well)

[@gedankenbalance]

Thanks for that raw video on block properties in combination with query tables. You get an idea of what is possible if you put in the work and create a detailed database. Of course the "no mayo" statement is controversial - i am with you on that one. Could very well scare away some subscribers. Who knows, maybe the logseq community consists of mayo aficionados - it´s to soon to tell. :)

[@toolsontech]

I'll keep an eye on the statistics, but then again, the absolute mayo lovers probably wouldn't like my content anyway ;)

[@RameshKumar-ng3nf]

I ended working in logseq and moved to CRAFT app. The only reason being logseq is not syncing properly with the different apple devices like - ipad . PDF annotation option is not there in ipad. Not sure when it will come. Logseq is great way of organizing but Sorry to say, it is still very buggy to use.

[@luxusAI]

in what way is it buggy?

[@RameshKumar-ng3nf]

@@luxusAI Kindly note below for the buggy things i experienced for 6 months working with logseq . 1. After every tag updates when I refresh, it gets stuck in the middle and gets unresponsive, i had to exit from logseq and try it again. 2. During typing notes , it becomes unresponsive most of the times, i had to again exit and login again. 3. There is always sync issues when i keep all data in my iCloud Drive , still dosent sync properly with my ipad and iphone. 4. There is NO pdf annotation in the ipad which is a downside, which work i do in mac in PDF annotation, i cannot do it in my ipad . I requested so many times for this feature in ipad, they are least interested. Due to all these issues during my work , i decided to move to a different app , paid app but no headaches , it works smoothly. I have the basic backlinking i needed and minimalism and i am happy with the paid app now as it works smoothly.

[@Damienxx]

Why not Obsidian if you gave up on Logseq?

[@RameshKumar-ng3nf]

@@Damienxx i tried Obsidan before using logseq for 5 months, even i didnt like that also. Too many plugins to install for each and everything features. No sync for multiple devices. I was looking for native apps which works smooth for apple devices and i got it as CRAFT app. Wont be changing to any other notes app in future, i am sticking to CRAFT app as it works buttery smooth with iphone, ipad and macbook

[@toolsontech]

Finding the right tool for you is the most important thing. believe i looked at craft once but at that time it was Mac only and that won't work for my Android, Linux, windows setup.

[@andreaswinkler3755]

Thanks a lot. I have just started with Logseq and created a booklist with one page for each book and a booklist page with query. Now your video brings me to the idea to use not a page but a block for each book to avoid that my pages will become a mess. What do you think, is this a good idea?

[@toolsontech]

Both work, considering that Logseq is working on a page properties setup I would still go for pages, if you want to avoid the mess you could use a namespace so put each book in it's own book/ page. I'm confident both methods will work and I wish Logseq would just commit to everything being blocks to make the question simpler.

[@Damienxx]

Nice, but how could it be helpful? Is it possible to do calculation on those property values or something?

[@gedankenbalance]

If you query not only for "food", but for "food" and specific ingredients, you could potentially filter out what to cook if you have certain ingredients in the house. That of course requires a sound database with lots of meals registered.

[@toolsontech]

There are plugins to allow you to generate graphs from the dataset or export it for more complex calculations. Personally I mostly use it for overviews

[@Ibramusbah]

Thank you. ❤

[@duwill]

so practical👍

[@leonheiherbat1186]

perfecto