Currently, the search prioritization is not efficient for how we would like to use it. When you search for any general type (e.g., search for “anesth”), you will see that you may need to scroll through several pages of users to see all active users with that result in their identifiers.
We would like a way to optimize this by changing any current settings in the server.
Ideal priority for displaying the search results:
Departments/groups
Active Users
Inactive Users
Sort options are available in xmpp properties to update the search priority by rank, presence, name, patient and type.
/opt/EXTENSION/conf/XMPP/interface.user.properties
And the section of the file being updated would be:
# Sort ordering for roster searches
# Properties must follow the form roster.search.sort.<n> where <n> starts at 1 and increases.
# <n> specifies the order to apply sorting. Sorting options are:
# rank - Sort using match ranking based on frequency match on name then title for users/groups or name the location for patients/locations
# presence - Sort by available, unavailable, offline. Group presence is rolled up from users.
# name - Sort by name
# patient - Sort patients last (legacy support)
# type - Sort by User, Group, Department, Patient, Place
#
# To revert sorting to earlier than XMPP 4.2 use
# roster.search.sort.1=presence
# roster.search.sort.2=patient
# roster.search.sort.3=name
roster.search.sort.1=rank
roster.search.sort.2=presence
roster.search.sort.3=name
I believe this is actually being resolved with our current open case 528849, by changing the roster search order in Vina.
This is not on the roadmap for Vina but is something we are exploring as an overall enhanced user experience in future apps.