AdminAsaf Kline
(VP Library Solutions, Ex Libris)
My feedback
5 results found
-
66 votes
Dear community,
We are sorry to inform you that we have found an issue with this development, and as we want to be sure all features are high quality, we are delaying its release until we can test and make sure it is up to standard.
We will update when we have a final release date.
Regards,
Alma team
An error occurred while saving the comment -
30 votes
An error occurred while saving the comment In order to be certain about this idea and what is meant by permalink, could you provide examples and more details on what you mean by permalink
Alma Product Management
-
22 votes
An error occurred while saving the comment Improvements have been made in the November 2016 Release to the way in which the Back browser button functions while working in Alma. If a Back button exists on the Alma page, the Back browser button simulates the Back button in Alma. If a Cancel button exists on the Alma page, the Back browser button simulates the Cancel button. Otherwise, the Back browser button goes to the last Alma page in the browser’s history.
-
55 votes
An error occurred while saving the comment The suggested idea will be considered as part of the UX project initiative
-
53 votes
After reviewing this idea, Alma Product Management has decided to update our development plans to include this suggested change. Thank you for your contribution
An error occurred while saving the comment We are having difficulties understanding the workflows and scenarios where there are fields missing. There are many existing options for exporting data in bulk from Alma (e.g. Run an export Job, export a list from the Tools option, etc...). Please provide more specific details so we can progress with our analysis
In the May 2020 Release the following capability was introduced
UTF-8 Special Character Handling
Alma offers a new method of handling UTF-8 special characters (with diacritics). UTF-8 special characters may be represented in both the composed or decomposed version of the character in bibliographic or authority records. Now, you have the option to configure your system with normalize on save always to save the composed version of special characters. This may be especially useful to implement to avoid the use case where multiple records are changed due to their conversion to composed representation. Such records are marked for preferred-term correction (PTC) and cause heading updates (the only difference is the composed/decomposed nature of a special character).
See here for more details:
https://knowledge.exlibrisgroup.com/@api/deki/files/84227/UTF-8_Special_Character_Handling_in_Alma.docx?revision=1