195 results found
-
Facet Navigation and Display Improvements
Improve Facet display by better utilizing space in Refinement Panel and utilizing word wrapping when necessary to display full facet value.
In All Facet view display data in a single column of scrollable data and utilize word wrapping when necessary to display full facet value.
For Limited Value facets such has: format, location, collection, age group, language, donor; allow the full facet content to display in the refine panel when expanded and in all facet view by adding scroll.
For larger value facets such as concepts, persons, publishers; enable a Load XX more <facet> button in the All Facet View…
97 votes -
Display More Note (5XX) Fields
Note fields include useful information that is meant to be displayed to users. This information helps users decide if the resource described is relevant to their needs.
A subtitle that appears only on the cover of a book might only appear in a 500 note. A note might specify that a resource is a reprint of an earlier publication or give the original title of a translation, just to name a few examples.
Most notes are repeatable, so all instances of these MARC fields should display when there are multiple. Currently, only the first 505 (Contents note) displays.
MARC 500…
56 votes -
Ability to assign or group target ages into a specific age group facet w/o manipulating records
We'd like to have ability to change the mapping of the Audn: Target audience (BKS, COM, REC, SCO, VIS: 008/22; 006/05) to a specific age group facet. For example, many catalog records have a blank assigned for target audience. Search results will include these records but they fall out when the "general" facet is selected. We do not want to manipulate these records to "g" when [blank] is a valid option. Also, we'd like the ability to group the target audience a (preschool), b (primary), and c (pre-adolescent) under j (juvenile) without manipulating the catalog records in our database.
26 votes -
Increase Access Controls for Vega Discovery
Please add the ability for libraries to add their own permission groups with specific level of controls set by administrators, or build more granular permission groups. Currently, administration level access is required to do many of the features explained to us for showcase approves and Vega Homepage displays.
We do not want to give all of our librarians "admin" level and "staff" is not high enough to make our day to day work possible.
74 votes -
Sort search results by Author or Title
Our patrons are asking for the ability to sort search results by Author or by Title, in addition to Date and Relevancy.
52 votes -
Statistical Information for Showcases
Provide statistics for how many times a showcase has been selected by Vega users during a specific time period.
19 votes -
Navigation between consortia member instances of Discover
In a consortia, especially one with many member libraries that share patrons, it is important for users to be able to move from the main/parent domain instance of Discover to one of the individual library sites and also to be able to navigate between member library sites. This is functionality currently available in the Polaris PAC and heavily used.
23 votes -
Separate physical and digital checkouts and holds in MyBookshelf
Users would like to see physical materials listed separately from digital materials in Checkouts and Holds lists, or the ability to filter your list to see only physical or only digital checkouts/holds.
14 votes -
Where are we??? - we own stuff VEGA!!!
In a large consortia the locations with smaller collections are not showing up. Only 40 sites show. This means the large libraries with more content are always displayed, and the big sites always get top billing. Our little librarys deserve the same exposure (maybe more). In the location facet all libraries should be listed if the result set includes content from their collections. Locations should be listed alphabetically and not by the number of items in the set.
18 votes -
Display the Full Title (245) including Statement of Responsibility
Displaying the full title (245) including the statement of responsibility (subfield ǂc) will help users identify additional contributors associated with a title.
There are also sometimes additional titles within this part of the field. Subfield ǂc includes all information following the first slash.
Examples:
The point less taken / ǂc Geoffrey Young. Some trees / Lucas Reiner.
Shock shop. ǂn Volume one, ǂp Something in the woods, in the dark / ǂc written by Cullen Bunn ; art by Danny Luckert ; letters by Nate Piekos of Blambot. Familiars / written by Cullen Bunn ; art by Leila Leiz ;…
37 votes -
Use existing create lists / record sets from ILS for Showcases
Sierra Libraries can access Create Lists for creating Showcases.
Polaris Libraries can access Record Sets for creating Showcases.47 votes -
Scheduling Vega Homepage Layouts
Vega Homepage Layouts are an excellent way to communicate with our patrons based on spotlighting showcases, new collections, as well as upcoming programs.
Although this takes a lot of manual intervention whenever a change needs to be made. We'd love the ability to schedule Vega Homepage layouts for future months. Example: Saving Monthly Vega Showcases based on our libraries future focused campaigns (Summer reading, poetry month, heritage months, etc.).
54 votes -
Support indexing added title (subfield $t in 7xx, 8xx added entry or 6xx subject fields)
Support indexing subfield $t in the 7XX (added entry) and 6xx
Currently author title entries in the 700 subfield t are not searchable
RDA uses 700's in cases where there are multiple works together25 votes -
Request to Increase Character Limit in Announcements
The current 250-character limit in Vega Discover's announcement feature significantly restricts our ability to convey essential, detailed information in a single message. This limitation is particularly challenging when addressing complex situations that impact multiple services. Our public relations team is compelled to create multiple, shortened versions of the same announcement to fit this constraint, leading to an inefficient communication process that does not align with the capabilities of modern CMS platforms.
Increasing the character limit to at least 500 characters is a necessary enhancement. It will enable us to deliver comprehensive and clear messages without the need for creating multiple…
9 votes -
Video game roll up improvements
Improve the roll up logic for video games
33 votes -
Add 028 to Indexed Identifiers
This field is used for publisher’s/distributor’s numbers for video recordings, sound recordings (including audiobooks), and printed music. These numbers are important access points for these materials.
All 028 fields should be indexed, regardless of indicators.
29 votes -
Include all contributors in expanded detail display
Include additional contributors in the expanded details display for the individual manifestations (MARC 700), this is especially important when multiple versions are rolled up together.
Currently, all added contributors for all versions are displayed at the bottom of the page of the roll-up and it is hard to find and identify specific translations or audio-book narrators. This also results in a work with multiple authors only having the first one recognized29 votes -
Report incorrect images link in Vega
It would be nice to have a link in Vega Discover to report incorrect images and have a status note once its been reported so multiple reports are not being submitted for same image. Contact information seems to change often and can get a bit frustrating to get resolved.
13 votes -
Add options to exclude content via facet selection
The current functionality of Vega Discovery allows patrons to filter their search results by selecting one or more facets from the left-hand panel. However, there is no option to exclude results. For example, a patron who is looking for books on history may want to exclude ebooks or audiobooks from the results.
This enhancement request proposes to add an option to exclude content via facet selection and or other means. This would allow patrons to refine their search results more effectively and find the most relevant resources for their needs.
Adding an option to exclude content via facet selection would…
27 votes -
Failed Extraction Alert in Vega Admin
Add an alert feature to Vega Admin that will notify select users when an extraction fails. Currently, when an extraction fails in Vega Admin, there is no way to know unless you manually check the logs. This can be time-consuming and frustrating. By adding an alert feature, users will be notified immediately or on desired intervals when an extraction fails, allowing the user to take action quickly and minimize issues as a result of the failure.
35 votes
- Don't see your idea?