Settings and activity
195 results found
-
31 votes
Eric Young
supported this idea
·
-
4 votesEric Young
supported this idea
·
-
6 votesEric Young
supported this idea
·
-
10 votes
An error occurred while saving the comment Eric Young
supported this idea
·
-
10 votesEric Young
supported this idea
·
-
6 votesEric Young
supported this idea
·
-
22 votes
An error occurred while saving the comment Eric Young
commented
We are live with v7.5 and gearing up to determine our settings for Pickup Area and we will be reviewing all hold related services, such as looking at Vega LX (Starter, Discover, etc.), Innovative Mobile, and Polaris API. We have been working with our locker vendor to honor the new SIP2 extension, which is going well. The new pickup area functionality needs to be supported in all hold related features, functions, and services.
Eric Young
supported this idea
·
-
17 votes
An error occurred while saving the comment Eric Young
commented
This seems "easy" from an API standpoint at a high level. Notice queue comes into LX Starter, then an API call is sent to retrieve all items out and on hold, etc, adds those details to the notice and send...
I know, easier said than done but it is doable... please 🙏
Eric Young
supported this idea
·
-
2 votesEric Young
supported this idea
·
-
129 votes
An error occurred while saving the comment Eric Young
commented
This idea for enhancing facet navigation and display in Vega Discover is highly commendable. It addresses critical user interface issues, making search results more accessible and user-friendly. The proposed word wrapping, expanded content display, and scroll features for facets will significantly improve usability, especially for extensive data categories. The removal of the Apply Step simplifies the navigation process, while prioritizing the 'home location' in the Location Facet is a thoughtful addition. These improvements are not only practical but also essential for a more efficient and intuitive search experience.
Eric Young
supported this idea
·
-
8 votes
An error occurred while saving the comment Eric Young
commented
I completely agree with this suggestion! The current behavior in the Location Drawer can indeed be quite confusing for users. When you change the location and see the search term retained in the search box, it naturally implies that the results should reflect the inclusion of that search term within the new location. However, the fact that the results don't automatically update based on the new location can lead to frustration and misunderstanding.
To improve the user experience, it would be much more intuitive if the system either discarded the search term when the location changes or automatically re-executed the search with the new location settings. This would ensure that users get the results they expect, making the interface more user-friendly and efficient. Thank you for bringing this issue to attention, and I hope the necessary changes will be implemented to enhance the functionality of the Location Drawer.
Eric Young
supported this idea
·
-
78 votes
An error occurred while saving the comment Eric Young
commented
We are excited about the potential of Showcases in Vega, but we need a way to create them from our ILS data. We have a lot of staff-created lists and record sets in PowerPAC that we use for content carousels and other features. It would be very helpful if we could use them to generate Showcases automatically, instead of having to manually enter each record. This would save us a lot of time and effort, and make Showcases more appealing and useful for us.
Eric Young
supported this idea
·
-
10 votesEric Young
shared this idea
·
-
29 votesEric Young
supported this idea
·
-
11 votes
An error occurred while saving the comment Eric Young
commented
The inclusion of these merge tags is not merely an enhancement but a necessity for the feature to be considered complete and functional. Please also see and support the need for other missing merge tags.
Eric Young
supported this idea
·
-
21 votesEric Young
shared this idea
·
-
14 votesEric Young
supported this idea
·
-
13 votesEric Young
supported this idea
·
-
37 votes
An error occurred while saving the comment Eric Young
commented
We need this before we move forward with Showcases.
Eric Young
supported this idea
·
-
26 votes
We will consider this idea for possible future development. Thank you!
An error occurred while saving the comment Eric Young
commented
Following the recent implementation of LX Starter, we've identified a crucial need for a Non-Blocking Note to be added whenever LX Starter updates a patron's notice preference due to a spam marking. With our first batch of 6.8k messages, one was marked as spam, and without this note, it's extremely challenging for our staff to identify such modifications in the ILS. This feature would be in line with the existing system where a note is added for hard bounces.
For clarity, we propose the note to read: "Email address: xxxx@xxxxx.com was marked as spam on {MM-DD-YYYY at HH:MM pm/am}. Please update."
Thank you for considering this enhancement.
An error occurred while saving the comment Eric Young
commented
The added notes in the ILS will be extremely helpful as we don't plan on allowing staff to access LX Starter and having a full picture of what is happening with notices at the patron level in the ILS is key for staff success.
Eric Young
supported this idea
·
I concur, an "image manager" or selector feature within Vega could significantly streamline the image sourcing and reusing process, making it more efficient and user-friendly.