Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't see a file's #+title nor #+category #20

Open
Wonko7 opened this issue Jun 5, 2024 · 2 comments
Open

can't see a file's #+title nor #+category #20

Wonko7 opened this issue Jun 5, 2024 · 2 comments

Comments

@Wonko7
Copy link

Wonko7 commented Jun 5, 2024

Hi!

first off, thank you so much for this, I'm close to having a web interface on my org notes thanks to you!

Quick question: in my org files, I set a #+title & #+category, I'm not seeing these in the DB, am I missing something or is this not supported?
A roam daily file starts like this for me:

:PROPERTIES:
:ID:       43a3b72d-e69a-44dd-8c0f-f287406ab42a
:END:
#+title: 2024-06-05
#+category: 2024-06-05
@ndwarshuis
Copy link
Owner

first off, thank you so much for this

you are welcome :)

I'm not seeing these in the DB, am I missing something or is this not supported?

This isn't really supported. The closest that exists in the db now is the "outline_preamble" value in the "outlines" table which is just a string of that entire top section before the first headline. Probably not too useful since you would need to parse that yourself.

The only things that are currently taken from the top level are properties defined with "+PROPERTY" and filetags defined with "+FILETAG."

In theory it shouldn't be that hard to at least add the property drawer since this is just a different way of writing "+PROPERTY." Keywords would take some more work since there currently isn't a table for that. Note that if I added a keyword table that those dates would just be strings.

Is this all that you would want? The reason why I didn't focus too hard on the top section is because there's lots of little edge cases that didn't seem super common (different drawers, properties, keywords, lots of special flags that control the behavior of the file, free form text, etc) and thus it wasn't clear how to arrange a database schema around it.

@Wonko7
Copy link
Author

Wonko7 commented Jun 15, 2024

I hacked something together: #21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants