Listing all inline fields #620
Replies: 2 comments 14 replies
-
here is how you list all files grouped by ```dataview
list rows.file.link
group by type
``` this is how you list all the types: `$=dv.pages().groupBy(p => p.type).key` |
Beta Was this translation helpful? Give feedback.
-
Hi, I have also a similar issue. I would like to get all inline fields on
However, I would like to get not only the keys but their values (varying types) I saw a possible resolution here and tried it
but it only gives me back the keys:: I would like to see the values too. I tried the below two variations but neither of them worked to give back the values too, only the keys dv.list(Object.keys(dv.current()).filter(t => t != "file")).text
I tried also what was given here
but a little modified because of my tag selection requirement
It worked but it also gave back only the key:: part but the value not. ** @blacksmithgu could you help me please how to query all the key::value exactly?** Thank you for your kind answer. |
Beta Was this translation helpful? Give feedback.
-
Hi, I have asked on the general Obsidian forum, and people say I might be able to do that with JS. I need to learn it first :) so I thought I'd ask here as well before putting a feature request.
I have a vault of notes that are large chunks of text. To be more specific, they are what's called patient narratives -- story of a given patient's therapeutic course, expressed in natural text, which are updated by appending more text. For my research I need to be able to query and tabulate this text to get insights, and Dataview with inline fields is EVERYTHING. Seriously guys, this is a game changer.
However since inline fields are not like tags (= Obsidian doesn’t propose existing inline field keys when typing), my annotations are error prone: e.g. I can annotate oone thing with “CFS” and another with “CSF”, and this data will be missing from my table/list.
I thought that I can easily keep this clean if I create an index page where all inline fields are listed, a bit like tag pane; looking at this page from time to time would allow me to weed out typos and inconsistencies. I can search for :: in the search fields, but that returns each individual note, which won’t work.
Question: is there a way to create a note with a list of all inline field keys I have used? Or is there maybe another workflow that allows to keep the inline fields clean?
Thanks again for your amazing work.
Beta Was this translation helpful? Give feedback.
All reactions