Settings and activity
310 results found
-
1 vote
Shawn P. Farrell
shared this idea
·
-
3 votes
Shawn P. Farrell
supported this idea
·
-
3 votes
Shawn P. Farrell
supported this idea
·
-
2 votes
Shawn P. Farrell
supported this idea
·
-
11 votes
Shawn P. Farrell
supported this idea
·
-
1 vote
Shawn P. Farrell
shared this idea
·
-
5 votes
Shawn P. Farrell
supported this idea
·
-
10 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Shawn P. Farrell
supported this idea
·
An error occurred while saving the comment -
7 votes
An error occurred while saving the comment
Shawn P. Farrell
commented
This would be incredibly useful. So many bad actors these days, it's like watching an episode of Full House.
Shawn P. Farrell
supported this idea
·
-
4 votes
Shawn P. Farrell
supported this idea
·
-
5 votes
Shawn P. Farrell
supported this idea
·
-
4 votes
Shawn P. Farrell
supported this idea
·
-
2 votes
Shawn P. Farrell
shared this idea
·
-
6 votes
An error occurred while saving the comment
Shawn P. Farrell
commented
As Ray notes, this can happen again, as it did outside of our recent upgrade, only yesterday, with a batch of failed notices appearing at random. Not only did these (& those in the example in the original post) fail to send, there's no identifying data attached to the reporting.
Shawn P. Farrell
shared this idea
·
-
8 votes
Shawn P. Farrell
supported this idea
·
-
4 votes
Shawn P. Farrell
supported this idea
·
-
48 votes
An error occurred while saving the comment
Shawn P. Farrell
commented
We would like to see this, but as part of its implementation, we would like to be able to limit PTYPEs that can submit suggestions. For example, our Internet registrant PTYPE shouldn't be allowed to make any suggestions, until they validate their card for a more permanent PTYPE.
We would also like a limit on the number of suggestions that can be made by a given user in a specified period of time (for example, a max of 10 per month).
Lastly, if the suggestion is approved, an option should allow that a hold can be placed on the item for the requesting patron.
-
12 votes
Shawn P. Farrell
supported this idea
·
-
9 votes
Shawn P. Farrell
supported this idea
·
-
5 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
We would very much like to see this.
Shawn P. Farrell
supported this idea
·
On a related note, I would like to see the timestamp of the last checkin added, as it also appears for the last check out date field.
Use Case: While I'm sure there are any number of reasons to display this data, at the the moment, we have a security-related matter at one of our branches where the timing of a transaction would be useful in addressing it.