Karen Benko
My feedback
15 results found
-
77 votesKaren Benko supported this idea ·
-
544 votes
Dear all,
I believe we now understand the requirement better: To be able to paste a block of text in MARC 21 format, and have Alma parse it and populate the MARC tags, indicators and subfields accordingly.
This is a larger development, but we hope to be able to add a solution for it to our future roadmap.
An error occurred while saving the comment Karen Benko supported this idea · -
344 votes
Dear all, we are currently working on a design concept for a new form interface option for cataloging, which will make it easier to navigate long fields and subfields - we will take this request into account as part of this design. See our "Form Editing for MARC 21 Bibliographic Records" roadmap plans for more information: https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2024-2025)/Metadata_Management#Form_Editing_for_MARC_21_Bibliographic_Records
Karen Benko supported this idea · -
315 votesKaren Benko supported this idea ·
-
36 votesKaren Benko supported this idea ·
-
962 votes
Dear all,
We are adding physical item templates to our roadmap.
It will be possible to save an item as a template, and then use this template to pre-populate new items when they are created.
The system will remember the user's template selection, so they won't be required to specify the template each time they create an item (only when the item differs from the previous item created from a template).
Karen Benko supported this idea · -
167 votesKaren Benko supported this idea ·
-
42 votes
An error occurred while saving the comment Karen Benko commentedUsers interested in this idea might want to look at https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/32882308-allow-suppression-of-items-from-discovery-in-primo. That idea is now planned, after voting in NERS 2021
-
267 votesKaren Benko supported this idea ·
-
85 votesKaren Benko supported this idea ·
-
114 votes
Dear community,
Thanks for raising this idea.
The conceptual solution which is currently being evaluated, is to allow the user to choose/control the desired timeout session period from 4 options (in minutes) - 60 (current, and default) , 90, 120 or 150.
This reflects a potential increase of up to 250% in session timeout period.
Please let us know if you have any comments regarding the suggested solution.
Thanks,
Uri Beladev
Platform Product Management team
An error occurred while saving the comment Karen Benko commentedManu Schwendener, There are not two settings. Unchangeable aspects of the software are not "settings." We want Alma to stay open longer.
Text from the first of the two links at the idea you linked to on 5 March at 3:08: "Answer
Session timeout is set to 60 minutes, at which time the session will expire and staff are required to sign in again. This is not configurable."An error occurred while saving the comment Karen Benko commentedI wish it could be longer! Encounter one sticky question, or get pulled away from your desk, and you have to go through the whole rigamarole again!
Karen Benko supported this idea · -
145 votesKaren Benko supported this idea ·
-
78 votesKaren Benko shared this idea ·
-
41 votesKaren Benko supported this idea ·
-
144 votes
We will add the ability to use search criteria as pre defined search scope.
Design will be shared with the Alma UX Focus Group as part of Alma Working GroupKaren Benko supported this idea ·
Both management responses miss the point. People need to paste fields into a record open in edit mode in the MDE. See Lynne Billington's comment from July 11, 2018.