AdminLili Daie
(Product Manager, Ex Libris)
My feedback
11 results found
-
417 votes
An error occurred while saving the comment -
287 votes
An error occurred while saving the comment Dear all, thank you for posting this idea and for your helpful comments - we are in the process of assessing the complexity of this request, and will update the idea accordingly.
-
230 votes
An error occurred while saving the comment Dear all,
Thank you for posting this idea and for the helpful comments. We are reviewing this idea, and would like to make sure we fully understand the request.
Since the item description impacts fulfillment functionality, such as requests - changing an item's description unlinks it from any existing patron requests, which can lead to their cancellation.
Our concern is that bulk changes of item descriptions on a set of items could be risky, potentially leading to unintentional mass deletion of patron requests. I would therefore like to make sure that this is the desired functionality (meaning if item descriptions are inaccurate, the requests attached to them are also inaccurate, and request cancellation in this scenario would not cause any data issues).
Thanks! -
221 votes
We have added it to our plan. We will share more details as part of the design phase
An error occurred while saving the comment Dear all,
I'd like to update on some further improvements to Browse Shelf Listing planned for May 24 release, for MARC21 and KORMARC call number fields:
1. Automatic population of the "Call Number" field in the browse will be extended to not only $a, but also $b when cursor is in the following bibliographic fields: 050, 055, 060, 070, 080, 082, 084.
2. Automatic population of the "Call Number" field in the browse will be populated by $h and $i when cursor is in bibliographic field 852.In addition, following the semi-annual indexing, data from $b of the following fields will be part to the following call number search indexes in the repository search:
LC call number: 050, 055, 090
Universal Decimal Class Number: 080
Dewey Decimal Class Number: 082, 092
Other Classification Number: 084An error occurred while saving the comment Dear all,
I'd like to update on some of the requested improvements that were added to Browse Shelf Listing:
1. Ability to view more results surrounding the exact search request - this was done as part of the August 23 release and is available in production.
2. Making the drop-down menu values sticky - this was done as part of the November 23 release and is now available in Sandbox environments. Alma remembers the settings the user last set for "Call Number Level", "Call Number Type", "Library", and "Location" - the settings are updated only if the operator manually changes the selection in one of the drop-downs before triggering the browse action (note that the remembered settings are used only when opening a blank Browse Shelf Listing form, and not when opening a pre-populated form from a call number field or the Item Editor).An error occurred while saving the comment Dear all, I’d like to update you on the status of this idea:
The following requests from the original idea description, as well as some mentioned in many comments, are on our roadmap, and will be gradually developed and released in the coming releases:
1. Ability to view more results surrounding the exact search request.
2. Making the drop-down menu values sticky.
3. Adding Author/1xx information.For some of these requests, support was already added:
1. Ability to actually be able to see the entire call number in the call number field – the call number field is now longer, to show the entire call number.
2. Removal of the need to click into the call number field to search the shelf listing – the browse shelf listing and browse bib headings are available in the menu without having to navigate into a specific field. When browsing shelf listing from a bib record, if you do click on a specific call number field (e.g. 050, 082), the browse value is automatically populated from it. We are looking into the possibility of also auto-populating values from local call number fields (09X).We would also appreciate if you could please share some more details on the following requests, to help us understand the need:
1. Ability to view shelf-list in Primo with one click.
2. Ability to search the shelf list by call number that ignores sub-field labels.
Thanks! -
63 votes
Hi. 1. Are you stating that you want a new “Resource Type”?
2. The definitions of the resource types are explained in the table titled “Rules Used to Create the Resource Type Field – MARC 21/KORMARC and UNIMARC” at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/Searching_in_Alma#The_Resource_Type_Field
3. Do you want a new row in this table which would be as follows?
Archival materials. LDR pos. 8 = a
4. The table is read top to bottom and as soon as match is found it stops. Where in the table would you like this new row to appear?
5. How come the title of this suggestion states “LDR pos. 8 = a” but the comment from Feb. 2 also has “LDR pos. 6 = p”? We do not think “LDR pos. 6 = p” is a good idea. That is used for “mixed materials”. On the other hand “LDR pos. 8…An error occurred while saving the comment Dear all,
I'm looking at the details of this idea, and would like to make sure I understand the request here. You are asking for a new resource type that is effectively archival mixed materials, but will be called "Archival" (without detailing mixed materials) - is that correct?
Today, LDR pos. 6 = p is used for the "mixed materials" resource type, defined as:
LDR pos. 6 = p AND LDR pos. 7 = c.
Making this change would mean you will exclude Archival from the mixed materials resource type, meaning:
LDR pos. 6 = p AND LDR pos. 7 = c AND LDR pos. 8 = a -> Archival
LDR pos. 6 = p AND LDR pos. 7 = c AND LDR pos. 8 = !a -> Mixed materialsIn addition, LDR pos. 8 will be ignored for all other types of records, so archival information will not be reflected in the search for them - for example:
LDR pos. 06 = a AND LDR pos. 7 = c AND pos. 8 = a -> collection
LDR pos. 06 = e AND LDR pos. 7 = m,s AND pos. 8 = a -> map
etc.Am I understanding the requirement correctly? Would it perhaps be clearer to call the new resource type "Archival mixed materials"?
Thanks,
Lili -
151 votes
An error occurred while saving the comment Dear all,
As changing the location of an item can impact work orders (not all work order departments can handle all items) - the alert is required and removing it could adversely impact libraries.
We did, however, identify an issue with this alert, which caused it to be shown also for changes that could not impact work order requests (Material Type, Item Policy, Description) - this was fixed in the March 24 release. Following the fix, this alert will no longer be displayed for changes that can't impact work order requests. -
144 votes
An error occurred while saving the comment Dear all,
The CloudApp "Item updater by Excel" now allows uploading an Excel spreadsheet in order to bulk edit item information: https://developers.exlibrisgroup.com/appcenter/item-updater-by-excel/
For a detailed explanation on working with this app to bulk exit items, see: https://developers.exlibrisgroup.com/blog/how-to-activate-and-use-the-item-updater-by-excel-cloud-app/ -
21 votes
An error occurred while saving the comment Dear all,
Please note that the physical item APIs have been updated to include pattern_type and linking_number since this idea was created, and are available to you for retrieving and updating these fields. -
350 votes
An error occurred while saving the comment Dear all,
I would like to update that the "Undo Remove, Cut, Paste Field" (Ctrl+Shift+Z) action was released to the Sandbox environments as part of the quarterly August release.
It will be available on Production with the August Release Update, scheduled for the weekend of August 13.
We are also continuing our work to improve the browser's undo capability (Ctrl+Z) for undoing changes to the content of fields, and hope to introduce enhancements to this during 2024.An error occurred while saving the comment We would like to update that we are working on a new action to undo removing, cutting and pasting fields (Ctrl+Shift+Z), which will allow restoring data lost by removing or cutting a field without having to go back to a previous version of the record.
We've also noted the issues mentioned with the browser's undo functionality (Ctrl+Z) when used for undoing changes to the content of fields, and are in the process of analyzing this to see if further improvements can be introduced down the line. -
21 votes
An error occurred while saving the comment As part of NERS #7948, Add “Not contains” or “Not equals” to Alma Titles and Inventory Search Indexes Where "Contains" or "Equals" Currently Exist, we will be adding not operators as the comment below suggests.
Please note that, since Alma offers combined enriched bibliographic and inventory search index, and it is possible to search titles by inventory information, the behavior of queries which retrieve bibliographic titles using inventory indexes with NOT operators will be as follows: When searching with a lower-level index "not contains" or "not equals", the search will retrieve all results where one or more inventory entities match the query. For example, searching for titles with location "not equals" library A will retrieve a title with items in both library B and library A, as there is an item that matched the search query.
This behavior was agreed upon with the NERS representatives. -
510 votes
We are investigating the options for enhancing the job reports as part of a general enhancement to the jobs UX, which will then allow gradually deploying report enhancements to the different jobs in Alma.
An error occurred while saving the comment Thank you for posting this idea, and for the informative comments! We've noticed several different jobs mentioned in the comments - could we please ask you for a prioritized list of job reports that you would like improved?
Dear all, thank you for posting this idea and for your helpful comments - we are in the process of assessing the complexity of this request, and will update the idea accordingly.