Settings and activity
323 results found
-
10 votes
Shawn P. Farrell
supported this idea
·
-
2 votes
An error occurred while saving the comment Shawn P. Farrell
shared this idea
·
-
2 votes
An error occurred while saving the comment Shawn P. Farrell
commented
While working with the newly available Reference Log function, I noticed that when the mode is launched & you begin recording reference transactions, the date is displayed as MM-DD-YYYY.
However, when exporting transactions, it's formatted as DD-MM-YYYY. This is a little confusing.
We would like to see this made configurable at the local library level, so the staff member's experience is consistent throughout their workflow.
Shawn P. Farrell
shared this idea
·
-
23 votesShawn P. Farrell
shared this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
14 votesShawn P. Farrell
supported this idea
·
-
15 votesShawn P. Farrell
supported this idea
·
-
11 votesShawn P. Farrell
supported this idea
·
-
14 votesShawn P. Farrell
shared this idea
·
-
9 votesShawn P. Farrell
supported this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
-
22 votesShawn P. Farrell
supported this idea
·
-
20 votesShawn P. Farrell
supported this idea
·
-
3 votesShawn P. Farrell
supported this idea
·
-
16 votesShawn P. Farrell
supported this idea
·
-
8 votesShawn P. Farrell
supported this idea
·
An error occurred while saving the comment Shawn P. Farrell
commented
As a library that floats most of our collection, we too often see this problem & without this nuance, these items are very difficult to look for in the reports we produce. We'd love to see this addressed.
-
11 votesShawn P. Farrell
supported this idea
·
An error occurred while saving the comment Shawn P. Farrell
commented
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!
-
37 votesShawn P. Farrell
shared this idea
·
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?
An error occurred while saving the comment Shawn P. Farrell
commented
Can we get some new skins to choose from for the SDA/Sierra Web?
There are currently two: Half Dome & Glacier Point.
We currently use colors to differentiate between our Production instance of Sierra & our Test version. However, we also have a Training database.
Variety is the spice of life! How about a rose-colored skin, a powder blue, or a "Millennium Green" as an homage to the Millennium database?
-
12 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
·
An error occurred while saving the comment Shawn P. Farrell
commented
As I'd done in similar scenarios countless times before, yesterday, I was in the process of modifying the activeholds on my account in Sierra to change them to a newly created pickup location.
There were several that needed changing, so I selected 'All.' However, rather than make a batch change of the half dozen or so that needed updating, Sierra cycles you through each item individually, forcing multiple arguably unnecessary clicks, when the expected & more intuitive outcome in this scenario would be to indicate the desired change once & see it changed for all selected records.
-
15 votesShawn P. Farrell
supported this idea
·
While working with the newly available Reference Log function, I noticed that when the mode is launched & you begin recording reference transactions, the date is displayed as MM-DD-YYYY.
However, when exporting transactions, it's formatted as DD-MM-YYYY. This is a little confusing.
We would like to see this made configurable at the local library level, so the staff member's experience is consistent throughout their workflow.