Hi, Romero!
Look at this project which does search for Documentation with iKnow and iFind by @Konstantin.Eremin. Demo. Github.
It uses iKnow for autocomplete functionality in a search box.
- Log in to post comments
Hi, Romero!
Look at this project which does search for Documentation with iKnow and iFind by @Konstantin.Eremin. Demo. Github.
It uses iKnow for autocomplete functionality in a search box.
Hi, Vitaly!
Thanks for your input! This is very interesting and totally different approach to solve the task which I like every time about InterSystems technology that problems can be solved with different approaches and you never know how many options even exist )
Hi!
Here is the remastered version of Meetup live stream recording.
So, the final recipe looks like following:
For Insert and Update calculate the hash e.g. with MD5 and put it in Hash property. Index it with not unique index.
Find duplicates with SQL query on Hash where group by for hash shows more than one occurrence.
Loop through all the values with same hash just and check Text property values to be sure that they are duplicates but not hash collisions.
Thanks, Alex, Dmitry, Robert!
True, but it can find also similar, but not identical, right?
Thank you, Mike! Indeed the results are odd sometimes. We'll investigate the case.
Hi, Robert!
Thanks! That's really nice!
Thanks, @Alexey Maslov! What is the preferred algorithm to use hashes in this case?
And what about collisions? Should I care about that too?
Thanks, Eduard. But I'm looking for duplicates, not for similar records. How can %SIMILARITY help here?
Thanks, Dmitry. Yes, the focus is - best performance.
But what about the index declaration? There is a limitation of 511 symbols in an index, right?
Should I put that in an index declaration or it will solve it for me automatically if I index an entry with value >511 symbols?
I also want to share Atelier playlist on the InterSystems Developers YouTube Channel which contains several "How to with Atelier" videos. Stay tuned!
Danny, thank you for this fantastic series!
Glad to hear that!
Hi, Lin!
You are creating this calculated dimensions as shared members. In this case, they are stored in some ^DeepSee.* global.
One of the options to avoid calculated dimensions' storage in the global and further deployment difficulties you can use calculated members with Shared Storage option turned off.

You can alter this option if you create calculated dimension in a named and saved pivot.
In this case, the calculated measure definition will be placed directly in the MDX query of this pivot thus you don't need to deploy it, cause it will live with the pivot.
Hi, Ron!
Just checked it - all works fine. What is the error you are having?
Thanks, Eduard!
This is very helpful.
May I ask, what are the caveats using basic authentication instead of CLP (Caché Login Page)?
This is really nice!
And short, so very is suitable for macro.
Sergey, thank you for the thorough answer!
Then, in your client app settings
Do you mean web-app settings like in the following screenshot?

But why not using basic authentication? Can I consider using it?
Hi, Dan!
Sure, it is the option, thank you! And I can mention your series of posts with the step-by-step implementation of it.
Hi, Danny!
iFind search on documentation is implemented. Try it out ;)
Hi, Constantin!
When I search documentation with your online tool what is the version of documentation it works with?
Would you please add the version of the product in the results or somewhere?
Thanks in advance!
Hi, [@Rubens Silva]!
You mean we shouldn't be shrinking replies?
But how about indent in the discussion tree? I think indent helps to follow the discussion. Thoughts?
Yep, we will post remastered version soon )
Sure, Jeff! Hope you can make the next one. Prepare your questions! )
Join Live Stream today and ask your questions online!