Settings and activity
20 results found
-
18 votes
An error occurred while saving the comment -
18 votes
An error occurred while saving the comment 
Martin Boyce
commented
I understand the issue and use case for this idea, however, I have to show some sympathy and support for the Vega team in relation to this. I don't think it is as simple as just showing the call number in the main display. What if there are different call numbers for items of the same format at different locations? How would Vega decide which call number to display? I guess the call number for each location would have to be shown alongside the location name on search result cards and on work detail pages.
-
23 votesMartin Boyce
supported this idea
·
-
26 votes
Selected for the Sierra 6.7 release by MEEP enhancement process
An error occurred while saving the comment Martin Boyce
commented
We use Web Access Management in Sierra to provide remote access to some of our digital resources for our members. This requires us to have a wildcard SSL certificate. It would be great if organisations like LetsEncrypt and DigiCert could provide Wildcard SSL certificates via their auto renewal infrastructure.
-
30 votesMartin Boyce
supported this idea
·
-
10 votesMartin Boyce
supported this idea
·
-
11 votes
An error occurred while saving the comment Martin Boyce
commented
At the very least, a showcase created from a review file in Sierra should maintain the sort order from the Review File itself. At present, the titles from the review file appear to populate the showcase in a random order. There is some sorting possible in the review file itself, so maintaining the sort order from the review file would give some options.
For example, we created a review file of the most popular fiction/non-fiction titles based on loan counts, with the most popular title in position 1, and so on. When we created a showcase from this review file the order is not maintained.
If sorting options are developed within the showcase settings in Vega Discover, I imagine it would be difficult to have the original list order as an option after the fact. Thus, I think that starting with the order of the original list would be a logical default.
Martin Boyce
supported this idea
·
-
14 votesMartin Boyce
supported this idea
·
-
38 votesMartin Boyce
supported this idea
·
An error occurred while saving the comment Martin Boyce
commented
If there was an option to choose a stat group for Vega renewals/transactions, we would also use it. It would be good to be able to differentiate transactions between platforms. It also seems like an easy thing to implement - adding one extra key/value pair to the payload for API requests. Would need some UI in Vega admin to allow libraries to set the stat group variable, but not too hard I suspect.
-
17 votesMartin Boyce
supported this idea
·
-
11 votes
The product team will review this idea for consideration for a future release.
Martin Boyce
shared this idea
·
-
16 votes
An error occurred while saving the comment Martin Boyce
commented
Would it be possible to redesign the Resources section of the person page to use the grid view layout - so that users can see the formats held and availability? Instead of the supplied screenshot it would look more like the attached view.
-
92 votesMartin Boyce
supported this idea
·
-
82 votes
An error occurred while saving the comment Martin Boyce
commented
Our patrons are fans of SMS notifications, so we would appreciate this enhancement. Am I correct in thinking that I recently heard a suggestion (maybe in a strategic partner meeting?) that Innovative was looking at revamping the whole SMS notifications as part of LX Starter? No mention of this in the Roadmap yet though.
Martin Boyce
supported this idea
·
-
9 votesMartin Boyce
supported this idea
·
-
12 votesMartin Boyce
supported this idea
·
-
88 votesMartin Boyce
supported this idea
·
-
60 votesMartin Boyce
supported this idea
·
-
47 votesMartin Boyce
supported this idea
·
-
123 votesMartin Boyce
supported this idea
·
I'm happy with the way timeouts currently work. Apart from patrons not logging out, the timeout forces the catalog to revert to the home screen, which is my preference. If there is no patron logged in, what is the argument for leaving Vega on the last user's search results versus resetting it to the homepage?