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

Feature idea: Use other list properties besides "tags" as well. #105

Open
MMesch opened this issue May 29, 2024 · 1 comment
Open

Feature idea: Use other list properties besides "tags" as well. #105

MMesch opened this issue May 29, 2024 · 1 comment

Comments

@MMesch
Copy link

MMesch commented May 29, 2024

Hi,

Thank you very much for writing and maintaining this great plugin.

I am trying to structure my notes as an internal knowledge graph. That is, a knowledge graph with labelled edges to account for different relationship types that a subject could have with an object in the spirit of a Triple store or other knowledge graphs.

With tags you can only emulate one relationship type, generic associations of the note to one or several tags, but not what those associations are. To go to knowledge graphs, you need to use a different list property for each edge type. For example, one list property could be is a and another used in. For example a note about Obsidian could be:

---
is-a:
  - computer-program
used-in:
  - personal-knowledge-management
---

It would be awesome if you could then use tagfolder in the same way as of now but taking into account other (selected) list properties as well, displaying them in the same way as different tags are displayed right now:

Tag Folder

> is-a:#computer-program
    > used-in:#personal-knowledge-management
> used-in:#personal-knowledge-management
    > is-a:#personal-knowledge-management

That way you would get the full power of a knowledge graph with Obsidian. Is this something you consider feasible to do with tagfolder? Is there an alternative to get similar behavior?

@MMesch
Copy link
Author

MMesch commented May 29, 2024

I realize that this may need a setup more similar to what is implemented with Link Folder where list property elements are links to other files rather than neutral tags—and in addition also transitive links to allow for building a hierarchy as with nested tags.

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

1 participant