Search Behaviour (ISLG & ILG)
Hi Morgan,
We have discussed search behaviour several times throughout the UAT process, although there are still some discrepancies in the search behaviour across the applications. In both ISLG and ILG there seem to be 3 separate types of searching behaviour applied to each, they are written down here:
For consistencies sake, it seems a good way forward would be to apply the same behaviour in all search scenarios. Since performance was discussed as a reason to not have search run on 'key up', it might make sense to implement: searching only upon hitting 'enter' or the search icon, regardless of the number of characters inputted into the search field, and no 'key up searching' functionality.
Just to clarify, this would only be for the admin side, as search behaviour on the front end has been designed separately and specifically for each research tool.
Thank you,
Naomi
We have discussed search behaviour several times throughout the UAT process, although there are still some discrepancies in the search behaviour across the applications. In both ISLG and ILG there seem to be 3 separate types of searching behaviour applied to each, they are written down here:
For consistencies sake, it seems a good way forward would be to apply the same behaviour in all search scenarios. Since performance was discussed as a reason to not have search run on 'key up', it might make sense to implement: searching only upon hitting 'enter' or the search icon, regardless of the number of characters inputted into the search field, and no 'key up searching' functionality.
Just to clarify, this would only be for the admin side, as search behaviour on the front end has been designed separately and specifically for each research tool.
Thank you,
Naomi
Thank you for putting this document together. It will be a useful tool for getting a comprehensive look at all the searches across the system. We should probably do something similar on the subscribers sides as well.
It makes sense to keep things consistent across both applications, and searching only upon hitting 'enter' or the search icon is fine with me. How do you suggest we implement this?
Also, at what point should we bring Contegra into the discussion to help with the performance of the searches. I think they can bring a lot of value to the table, particular for searches that are going to be relying on dtSearch.
Thanks,
Morgan
Thanks for your feedback. We will create a card in Target Process to address the updates to the necessary search fields.
In terms of Contegra's input on search do you foresee this being more to do with design, implementation or both? We can document the subscriber side searches along with the desired behaviour as it has been designed and share that. We are happy to discuss this with Contegra at any time but will need
Mel
Yes, documenting the searches as you've suggested sounds great. Assuming
Thanks,
Morgan
I am reviewing this requirement of search functionality in Subscriber site. What I would prefer is let us first define scope of this feature from our side and then we can discuss internally first and check if any challenges there with
Thanks,
Ketan
Thanks,
Morgan
Note that I have added this item to tomorrow's agenda under ISLG Rebuild Project: Issues to be discussed. Please provide any relevant updates.
Thanks,
Morgan
Please find below a link to a document outlining the subscriber side search behaviour. Please let us know if you need anything else.
https://docs.google.com/document/d/10TP4xS4YUgmnznIUI2pzzMA2HOZu1FPm8dE7zmgudtA/edit?usp=sharing
Mel
Morgan