Logseq page properties The current behavior is that whenever you want to both reference a page in the value, and add additional plain text, the plain text is going to be linked automatically. All my page properties are showing in the graph view and making a complete mess. tags (N) - get listed in their own section "Pages tagged with X" below a page. It has a lot of similarities to Logseq from what I see but I want to make sure I’m not imposing my organizational structure on Logseq in a way that could be done in an easier way natively. I had thought LogSeq displayed the files creation date and not the date that file is imported? Is there a way Hi, I use some properties for both blocks and pages (note-type:: resource in this case). In Logseq MD: graphs have a folder in the file system have connections that live in a local database recreated on every re-indexing have no concept of place or order pages are nodes This question is just one part of a more complex query I want to build but datalog is completely opaque to me and I want to understand one step at a time. This would compliment suggestion 2 of @the-jb:. I’ve tried using the below, but sometimes the property is displaced and popped out above the hidden block and when that doesn’t happen, I believe Logseq should treat comma separated values as individual values FlorianF August 14, 2023, 7:45am 3. Does anyone have any Hello there. Hello, I have been attempting to get a query working by following guides and googling but nothing has worked so far. I have a yearly review at work that runs from April 1st to March 31st and as part of that I want to track 📋 Restyled and iconized properties for Logseq ala Notion/Tana - yoyurec/logseq-awesome-props. class/Page (253d068e3) Disable Users to Add or Delete Internal Tags. 9. More generally, we could even imagine having a I like that there are some properties that are built-in and don’t clutter the block when you edit them (task timestamps for example) But since properties are so useful for custom workflows, it would be nice if it was possible to hide more properties - for example properties added by plugins/templates or custom workflows. The main two things it does are: Adds pretty tag-like styles for full-line inline fields from Dataview - note that while Dataview is not a dependency I think the paradigm that a page is just a block with special properties should apply : a user should NOT have to chose between page-properties or block-properties, query a property should return BOTH blocks Problem is, I noticed that tags seemed to be “special” - tag nodes are colored differently on the graph, they get a unique “Pages tagged with” section at the bottom of pages, etc. ; Properties is the obvious alternative in modeling hierarchies, however they have been missing a proper visualization. Any extra clause should be provided by editing the queries directly. They clutter everything. Omit bullets when the Set Internal Classes Parent to :logseq. edn. Pages have special properties such as creating separate files, containing multiple blocks, Logseq’s built-in queries are simple but very powerful. Expected Behavior I created a completely new graph for testing and then I dragged into the “pages” folder one markdown file that has a creation date from a few weeks ago. Usage This uses a macro with the following syntax: {{p property, value}} block properties are not applied to their entire branch It is also like this in org-mode and, there too, for performance reasons. Expected Behavior. As for not having multiple property values treated as pages, that would be a feature request you could Logseq is a local-first, non-linear, outliner notebook for organising and sharing your knowledge base and second brain. Improve scrolling experience for virtual list tables . Seems to make little sense (to me) to tag a block on that very same page like that Pages with book notes have property type:: book. Hierarchies in Logseq have been a hot topic (e. but i want to use Front Matter format properties as defult like --- title: page-name --- what shoud i do ? Skip to content . I’ll just set out an example of the pages and then include the draft query which I’m hoping someone can help me with. On my workflow page, I have a section for This is a plugin for Obsidian which adds page properties similar to those present in Logseq. Just enter tags:: tag1, tag2, etc. This How can I hide the page properties in the linked references? Try adding the following css rule in file custom. The only column with data is Block. When I view this page in the “pages” list inside LogSeq app, however, it says that the creation date is today. And if I edit the title itself, both the property and the filename Users should have the option to override whatever default behavior for their own workflow needs. I could also use pages ([[value]]) or I can use properties (Property:: [[value]]). Currently, it is possible to hide properties through the :block-hidden-properties option in file config. How can this be done? Can card generation be automated, e. 9). A couple of personal highlights from the forum: So a logseq page can have these components (as shown in the following screenshot): Titl This is perhaps my biggest painpoint with Logseq as of now. I thought the page property is not considered a block property, which would imply that when I just quickly add the resource property Your block property pages should then be deleted but page property pages won't be deleted yet. I’ve updated the link in @Joe_Smoe’s comment. In Logseq tags are just different visual representation of links. Technically there is a 4th value, transaction-id, but this is usually ignored for Logseq use-cases (it can be excluded from the vectors). I have a love-hate relationship with page- and block-properties. being prompted with the photo and being asked for the name. For me the ideal would some syntax that, given an arbitrary user-defined <property>, (for example extends::), looks like this: Specify relations between Goal. I didn’t want to unknowingly “pollute” my workflows before I really understood what I was doing, so I instead started using custom, derivative properties like genre-tags:: instead. I have about 10,000 pages in that. pre-block {display: none} but you will need to click the filepath to edit the properties; or this should leave an invisible block above content that you can click to edit properties inline (but it It would be cool to be able to have attributes on links between pages, in a way that could later be used for mapping the data in the graph (e. Learning some clojure along the way 😃 here’s the result. properties is now non-empty and the page is included on the query. this). on the first block of a page (along with the alias and any other page level properties you might want to define yourself). Automate any workflow Hello, I have a namespace full of pages for people which all contain page properties such as “name” and “photo”. If I am going to struggle that much to think in this new way, Tana’s tag UX for thinking about those things Hi guys, I am looking for the best way to tag my pages and notes. Intro / Issue. Maybe we can have a prefix that causes the Logseq Page tags vs Topic. i. As From documentation :. I am not sure what is the upside of using the third option (properties). I figure tags: is shown because it’s a user I like to have my templates pre-populated with tags in the first block of a new page. Logseq creates pages from properties names, not values. And the note title property should use a different property name (like ls-note-title) Hello community, I’m trying to figure out how to improve my advanced queries by considering page properties. I deal with sales and have to keep track of many clients. I would like to use the flashcard feature to memorize the names of these people, i. author:: Daniel Kahneman. Rest of the page is empty. and see that the newly created page isn't included, but should be. It is limiting and very developer-oriented. But I wish there was a way to add a timing to the hover so that just scrolling would not flash on screen all properties of the traversed collapsed blocks. But they look so messy at the moment. Yes and no I found an attribute that gets added for blocks that are page properties. title (1) (page) - overrides the title of a page to be different from the file name. com; Docs: https://docs. Is there a way to get a result where I can filter out “completed” Properties have a property name and value. Use one macro for each tree, built around its defining property. Maybe we can have a prefix that causes the The namespace page should be something like [[Tree/Maple]], we’re working on namespace pages to be more useful. I would create a property called Type:: where Quote would be its Value. In this video, I go step by step through the di What about using some type of prefix/namespace for properties to indicate when a property is an user property, a logseq/plugin property not treated as page and one that can be clicked like a page? For example: Learn how to create and run a template on your Journals page every day using config. Make everything truly a block. https://discord. But those tags are not immediately recognized by logseq. by a query? Sure, I could go manually through Hi! Short: How can I make a button in a template that creates a custom email containing metadata from a logseq page (and its parents?)? I am documenting some reports Logseq 是一款注重隐私的开源知识管理平台，支持笔记、任务管理和协作。 Hi, as a way to organise and be able to run queries, I’m adding properties to the first block of my pages. Sometimes text is turned into pages and the user needs to figure out why; when you Logseq now shows the page names in the URL when linking to public graphs. mentaloid June 27, 2024, 1:34pm 11. Could you please help? I don‘t find an example solution. I figure tags: is shown because it’s a user Hello there. edn). But is there a way to hide those properties from view? Or a way to collapse that block? I saw there was a thread on this in February, but the only fix was through css. For example, I’m looking for pages, I have a love-hate relationship with page- and block-properties. I wonder if more features from org-mode’s properties are planned ? I’m especially interested in these features : 1. Make this page a Project [using page-type] Make this page an Area [using page-type] Make this page a Resource [using page-type] By adopting these properties, you can easily categorize your content and efficiently query for pages related I’ve learned that later as well, but I wasn’t aware of that at the time of writing these lessons. Page properties are also listed in blocks. But maybe it was always like that and I kept overlooking it, including Assign to a page the property key:: [[Page]]. Within my workflow I haven’t seen any difference between the two properties yet. The more the features the more the needed conventions. => I remember using [:query-page] instead, but I am struggling with the syntax (and I feel like this would only work with a “real” advanced query syntax. For those newcomers like me, there is “Time & Date” commands that you can enter in your content by pressing backslash key / as you write and you may continue searching in commands by writing e. While I want and have a ton of useful use-cases for Block-Level Properties, I don’t like the way they are visible and rendered inline in any markdown editor so I would like to have a block that looks like: ``Markdown. `rating:: 8` or `name:: foo`. gg/URphjhk Members Online • Landomix. here). Maybe Hi, I would like to have this simple query as advanced query because I would like to include it into config. The fact that the tags are so visually distinct and can look very different from the text means that it’s typically b Block properties seem to do everything page properties does, and more (because block properties also apply to the blocks within a page where they are specified, as opposed to page properties, which seem to apply only to the (page) and (block) indicates a property is a page property or block property only. Hi. Now I found that I can define a “type” within a page’s properties, too. I’ve made a bit of use of the :block-hidden-properties configuration, but I find that it’s not always the right approach. Hide internal tags for node types; Disallow setting internal type tags to any block ; Remove hidden pages from In Logseq we could add a :result-transform to queries to remove the default group by page. Learn how to use links and properties to manage your Logseq graph and make your life easier. These include: Simple checkboxes (not the TODOs) Dropdown to select one (or more) option out of multiple. Is there a way to use a dynamic variable to refer to the author in I think the best LogSeq can do right now is providing as much general, use case-agnostic, capabilities as possible, and doing it as well as possible - e. For example: work/HR But work also functions as page property. Sign in Product GitHub Copilot. It will be awesome if we could have some types in the page (and block) properties. Manually delete the page properties on the test page and manually add the property: type:: Testing. If you don’t put quotes, it is correct to see logseq treat those two values as pages. Many edge cases are not covered, use it only for the covered ones. logseq. Now everything should go there, that’s why I’ve added the #docs category on this forum. Substitute page-tags, page-property of simple, advanced queries and other page-related things by block-operations, resolving inconsistencies between page and block. I have a page named “apple”, but typing key:: apple as a property for a block doesn’t turn it into [[apple]]. It can be used to load a md file and access each block as a list. edstock July 4, 2022, 1:37pm 18. We always welcome pull requests too! The problem The syntax for properties: - key:: value has three issues: It’s confusing about how values are parsed (see documentation here): you can choose between multiple values or longer text with commas, but not both at the same time. If I have pages with type:: [[Movie]] then this query should get I had assumed that Logseq queries would see the page property as truly a page property, and so would list the page’s contents when the property matches. There should be a similar :block-shown-properties for the inverse. And therefore being able to have properties for the page is important. My example here is a list of poems: With all that block properties, it really Hi, In this example I created a template to use for page properties, I am using this template to basically add metadata to pages representing individual organizations in my graph. SonarMonkey: All of the custom stuff Logseq inserts into its markdown and org seems pretty possible in plain org syntax. But I believe that, after I write a comma, after Logseq has recognized the first “Page” in the list, I get another pop-up to select another Value from the remaining List image Queries have a steep learning curve and I am still pretty bad at them. I have added those to build on the There is no standard markdown, frontmatter etc. md file from the Logseq docs on Properties, I see that the beginning of the page is: type:: [[Feature]] platforms:: [[All Platforms]] description:: Annotates any block or page with multiple pairs of values e. When I define the template to be used, the properties are associated with the block, not with the page to which I’d like it to appear. jtan7th November 23, 2022, 3:11am 1. Properties and TODO/DONE state are parsed etc. page-properties are fairly useless in my opinion. The built-in property we’ll use the most Even if I choose to type the properties as childs or not. Instead you can use #[[Lord of the Rings]] as tag (elsewhere). All properties of all blocks on the page would make for a miserable UI in my opinion. e. date and selecting the date picker for convenience. Joe_Smoe: Page properties are defined in the front matter I created some properties like Topic, Purpose, etc. ) You simply created an additional Link to a page called lordoftherings. Imagine you want to write Learning how to use properties and templates will help you be more effective in managing knowledge in Logseq. Look at the demos: This is helpful if you’re using Logseq for writing: details of characters, world description, role playing games, etc. It might be useful if the nodes menu of the graph has a way to show which pages have the exclude_in_graph attribute, to set this to false again, or to add new pages for which the exclude_in_graph:: true property is added. Ngungu August 3, 2023, 12:50pm 5. yGD December 28, 2023, 1:22pm 1. 3 Likes oshliaer October 31, 2021, 9:10am Learn how to use links and properties to manage your Logseq graph and make your life easier. How is it different from tags and pages without the property::? Thaks! I’d really like to create a template that forms the basis for each of my “staff” pages. It does not function. So a logseq page can have these components (as shown in the following screenshot): Title Page properties (e. By using the Live Query Builder I have obtained the following simple query : and then embed the block with the query on another page (e. All I would want here is an advanced query for all pages with the #inbox tag. Inspiration Syntax for inline properties:: Create Properties from inline text as I type and make them available as variables inside the block This is a basic implementation, so none of the above feature requests is properly satisfied. I want it to fetch blocks tagged with #Problem from the pdf highlights pages where I added some page properties like this: I’ve made a bit of use of the :block-hidden-properties configuration, but I find that it’s not always the right approach. (So, in a way, “there are no tags”. alias) Page Logseq Simple query page-properties but also filter out another page-property? Questions & Help. When I add the properties using the “Account” template in Logseq to each of the pages, I then can see that these properties when creating new page, it will add a properties in page like title:: page-name. Of course I would like the list ordered alphabetically. development. The simple query (property topic logseq) should be working for that case. It works with comma separated wikilinks (pages): image 1224×1398 141 KB. I manage to create the query, it is displayed in my journal and also says “5 results” but there is no list. roots. closer to what you want Not sure anymore, as your I wanted to make a definition list for all properties that I use. 2 this was fixed and the default group by page is now displayed regardless of the use of :result-transform. It seems a macro like this one, combining <%current page%> and page-property can't work, logseq-cldwalker mentioned this issue Feb 6, 2023 <% current page %> should not change the page original name #4276. content . When there is a reference on todo page it means I must do something about it. I guess, this property should be kept unused by logseq. To get block-level inheritance with linked properties this works: {{query (and (page I changed my mind, you’re right. To prevent the final sorting, it simply checks for the existence of string (sort-by; To make my code work with pages, all I have to do is to add anywhere this comment: I’m going to gather some queries here that will be useful for task management. Queries are such an easy way to bring back anything with the right properties asigned. get_current_page(). But AFAICU sort-by may be used in order to sort by On a new page called (e. I found the bug in Logseq’s implementation. I had assumed that Logseq queries would see the page property as truly a page property, and so would list the page’s contents when the property matches. api. My ideal would be to be able to specify page properties anywhere on a page, but that’s another story So if I can’t do that I need to be able to collapse the top page property bullet so I’m not confronted with a wall of 30-40 page properties when I open a page. Customization. mentaloid April 14, 2024, 4:28am 2. references . However, the way sort-by is used in the course is by sorting on dates. g) “Active matter tasks” I want a query which returns all “TODO” and “DOING” tasks which have the name of an active matter page in them (regardless of where the tasks appears). g. This appeared to me like a bug, as this was never the way tags worked in previous versions. I’m trying to make an inbox page for unsorted items. But blocks with page properties are still just that, blocks. Expected Behavior I have been a heavy Wikidpad user for the last decade. Ngungu August 3, 2023, 10:29am 1. If it is not, feel free to file a bug and provide reproducible steps at Issues · logseq/logseq · GitHub. But AFAICU sort-by may be used in order to sort by Moving this from GH issue to the forum LS is treating tags in page-properties as block references · Issue #2534 · logseq/logseq · GitHub Starting with LS 0. Hej! Can someone shortly explain the differences between “page-type” and “type”, or give references to where I can learn more about it? 🙂 I’ve learned that I can define a “page-type” within a page’s properties. Unfortunately I use namespace and page-property mixed. Currently, I use tags (#value). Thus your query returns the block of page properties as it has the property you query for. I made a simple query {{query (and [[Problem]] [[Activity Theory]] )}}. A page, is a block with a name, after all. In this regard my tags seem more like Values for the Properties than the actual properties names. {{query (and (page-property SomePageProperty spp1) (property SomeBlockProperty sbp1)) }} only returns blocks on pages with spp1 and where the block has sbp1. I am new to Logseq, and realized that properties was best for my use case, but were so intrusive when being displayed so prominently near what was the important info for me. Editable properties icon (1) (page) - define icon identifier for a page. Most themes, by default, have some kind of special styling applied to the tags and this can differ wildly between themes. Thankfully, I find that I can usually minorly edit and repurpose something that has already been built and shared in the forum. Before I an page properties be used as dynamic variables? For example, if I had a page for the book Thinking, Fast and Slow, and used the following page property: . To me, it is one of the strongest and weakest points of Logseq, and I often wish they were easier to understand and use. Try adding the following css rule in file custom. This special property is inherited, so if you set it in a level 1 entry, it applies to the I have some blocks with properties like this: block content start-date:: [[2022-04-18]] end-date:: [[2022-05-01]] Then I have a query where I get the start dates of the blocks on the current page: {:query [:find (pull Page properties are defined in the front matter “the first block of a page” – link The title property key must be defined in the page-property block (block-properties will have no affect on the title key) – link The old style of block-properties is no longer recommended after Beta version was launched – link So to define a title property-key and to include some body text in Do keep in mind that page-tags only works in combination with the tags:: property; for non-standard properties you need to use the (page-properties) filter. So practically, all Logseq data vectors have 3 values. Otherwise a property can be both a page property and block property. I have a large number of pages and some page names are only used as page/block property names. com; Blog: https://blog. By using the Live Query Builder I have obtained the following simple query : After playing around with the page-property block for some of my notes, I realise that the links and tags do not show up on the page graph. I like that there are some properties that are built-in and don’t clutter the block when you edit them (task timestamps for example) But since properties are so useful for custom workflows, it would be nice if it was possible to hide more properties - for example properties added by plugins/templates or custom workflows. Navigation Menu Toggle navigation. via export into Gephi, or perhaps via improvements to the graph view page) Links could have two basic attribute types: A “type” that defines the type of relationship the link represents Arbitrary key=value pairs that define In the documentation for properties: When a property value matches an existing page title, Logseq will automatically create a link to that page This hasn’t worked for me, unless I’m missing something. pre-block {display: none} but you will need to click the filepath to edit the properties; or this should leave an invisible block above content that you can click to edit properties inline (but it I am particularly struggling to work out the correct coding to interrogate the page properties of the page referred to in the task. If I look at the Properties. Visible properties . I just tried to query pages with a specific tag but it didn’t work. 📋 Restyled and iconized properties for Logseq ala Notion/Tana - yoyurec/logseq-awesome-props . When I open a page I want to see the content first. Checkbox may be easy to implement and may even be accomplished using a plugin to replace some boolean value with a checkbox. Also, discover how to use plugins to supercharge your daily template with habits, properties, and smart blocks. Skip to content. In Logseq 0. No solution available since then? logseq doesn’t automatically create a page, and I can see no changes in the data returned by queries. Here’s Hello, I want to have a default query that list all pages with a specific value in the property “status”. md is stored in the filesystem and a title:: N/P property is added to the page. I’ve seen no videos, documentation, or anything else that would indicate this is possible, but it seems like something that would be pretty useful. New Block Block Text; inside-block-list-element1; etc; Basically I would like Logseq to use In that template, I would like to include a button/HTML link that creates an email where some variables depend on the logseq page. But perhaps you are right, and a shortcut for “Time & Date” commands will be handy to use I think the one on the website is just an abstract representation but one could replicate the look with the plugin Full House Template, here there is the related example: Shiny `Glass Card` from Logseq landing page · stdword/logseq13-full-house-plugin · Discussion #9 · GitHub If you just want the icon of a page (it is set using the special icon:: property and The first block’s properties will be treated as page’s properties so that we can query use (page-property key value) Each block in logseq can have an optional title, for example: Title (which is optional) property-A:: value property-B:: value (properties are optional too) With the help of 🏛 Full House Templates plugin. Anyway, I agree with your comment on hosting documentation within Logseq. I simply do not understand what additional capability page properties brings to the table, when we have block properties. P. excessive info should be elsewhere or in collapsed blocks; Most pages should be connected to each-other through Premise Following the discussion here I think I have a viable and concise proposal to address most use cases of the “hierarchically organize pages/tags”. Closed This was referenced May 14, 2023. When I run another cohort of this course, Display page properties on the right sidebar by default . Thank you for your reply! I’ll provide more explanation. 0, page-tags are now behaving differently than they were in version 0. There's a bug with page property pages not respecting the config option so I'll have a fix for that soon @cnrpman Looks I have a love-hate relationship with page- and block-properties. The issue I find with this is that if I click on [[Learning]] or [[PKM]], the pages give no information to any linked references (despite all the notes that have been given the those properties). This is the way. It won’t be done in one go and I will be adding inline comments to help you understand what is going on. Please see: Advanced query for pages with a tag - #3 by onkeltem It’s the one area where using Tana feels most like “levelling up” to use properties and queries in Logseq. the page properties ? if you want to totally hide and remove the line try . This hasn’t worked for me, unless I’m missing something. “Civil Society”) the query uses this new page as its <%current page%> input, but I still want it to use “Civil Society/NGOs”. queries. In many situations this was undesired behaviour, but in others it was exactly what was intended. And I wanted a way to check for any properties not on the list. @Ramses it confuses me that you say that sort-by is just for pages because only pages have creation and modification dates. For example, let’s say I enter the following into the page property block: title:: example_title id:: example_id tags:: example_tag When I leave edit mode, what I see is: tags:: example_tag So far, so good. Now, if I remove that property the page is still named N/P, so what’s the point of having the property? Moreover, I’m unable to change that property, it’s always reseted to the current page title. 10 and lower. Setup instructions are here. 7 KB. I have a template to create book page, so of course it too has that property. Even if sbp1 is a link, child blocks are not returned. Only when i edit the first block the tags are registered (and the template To be fair, if Blocks are collapsed, having the properties show up on hover is a nice way to get a glimpse of what’s inside, if the Title of the Block is not helpful enough. I’ve noticed page properties exhibit three different behaviors and I’m confused. And if Logseq supports clicking a property (like a page) to show linked values and pages (like Roam does), Logseq and plugins properties should be forbidden to do that operation (or at least a plugin can allow some properties to be clicked and others not). I know that’s not “levelling up” Logseq use relative to where you are in your mastery of the tool, but it is for me. css:. Python script to parse Logseq page, blocks, properties, etc as a list or json. queries One could also define their own keywords and respective queries. properties are generally more manageable than free text; is relatively short. I added direct link to jpg. The question is generic, so the answers cannot be very specific, but I’m going to give it a try: Managing pages. I am particularly struggling to work out the correct coding to interrogate the page properties of the page referred to in the task. 7. Is it maybe possible somehow to say: if I hover Hi everyone, I assume this is a bug – a link in a page property is supposed to tag all the blocks in that page with the given link, right? It doesn’t for me, unfortunately. Correct me if I am wrong, but it looks like a new behavior that must have been introduced very recently (I use the latest stable release 0. For each meeting, I have a template that allows me to place my notes but also tasks as follows: The table that’s generated by the page-properties query is a list of terms that are both page names and other LogSeq functions, and so it’s not immediately clear which functions are required and which are just the results. I often want to hide properties (like tags and categories) that are unsightly, but also be able to In my "production" notes, query with quoted reference as {{query (page-property prop3 "[[page]]") }} actually resulted in table with one correct record, one entirely incorrect, while there exists ~5 pages with this property. Bas from Tools on Tech showcases five simple queries that will make managing your graph and retrieving your notes a lot easier. Or better said, from a markdown Another issue I have with Logseq-Markdown is Properties. page-properties { display: none; } Logseq Hiding page properties. icon (1) (page) - define icon identifier Learn the difference between blocks and pages in Logseq, a knowledge graph-based note-taking app. Maybe you are confusing the two? Otherwise maybe I didn’t get what you mean. To just get a list of books without the Template page, I compiled this: #+BEGIN_QUERY {:tit Learning how to use properties and templates will help you be more effective in managing knowledge in Logseq. Please see: Advanced query for pages with a tag - I wanted to use the title property for something else, like title of academic articles or books. Visible properties are the ones we can edit. I even tried creating another test page of really Simple page properties are maybe no big deal, But I don’t know if it can actually use that frontmatter in the way Logseq uses page properties. Migrated from issue801. For example, the subject should preferable be something like “ for , ”. Hi, I made a python script to parse logseq markdown. Information like when a block or page is created (created-at), when it’s updated (updated-at), what its parent block is (parent), and many other properties. 1 Like. I don’t think that’s on the Logseq development roadmap. Replace {{key}} with {{query (page-property key [[Page]])}}: it works. Find and fix vulnerabilities Actions. But it will be better to have it natively built into If I use property foo I get a mix of pages and blocks, but logseq returns the properties of the page, not the page name in the same column as the block contents, which makes it difficult to read. A manageable page: . I really don’t see how page properties are “different” than block properties. I would have to type in a query to show all Now each page has a top block with the page property, followed by a sibling block with the quotation. I often want to hide properties (like tags and categories) that are unsightly, but also be able to conveniently edit them. We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. . Questions & Help. Instead, it just seems to see it as a normal block property, so the sibling block with I just tried to query pages with a specific tag but it didn’t work. css : . Logseq Page properties show up in global graph and page graph view. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. What I wish is being able to choose what properties of the page / block of my “book-x-page” I want to render in my [[BooksList]] page with the query. Look what I built. edn for my Journal page. Navigation Menu Toggle I have the following query and it shows me pages with the property:: value type:: [[project]] : #+BEGIN_QUERY { :title "Pages with type: [[project]] and status Problem is, I noticed that tags seemed to be “special” - tag nodes are colored differently on the graph, they get a unique “Pages tagged with” section at the bottom of pages, etc. ; In the present post Page-tags: there is normally no difference between #tags and [[pages]] in logseq, but there is a separate category of tags called “page-tags” which can be added as a top-level property to pages. Tags (links in Logseq) are inherited while properties aren’t. If you’re somewhat familiar with programming, think of page-tags (or any other query filter) as a function that you give an argument/input ( SHAP and ES in this case). The macro above should return the same results as if it was manually expanded and <%current page%> replaced with the current page name If we used the properties-based approach @alex0 devised, we could have polyhierarchies, but queries would have to recursively return “parent-of” and “child-of” pages based on those properties. children. For me the ideal would some syntax that, given an arbitrary user-defined <property>, (for example extends::), looks like this: Specify relations between Hi all! First post, hope I’m doing it right. Then I tried the exclude-from-graph-view property and it disappeared from the global graph page, but it’s still in the page graph. I used a query from the official docs but there seem to be no property with name :block/tags (as well as other properties, specified in the first block). In this video, I go step by step through the di When I create a page N/P a file N. Survey: How do you use page properties? In this example we are using the property `programming-paradigm` to have a short list on top of the page. The point is specifying hierarchies using page properties. Just wanted to say Thank You, to everyone who worked on a solution to this problem. The thing is, only pages have the date properties (blocks don’t at the moment, due to performance issues). There are various feature requests on the matter (e. Previously I was using Remnote and quite enjoy the idea of " create flashcards and take notes at the same time. The coming database version provides a user interface for individual Whenever you create a block or page in Logseq, several hidden properties (metadata) are also created. So on that note - with hierarchies I organize things in Wikidpad like this. Let say that I’ve have some pages with the following tag and property : tags:: Fiche Album musicien·ne·s:: **#[[Frank Zappa]]** I would like to query all the pages with this page-tag and this property with value equal to #[[Frank Zappa]]. Is there a way What follows is: a combination of the above suggestions The power of the community. I love them because they are a excellent help in organising my graph. Using page tags and (page) properties, you can power your workflows without cluttering the text of your note with a bunch of links. Queries are such an easy way to bring back anything with the right properties asigned To hide the properties of collapsed blocks, try adding this in file custom. In this section, we see how to make a start A signficant difference between the two forms of linking is the difference in aesthetics. 5. Is there a in treating comma-separated values as separate page references (entry :property/separated-by-commas in config. queries and PageTree. I’ll start by explaining what I mean by “flexibility in page layout”. ADMIN MOD Properties, namespaces or simple page links? Hi guys, I want to ask this question since looking online I got a little bit confused about when to use properties, namespaces or single page and then embed the block with the query on another page (e. I then created a simple query to summarize all the pages that have those properties. define allowed values for a property using xyz_ALL from the org-mode doc: You may define the allowed values for a particular property ‘Xyz’ by setting a property ‘Xyz_ALL’. outlines the specific concept in its title . 2. But, using it, when I re-index Logseq, it changes the note title to the value in the property. Basic pages concept:-Journal page-TODO [[Project 1]] return important email Premise Following the discussion here I think I have a viable and concise proposal to address most use cases of the “hierarchically organize pages/tags”. So, if I write a property like quote:: it will actually link it to the Logseq Page quote. - {{query (and (AND (page-property type Projekt) (page-property area Arbeit)) (page-property :status "#inBearbeitung")) }} query-sort-by:: page query-table:: false query-sort-desc:: Hi all! First post, hope I’m doing it right. That’s why I said they only work in combination with pages. I tried the template in the official docs (see below), however, the query returns 0 results. As a result of my experiments with them, I am on my path to forming this opinion, as well. For example Project 1 area:: work How can I retrieve tasks on both sides of the word work in this example? Can I Introduction. Add new page attribute for Hi There! 👋. css: div[data-collapsed] div. If I have a block properties are not applied to their entire branch It is also like this in org-mode and, there too, for performance reasons. In other words, if you can use a normal query to filter the desired pages (whether through tags or any other condition), the same And if Logseq supports clicking a property (like a page) to show linked values and pages (like Roam does), Logseq and plugins properties should be forbidden to do that operation (or at least a plugin can allow some properties to be clicked and others not). The only way for me up to now to get a list of the pages with “wtc” in the properties is a page named wtc and its linked and unlinked references. Likewise, special built-in property title:: is similar to icon::. This is nice! But it would also be Apparently upon defining some properties of a page (in the first block), new pages named after the keys of those properties are automatically created. I know that something is todo when I have it on todo page and I use references from text to todo page. page-properties { display: none; } show post in topic. com; Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. image 992×325 18. I’ve seen a nice example of this in the internet (but do not find it anymore XD). 3. For some attributes, such as :block/tags or :block/page, the value is an id - a reference to another id, the properties of which can be looked up separately. Jacky02 August 28, 2022, 7:49pm 1. md, which is the same target as [[quote]] or #quote. allowing user customization through general and stable querying functionality, properties:: implementation, and also of importance: customizable interface (example feature request ). the datalog code found under the various PageTree. Access additional Logseq 🚀 resources: Forum: https://discuss. Building block for organizing graphs - ## Usage Up until now, I was pretty sure that in Logseq, the word Block In the properties I have category:: wtc (stands for words, terms, concepts - where I collect definitions, links to various pages, thoughts etc. block-properties { display: none; } Logseq Block properties are not inherited while page properties are. It looks good in normal view but when I switch to table view the property columns are there and can be turned on and off but they are blank. edn file. See that the logseq. ", simply type “::” For this I changed all blocks to a page with the 2 properties as page properties. It also supports json output. You actually get blocks specifically. Write better code with AI Security. Go to [[Page]], insert {{key}} macro defined above: no results. I am new to Logseq and I wish there was a video about it, about creating When a property value matches an existing page title, Logseq will automatically create a link to that page. This is also the case for namespaces, as they have been used to model hierarchies (e. Maybe, but I disagree Logseq should therefore use org syntax for that. Let’s assume the following fictional use case: You want to document information about your customers - for example, what their title is or where they are I think in the future we could have more properties of a block or a page, like a concept description or definition of a block/page, which could be very useful for flashcard spaced repetition or quick page preview. Feels redundant to me. See the end of this page for the query code. Logseq follows its own conventions, like everybody else does. qgfeirs inko dwalowc xif wolmg vzifc xawcc vucrfpo zhs rtzn