Alma
Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
678 results found
-
Include MMS ID in Excel output from Manage Sets Results pages
The MMS ID is essential information when dealing with spreadsheets of records, and yet it is missing from Excel output of lists of sets and search results. Please include the MMS ID in all output Excel spreadsheets of Repository records.
33 votes -
Add Proxy Users to "Users" subject area
Adding Proxy Users to analytics would allow us to search for users that are proxies to another user, and also users that have proxies for themselves.
This information isn't completely available within Alma, and it seems like an oversight that it's also unavailable in Analytics.
63 votesThe User Details subject area has been enhanced with the following improvements:
You can now create reports with fields from different folders as is possible in other subject areas.
The User Measures dimension was added, which contains measure fields relating to the number of users.
The following fields were added under the User Details dimension:
Cataloger Level – the cataloger level of the patron
Patron Letters Opt In – the letters for which the patron has opted in
Patron Letters Opt Out – the letters for which the patron has opted out
Has Role Other Than Patron – indicates if the patron has a role other than Patron
Has Role Other Than Patron and Instructor – indicates if the patron has a role other than Patron and Instructor
Is Blocked – indicates if the patron is blocked
The Proxy For dimension was added, which contains fields that indicate for whom… -
Find and Manage Users by User Group
Add the ability to find and manage users and create user-based sets based on User Group.
499 votesAs part of the Alma July 2020 release “Advanced Search for Users” feature, new search options have been added for searching user records. The option to run advanced searches has also been added. One of the many new search indexes is the User Group.
Search results may be saved as a users set.
For more information, see https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes_Included_Material/2020_RN_07_Main#Advanced_Search_for_Users
-
LC call number search and index
LC call number should support indexing all valid MARC fields as mentioned in http://www.loc.gov/marc/bibliographic/bd050.html and not only 050$a or local 090$a fields.
It should index also $b and than enable to search for full LC call number, of course this should reflects also in the holdings level (i.e. $h,$i etc)25 votesThe LC call number search index is now enhanced and includes more fields.
For more information, please refer to the Alma May release notes and online help.
-
Less Scan In operations
Despite the fact that Work Orders (WO) can be linked to a Circulation Desk, working with Work Order Departments and Circulation Desks in a same session can still cause many Scan In operations for the staff.
There might be indeed several scan-in operations before an item becomes finally indicated as available (on shelf) on Alma/Primo. This is particularly the case for smaller libraries or library branches when most of the operations are made in the front office, at the library desk itself.
We would like to reduce the number of scan-in operations so that for example at the end of…
70 votesAs part of the November release you can now set relation rules between libraries so that transit for reshelving will not be required between certain libraries, departments, and circulation desks. This reduces redundant work effort by not automatically putting items in transit for reshelving when the libraries are close to each other. This does not affect other transit types, such as hold shelf, work order, and processing.
A new link, Reshelve Without Transit Rules, is now available in the Fulfillment configuration menu. By default, a rule is created with no input parameter and an output parameter set to false to maintain current functionality.for more information see: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/020Library?mt-draft=true#Configuring_Reshelve_Without_Transit_Rules
-
Make 245 $p, $n, $s, $k, $f, $g part of "Title" criteria in Analytics &/or make them available as separate criteria
Currently, the Analytics criteria “Bibliographic Details – Title” returns the 245 $a and $b in combination. This leaves out a good portion of the information needed to distinguish titles in series or parts from one another. Works of classical music are another area which require information from the other subfields for clarity. In the case of many archival materials, the current results leave the title field completely blank or skip many records, as there is no data recorded in either 245 $a or 245 $b. (Please see the attached file for examples.)
In order to use these reports in any…167 votesThe Title (Complete) field was added to the shared Bibliographic Details dimension in every subject area in which it appears. It includes the information from MARC field 245, subfields $p, $n, $s, $k, $f, $g.
For more information see:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes -
receiving note - sizable
It would be terrific if we could resize the Receiving Note field when we are editing, just as you can with the POL note fields.
5 votes -
"Save and dismiss" button in "Manage EDI Tasks"
In the "Manage EDI Tasks", when using the "Update Expected Receipt Date" action, updating the date and clicking on "Save", it would be great the concerned line would automatically be removed from the list without having additionally to click on "Dismiss". A new function button like "Save and dismiss" would be helpful.
263 votes -
Change physical items job -- adding notes
The Change physical items job allows you to add Internal notes 1-3 or Statistical notes 1-3 by REPLACING any notes that already exist in that field, but not by adding the note IN ADDITION TO already existing text. This option needs to be added. Also, the current job allows you to skip records that already contain notes in your selected field but a "successful" run does not report out which records were SKIPPED as a result.
402 votes -
Include "Quantity for Pricing" in EDI for ebook POLs
It is currently not possible to send the correct quantity to the vendor via EDI. When EDI is sent for POLs of type "Electronic book - one time", the quantity field in the EDI is always 1, even if the Alma POL has a different Quantity for Pricing value. We often need to order multiple "copies" (i.e. sets of access credits or user licences) for an ebook, but only want 1 portfolio on Alma.
Please consider using the "quantity for pricing" in EDI for electronic - one time POLs.225 votesThe PO Line information is enhanced when sent with EDIs.
For more information, please refer to the Alma May release notes and online help.
-
Add Transit Information to Analytics
In order to track materials traveling between libraries, it would be extremely helpful to have transit information such as Transit Date, Transit From, and Transit To included in analytics.
8 votes -
Add Holding Modification Data to Analytics
It would be really great if you would add Holding Creation Date, Holding Modification Date, and Holding Modified By to analytics.
9 votesthe following fields exist in the “Holding Details” folder of the “Physical Items” subject area and therefore this ideas exchange has been completed:
“Holdings Record Creation Date”
“Holdings Record Modification Date”
“Holdings Record Modified By” -
Better correspondence between number of items ordered and Quantity for pricing.
As a Purchasing operator, I would like a better correspondence between the number of items ordered and the "Quantity for pricing" in the PO line summary.
When we are ordering more than one item of a physical title, we have to add the extra items in the Quick add field, and then have to update the Quantity for pricing field manually. We see that Purchasing operators tend to forget to update both fields. The result is that the number of items that we intended to order, not always corresponds with the number of items that is supplied by our vendors.…
245 votesCompleted as part of Alma February release Enhancements to the PO Line Pricing Section
For more information please see Release Notes
-
Display OCLC Number in Brief Results Lists
In the brief results display in Alma, the Record Number field is extremely useful in all types of technical services workflows. However, at times a non-OCLC number is displayed in the Record Number field, even though the record contains an OCLC number. The most useful control number from any record is, if present, the OCLC record number.
It appears that the current behavior is for Alma to display the value from the last 035$a subfield in the record. Can we configure this field, or can Ex Libris modify this field, so that if an OCLC number is present in any…
76 votesThe All titles, Physical titles, Electronic titles, and Digital titles repository search results now display all 035 $a content.
For more information please August Release Notes:
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes?mon=201908BASE -
Ability to log 2 sets of dates on electronic portfolios - Perpetual and Current Access
Most publisher packages only allow perpetual access for subscribed years, post-cancellation, but they give you access to a much larger set of dates during your active subscription. For example, many of our Wiley titles have access back to 1997, but our perpetual access does not begin until 2003. If we could select both perpetual and current access for a title, and have the ability to log both sets of dates, that would be very helpful. Ideally, we would like to use this to do a broad overlap analysis between our print and perpetual electronic holdings.
112 votesIdea was implemented as part of August release.
When a resource has both current and perpetual access, there is now an available access type combination option (Current and perpetual) for electronic collections and portfolios. This option is available in the Electronic Collection Editor and the Electronic Portfolio Editor, and supported by the portfolio loader and Excel exports using the extended export option. -
Ability to change Purchase Type / Order Line Type after an item has been ordered
When ordering an item a purchase type must be selected to create a POL. It appears as Order Line Type in the POL after the item has been ordered. It would be nice to have the ability to change the Order Line Type within the POL instead of canceling an order and having to create a new one from scratch. An example would be having the ability of changing the order type Print Book - Standing Order to the order type Print Journal - Subscription within an item's POL.
190 votes -
Authorities ordered according to the correct order rather than subfield alphabetical
Alma organizes the name/title results in MARC subfield order, rather than RDA/MARC order.
For example, instead of this expected order:
700 |a Rolvaag, O. E.,|q(Ole Edvart),|d1876-1931.|tWorks.|kSelections.|f1936you instead get the subfields in alphabetical order, like so:
700 |aRolvaag, O. E.,|d1876-1931,|f1936|kSelections.|q(Ole Edvart).|tWorks.Please fix this so subfields are ordered properly which will allow the new browse feature to work properly.
4 votesSubfields of MARC 21, UNIMARC, and CNMARC authority record fields used to create display, sorting, and search elements, were extracted in alphabetical order rather than in cataloging order. This was fixed. As a result, additional bibliographic record elements were created. For MARC 21 display elements, this includes 5XX note fields excluding 59X, 520 and 505; 59X local note fields and 69X local subjects. For MARC 21 search elements: this includes 59X local notes, 9XX local fields, 09X local call numbers, and 69X local subjects. For UNIMARC and CNMARC, display elements include 69X local subjects. Search elements include 69X Other Classification Number, 3XX notes, 9XX local fields, and 69X local subjects.
-
More PO line options for Create Purchase Request
Purchase Requests functionality is great idea (ACQUISITIONS --> Purchase Requests); unfortunately, the usefulness of this new feature is limited because it appears that it can only be used with certain PO Line Types (Print Book - One Time, Electronic Book - One Time; Print Journal - Subscription; Electronic Journal - Subscription). We cannot use the purchase requests workflow for physical media, for example, because there is no option for a requester to choose a "Citation type" that would map to a PO Line Type of Visual Material. We cannot use the purchase requests workflow for streaming media, because this is…
27 votesAs of March release you can select a material type for purchase requests in Alma. The field previously called Requested Format has been renamed to Material Type and moved to the Resource Information section.
The accompanying modifications for the Primo Purchase Request Form will be added in an upcoming release.
For more information please see Alma Release Notes at https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes -
Replace copyright statement for digital representations
The copyright statement should display at the front of the digital representation for the patron before they download the contents. The copyright statement is not visible unless the patron clicks on the Copyright Symbol on top right corner of the page of the digital representation. To make the copyright statements meaningful, it should appear before the representation.
18 votes -
Maybe Search indexes is not updated? I want 773 $$t indexed as Title.
I often check this Help site https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_%28English%29/Resource_Management/020Using_the_Repository_Search/Search_Indexes
to check how things are indexed. It looks like 773 $t is indexed as Content related data. Shouldn't it be indexed as Title? I suspect that it is indexed as title, but the information in Search indexes is not correct? Search indexes is very useful, and I would appreciate it updated.1 vote
- Don't see your idea?