What happens if a connector goes down?

Monitoring is part of the ongoing service FUSE provides. A problem can occur, for example, if a webservice isn’t available or a vendor updates their API which breaks FUSE’s connection to your content.

First, no worries — your users won’t notice anything amiss. FUSE will continue to seamlessly use the latest successful index of that content. The index won’t have content that is new between the time of the connector outage and the search being conducted, however.

Next, we get alerted when this type of thing happens. Nine times out of ten, the problem fixes itself at the next indexing attempt. If something really is down, however, it’s up to the FUSE team to get it running again — the are no fees or development costs. This is part of the ongoing service you’re paying for.

Our content does not have an API. Will FUSE work?

FUSE’s numero uno choice to reach content is via API since we can get all of the nice juicy taxonomy and other metadata that way (which feeds our powerful filters). This isn’t always possible, however. As a last resort, we’ll crawl a content source just like Google does. Also called “scraping,” we avoid if we can because it often produces messy and inconsistent output that we then have to process/parse additionally.

No worries about authentication if the resource in question is behind a wall or a mixture of public/private - we can handle both scenarios no problem. Scraping/crawling makes sense sometimes when there’s a source you want to index but just aren’t interested in the metadata or there’s really no metadata to be had.

Can FUSE categorize different content from a single source?

Sure can. It’s not uncommon that an organization has things like press releases, blog posts, and general web pages stored in one system, like a CMS. FUSE can display those items as one or split them up so as to appear they come from different spits. In terms of billing, you’re still charged for just one source/connector.

How does FUSE handle sorting by date?

There may be certain cases where your content comes over as month and year (like a newsletter or publication) and others when it’s month, day, and year. Then there’s the “authored on” and “updated on” dates to consider. Date handling is highly configurable on a source-by-source basis in FUSE. We’ve seen all sorts of wacky requests over the years - go ahead and try to stump us!

Can you weigh certain search results?

Yes. That’s the beauty of FUSE. There’s no black box (ahem, Google Search Appliance, Mini, or Site Search or any number of other search products). You have full control over what shows up on top. We advise clients that it can take six to twelve months for your search to ‘mature’ in-market. This means that you’ll continue to refine it over time until you have it just. the. way. you. want. it. And the best part is FUSE will be with you each step of the way with no additional fees to pay or billable hours to worry about.

How can FUSE group results using the same taxonomy across varying content types?

In an ideal world, each content source FUSE indexes would have an identical taxonomy. We can get around mismatched (or no) taxonomy in a few ways, however:

  1. Since each content source can have its own set of taxonomy-based filters (e.g. topic, audience), we’ll show the filters for those sources that have it and hide them for those that don’t.

  2. If the sources in question each have taxonomy but they don’t match, we can map them to each other (e.g. Intellectual Property is mapped with Legal Technology and vice versa).

  3. Allow FUSE AI to ‘suggest’ taxonomy for your content. This works best when you feed FUSE a list of taxonomy from which it can choose to apply.

How is performance of our website or our sources affected?

When FUSE first indexes your website or external content source, there will be a performance hit since we’re indexing potentially thousands of content items potentially going back several years. Performance is usually moot since it's a onetime event never to be seen again (unless for some reason a complete re-indexing is required again down the road). After the initial indexing, FUSE only indexes new items with no discernable performance penalty since it’s essentially the same as a web user requesting a webpage. We figure out what’s new content by performing a single item query at the next scheduled pull: Get most recent item from this content source. Does it match the latest item we already have in our index? If yes, stop. If no, get ten latest items. Now do we have them all? Rinse and repeat.

As for your website, there is no performance concern since we store your index in AWS and all of the computing power to run queries is happening there. A good analogy is YouTube. You can embed five hour long YouTube videos on a page on your site with no performance issues since the streaming/computing power comes from YouTube’s infrastructure.