Settings and activity
341 results found
-
5 votes
Shawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
supported this idea
·
-
4 votesShawn P. Farrell
supported this idea
·
-
2 votesShawn P. Farrell
supported this idea
·
-
6 votesShawn P. Farrell
supported this idea
·
An error occurred while saving the comment -
26 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment Shawn P. Farrell
commented
2027 marks the 15th anniversary of Sierra! How exciting would it be to mark the milestone with some celebratory new skins? In addition to the above, perhaps a crystal colored skin in line with 15th anniversaries?
Shawn P. Farrell
supported this idea
·
Shawn P. Farrell
shared this idea
·
-
4 votes
An error occurred while saving the comment Shawn P. Farrell
commented
Here's an example. Happens enough to be a bit of a hassle.
Shawn P. Farrell
shared this idea
·
-
4 votesShawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
supported this idea
·
-
5 votes
An error occurred while saving the comment Shawn P. Farrell
commented
@Kathryn noted & voted!
Shawn P. Farrell
shared this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
An error occurred while saving the comment Shawn P. Farrell
commented
Yes, they're copy specific holds, but they're placed for a reason. We'd like to see this as well. Remain on the list until they're filled or marked missing or some other status that would prevent fulfillment.
-
5 votesShawn P. Farrell
shared this idea
·
-
2 votesShawn P. Farrell
shared this idea
·
An error occurred while saving the comment Shawn P. Farrell
commented
Our Acquisitions staff does not use List Price when ordering, & is hoping that Estimated Price could be modifiable via Rapid Update. At the moment, this would help them modify 200+ order records, which they now have to do manually.
-
2 votesShawn P. Farrell
shared this idea
·
-
3 votesShawn P. Farrell
shared this idea
·
-
16 votesShawn P. Farrell
supported this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
supported this idea
·
-
5 votes
An error occurred while saving the comment Shawn P. Farrell
commented
CHPL would appreciate this as well, especially if the point at which old notices are purged can be determined by the library. Because of the volume of notices we send out & how long we've been using LX Starter, our performance metrics for configured notice jobs take a while to populate. Retrieving log data can also take quite a bit of time.
Optimally, we'd like to be able to set the same retention limit for logs on all notice types, whether they're e-mail, phone, or print.
Shawn P. Farrell
supported this idea
·
-
13 votesShawn P. Farrell
supported this idea
·
This is an intriguing idea for sure! Not only would it make searching through common names more effective out of the gate, it would standardize & make more intuitive the search options across functions.
Like most libraries, we allow for the searching of additional indexes in Checkout (Circulation Desk) mode, but a preset limit would expedite finding the record you're after. Searching by Name + Street or Name + Home Library could potentially be very helpful.
Though to be fair, I was surprised we don't have nearly the number of patrons named Smith, John in our database that I might have thought!