[jm289765]

Originally Posted by MSBack

I have a feature request related to headers

I've lost interest in H2O and probably won't do any further development on it, except maybe for important bug fixes. I originally made it so that I could easily review and update notes and important points from books, but I've found that incremental learning is a much more efficient way to do this.

If anyone else wants to add these features, my thoughts here might be useful to you:

Originally Posted by MSBack

a more seamless way to only add the header once

Since there isn't a way to ask Obsidian whether a file already exists, you would need to store a list of file names that highlights have been sent to. But this is a bad idea. It would cause problems if you delete a file and resend that book's highlights with different formatting, which I think is a relatively common use case.

So there isn't a way to fully automate once-per-file headers. But here's a way to make it easier for the user: add a second header format in the config and add a menu button to send only that header, and nothing else, for the currently selected books. (also put the header format options in their own config submenu, since the formatting menu is already pretty big).

Originally Posted by MSBack

More metadata about the books, such as ISBN, publisher and tags or even the comments block.

You would need to add a new input to make_book_format_dict(...) in highlight_sender.py. The "data" arg only has information that's stored in calibre annotations, which doesn't include most of the book's metadata. The book's metadata would be accessed from button_actions.py, send_highlights(...) function, "db" object.

Originally Posted by MSBack

Information about the color of the highlights so these could be either grouped together or somehow indicated by each highlight.

Unlike book metadata, highlight color is included in calibre annotation data and would be pretty easy to add to make_highlight_format_dict(...). They can be grouped together by using color as the sort key in H2O's config. It might be useful to add a way to use more than one sort key, e.g. sort by color and then location.

Originally Posted by MSBack

In my view, "Send All Highlights..." and "Send New Highlights..." could be called "Create Literature Note in Obsidian" and "Update Literature Note in Obsidian" or something similar. However, I'm sure there are other workflows and situations where this might not be so simple. But I think it is worth discussing.

Changing them from "All" and "New" to "Create" and "Update" would be misleading, since both of them will create and/or update notes, depending on whether the note already exists. And changing their functionality so that they can only create or update notes would have the problem mentioned above for once-per-note headers.

Regarding the term "Literature Note": Since H2O is used from calibre, it makes sense to label its functionality in terms of calibre ("Highlights") instead of Obsidian ("Note"). And it's unclear what the difference is between a "literature" note and a normal note.

I will continue to receive notifications from this thread.