Mathias Kratzer
My feedback
11 results found
-
103 votesMathias Kratzer supported this idea ·
An error occurred while saving the comment -
320 votes
Thank you for this idea.
We are currently examining it and will update once we have more details.
An error occurred while saving the comment Mathias Kratzer commentedDear Alice,
Since we also agreed that the issues perfectly described by you are rather bugs in the sense of lacking basic functionality than some problems that suggest an enhancement subject to community voting we submitted a meanwhile already escalated case (reference for Primo Product Management: #07188268) for them. As of Sep 24, 2024 Ex Libris told us:
"Unfortunately, after additional examination and prioritization, we have decided that a fix for this issue will not be part of our current development work plan."
In response to that we pointed our support analyst to both Manuela's earlier and this idea and hopefully made clear that the community obviously feels an urgent need for "a fix for this issue".Hope this helps
MathiasMathias Kratzer supported this idea · -
16 votesMathias Kratzer shared this idea ·
-
19 votesMathias Kratzer shared this idea ·
-
9 votesMathias Kratzer shared this idea ·
-
8 votesMathias Kratzer shared this idea ·
-
4 votesMathias Kratzer shared this idea ·
-
21 votes
An error occurred while saving the comment Mathias Kratzer commentedDear Sean,
Thanks for this idea. I stumbled upon the sam lack of functionality but could imagine that local identifiers like the item id are only just the most obvious examples of what is needed to build certain links but is not included in the Alma Context Object ("CTO"). That's why I created https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/45442483-make-all-pnx-elements-referable-in-template-urls a few minutes ago. If you or anyone who has voted for your idea agree that it is covered by mine, please consider to vote for it.
Best regards
Mathias -
153 votesMathias Kratzer supported this idea ·
-
96 votesMathias Kratzer supported this idea ·
-
134 votes
Dear community,
Thank you for sharing this idea. I order to better understand it, can you please give specific examples where the performance is not sufficient?
This would help us to better understand the root cause and see what can be done.
Thanks,
Tamar Fuches
Alma team
Mathias Kratzer supported this idea ·
Great idea - but as far as I can see nothing specific to EZProxy. We are using HAN (Hidden Automatic Navigator) because we even need to emulate different access IPs for different groups of patrons (or more precisely: different types of subscriptions) and Ex Libris already added a way to control this in the proxy settings on the service level of any given collection. However, for the "link in record" cases all these setting are currently ignored by Primo :-(
So, please make Primo VE aware of the collection that provided the record in question and let it evaluate the proxy settings for that collection instead of applying a globally defined proxy setting. And please do not implement this enhancement for a specific type of proxy only but for all supported ones!