Indexing Entity contents and Docs for Search

Hi again Guys,

I find myself needing this feature more and more as I work in Fibery and my instance grows. There is a topic here about it:

But this is not explicitly a request, so I thought it would be worth creating one just to make sure it’s clear I am interested in this feature being added.

I presume you have this on the backlog as it seems obvious, but wanted to flag it up all the same, perhaps others in the forum will add a vote if they are feeling the same pressing need as I am!

I will say that even with the minimal search now, that only looks at Entity titles, you have some great elements so far:

  • Showing the most recently views Entities as a first choice
  • Allowing anything to be searched, including views - very helpful!

Thanks guys!

3 Likes

+1 for this, needing it badly. This is one of the main reasons i need to keep some of use cases on Coda

1 Like

Running into this more and more as I finish build-out of the system and start transferring data and using it for daily functions. We’re gaining a lot of efficiency in other areas, so that’s good, but discoverability of our data is suffering vs. e.g. Google Docs.

And while I’m replying, I’m sure they have plans for this already, but I’ll just put in a vote for customization of search down the line, e.g. filtering of results from the search box or results page. Something quick and easy to do, but maybe even an “advanced search” option eventually, with more control.

1 Like

We are working on full text search, not sure when it will be done though, but developers are telling that “quite soon”

1 Like

Glad to hear that. This is also a big pain point for me.

And @Oshyan presumably you’re aware a big hole in Notion is they don’t index comments in their “new” search from earlier this year? So big opportunity for Michael and co. if the comments also come through as part of the search. I would really like to petition to include that, as my team endeavors to keep as much communication in our tool as we can, and not outside in Email, Slack, etc.

Thanks!

Ah, interesting, I didn’t actually notice that as I use Notion solo and don’t use Comments that much lately. But I do use Comments in other systems for my own reference, and ultimately would prefer Notion to have that too. So it’s good to know that got removed, and hopefully will be coming back. Their search update was overall a good improvement from before (though what they had before was… terrible, hah). But it was not a total fix, clearly…

1 Like

Hey, just a point of clarification, although may not be necessary: Notion in the previous iteration of search, which you pointed out was not good, did not actually index comments at that time, either. So they keep missing that big piece. And I’d say Fibery with the “most recently viewed” at the top of the limited search we do have right now, is superior even to Notion’s old “original” search.

1 Like

Michael and @Oshyan (and @Chr1sG as I assume as you increase use this may be of need to you) - I was thinking about the fact that Notion doesn’t include comments in search and we have an opportunity to beat them to that function. So when I saw the huge AirTable release today of synced bases and Automations, I thought about do they have that? Well, they don’t - first request in 2015!!

While I’m at it, I’ll close the loop on the “big 3” and add that Coda doesn’t do this, either.

So real chance for you guys. As. I mentioned in your post @Oshyan about use cases, I am really big on Fibery becoming as much of a central communication hub around the work my team does in here, so a good search function is absolutely key to that long-term goal. I assume all reading this may know that Slack really has pushed hard for its search functionality, and they have big benefit from it. If you think about it, aren’t comments in Work Mgmt tools like Fibery, Notion, etc. essentially just as important to a team? So it seems really a travesty that when you’re in those tools, you can’t search through what was discussed in comments!!

If you have a moment Michael, would love to hear from you as to whether you guys plan to include comments in search results. Thanks!

1 Like

Agree, and I’ll just add here that for me personally, when a feature cannot be added, or is more difficult to implement, I would appreciate knowing that fact, even if there can be no indication of whether or when it might be added.

So in the case of Search in Comments, let’s say that extending search to index comments would make it 10x slower for all queries and/or make search indexes 10x bigger, both of which would cause problems for Fibery dev/hosting/etc. It would still be really good to know from @mdubakov or others on the team that they have looked at the request and unfortunately have identified significant blocking challenges like this. Or if they want to do it but identified UI issues that need to be solved first, such as search filtering.

1 Like

Great points! Indeed, if it turns out this particular request, or others, can’t be done for a certain reason, I feel like most of the user base will be understanding. So I don’t see why it’s that risky to explain and effectively “reveal” a part of the roadmap in this case, although I realize it is a very thin line to promise too much roadmap to users as that can be hard to deliver.

Thanks again!

1 Like

How about just an option to select which fields to include in the search query? Depending on the type for our case, different fields of information would be useful to display.

In our case, it’s mostly just 1–2 fields like a customer ID or a product state, which would be huge time savers so we didn’t have to investigate a lot of the results (thank God CTRL+Enter is possible!).

If this or something like it would be implemented, I am fairly certain that would be my main method of navigating around our workspace. Just CTRL+K, write, find, enter. Boom, I am where I want.

I still use search a lot to navigate around, but problem is that it shows only name fields. In our “main” place of interest (table) the name of the row not important at all. The only purpose it has at the moment is being identifiable in searches and references. We generate the name though a button by combining pieces of information from other fields and entities of the parent.

2 Likes