395 results found
-
Sort the Limit By Collection setting list alphabetically
Content Scoping -> Limit Content -> Limit By Collection list should list the collections alphabetically. Not sure how they are currently sorted, but it is currently difficult to select these in a consortium setting.
3 votes -
Announcements - Permission for Content Admin
We would like to see Announcements (Premium option), which is currently under Settings > Page Customizations be part of the permissions for the Content Admin role. The person who handles our promotions for our homepage(s) would like to handle the announcements, as well (this is how it works for our website), but that would require making her a Site Admin, which is not appropriate - don't want her to be able to access all of the settings, nor does she want to see all of that. As Content Admin, she just sees the drop down for homepage(s) and goes from…
2 votes -
Delete multiple showcases
Option to delete multiple showcases at once as an admin.
Currently it is one at a time and if you are at the bottom of a large list, the update puts you at the top after removing a single showcase.6 votes -
Alphabetize Format Filter
The format filter in Discover is currently sorted by number of items in the filter (i.e. largest amount is Books, smallest is Book+Cassette). This is NOT intuitive for searching - if I want to apply a format filter, I'm going to look for the name of it alphabetically, not by how many items I think might be available in that format. With the addition of custom TOMs, this is even more important as we are adding more formats available to filter by.
6 votes -
Customization of "Duration of temporary status (hours)" per branch
In the current configuration, libraries can only apply the “Duration of temporary status (hours)” setting as a global value across all items. We would like to request the ability to configure this setting at the branch level.
Circulation varies significantly across our branches. Some experience high turnover while others have low activity. As a result, the time required for staff to reshelve materials differs from branch to branch. Allowing this setting to be adjusted individually for each location would provide patrons more accuracy of where they can find items in the branch.8 votes -
Vega - Payments made via Polaris API / PayPal Payflow Pro integration should show up as Credit Card, rather than Debit Card
clarivate arbitrarily selected a PaymentMethodID of "13 - Debit Card" for all Vega Discover Fine/Fees payments. This makes all payments show up under the Debit Card category within Polaris Reports (e.g. "Financial Transaction by Payment Type"). The PaymentMethodID should actually be "12 - Credit Card," as all of these Vega transactions are actually processed via PayPal as credit card, regardless of whether the card is actually a debit card or a credit card.
3 votesNote that: PayPal does not deliver the payment card type used by the end user payee. Whatever is implemented here potentially in the future must be an all or nothing toggle for all payments received from paypal.
-
Geolocation authentication for Vega's patron registration
We would like to see Vega's patron registration to include geolocation authentication so we can limit patron registration to only those residing in NYS, and potentially just our service area.
6 votes -
Online Patron Registration in Discover
It would be helpful for our consortia if the new patron registration form in Vega Discover had some additional options that could be added:
-Patron preference for receiving notices (Email, Mail, TXT Message)
-Text Messaging Phone (Phone 1)
-Password [choose password here rather than link to do so later]ADD the Opt in to text messages statement
- My preference for receiving library notices:
- Phone number for TXT messages and Carrier
- Logon Information – Password
- Opt in to text messages statement
- My preference for receiving library notices:
- Phone number for TXT messages and Carrier
-…6 votes -
Option to hide or remove Message field in Vega Discover for Polaris libraries
Our consortium is in the process of implementing Vega Discover. We currently use Polaris.
We recently noticed there is a blank Message field under each title’s Edition information in Vega (screenshot attached) and asked our implementation team about it.
Turns out, it only applies to Sierra libraries and there is no corresponding field for it in Polaris. Currently, we are not able to hide or remove it.
Since this field does not apply for Polaris libraries, and would always be blank, we would very much like the option to hide it from view or remove it completely.
8 votes -
Allow Vega Showcases Created From Saved Search to Appear on Record Pages
Reopening an idea that was closed for lack of activity, but is still important to us:
Currently, only Vega showcases that are created from a set of bookmarks can be displayed on Record Pages, which is NOT an option for showcases from saved searches. In some cases, we prefer using saved searches vs. bookmarks, as they are easier to maintain. We still want to see those showcases show up on record pages. The documentation (https://documentation.iii.com/vega/admin/admin/Create_Showcase.htm) doesn't call out this limitation in the "To create a showcase from a saved search" section. We found out the hard way, after…
6 votesThis work was not done previously because it was deemed to be too much of a performance hog. In order to deliver a Saved Search showcase or 4 on a Full Title View we would need to run said searches and load the results within the view each time it was loaded.
We can see if there are new options to achieve this enhancement now if chosen by the MEEP group.
-
display patron message (fixed field in Sierra patron record)
Sierra has a fixed field in the patron record that can be used by Sierra libraries in many different ways. It is not a free text field. It has a controlled vocabulary.
This field has the ability to block Patron activity via APIs and SIP2.
Libraries may use this field to request that library users have address checks, promote services, ILL updates, or other standardized messages rather than manually editing individual messages.If libraries use this field to block circulation, it would be helpful for this to display in the patron account in the catalogue. These messages could alert patrons…
4 votes -
display patron message (non-marc field in Sierra)
Sierra has a non-MARC field in the patron record that is used by staff to communicate relevant, timely information to a patron within the context of their catalogue activity. This is a free text field. It used to display in Encore.
Why this is helpful for library?
1) we developed workflows that include this field
2) Messages could alert patrons to issues such as an expired card, account restrictions, required updates, or other actions they need to take.Why is this helpful for the library user?
1) Messages can be targeted to a specific patron rather than displayed as a…4 votes -
Add SmartPAY from Comprise fine payment integration to Vega Discover
Patrons should be able to pay their fines and fees through Comprise SmartPAY like they were able to with Polaris PowerPAC. Since we've implemented Vega Discover we had to have a link to our own SmartPAY portal where the patron is prompted to login with their barcode and password again in order to fetch their fines/fees prior to payment. These are extra steps that shouldn't really be required.
9 votes -
Vega Home Page: Store Images for re-use in admin
We often re-use images for our Vega home page, specifically the Hero, and there is no way to quickly access those images - you are forced to upload what would be considered "evergreen" content again and again. For example, maybe we opt to promote/use one of our Hero images every 3 months for a particular service. When you go to promote that service again, you have to try and find the artwork you stored locally again, upload. It seems like this could be store somewhere, maybe make it optional when you upload to keep/store the file (so you could say…
6 votes -
Vega - PayPal Payflow Pro integration: Comment1 Field
PayPal confirms that Vega currently passes the contents of the "Comments1" and "Comments2" field to PayPal's PayFlow Pro during the process of authorizing transactions, tokenizing the transaction, etc. The contents of the "Comments1" field are currently reflected as simply the letter "f". We would like this Comments field updated to read "Fines/Fees" so that it's more descriptive, please. The Comments2 field is fine; it contains the patron's Library Card #.
3 votes -
Include date returned in borrowing/reading history
Sierra (6.4+) has the ability to store a return date and to provide that date via Sierra API. Discover does not support this date. Please add it to Discover so patrons can see their return dates. This would help with finding or remembering specific resources, plus patrons like seeing information about their histories and library habits.
10 votes -
Don't disable the hold button if there are no holdable items but there are open orders
Right now, if a non-holdable item comes in first (fairly common occurrence) and holdable items are on order, customers are not allowed to place holds.
13 votes -
Use bookmark button in header instead of sidebar for lists and saved searches
The bookmark icons in the header and the new right-hand sidebar both toggle the user's lists open and closed. On mobile devices, this sidebar takes up a lot of screen space, much of it not necessary. To reduce redundancy and improve the mobile experience, I would prefer no sidebar and instead having a widget that appears and disappears with the header button only. The widget could have tabs within for getting to saved searches as well as showcases if applicable.
7 votes -
Integrate Ebsco Discovery Service or Explora into Vega searches
Our state has recently signed a contract with Ebsco to provide all libraries in the state with access to their Explora database system. It would be wonderful if this could be integrated into Vega searching. I have two academic libraries that would really like to see integration with EDS (Ebsco Discovery Service) as well.
5 votes -
Account Portal Showcase based on History
The 'Your Next Read' showcase in the customer Account Portal should pull from the customer's History (reading and/or checkout) instead of pulling from Bookmarks and saved searches. Not too many of our customers use either bookmarks or saved searches, but most opt in for saving reading history. Pulling from history would provide a much better service to customers IMHO.
9 votes
- Don't see your idea?