James Hammons
My feedback
11 results found
-
9 votesJames Hammons supported this idea ·
-
5 votes
An error occurred while saving the comment -
67 votesAdminTamar Ganor (Admin, Ex Libris) responded
Hello,
This idea has been closed by mistake, I apologize for the inconvenience.
It will be reviewed and addressed according to the regular workflow of content requests.
My sincere apologies.
Kind regards,
Tamar Ganor
Content Product Manager
James Hammons supported this idea · -
28 votes
Moving this back to no status and adding a note to clarify. For Summon over Alma customers, we can schedule delivery of reports via email. But currently OBI statistics from the Summon UI are not covered under these reports.
This idea covers reports and usage outside of Alma.
James Hammons supported this idea · -
5 votesAdminAmy Pemble (Admin, Ex Libris) responded
Returning this to the Ideas "pool" for voting by the community.
James Hammons supported this idea · -
269 votes
Hi,
Of course ! We will add a job that will be able to run on a set of user records and purge them, using standard validations (such as no existing loans, fees).
Thanks !
An error occurred while saving the comment James Hammons commentedTo add my own use case to the mix (and sense of urgency): We need the granularity afforded by sets to give us more control over which records are purged. Our accounting office requires us to produce information about fines/fees for a set number of years after they've closed, and the standard checks for active fines for purging a user isn't good enough.
-
85 votesJames Hammons supported this idea ·
-
173 votesJames Hammons supported this idea ·
-
178 votes
An error occurred while saving the comment James Hammons commentedWhy not just add the privilege to the Catalog Manager role?
James Hammons supported this idea · -
9 votesJames Hammons supported this idea ·
-
46 votesJames Hammons supported this idea ·
We dealt with this a few years ago by customizing names of languages in the Translations table in the Summon Admin Console. For example, we were able to change:
ไทย
to
Thai (ไทย)
This affects both the menu used to select the UI language and the appearance of the language names in the Language facet. You should be able to do this for any language supported with a Translations table. Have you looked into this?