Searching diigo (i.e. "Links") is not searching our index only - it looks like its searching all of diigo. Very odd behaviour.

• We have a large database which uses MSSQL server.
• We would like to create an endpoint that searches fulltext across a bunch of tables we provide..

? Whether we create a script to input into ES or do live searching on the SQLServer. NB: Although data is updated frequently - nightly dumps will be plenty frequent enough.

More details to come - but for now

It would be nice to create a bot for our MS Teams (https://docs.microsoft.com/en-us/microsoftteams/platform/build-your-first-app/build-bot)

• so if user types in "/searchace string"
• Bot responds with top 5 items - and links to those items..
• we could expand it to /searchace title:string collection:sharepoint" or other aspects

We have a couple of NTFS Shared drives. We would like to be able to index the files/folders on these shared drives. I guess the index would need to cover:
Author
Date
Content (so if txt, docx, pdf etc try and extract the content).
File name
Folder path

Any better way??

(See also #3 which may replicate this)

So if a search is done for "Bees", 5 things are returned. If everyone clicks on the 4th one - then this goes up in its ranking and becomes item number 1

We have a few manuals and company documents on gitbook (http://acecentre.gitbook.io).

NB: All these docs are largely Markdown. We could do a nightly export - and then create an import script to ES.

(or we just use https://developer.gitbook.com/rest-v1/search)

Would be sensible to make frontend web app accessible by a 365 Auth box - so the entire thing "could" be public facing..

NB: We intend for the app to be internal only - but by putting this in place its an added security feature (and allows us to move to a cloud host in the future)

We need a way of searching our MS Teams platform

Ideally we would like a way of searching our slack channels

The whole stack is a little outdated - it would be wise checking the entire stack is good - and upgrading components as we need to

• Is ElasticSearch still the right tool?
• Node/Cofeescript stack still right?

NB: We want to open this project to allow other people to use it - so using tools that allow open development as best as possible is a priority

Our site is currently a wordpress site..

http://acecentre.org.uk

Two ways I see of doing this either:

1. We use the wordpress REST API to get all data and put that in our elasticsearch index.. e.g. http://wp-api.org/node-wpapi/
2. Use something like this.. https://github.com/parisholley/wordpress-fantastic-elasticsearch/

however, note we don't want our elasticsearch index publicly available.. -or our site to use this as search system

• We have a 2-3 LARGE sharepoint drive (several TBs)
• We can mount this as a drive on a machine - or we could use APIs to search.. (https://docs.microsoft.com/en-us/sharepoint/dev/general-development/sharepoint-search-rest-api-overview)

We need to add these Sharepoint stores as search points. And either input into the elasticsearch store - or do live searching (and maybe wise caching them if this turns out to be slow)