created: 2024-03-18 06:10 tags: - daily-notes

Monday, March 18, 2024

<< Timestamps/2024/03-March/2024-03-17-Sunday|Yesterday | Timestamps/2024/03-March/2024-03-19-Tuesday|Tomorrow >>

🎯 Goal

• To learn about the Obsidian Dataview notetaking structure and how I can integrate that into my current set of notes. Also to better understand how to think of notes using the Map of Content framework.

accomplished:: true

🌟 Results

• Continued to learn about the Obsidian Dataview syntax
• Hoping to use the ## separators to allow one note (such as a daily note) to be used as a reference that can update information in a bunch of other notes.

🌱 Next Time

• Continue to look into how to use headers (##) to separate information. If this works like I'm thinking it does, it could open up a whole lot of opportunities for streamlining my note-taking procedures.

📝 Notes

I'm trying to learn how to set up my notebook to follow the CODE method of Personal Knowledge Management. I think a solid way to do this would be to update my Issues Reference file, a file intended to help me track issues that I either resolved or still need to resolve all in the same place. This would be a great way to learn about how to use the Obsidian Dataview plugin in a practical way.

I think I need to use Obsidian Inline Fields syntax, a syntax which doesn't require me to create a new note every time I want to add something to add information. For example, I could use the following syntax to create Issues Reference right as I find them in my daily notes with the following syntax

• issue: This is a test issue! desc:: "The issue with this issue is that it's a solved issue ahaaaa" tags:: #dimmin-app status:: #closed priority:: #priority-low

Unfortunately, I learned that I can only have one of these issue formats before I ran into trouble. For instance, if I added another issue to the note:

• issue: This is a test issue! desc:: "The issue with this issue is that it's a solved issue ahaaaa" tags:: #dimmin-app status:: #closed priority:: #priority-low
• issue: This is a separate / different test issue! desc:: "This is another issue in the file and should also be query-able" tags:: #hithub-app status:: #open priority:: #priority-high

Then the second issue would be the only issue stated in the note. This is because these inline fields are meant to provide meta-data at the note level (for the entire md file) instead of at the bullet point level. I wonder if there is a way to take notes on a variety of different topics without having to over-complicate things with Javascript.

ChatGPT offered the assist by using ## to separate different fields. Apparently this will allow me to treat each header as its own note with its own metadata (allowing each header to include its own tags). Let me try it out here:

Project A

• Status:: Check
• Summary:: Tried out the Obsidian Dataview note-taking strategy
• tags:: #ProjectATest

TABLE status, summary
FROM #ProjectATest 
LIMIT 5

This isn't quite what I'm looking for but it's getting closer. Also I want to be able to access the header (##) itself as its own tag instead of having to specify that in that tag in the metadata.

Notes created today

List FROM "" WHERE file.cday = date("2024-03-18") SORT file.ctime asc

Notes last touched today

List FROM "" WHERE file.mday = date("2024-03-18") SORT file.mtime asc

(Template referenced from Dann Berg, can be found here)