16 Matching Annotations
  1. Mar 2024
    1. Die onderste link wordt veroorzaakt door deze query (dank Joost Plattel ):```oqlname: "This day in my history"query: {$and: [{"path": "'Deze dag op"}, {"title": "'11-04"}]}template: 'list'fields: ['title']sort: 'title'badge: false```Deze query verwijst naar een uniek .md bestand met als titel de maand en de dag van vandaag.Zo heb ik voor de 365 en soms 366 dagen per jaar een uniek bestandje.Door op de link te klikken kom ik op de pagina van vandaag in mijn persoonlijke geschiedenis:
  2. Jan 2024
    1. ew, show all notes created today on daily note with DD-MM-YYYY? .t3_1689wtl._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #edeeef; --postTitleLink-VisitedLinkColor: #6f7071; --postBodyLink-VisitedLinkColor: #6f7071; } Tried all the stuff I have seen, simply get an empty table. Any ideas?If anyone has a way that would link it on the graph too, that would be great. Thanks :D

      Obsidian Dataview query — Show all notes today on daily note

  3. Nov 2023
    1. Beginner tutorial for Obsidian Dataview by Danny Hatcher<br /> https://www.youtube.com/watch?v=G8eOF61wmzI

      Not bad at all and has a few nice examples that slowly build on themselves.

  4. Oct 2023
  5. Jun 2023
    1. This is a page I found while trying to learn the syntax of Dataview (an Obsidian plugin that allows database queries on one's own vault).

  6. Apr 2023
    1. Dataview query for table of incoming outgoing links

      dataview TABLE length*file.outlinks) as "Outgoing", length(file.inlinks) as "Incoming" where !contains(file.path, "Genie") and !contains(file.path,"Daily") and !contains(file.path,"Private") and !contains(file.path,"Weekly") and !contains(file.path,"FolderA") and !contains(file.path,"FolderB") and !contains(file.path,"FolderC") and !contains(file.path,"FolderD") and !contains(file.publish, "false") SORT length(file.outlinks) DESC LIMIT 50

      via timestamp 00:11:23

  7. Jan 2023
    1. Anybody using this approach to manage contacts? How?

      reply to IvanFerrero at https://forum.zettelkasten.de/discussion/1740/anybody-using-this-approach-to-manage-contacts-how#latest

      Many of the digital note taking tools that run off of text allow you to add metadata to your basic text files (as YAML headers, inline with a key:: value pair, or via #tags). Many of them have search functionality or use other programmatic means like query blocks, DataView, DataViewJS, etc. for doing queries on your files to get back lists, tables, charts, etc. of the data you're looking for.

      The DataView repository has some good examples of how this works with something like Obsidian. Fortunately if you're using simple text files you can usually put them into one or more platforms to get the data and affordances you want out of them individually.

      As an example, I have a script block in my daily note in Obsidian for birthdays in my notes that fall on today's date:

      ```dataview LIST birthday FROM "Lists/People" WHERE birthday.day = date(2023-01-18).day ```

      If I put the text birthday:: 1927-12-08 into a note about Niklas Luhmann, his name and birthday would appear in my daily note on his birthday. One can use similar functionality to create tables of books they read with titles, authors, ratings, dates read, etc. or a variety of other data input which parses through your plaintext files. Services like Obsidian, Logseq, et al. are getting better about allowing these types of programmatic searches for users without backgrounds in programming and various communities usually provide help for pre-made little snippets like the one above that one can cut and paste into their notes to get the outputs that they need. Another Obsidian based example that uses text files for tracking academic journal articles can be found at https://nataliekraneiss.com/your-academic-reading-list-in-obsidian/; I'm sure there are similar versions for other text-based platforms.

      In pre-digital times, for a manual version of a rolodex like this in paper, one could use different color cards as pseudo-tags (doctors are on yellow cards, family members on blue cards, friends on green cards, etc.) or adding edge notches or even tabs to represent different types of metadata. See for example the edge colored cards in Hawkexpress' Pile of Index Cards: https://www.flickr.com/photos/hawkexpress/albums/72157594200490122

    1. Some conflicts and misreading of what’s the structure of the metadata. When you create some tag in the content - #tag - it becomes a “real” tag to Obsidian and to dataview (an implicit field - file.tags). When in frontmatter you write tag: [one, two] or tags: [one, two] it happens two things: Obsidian (and dataview) read the values as real tags (#one and #two) and for dataview they’re target by file.tags (or file.etgs - see docs for understand the difference) - and attention: file.tags are always an array, even if only one value… even if you write tags: one, two But for dataview tag: [one, two] it’s also a normal field with the key tag (or tags) - that’s why if you write tags: one, two it’ll be read as an array if targeted as file.tags and a string - “one, two” - if targeted as tags As normal tags they’re metadata at page level, not at task level or lists level (that is another thing). As tags field it’s also a page level metadata. Topics above are intended to explain the difference between targeting tags or file.tags. And as file.tags they’re page level. So, if you ask for tasks to be grouped by a page level (parent level to tasks), there’s no way to you achieve what you want in that way… because the file.tags is a list of tags, not a flattened values (maybe with another query, with the flatten command…) A second point is related with the conflict you create when you’re using a taks query with the key tags. Why? because task query is a little confusing… it works in two levels at same time: at page level and at tasks level (a file.tasks sub-level of page level). And the conflict exists here: inside tasks level there’s an implicit field called “tags”, i.e., a field for tags inside each task text. For example: - [ ] this is a task - [ ] this is another one with a #tag in the text in this case the “#tag” is a page level tag but also a task level tag. It’s possible to filter tasks with a specific tag inside: TASK WHERE contains(tags, "#tag") This to say: when you write in your query GROUP BY tags it try to group by the tags inside the task level, not by the field you create in the frontmatter (a conflict because the same key field). In your case, because they don’t exist the result is: (2) - [ ] Task 2 - [ ] Task 3


      A good description of tags in Obsidian and how Dataview views them at the YAML, page level, and task level.

  8. Mar 2022
    1. I came up with a couple of criteria to help identify practical uses for the Dataview tool, over say, a embedded search query. Here are a few of those criteria: Use to access or summarize frequently-accessed data.Use in situations where the data is dynamic, and can change over time.Use to help automating a process

      When will I need Dataview plugin

  9. Dec 2021
    1. > possibly useful quote that supports my argument - keyword:: #representation_of_race #western #masculinity - film:: [[The Searchers]] - project:: #CLASS101 - comments:: this is really great, should use it in section B!

      Quote Dataview