Constructor.io Search vs. HP Autonomy Intelligent Universal Search (discontinued)

Constructor.io Search takes all of the guesswork out of maintaining a search engine. As merchandisers or product teams, we have educated guesses at how search relevance should work but the customer is always king. We can't always predict the ways in which consumers will search or what their intent is. That's why the behavioral-driven approach that Constructor.io employs works so well. It means that merchandisers can focus on their sales and promotional responsibilities, instead of wasting time and bandwidth on base-level relevance questions.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

It does a decent job at its core functions (that other free software does just as well or better).

• Optimizes for business KPIs, not string matches, so merchandisers can focus on strategy instead of maintaining a dictionary.
• Gives merchandisers control to curate the right customer experience per their expert understanding.
• Customer/technical support during and after implementation.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• It adheres to traditional Microsoft standards such as: fact-dump documentation with no coherent story or 'best practices' information, inability to automate common tasks, intentional obfuscation of its basic operations.
• It provides OK search results. Not great, but OK.

• Visibility of the personalization algorithm.
• Exposing detailed analytics within the customer-facing dashboard.
• "Top searches" available via API.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• There are about a dozen different config files to maintain, and the most important one is dynamically modified by Autonomy itself while it runs. Which means that it is impossible to automate the configuration or keep the configs in versioned source control. Even `cp *.cfg ~/cfgbak/` won't help you roll back a change, because it is never safe to restore a previous config. You'll be using `diff new.cfg old.cfg` a lot.
• The Linux port is poorly thought out. The binaries are named *.exe. The StartService.sh scripts contain both `echo 'Are you sure you want to start the service? Hit ctrl-C to cancel''; read dummy` and, I kid you not, a `chmod a+x /path/to/my/binary.exe`.
• Many features are poorly documented, leading to lots of back and forth with the support department just to answer basic questions like "what does this error code in my logs signify?"
• It seems to reinvent the wheel, poorly, everywhere. E.g. the scheduled backup feature rolls through a user-defined finite list of directories in which to store backups. On day 0 it uses directory 0, on day 1 it uses directory 1, and after day N it rolls back and overwrites directory 0. Why would this be preferable to using a single directory and naming zip files based on the current timestamp?

Management wants to see ROI on the (hefty) cost of purchasing this software, and has mandated that we continue using it. We would prefer to switch immediately.

• I have learned to tack a zero onto the end of any estimate I make for how long an Autonomy change will take in both planning and implementation.