improved search

[Yuvraajb]

1. Enhanced Search Suggestions
   Enabled search suggestion features, allowing users to see likely completions for their queries as they type. This improves user experience by making it faster and easier to find relevant content.
2. Search Term Highlighting
   Implemented search term highlighting, so that when a user selects a search result, all occurrences of the search terms are visually emphasized on the destination page. This helps users quickly locate the information they need.
3. Search Query Sharing
   Added a search sharing capability, which introduces a share button next to the search reset. Users can now generate and copy direct links to specific search queries and results, facilitating collaboration and reference sharing.
4. Search Result Ranking (Boosting)
   Incorporated search boosting by configuring certain pages or sections to rank higher in search results, ensuring that the most relevant or frequently accessed documentation appears first.
5. Search Exclusion
   Provided the ability to exclude specific pages or sections from the search index, reducing clutter and ensuring only pertinent content appears in search results.
6. Performance and Usability Enhancements
   Optimized the underlying search index and improved the responsiveness of the search bar, resulting in faster query processing and a smoother user interface.

[netlify]

✅ Deploy Preview for caplex ready!

Name	Link
🔨 Latest commit	d71fe83
🔍 Latest deploy log	https://app.netlify.com/projects/caplex/deploys/685ceba0b17b5700083df700
😎 Deploy Preview	https://deploy-preview-88--caplex.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[MRdep]

Hi Yurraaj, Thanks for spending time to try to fix this. A key function of the search will be to lookup items in the tables located in Sections via their OSIPI name. Perhaps you can limit the search bandwidth to only look in those headings? We want to prioritise these in the search so that if I search '"Signal" then it brings up the row of the Quantities table and the "Signal" row. At the moment, even with your new changes, it brings up lots of irrelavant information. We want to therefore deprioritise anything that is not in these tables, so they appear further down the list. The second functionality we need is to be allow Notation volumn to also be included. This is a bit more difficult because there is not a way to specify subscripts etc, but perhaps it is possible to do this in a case-insensitive and sub/sup screipt insensitive way.

…

-------------------------------------------------------------------------- Ben Dickie, PhD Senior Experimental Officer and Senior Research Fellow in Preclinical MRI 7T MRI laboratory, G727 Stopford Building The University of Manchester mob: 07837837807 | e: ***@***.*** ------------------------------------------------------------------

________________________________ From: netlify[bot] ***@***.***> Sent: 26 June 2025 07:42 To: OSIPI/OSIPI_CAPLEX ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [OSIPI/OSIPI_CAPLEX] improved search (PR #88) [https://avatars.githubusercontent.com/in/13473?s=20&v=4]netlify[bot] left a comment (OSIPI/OSIPI_CAPLEX#88) [github.com]<https://urldefense.com/v3/__https://github.com/OSIPI/OSIPI_CAPLEX/pull/88*issuecomment-3007333850__;Iw!!PDiH4ENfjr2_Jw!DssfQ_Bwrfy1MLVs-iZOfTiuf5vqsmHwLdyRuuGPE_mbnXHn5Q4W6io-WsvWffleMEUhiBV3iWLLCDelK3tt0AfCxwo0PfsK$> 👷 Deploy Preview for caplex processing. Name Link 🔨 Latest commit d71fe83 [github.com]<https://urldefense.com/v3/__https://github.com/OSIPI/OSIPI_CAPLEX/commit/d71fe834bdbd5eb5abad38b350979f5e346badd1__;!!PDiH4ENfjr2_Jw!DssfQ_Bwrfy1MLVs-iZOfTiuf5vqsmHwLdyRuuGPE_mbnXHn5Q4W6io-WsvWffleMEUhiBV3iWLLCDelK3tt0AfCxzJ1Djn1$> 🔍 Latest deploy log https://app.netlify.com/projects/caplex/deploys/685ceba0b17b5700083df700 [app.netlify.com]<https://urldefense.com/v3/__https://app.netlify.com/projects/caplex/deploys/685ceba0b17b5700083df700__;!!PDiH4ENfjr2_Jw!DssfQ_Bwrfy1MLVs-iZOfTiuf5vqsmHwLdyRuuGPE_mbnXHn5Q4W6io-WsvWffleMEUhiBV3iWLLCDelK3tt0AfCxztTxg2x$> — Reply to this email directly, view it on GitHub [github.com]<https://urldefense.com/v3/__https://github.com/OSIPI/OSIPI_CAPLEX/pull/88*issuecomment-3007333850__;Iw!!PDiH4ENfjr2_Jw!DssfQ_Bwrfy1MLVs-iZOfTiuf5vqsmHwLdyRuuGPE_mbnXHn5Q4W6io-WsvWffleMEUhiBV3iWLLCDelK3tt0AfCxwo0PfsK$>, or unsubscribe [github.com]<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABWSCP2DDW5S7UBPN2OCYUT3FOI35AVCNFSM6AAAAACAFIEBP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBXGMZTGOBVGA__;!!PDiH4ENfjr2_Jw!DssfQ_Bwrfy1MLVs-iZOfTiuf5vqsmHwLdyRuuGPE_mbnXHn5Q4W6io-WsvWffleMEUhiBV3iWLLCDelK3tt0AfCx0AxAHCo$>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Yuvraajb]

Thank you for your thoughtful feedback and for outlining the key priorities for the search functionality. Your points about focusing search results on the OSIPI names within table sections and prioritizing these matches make a lot of sense. I’ll look into refining the search algorithm to limit its scope to the relevant table headings and rows, and to boost their ranking so that terms like “Signal” bring up the most pertinent entries first, with less relevant results moved further down.

Regarding the inclusion of Notation volume and handling of subscripts/superscripts: I agree this is a challenge, but I’ll explore implementing a case- and script-insensitive comparison to improve matching accuracy for these notations.

I’ll update here as soon as I have a revised approach or prototype for you to review.