geolexica / isotc211.geolexica.org

ISO/TC 211 online version of the Multi-Lingual Glossary of Terms
https://isotc211.geolexica.org
4 stars 2 forks source link

Use Algolia search #10

Open ronaldtse opened 5 years ago

ronaldtse commented 5 years ago

We should use Algolia search rather than locally-searching through a concepts.json.

ronaldtse commented 5 years ago

@strogonoff thoughts?

strogonoff commented 5 years ago

not sure it can beat current search but we can see (I can take this later after other ISO TC sites though)

On 18 Feb 2019, at 10:02 AM, Ronald Tse notifications@github.com wrote:

@strogonoff thoughts?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

ronaldtse commented 5 years ago

Agreed.

strogonoff commented 5 years ago

For the record I see https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/#fetching-and-reworking-your-data-for-algolia, but not sure yet if it’s available on our Algolia plan. cc @ronaldtse we can send a JSON index to Algolia, right? Will this count under Algolia Open Source?

ronaldtse commented 5 years ago

@strogonoff I believe so, I think it currently falls under the Algolia free plan (10,000 records).

strogonoff commented 5 years ago

Great, if we can send a custom index then I’m breaking this down into steps for me to take as I see them:

ronaldtse commented 5 years ago
  • If that’s not enough for good concept search experience (I believe a website like Geolexica should have a purely concept search rather than generic website-wide search), we may be able to create our own concept index (we already have some indices for other purposes), and send it to Algolia on build using their Ruby client wrapped into a simple Jekyll plugin.

Agree!

strogonoff commented 5 years ago

@ronaldtse might need Algolia admin API key for Geolexica here; let me know if we have it & maybe using another channel is better for this!