446 results found
-
Improving search with stemming and truncation
We have noticed that stemming in Vega Discover seems to work mainly for English. For example, ‘history’ also retrieves ‘histories’, but the Swedish word ‘historia’ does not retrieve ‘historier’. Since we are a Swedish library, it is important that stemming also works effectively for Swedish, not only for English.
As stemming can be challenging and sometimes unreliable, truncation is a vital complement. Truncation gives users more control and helps capture all inflected forms or compound variations of a word (which is especially important in Swedish). For example, searching for compounded words with a wildcard (e.g. ‘histor*) would ensure broader and…
3 votes -
Add Availability Status to Showcase Items
Like many libraries, we have a Library of Things and many of the items can't be stored out on the shelves. This makes it difficult for patrons to browse our LoT collection when they visit the library. We're creating a system of cards, but that is fussy and requires regular inventory to make sure cards accurately reflect what is here.
I know we can make a carousel list of LoT items in Vega. What I would like is a carousel that indicates if items are available at a location or checked out.
In my imagination, we'd have a large TV…
1 vote -
Social sharing of lists
Expand the current social sharing via X and Facebook to add Instagram, as many libraries have Instagram presence.
1 vote -
Google Analytics Field in Vega
Could you please add support for a single configuration field where we can paste our Google Analytics Measurement ID (tracking key)? Ideally, this would be a dialog box or settings field in the admin/back-end interface that automatically injects the Google Analytics script across the site once the key is provided.
This will allow us to manage our own Google Analytics account without requiring us to write custom scripts to go in page footers, etc.
8 votes -
Logging when a customer logs into their Vega account
We would like to have some logging of when a customer signs into Vega. This would help us troubleshoot certain transactions the customer may have issues with. It would also provide counts for other types of usage reports pertaining to Vega usage.
2 votes -
Have fields to hold translations for Showcase titles
We currently use English, Chinese, French, Polish and Spanish languages as options in our Vega Discover. While toggling between languages, I noticed that embedded showcase titles remain in English regardless of the language selected (I wasn't expecting it to translate).
Proposed idea: Could there be an option to enter additional languages for Showcase titles that can be pulled when the overall platform language is changed so that native Chinese speakers see the librarian-inputted Chinese Showcase Title instead of the English title? If no alternate language title was entered, it should default to the English language title.
Thanks for your consideration!
11 votes -
Prioritize 800/830 for series display before 490 field
Sometimes the series displayed on the item (i.e. what goes in the 490 field) is not unique enough to distinguish it from another series with a similar title. However, the 800/830 fields allow for this distinction by displaying the unique authorized version of the series. Therefore we would like the 800/830 prioritized for display and the 490 to only display if there is no 800/830 field. Attached is the example we encountered where the series statement displayed on the graphic novel series (490 field) exactly matched that of the regular print (not graphic) series. This resulted in the link to…
18 votes -
Adding Irish as a language option
We would like to see Irish as a language option in Vega - we can provide the translation itself and just need the framework to be created.
2 votes -
order the contents of facets by # of hits or alphabetically
With Encore we could select how our branches (collections) sorted. With 39 locations this is important to us. Ideally there would be a synch between the patrons "home library" and the top branch, but for now, we would appreciate the ability to sort locations alphabetically. Seeing a differently ordered list after each search reduces usability.
15 votes -
Prevent SHR information displaying under title
We need a way to prevent serial holding record information from displaying in the work card. SHR info is very useful when looking at an individual library's location drawer, but since it can differ from library to library in our consortium is often incorrect when displayed under the shared title. An example is Vogue magazine. Not all of our libraries limit circulation on the current issue, nor do they all keep two years of issues. But because the SHR for the library that is alphabetically first has those limitations in the shared public note and retention designation, it shows under…
11 votes -
Display the MARC 773 field and index 773 $t
We have over 23,000 bibliographic records in our legacy ILS that represent articles within serials and we continue to add new ones on a regular basis. We use the MARC 773 field to list the parent serial title, volume and issue number, and pages of the article, but this field does not display in Vega or Leap, making these articles impossible to find (unless a staff member views the MARC in Polaris.)
Also, 773 subfield $t is not indexed so these records are not findable by a title search for the parent journal, only by searching the title and/or author…
3 votes -
Unified Authentication: OAuth (or SAML) Integration for staff Vega Discover access
Our library currently leverages OAuth 2.0 with Google as our identity provider to authenticate librarians into Polaris LEAP. We would like to request the ability to integrate this same OAuth 2.0 (or SAML)/Google authentication workflow with Vega Discover. Since we understand that Vega Discover utilizes Keycloak on the backend, this integration should be technically feasible through Keycloak's identity brokering capabilities, where Keycloak would act as an intermediary between Vega Discover and our Google identity provider. This would allow our librarians to use their existing Google credentials to access Vega Discover, maintaining consistency across our library systems while providing centralized user…
2 votes -
Placing a hold reflects holdability settings on item record
We would like Vega Discover to take into account the holdability of an item when placing a hold based on the settings that are applied on the item records (we use Polaris). This would include the various options in the "hold limited to" section that can be configured at the bottom of an item record in Leap (see picture for more information).
If this is done, the holds logic would skip an edition if all its copies were not holdable for the patron, even if they were available, and would not return the error it is resulting in now. It…
10 votes -
Turn off ability to cancel ILLs from holds list
In the course of trying to solve how an ILL had been cancelled before it even arrived, we learned that patrons have the ability to cancel them from their accounts. It would be nice to be able to customize the cancel button to not function for certain collections/ types of materials. ILLs take so much time and effort to obtain and process and it is frustrating that patrons can easily/accidentally cancel this.
4 votes -
please add Blackstone as a supported eVendor.
Supported eResource vendors have added visibility in Vega Discover. We have integrated bibliographic eResources with that vendor and would like to maximize the visibility of this vendor.
2 votes -
please add PressReader as a supported vendor
Supported eResource vendors have added visibility in Vega Discover. We have integrated eResources with that vendor and would like to maximize the visibility of this vendor.
6 votes -
Hero Carousels
For Hero Carousels, when you add a showcase there's no option to display the showcase title. Having just the image doesn't give context for patrons to know what that leads them to. We would like the option to include the showcase title with each picture.
7 votes -
Search by item barcode
Searching by item barcode was available in our previous discovery layer and staff found it very beneficial.
10 votes -
Support for multiple ADs for Vega User Management
Self-hosted Polaris Customers who have Vega Discover can allow a connection between their Polaris installation and Vega Discover for the purpose of using existing AD staff accounts for Vega user management. Currently, only one AD is supported. In consortia, there may be multiple ADs (e.g., in our environment, we have four).
We'd like there to be support for multiple ADs so consortia can benefit from the convenience of using AD credentials to access Vega Discover.
11 votes -
Allow for non-MARC language codes
For a better customer experience with our Chinese titles, we created some new non-MARC language codes in Sierra to separate out the Simplified and Traditional Chinese titles. Vega does not support non-MARC language codes, so it shows as codes instead of the label in Vega.
We'd like to see Vega be able to pull codes from the LMS along with their label.
4 votes
- Don't see your idea?