Mathias Kratzer
My feedback
14 results found
-
93 votesMathias Kratzer
supported this idea
·
-
25 votes
An error occurred while saving the comment -
275 votes
Hello,
We’re currently analyzing the various scenarios related to this request, and believe we can implement a solution that will preserve moved titles within collections, rather than removing them.
This solution will be integrated into our collection addition and update workflows. When title lists are picked up by our automated cycle, any title with a URL that differs from the collection’s parser will be assigned a Bulk::BULKdoi parser to accommodate the change.
Developing a separate process to dynamically match and override collection parsers with dedicated ones isn’t feasible at this time, as the complexity and volume of potential matches would require a significantly more advanced logic framework than we currently support.
I will update this idea once I have a clear timeline.
Kind regards,
Tamar Ganor
Content Product Manager
Mathias Kratzer
shared this idea
·
-
65 votes
An error occurred while saving the comment Mathias Kratzer
commented
Dear esteemed Colleague,
If you have just come across this idea and are considering voting for it ... please, don't do it! I have submitted a more generally understandable version of it here: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/49908636-allow-for-almost-arbitrary-conditions-in-general-e which will hopefully attract more votes.
Thanks and best wishes
MathiasMathias Kratzer
shared this idea
·
An error occurred while saving the comment Mathias Kratzer
commented
For SFX a "plugin threshold" is known as an almost arbitrary complex condition (evaluated by any sort of locally developed script code returning 1=true or 0=false) on the contextual relevancy of a certain service. The Alma link resolver should not stand behind and be able to employ any third party web service for the evaluation of conditions too complex to be stated by means of its out-of-the-box types of thresholds.
-
42 votes
An error occurred while saving the comment Mathias Kratzer
commented
Just found idea https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/19479604-alma-emails-provide-matching-plain-text-alternati which is not only closely related but, unfortunately, already closed for a reason that I do not understand.
Mathias Kratzer
shared this idea
·
-
51 votesMathias Kratzer
supported this idea
·
-
19 votesMathias Kratzer
supported this idea
·
-
115 votesMathias Kratzer
supported this idea
·
An error occurred while saving the comment Mathias Kratzer
commented
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!
-
383 votes
Hi all,
This idea was reviewed as part of planning 2026 roadmap, as the solution yet is not clear and we are still examining the possible solutions.
This kind of sorting is more complex as it involves free text values and it requires different sorting method than what currently being used.
This is currently not included in the 2026 roadmap.
We will continue evaluate the possible solutions.
An error occurred while saving the comment Mathias Kratzer
commented
Dear 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
·
-
27 votesMathias Kratzer
shared this idea
·
-
10 votesMathias Kratzer
shared this idea
·
-
4 votesMathias Kratzer
shared this idea
·
-
21 votes
An error occurred while saving the comment Mathias Kratzer
commented
Dear 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 -
159 votesMathias Kratzer
supported this idea
·
Yeah, I agree. The automatic update of electronic holdings from a specific vendor is a content related idea because it would take a correpsonding autoholdings collection. If Cambridge advertise them being able to support the workflow that should be a low hanging fruit for Ex Libris and my institution would love to see CUP integrated in the autoholdings service but I cannot afford to cast my few votes on functional ideas on this one, sorry!