Dennis Müller
My feedback
7 results found
-
2 votes
An error occurred while saving the comment
Dennis Müller
supported this idea
·
-
51 votes
An error occurred while saving the comment
Dennis Müller
commented
I absolutely agree. This just adds to the questionable choices in implementing e-mail in Alma (e.g. wonky or lack of DKIM/SPF, forcefully attaching the institution logo to messages).
-
158 votes
An error occurred while saving the comment
Dennis Müller
commented
Thanks for bringing this to our attention. At leat I wasn't aware that the current implementation was so poor. It seems to me this could and should be fixed timely using the mentioned tried and tested standards available.
Dennis Müller
supported this idea
·
-
143 votes
Dennis Müller
supported this idea
·
-
2 votes
Dennis Müller
shared this idea
·
-
33 votes
An error occurred while saving the comment
Dennis Müller
commented
There are API calls for configuration items, but they behave somewhat erratically, e.g. if you request the list of mapping tables, the returned list is incomplete - meaning you some items can only be requested if you know the name, effectively putting the burden of finding each and every config item on the customer. (see also case 06611916)
I could think of two solutions: Either implementing a new API call that returns all the configuration. Or Ex Libris could provide customers with a maintened little program (e.g. a python script) that does the heavy lifting requesting all configuration items from the API as it currently behaves.
Dennis Müller
supported this idea
·
-
1 vote
Dennis Müller
shared this idea
·
We strongly support this idea. In fact, I'd rather view this as a bug: With lots of objects in Alma (titles, holdings, items, job processes, ...) there is an ID shown in the details page. I see no rationale for this not being the case with licenses.