Simon Read
My feedback
45 results found
-
56 votes
An error occurred while saving the comment
Simon Read
supported this idea
·
-
19 votes
Simon Read
shared this idea
·
-
96 votes
Simon Read
supported this idea
·
-
14 votes
Simon Read
shared this idea
·
-
68 votes
Simon Read
supported this idea
·
-
44 votes
Simon Read
supported this idea
·
-
2 votes
Simon Read
shared this idea
·
-
342 votes
Simon Read
supported this idea
·
-
321 votes
Simon Read
supported this idea
·
-
182 votes
Hi,
This is to update that this issue is still not planned to be developed in the current road map. We will continue to evaluate it for a future release.
Therefore we are keeping this under "Under review" status.
Best regards,
Yael.
Simon Read
supported this idea
·
-
99 votes
Simon Read
supported this idea
·
-
60 votes
Simon Read
supported this idea
·
-
19 votes
Simon Read
supported this idea
·
-
69 votes
Simon Read
supported this idea
·
-
47 votes
Thank you again for sharing your idea and for the thoughtful input you've provided. When we first discussed it, I was optimistic about exploring it further,
While I had hoped to prioritize this enhancement, it hasn’t gained the traction we typically look for to move forward. As a result, it’s unlikely to be implemented in the foreseeable future. That said, your feedback remains valuable, and I’ll continue to keep it in mind as our roadmap evolves.
An error occurred while saving the comment
Simon Read
commented
Hi Dana,
Thanks for the update. I've tested the hourly booking functionality and as far as I can see the end date and time does not automatically populate the request form in either Alma or Primo. I can't find specific mention of the auto population in the release notes either - just mention of the ability to change to hourly bookings rather than bookings by minute. How are we meant to activate the functionality?
Simon Read
shared this idea
·
-
39 votes
Simon Read
shared this idea
·
-
36 votes
Simon Read
supported this idea
·
-
44 votes
Simon Read
supported this idea
·
-
112 votes
Simon Read
supported this idea
·
-
56 votes
Simon Read
shared this idea
·
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