420 results found
-
Use first name first or nickname for patron account portal
In the account portal, use the initial of the account's first name instead of last name and show the name in the format "First Last"--except when there is a nickname, in which case use the nickname. The circled letters seem designed to differentiate between linked accounts, so I can foresee families in which everyone is labelled with the same letter and you can mostly only see the last name.
(This would only apply when there are multiple accounts. I agree with this idea when there are no linked accounts: https://ideas.iii.com/forums/951766-vega-discover/suggestions/50968153-suppress-the-patron-name-when-account-linking-is-n)
Also, use the first name, or nickname if there…
7 votes -
disable renew button
In the patron record checkouts it would be useful if the renew button would disappear completely if the item out has existing holds on it (like it does in the powerpac now). Why give the illusion you can renew something to then just be denied?
70 votes -
Promote Relevance Button
In Encore there was a button for staff to manually promote the relevance of certain titles to appear at the top of search results. We'd like to see something similar implemented in Vega to ensure titles that we expect patrons to want to see first are listed first. Example below, of Ulysses by James Joyce being fourth in the results for a basic search of "ulysses"
6 votes -
import saved searches from PowerPAC as well as saved lists
During implementation, saved searches should be imported as well as saved lists when a library requests it. We recently went through Vega implementation and patrons are very disappointed that their saved searches aren't in the Account Portal. While they can recreate the searches, this discourages Vega adoption by a large number of our patrons. They would rather say within the PowerPAC and continue running their searches there.
6 votes -
offer hyperlink to eResource site
We have had feedback from customers and staff that they would like the option to pass through to the eResource vendor from the resource record (via the 856). There is a "details" > "Note (electronic)" field that could be hyperlink.
Right now many libraries have their 856 $z or $y in the Note (Hyperlink) field that says something like "Click here..." or "Click link" - but this field is not hyperlinked.
12 votes -
Increase length of title and author in Showcases
The amount of characters for the title and author names is limited (exact number seems to vary) and they are therefore not being completely displayed in Showcases. Can this be increased so in more cases the full title and name is displayed?
14 votes -
add magazine issue to My Bookshelf checkouts and holds
Magazine issues do not display in the My Bookshelf checkouts and holds. If someone checks out many issues over a period of a couple of days or weeks, they have no idea which issue may be overdue or coming due.
16 votes -
thumbnail update
Now that the thumbnail updates based on which tab of the roll-up is selected, if the thumbnail does not exist for that item type, it should display the image that does exist. For example, if the thumbnail exists for the book, but not for the audiobook, when you click on the audiobook tab, the thumbnail should display the book rather than displaying a generic blank image.
10 votes -
Provide a public API Endpoint or structured Data Export for Showcases
Implement a new function or API endpoint that allows libraries to easily retrieve the structured data (metadata, ID/ISBN, image URL, link) for any active "Showcase". The data should be presented in a standard, machine-readable format like JSON or XML.
While Vega Discover allows us to embed the visual display of a Showcase on other websites, this does not give us the underlying data. This data could be used to include Showcases i mobile apps and integrate with other systems and external analytics tools. They could also be used by patrons to easily keep track of new additions to "permanent" showcases.
11 votes -
Display subfield c from 520 in summary
Currently, the summary from the 520 field is displaying on the full resource card and dynamically updating by format, which is great. However, the subfield c is hidden, so anytime there is a subfield c present, there are simply two dashes at the end of the summary, suggesting that there might be something missing or cut off (which there is, in fact). Can the subfield c please be displayed along with the summary?
13 votes -
Option to hide "Request any edition" button
We would like there to be an option to hide the request any edition button, so that patrons would always have to pick a specific edition. We do very little weeding of older editions and have a large collection of early printed books which can be mixed in with regular open access copies, so depending on the holds ratio patrons could get served up a much older edition of a book than is useful for them if they use the more prominent "Request any edition" button.
4 votes -
Consider $c field when matching visual media for roll-up
Vega BibFrame should consider the 260$c field when matching for roll-up in visual media as often it's the determining indicator between two different versions of film. For example, see "The Italian Job" ... both are Hollywood, CA, Paramount pictures but in different years (1969 and 2003) but because the matchin doesn't consider the $c field, they roll up with each other even though they're very different films.
9 votes -
Showcase Ordered Alphabetically includes 'The'
When a showcase is opened and it is sorted by title 'The' is not excluded. For example, The Gatsby would be under T when we think it should be under G.
26 votes -
Improved Blocked Account Display
Currently, if a patron is blocked from borrowing due to too many fines and/or long overdue items they can still place hold requests. This causes issues when the patron comes into the library expecting to be able to check out their held items and is met with a block.
To make it clear to the patron, can there be a pop-up or banner displayed on Discover explaining this so patrons are made aware in the catalog before they place a hold.
11 votes -
on shelf at location.multi : bib locations should be mapped to bib records
We have 39 branches. Our magazines are fixed to one location. In Encore, the bib location mapped to the bib record so that library users knew where the magazines were located. Now, we just see the message: "on shelf at location.multi". This behaviour is not what customers want. They want to see the specific branch locations.
I have attached an example below.
2 votes -
add On Order facet
Please work with libraries to determine a way to add an "on order" facet. We ingest all bibliographic records before we receive the physical copies. Library users can also place holds on these "on order" bibliographic records. Library users want to distinguish between "recently received" by the library and "recently ordered" by the library.
62 votesMEEP 2026 Winner.
-
add 505$t should be included in title search
The 505$t subfield should be included in the title search.
Here is an example of a situation where that is valuable. If a library user is searching for Kurt Vonnegut's "Cat's Cradle" and uses the Title search, they will only find the actual work "Cat's Cradle". However, this book is also contained in short story compilations. They will miss this short story compilation which may better suit their reading needs.
24 votes -
Ability to use facets to refine/filter Showcase results
It would be helpful for patrons to be able to refine Showcase results by selecting facets as in the advanced search (e.g., to filter by availability, location, format, etc.).
24 votes -
Enable Syndetics tags in Vega
The tags are available in Encore and is a much used resource.
8 votes -
Create a data sync process or 'integrity check' for Vega/Polaris
We have had issues recently where items have been transferred to new bib. records and disappeared from Vega as a result and others where items were deleted and disappeared as expected, but then never reappeared once they were undeleted.
We would like to have a database sync process that can be run which compares the Vega database against the ILS to confirm that everything is in sync - basically a cross-system data integrity check or verification process between systems that would let us know if there was anything that was out of sync so we could investigate and correct it.
…
12 votes
- Don't see your idea?