Settings and activity
23 results found
-
6 votes
Martin Boyce
supported this idea
·
-
3 votes
An error occurred while saving the comment -
5 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
·
-
13 votesMartin Boyce
supported this idea
·
-
35 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.
-
21 votes
An error occurred while saving the comment Martin Boyce
commented
This idea appears to be related to another one:
Ability to copy showcases and parent list/search from one staff patron to anotherAn error occurred while saving the comment Martin Boyce
commented
I agree this would be very useful. We have showcases created by staff in particular roles. When staff move around, and new people take that role it would be good to be able to transfer the 'ownership' of that showcase to a different user account. We also have examples where we would like more than one staff member (i.e. user account) to be able to add and remove titles from a particular showcase, e.g. job-sharing arrangements.
I realize it is possible to have multiple staff members login to a single Vega admin account, but it's nice to be able to maintain individual Vega admin accounts so we still know who is authorized to access and edit showcases. Maybe there's a need for an additional role for Showcase editors that can add and remove titles from any user's lists? Or perhaps a tweak to the permissions for the Showcase Admin role that enables this?
Martin Boyce
supported this idea
·
-
14 votesMartin Boyce
supported this idea
·
-
8 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.
-
84 votesMartin Boyce
supported this idea
·
-
68 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
·
-
26 votesMartin Boyce
supported this idea
·
-
115 votesMartin Boyce
supported this idea
·
-
7 votesMartin Boyce
supported this idea
·
-
12 votes
An error occurred while saving the comment Martin Boyce
commented
Along with colors and logos, typography is one of the main brand identifiers for most organisations.
Martin Boyce
supported this idea
·
-
12 votesMartin Boyce
supported this idea
·
-
23 votesMartin Boyce
supported this idea
·
-
11 votesMartin Boyce
supported this idea
·
-
26 votesMartin Boyce
supported this idea
·
-
79 votesMartin Boyce
supported this idea
·
I think as far as the labels on the login form, that is controlled by the html in your login app config files (ipsso.html, etc.) - in Sierra at least. As for the Reading History, would it be possible to use the translation file to achieve the changes required?