We have many types of users with different areas of expertise and different levels of technical backgrounds, my best guess is that this would confuse at least some. In my opinion, something like Graph View presets to save and load filters & display settings would work better if you can preload a filter that does not include X folders.
1 Like
I agree. Itâs a better UX to keep controls for graph view, like hiding files/folders, in the graph settings. And Graph View presets to save and load filters & display settings is a clean way to fulfill this threadâs feature request.
1 Like
I think we could have both:
- Graph UI could have the controls for temporarily hiding stuff. Basic users without advanced skills can use this.
- Have a meta option that can be written at the top of a file that should be hidden, like hide-from-graph or something. This would serve the purpose of permanently hiding individual files, and it would be out of the way of people who do not use it, because there is (maybe) no UI controls for this.
For the latter, I personally think that it would be a good feature because if I want to hide something permanently from the graph, I find it a bit annoying if I need to preserve it in the graph filter string. It Takes up space there and I might accidentally remove that filter. But if I have written that hiding mark into the hideable file, it stays there permanently.
@Soncro also had a good idea about showing a message âx files are hidden from the graph-viewâ. That should help to make users understand why some of the notes are not visible in the graph. Maybe make that message clickable so that it can then show which files were hidden.
1 Like
I will love to have a metadata key to âhideâ a specific file from graph
1 Like
+1 for filtering out notes via meta data in the note itself or even better a saved setting in the graph filter, which filters out notes with a certain #tag . The later would then also enable the user to search graph view for tags that have this certain #tag (eg #not_in_graph), which could lead to interesting visualisation of the interconnectivity of notes that are for whatever reason not deemed to be âworthyâ of the graph view.
Really late to the game, but this simply does not work for me. I know I have the correct path because it changes the color thatâs set for that group but when I put the - in front of it nothing happens. Any ideas on that, anyone? Iâve also tried adding a space after the hyphen since I saw that somewhere but that doesnât work either.
+1 for OPâs request. I would also like to filter out notes by adding metadata to the note, rather than using the graph UI to filter. I agree with Jare, we could have both. A Graph UI option for users without advanced skills, and a separate meta option for other users to add to their files.
1 Like
Honestly, I just want them to add a function somewhere so my template files donât show up on graph view. I donât want to have to turn off âshow orphansâ just to get them out of the way in case I accidentally didnât connect some of my notes.
Another +1 for this request.
Just a toggle for folders or exclusion setting would make graph a lot easier to parse.
+1 100%
I use the Group function of graph view to show different color of nodes by different tags or the types that i created by yaml. This make me distinguish the notes that i want to focus from the whole graph. Also, you can add blank groups, such as "tag: " or "file: " , using them as flexible color filters. When they are blank, they are off and show no color. Or, you can add other symbols in front of them ( " !tag: " ),and then the function disabled.
Iâd like to +1 this feature as well. I have a lot of âindexâ notes that clutter up the graph view and make it completely useless for looking at the depth=2 level, which is where I would expect to find the most useful connections⌠if I could only see them among all the noise.
5 Likes
+1 really need this feature too!
1 Like
+1 to this idea. I use graph view a lot and I would like for it to be more customizable, I hate having notes that are useful due to their content, but are cluttering my graph.
Graph View presets idea is definitely cool, and I concur to Jareâs idea that you can have two options to fulfil this request. Both Graph filters/presets UI and right click on notes/folders to hide them.
1 Like
+1
I dont know if they have implemented a solution or if there is a community plugin that fulfills this, but as someone that makes a lot of definitions for words and also makes notes that include articles of law
(imagine having 2000+ articles filling the map for no reason)
As of now I manage with tags, but it is a pain that I cant at least save the preset.
+1
There should be a frontmatter graphhide: true, false, stop
false - shows node, default behavior
true - hides the note from graphview
stop - stops view of all outgoing links from this note, but allows incoming links to show. So you can reference people, locations, etc. in a note without making a lot of outgoing connections in graphview.
Use case: daily meetings where you link attendees and locations.
3 Likes
Problem statement: graphview is great, but quickly becomes unusable if the user links too many internal links, i.e. meeting notes referencing attendees, locations, projects, and tasks. Some would say use graphview tag filters, but this is a non-permanent per-viewing mechanism. Iâve seen people turn to having a note page with filter lines they cut and paste into the graphview Filter each time they use it.
The reason to put it at the notes control is to support exceptions to the rule. For example: one meeting that is so important that you want to see all outgoing links, but once the project is done, you may want to stop all outgoing links from this note.
Solution, a frontmatter graphhide: (true, false, stop)
false - shows node, default behavior
true - hides the note from graphview
stop - show note, but stops view of all outgoing links from this note, but allows incoming links to show. So you can reference people, locations, etc. in a note without making a lot of outgoing connections in graphview. Example: project referencing people and subproject pages, or referencing academic papers and references.
Some use cases:
-
daily meetings where you link attendees, locations, projects, etc., graphview is not good at handling this. This quickly becomes a cobweb of links. Programs like TheBrain handle this by focusing in on the selected point, but since Obsidian keeps the same view, it quickly becomes unusable when the link counts become too high.
-
a DB Folder page: Recipes for example. Each recipe note may refer to the DB Folder Recipes note, but you may not want every recipe showing in graphview, just the DB Folder page.
You can bookmark the graph to save the current configuration. Each graph bookmark, when clicked, loads the graph with the settings it had at the time of the bookmark.
It sounds like you might also find the local graph view useful. https://help.obsidian.md/Plugins/Graph+view#Local+Graph
Hi Obsidian Dev Team. This really needs implementing! It shouldnât take long to implement. It really limits the utility of the graph view right now. Also, API access to alter aspects of the graph view would be really appreciated!