Hi Irit ,

The search is the Subject Navigator is currently being worked on by the development team.

However, Harsh and Ketan , I experienced the same problem in the Dispute & Document Library search: http://rebuild.investorstatelawguide.com/DisputeDocuments

image.png 122 KB • Download

Shouldn't this be working?

Morgan

Hi Irit and Morgan ,

This issue is resolved on staging.islg. Please check and confirm.

Hi Harsh ,

Further to the video below, could you confirm whether this is final UI for the Subject Navigator search? Currently, the initial page of results skips the step of providing users with contextual results where only the relevant branch and its parent branches are displayed in the results, and then the user is taken to the full branch when they select the branch.

Naomi and Melissa was this something missed in the requirements? Because I'm really surprised if this is something we missed.

Problems with Subject Navigator search results (1-Mar-21).mp4 14.7 MB • Download

Thanks,

Morgan

Hi Morgan ,

Yes this is the Final UI of SN Search. 

As we decided in Thursday meeting at the time of discussion of SN Search, We decided to render all Parent and Child branches with matching result. so user wants to navigate with other branches after search so they can.

Ok. Thanks Harsh ​.

Melissa ​ and Naomi ​, could you please consider what efficient solutions we could introduce to ensure we resolve this issue before launch. I'm really uncomfortable with how the results are presented currently, and this is our most important tool in the application.

Morgan

Hi Morgan ,

It seems the design of the SN search has changed a couple of times since the original wireframes due to various conversations along the way. Going back to the original proposal this seems like that approach would meet all of the requirements outlined in the video as well as would be consistent with the UI for search in other research tool modules:

image.png 155 KB • Download

The proposal here would be to display matching search results within a modal (similar to how it works in the Article Citator). Users would have the context of the letter, oldest parent branch and direct parent branch for each matching result and could select their desired result to be anchored to that location in the SN tree where all branches would be available for further context. Likely we could maintain the current functionality as well (upon search matching branches are expanded with keyword matches highlighted) so that if users preferred they could close the modal and navigate through the search results from the tree to immediately see all branches surrounding the keyword matches.

The other benefit to the modal approach is that the modal can be closed and re-opened without the user needing to re-perform their search, so they can navigate between the two ways of browsing search results easily. Additionally as mentioned above, this would keep a more consistent search experience across research tools.

Harsh would of course need to inform us on how feasible this would be for launch. 

Would this solution work for the problems addressed above?

Hi everyone,

Following up on above, I'm going to add this item to the agenda for Thursday's team meeting. However, could you please you all spend some time internally discussing solutions to the problem according to the following:

Thanks,

Morgan

Morgan

I am concerned that displaying the tree structure for search result branches within the modal will be difficult to browse and may negatively impact performance. The thinking is that the user would select a search result to view the full context.

Do you think including the full path rather than a truncated version above the search result is adequate?

image.png 31.3 KB • Download

Mel 

Hi Melissa ,

Can we have a quick call. Connect here: https://us02web.zoom.us/j/6046323469

Morgan

Hi Melissa ,

The modal doesn't provide the context required, particularly when you have multiple results within the same subject. Further to the screenshot from the legacy app:  https://www.investorstatelawguide.com/ResearchTools/SubjectNavigator?toc=content&id=50&tab=r&search=enron&searchType=boolean&stem=1&thes=&ftypo=1&fuzziness=1

image.png 209 KB • Download

displaying the results within the tree gives the user context on how many results are located within a particular subject or sub-branch. Separating the results into individual listing within the modal strips away that context.

Also, why would this compromise performance? It works quite well within the legacy app.

Thanks,

Morgan

Hi Morgan ,

As discussed in last week call, We render only matching keyword branches and set View Context link beside branch name which will open in new tab with all data.

We have deployed on staging.islg.

Thanks Harsh ​.

Naomi ​, can you please test and confirm that this meets the requirements under the applicable user story.

Thanks,

Morgan

Hi Harsh ,

Further to the video below, the search results are still taking a very long time to load, which is preventing the user from selecting links on the page. Why is this still a problems after removing the highlights?

Morgan

Problems with Subject Navigator search (16-Mar-21).mp4 2.09 MB • Download

Morgan , It is depending on branches and Dispute Documents card which is going to render at one glance. If there are larger data then it is obliviously taking time to render all things and open all branches.

If you find with abuse of process word then it is finding in less number of branches and Dispute Document card so it will render within 3 second.

Ok, Harsh , but I'm not searching "abuse of process". I was searching "good faith" and as you can see in the video, I was experiencing problems. How do we resolve the issues demonstrated in the video?

Morgan

Hi Morgan ,

Can we remove the Dispute Document Card which is rendering with search. We can display only Parent and Child branches without Dispute Document Card.

If we go with this approach then "Good Faith" word will give result within 7 to 8 Second and abuse of process will give result within 2 second.

If user wants to see dispute document card then they can click on view context link which will open in new tab.

Please confirm.

Ok. That's fine, but 7-8 seconds is still too slow. What is slowing things down?

Hi Morgan , 

Regarding the updated view I have moved that card to done. There are still outstanding issues related to the search functionality, but that is being tracked between bugs and the "Search Implementation" on basecamp.

Great. Thanks Naomi .

Harsh , I'm going to keep this to-do open until we're satisfied that the Subject Navigator search is fully operational.

Thanks,

Morgan 

Hi Morgan ,

As per my above comment, We have removed that Dispute Document Cards in Search result. Only matching keyword Parent and child branches are rendering.

now good faith search result is populated within 5 to 7 Second now we can't optimize further as it is depending on result. The abuse of process result populated in 1 second.

Hope this is fine. 

Hi Harsh ,

We'll work with this for now. One more issue, I've noticed that the link for node above the document cards still appear active even though selecting them has no effect, because we have suppressed the document card. Is it possible to suppress these links when viewing the results in this view? Then it will be clearer that they need to select the "View in Context" link.

Thanks,

Morgan

image.png 247 KB • Download

OK Morgan . When user search in SN will display as branch label instead of link.

Hope this if fine.

Ok. Great. Thanks Harsh . Also, just to confirm this should only apply to this search results view.

Morgan

Yes Morgan . It will be applied to only search result.

Hi Morgan ,

We have removed the link and display as label in search result view on staging.islg.

Looks good, Harsh . Marking to-do complete.

Morgan