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.
121 results found
-
bulk remove titles from collections (not the electronic type)
Add the ability to remove titles in a set from a collection (not the electronic type) in bulk, as well as add titles in bulk from a set.
58 votes -
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…
54 votes -
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…
38 votes -
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 votes -
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.
32 votes -
Allow copying of publishing profiles
Please allow copying / duplication of publishing profiles, much like you can currently make copies of import profiles. In other words, this would allow for "save-as" type functionality, allowing us to easily spin off another slightly modified publishing profile (like we can do now with import profiles).
thanks!
16 votes -
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 votes -
Add members to set from results screen
We would like an easier way of adding individual titles to itemized sets. It would be nice if, on the results screen after performing a search, you could click the ellipses menu for more options and see "Add to set" there, which would then direct you to select a set to which you'd like to add that record.
12 votes -
Combining multiple itemized sets
We'd really like the ability to flag multiple sets to be combined to create a single combined set. Several times we've wanted to do this to facilitate data analysis (e.g. on sets created logging weekly data loads), but it's far too time-consuming to combine them two at a time!
22 votes -
Enable 'recall' option on individual work orders
At present work order types can be set to recall items or not.
It would be useful to have this as an option for individual work orders (much as 'do not pick from shelf' is an option).
This would make work orders more versatile and save having two work order types ('recall' and 'no recall') for essentially the same process.
25 votes -
Allow **** or Python plugins for normalization rules
The Drools framework in place for normalization rules is very limited compared to real programming script languages like **** or Python. Live would be way easier, much more efficient and some things impossible with Drools would be possible with **** (like in SFX parsers) or Python for those who can use these languages.
54 votes -
Add active link function to all fields where a URI in subfield u is valid
Subfield u for uniform resource identifiers has been defined as a valid subfield in many bibliographic fields to provide automated access to electronic resources.
As noted in the OCLC bibformats: "Subfield ǂu defined as the URI is valid in the following fields: 031, 370, 381, 505, 506, 510, 514, 520, 530, 538, 540, 542, 545, 552, 555, 561, 563, 852, 856, 880, 883, 884, and 956. Additionally, subfield ǂu can be used in fields 901-907 and 945-949, either in accord with its control subfield definition or as a locally-defined subfield" (http://www.oclc.org/bibformats/en/controlsubfields.html#subfieldu).
Currently, only URIs in 856 subfield u…27 votes -
Need ability to search 79X fields
We plan to implement use of the 790 field for local tracings (such as former owners) to be used for special collections materials, and have set up a separate search field in Primo. Now we see that we can't search that field at all in Alma, only Primo. Since Alma does index 59X fields as "local notes" and 69X fields as "local subjects" we propose that the 79X be indexed as well.
58 votes -
New UI-Call Number as an option in the search customization
In the old UI when conducting a search the call number would display in the search results. In the new UI each individual title now has to have the physical title clicked on to see the call number. It would be helpful to have a call number option under the customization options so that it would eliminate all of the unnecessary clicking when trying to view call numbers during a search.
59 votes -
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 votes -
Ability to edit records during import when manual handling required
During the import of records, we sometimes get the "Manual Handling Required" notice, from which we can view the record in question as well as its error.
On that screen you can view the record and we have often found that only a small fix is needed to correct the error, and would be best done at this point in the process rather than getting the original file, making a change, and either reloading the whole thing or extracting the one file to fix and reload it alone.
It would be nice if, along with the ability to simply view…
9 votes -
Allow sorting of itemized set members similarly to logical set results.
In Manage Sets, enable sorting the members of itemized record sets by title, creator, and publication date, similar to the criteria available for sorting results of logical sets. Currently our only option for sorting the members of an itemized set is by exporting to Excel and manipulating the resulting spreadsheet, which doesn't allow for clean sorting by the same criteria.
115 votes -
Editing multiple collections from a set in bulk
We have a lot of historic collection records left over from our migration which we would like to update in bulk, for example, there collections have no portfolios so I would like to be able to add services to them all at once rather than individually. I'd also like to be able to update the "Library" field etc.
I can create a set of all these collections however, I can't make bulk updates to it. It would be great if there was an ability to run a job to add services and download a spreadsheet of all the fields in…
19 votes -
Ability to browse all call numbers in a single search
We would like the ability to browse all call numbers, regardless of call number type. In Alma, many of our local Library of Congress, Dewey, and SuDocs call numbers are retrievable only by the call number type Other Scheme. An “all call number” browse would allow us to retrieve a complete shelf list of our call numbers and would be especially helpful when assigning new call numbers.
20 votes -
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 votes
- Don't see your idea?