Simon Read
My feedback
42 results found
-
2 votes
An error occurred while saving the comment
Simon Read
supported this idea
·
-
64 votes
Simon Read
supported this idea
·
-
8 votes
Simon Read
supported this idea
·
-
213 votes
An error occurred while saving the comment
Simon Read
commented
Thanks Moshe,
I think that would work for our use case, which is fairly limited in scope (Just a small number of locations that have pickups that are the exception to the rule). Not sure if limiting to 3 groups will be too narrow for some sites that have more complex pickup exceptions than we do
Simon Read
supported this idea
·
An error occurred while saving the comment
Simon Read
commented
We're in a similar position where we wish to enable specific locations in a Library to be able to be picked up at a Library (or libraries) that we define but the current rules just aren't granular enough for us to be able to do that. We've looked at the relationship rules but they define what happens at the Library rather than location level.
Like Aya we'd like to have another pickup location rule added in the TOU that would allow us to specific which libraries could be selected for pickup
-
6 votes
Simon Read
shared this idea
·
-
21 votes
Simon Read
supported this idea
·
-
441 votes
Simon Read
supported this idea
·
-
58 votes
Simon Read
supported this idea
·
-
4 votes
Simon Read
supported this idea
·
-
49 votes
Simon Read
supported this idea
·
-
97 votes
Simon Read
supported this idea
·
-
22 votes
An error occurred while saving the comment
Simon Read
commented
Hi Luigi, No, I haven't posted to CERV - you are welcome to do so. There was some discussion with the Esploro Product Managers last year about making improvements to the indexing of Esploro records in Primo that would, I think, solve the problem we have here. They were in discussions with the Primo Product managers about implementing some changes but there were no timeframes around it, so adding a CERV request would help indicate the continuing need for improvements in this area
Simon Read
shared this idea
·
-
68 votes
Simon Read
supported this idea
·
-
109 votes
Simon Read
supported this idea
·
-
107 votes
Simon Read
supported this idea
·
-
57 votes
Simon Read
supported this idea
·
-
38 votes
Simon Read
supported this idea
·
-
60 votes
An error occurred while saving the comment
Simon Read
commented
I support the addition of view specific configuration. It is particularly important that titles that appear on the person entity card are actually accessible via that view. At the moment we can see electronic titles on the person entity card that users can't access because those titles aren't activated for that view (in our case we're using available for groups to control view level access). We can't realistically use the person entity functionality until this has been resolved
Simon Read
supported this idea
·
-
19 votes
Simon Read
shared this idea
·
-
96 votes
Simon Read
supported this idea
·
Totally agree. We have had to hide this field so as not to confuse patrons. At the very lest there should be a configuration option for sites to choose whether to present users with a pickup location or not