Bronwen Blatchford
My feedback
16 results found
-
3 votes
-
13 votes
-
18 votesBronwen Blatchford supported this idea ·
-
96 votesBronwen Blatchford supported this idea ·
-
9 votesBronwen Blatchford supported this idea ·
-
182 votesBronwen Blatchford supported this idea ·
-
61 votes
An error occurred while saving the comment Bronwen Blatchford supported this idea · -
70 votesBronwen Blatchford shared this idea ·
-
59 votesBronwen Blatchford supported this idea ·
-
343 votesBronwen Blatchford supported this idea ·
-
33 votesBronwen Blatchford supported this idea ·
-
20 votesBronwen Blatchford shared this idea ·
-
35 votesBronwen Blatchford supported this idea ·
-
165 votes
An error occurred while saving the comment Bronwen Blatchford commentedAgree wholeheartedly with this suggestion; we have been getting complaints from users that they didn't know an item was recalled. Emails get buried/treated as spam/hived off into 'other' rather than focused in Outlook web. We also have the problem that, if a user picks an item up from the hold shelf and there are other requests on it, they don't get the recall email at all (as we don't shorten due dates).
With auto-renewals in place, anything that can be done to highlight recalled items is welcomed. We are looking at re-purposing the loans.brief.2 field as per Toby's excellent suggestion.
Help from Ex Libris here would also be very warmly welcomed!
Bronwen Blatchford supported this idea · -
79 votesBronwen Blatchford supported this idea ·
-
105 votes
An error occurred while saving the comment Bronwen Blatchford commentedWe have just come up against this problem. I think the advice from Ex Libris is the same now as two years ago. We have two campuses and over 30 libraries and it seems like overkill to have to set up a separate circulation desk for self-service for each.
When you purge a user, the 'Users' table in Analytics moves the PID to the last name field (if the keep statistics option is selected in the 'Delete User Policy' config). Can't this be done for the Fulfillment table too?
Bronwen Blatchford supported this idea ·
This is causing us significant problems, since going live with Primo VE. The old Resource Sharing form didn't have a default selection. We're now getting about half of our requests going to the wrong library, as our largest library is the 2nd in the list alphabetically. The hold form doesn't have a default selection so we need the Resource Sharing form to match this. Our Resource Sharing staff are having to contact all the users who select the first library in the list to check if they really did want to select that library. This has led to a lot of extra, unnecessary work.