# Killer search function that is a NATURAL fit for Fibery **URL:** \ **Category:** Ideas & Features\ **Created:** [October 22, 2023, 4:34pm UTC](https://community.fibery.io/t/killer-search-function-that-is-a-natural-fit-for-fibery/5324 "2023-10-22T16:34:16Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 22, 2023, 6:10pm UTC](https://community.fibery.io/t/killer-search-function-that-is-a-natural-fit-for-fibery/5324/6 "2023-10-22T18:10:28Z")
> [@Robert\_B](#): > > I ran across YAML’s extensive use when I was working with ~~Fibery~~ Obsidian. It’s basically designed for cross-app, platform, os, type (etc) interoperability. Your point about it being in a database so why bother is understood. YAML enables more communication and comprehension across different data types and systems, which is much more important for some than others. Yes, it seems like a great method to potentially use for something like [development of a Fibery \<-\> Obsidian sync plugin (independent, open source)](https://community.fibery.io/t/proposing-development-of-a-fibery-obsidian-sync-plugin-independent-open-source/4514) (Obsidian new native “properties” also store to YAML in the .md). But it’s more of an interop/sync thing than something to support in Search explicitly IMO. I.e. you translate some other system’s fields/properties into Fibery’s in the sync, and then in Fibery it’s just regular Search on Fields. > [@Robert\_B](#): > > The chief reason I bring it up is two-fold (1) I have a process that makes database + flat file interoperability very beneficial and I’m planning to pursue it more and (2) I am still thinking about that Obsidian/Fibery integration we discussed, and my massive workload of late is finally clearing up. (By the way, on that subject, I had mentioned N8N previously. Two interesting things: first, there’s a user here who does a lot of N8N-driven Fibery and Obsidian stuff, I saw him active in the N8N forum, and (2) N8N is so good that we standardized on it and transferred our pipedream work there. I would still really prefer to see a “native” approach, probably as an Obsidian Plugin since I think that’s where the challenging stuff would have to be done, locally, and then just connect via the Fibery API. But I don’t have dev skills or resources, and if someone creates an N8N approach that I could use, well, I’ll probably use it. 😄 > [@Robert\_B](#): > > After reading your reply, I realized that perhaps there is a way to emulate what I’m looking to accomplish above with search, because truly that X1 search was wildly effective. I realized that - for example - I could take 10 example searches and then create 10 different views with certain filters in place. Then perhaps something that would do a popup to enter criteria. Maybe to achieve the results it’s possible to make a Fibery hack a la Yvette. Yep, absolutely. You can have a whole Space that is just “Search” if you want, and then just create a bunch of Views that can be re-used as Searches with sort of “default” parameters, sort them into Folders, etc. --- _[View the full topic](https://community.fibery.io/t/killer-search-function-that-is-a-natural-fit-for-fibery/5324)._