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.
231 results found
-
Change Repository Search "Contains" to drop-down to enable searching "Contains Phrase", "Starts With", and "Equals"
In the repository search simple search, the only search operator you can use when searching available indexes is contains (e.g., FIND all titles WHERE title CONTAINS ____.
We would like to request that the CONTAINS operator be turned into an advanced-style dropdown menu to enable searches like this:
FIND all titles WHERE title CONTAINS PHRASE ____
FIND all titles WHERE title STARTS WITH ____
FIND all titles WHERE title EQUALS _____In many cases, an advanced search is not required, it is simply the contains operator that needs to be modified, and performing an advanced search just to modify the…
136 votesThis idea was discussed with the Alam UX focused working group and it was agree it is lower priority. We will consider this request in future changes we might do in the search.
-
Improve Booleian searching in repository by including 'not' option
Currently there is no option to use a 'not' function in a repository search, there is only 'and' & 'or'. The ability to exclude certain records from a search is vital to enable correct records to be isolated for editing/updating. Not having the 'not' option makes it very difficult to narrow down results.
102 votesIn addition to our Product Manager Moshe Shechter’s comments on this idea of a few months back, we would like to add the following:
Alma’s search indexes have been designed and built to provide a whole new set of possibilities for searching for inventory based on the full set of bibliographic details and indexes. As a result of this combined enriched bibliographic and inventory search index, certain queries which retrieve the bibliographic titles but also use inventory indexes, can lead to non-intuitive results when used in conjunction with NOT operations. An example of this is the search for titles that don’t have items in library A. If a title has items in library B and in library A, it will still be retrieved. This is a correct result as there is an item that matched the search query, but it is not intuitive to the staff user.Ex Libris will…
-
Add Visual Materials to Quick Cataloging citation types options
Our library uses the Quick Cataloging tool/interface to create records for materials in course reserves. Currently, the only options for citation types are books and articles. We have DVDs professors place on reserve. When records for DVDs are created, they are created on a record type for book. It would be great to choose citation type "visual materials" at the point of creating the bib record via the Quick Cataloging tool.
59 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Change color of NZ icon to distinguish from the CZ icon
The new Alma UI has made the NZ icon and CZ icon the same color and very difficult to distinguish from each other. The previous interface had different colors for these icons, which made it very easy to distinguish them. Please change the color of the NZ icon so that at a glance we can easily distinguish it from CZ records.
57 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Make Suppressing a location function the same as suppressing a holding in all publishing jobs
Currently, the general publishing job exports inventory in locations which are ticked "Suppress from Discovery" in Physical Locations config, when "Excluded Suppressed Locations: is ticked in the Publishing Profile.
Alma should handle this flag as it does for Publishing to Primo and Publishing to Libraries Australia and ignore suppressed locations, otherwise what's the point of setting this at the location level and then providing an option to Exclude suppressed records. It is extra work to set this value for each individual bib/holdings record.
55 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Increase download limit on large sets
The limit on the number of records that can be download to Excel from a set is around 70,000 records. Sometimes it's necessary to download larger sets (200,000+) but this is limited by size. It would be better if there was an option to download in CSV so larger data sets could be exported. Or, the Retrieve Set Members API was improved to include the information that is present in the Excel file downloaded from the set's results page. Or, there was an additional export job that allowed a set to be exported using one of the bulk jobs under…
55 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
"Request re-indexing" option for withdrawn items
There is a re-occurring indexing error in Alma when withdrawing items, where these items sometimes do not disappear from the Alma instance and a re-indexing job must be performed to correct it. These items often cannot be re-activated from "Manage deleted repository" and can't be interacted with. (See attachment)
Ideally, it should be possible to request a re-indexing of the Alma-instance directly in Alma. This could be for a single record or the instance as a whole.
51 votesThis is a bug and should be reported to salesforce as a case to support
-
Massive copy of records from the community zone to the local catalog
In our institution, we have thousands of active electronic records for our institution but belong to the Community Zone. We want to copy massively these records to our catalog without having to do it one at a time.
Our usual procedure is, from an excel file in which we have the ISBNs or ISSNs of the electronic documents, to upload the portfolios from the electronic collection itself. In this way we bring and activate in our institution the portfolios of the collection, but this does not generate a local copy in our catalog of each of them. So, we have…48 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Ability to run a job on a set from the Manage Sets screen
Currently we need to create a set in the Manage Sets area then go to "Run a Job", select the job to run and then select the set.
Wouldn't it be great if you could go to Manage Sets then click on "Actions" for a particular set, then choose "Run a Job". You could then be prompted to choose the job to run but you wouldn't need to go through the additional step of choosing the set (and you wouldn't have to exit the sets screen to go to the "Run a job" screen). And only the jobs that can…
48 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Enhance Advanced Search to allow regular expressions
Allow the matching of regular expressions as one of the criteria to perform an advanced search. This would be a much more powerful and precise method for gathering sets.
47 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Fix Call Number Sorting for certain classifications
Certain call number classifications that don't follow the typical format (LC class code, class number, Cutter code, title code, pub date) aren't sorting correctly in Alma's Browse Shelf Listing or Primo's call number browse.
One example is from a classification concerned with books about Civil War troop regiments:
E
577.5
24th
.T55
2010Which should typically sort like this:
E577.5 1st
E577.5 2nd
E577.5 3rd
E577.5 10th
E577.5 24th
etc.However, it seems as though the call number normalization isn't set for these specialized classifications and they end up sorting incorrectly, like this:
E577.5 1st. P48 2004
E577.5 10th .W35…45 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Allow option to abort import once it has been submitted
Once an import has been submitted, there should be an option to abort or cancel the import.
Sometimes mistakes are made. The wrong import profile is chosen, the wrong file is chosen. Often the mistake can be noticed very quickly, but there is no choice but to wait until the entire import file is loaded. And by then the damage is done, it can be very tedious in Alma to undo certain mistakes (portfolios imported to the wrong collection for example).
Alma offers the action option to "abort" once a job has been submitted. This same option should be available…
44 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Fix $g in 773 / 774 related records
According to documentation (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/130Configuring_Related_Records_for_Physical_Inventory), $g in linking entry MARC fields (such as 773 or 774) "links to specific items for the record specified in the $w, $x, and $z subfields). According to support " it is outside Alma's current functionality to be able to be separate an item from a collection of related bib records. It would be an enhancement to this functionality."
I am proposing that Ex Libris fix or enhance this functionality so it will work. My institution has a large collection of 'bound with' physical materials from the 1700s with analytical cataloging. For example, 26…
42 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
create brief record
In Resource Management, there are options for creating a physical item using a template that list the MARC fields as their type, not like the field numbers in Metadata Editor. Such as, Title is listed with a field to enter this information, and Author and so on for the Resource Information. As a cataloger, I know the MARC field numbers and can easily catalog in Metadata Editor, but this is not the case for the acquisition coworkers I collaborate with to order new materials.
In the Add Physical Item function, you can create a brief record with only the title,…
42 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Improve ME Browse Call Numbers Tool
When editing a holding record in the Metadata Editor, the Browse Call Number tool shows the call number from the current holding record in a shelf list display. However, the resulting list starts with the call number in your holding record and shows the following call numbers. What we need is to see the call numbers both before and after the one we're working on. Request the list show at least 2-3 call number prior to the one we're working on, plus those following.
39 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Import Profiles - Match Profile add 028 - Publisher or Distributor Number to one of the match methods
When loading records via import profiles it would be great to be able to match on the 028 - Publisher or Distributor Number. Could this be added to one of the match methods currently available or added as a new match method>
39 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Further filtering in Authority control task list
We are regularly getting old bib records in the Authority control task list and they make it hard for us to spot new bib headings that we need to add to our local authority file. It would be very helpful if it would be possible to filter the list by creation date to limit the list to new bib records.
36 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Disallow deletion of sets that are used by jobs (publishing profiles, etc)
When deleting sets, please perform a check to see if that set is in use by a publishing profile or other job, and show a popup dialog telling the user that the set cannot be deleted because it is in use, or allow deletion but warn the user that the set is in use by a publishing profile etc.
35 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Authority linking issue with bibliographic field 240
We'd request that when Alma links up bib field 240 with a uniform title entered in authority record, it should take into account of bibliographic contents in field 240 PLUS field 100 ALTOGETHER, and link these combined contents with uniform titles entered in authority records.
Currently, it links up the uniform title in field 240 only with authority record. So, those generic uniform titles e.g. Works, Poetry, etc. will be ambiguous, and do not have proper linking with their authority records established with author's name.
Details, please refer to Salesforce case # 823121
32 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
-
Community Zone records: subfield t missing in 780 and 785 MARC tags
In the CZ please add $t (Title of the related resource) to tags 780 (Continues) and 785 (Continued by).
The lack of $t causes issues in discovery where 780 and 785 tags are set to be displayed, linked and searchable. With no $t this is not possible.
31 votesThis idea has not received sufficient support from the community through votes. As a result, it is being closed to allow those votes to be reallocated to other active proposals. We appreciate the contribution and encourage continued participation in shaping future initiatives.
- Don't see your idea?