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.
259 results found
-
Please add the ability to use the facets for Archival Materials according to LDR pos. 8 = a
Hello,
Most archival materials are cataloged as follows:
LDR pos. 6 = p
LDR pos. 8 = a
Currently, the facet in Alma show these kind of materials as "Undefined".
Adding a facet of "Achieve Material" according to LDR pos.8 = a, would be very useful.Thanks.
63 votesHi. 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… -
Searching titles with "&" vs. "and" in Alma
In Primo VE, when a title in the 245 contains "&", if the title is searched with "and" in place of the ampersand the correct record will come up. This does not work the same way in Alma, however.
https://www.screencast.com/t/1mlHd3mIv
In some cases, a 246 field could be added to have "and" spelled out but that is not a universal solution. We would like to ensure that "&" and "and" could be used interchangeably in Alma title searching as it seems to work with Primo.
1 vote -
Show linked purchase requests in 'Other details' beneath title record
It would be great if purchase requests that are linked to titles could be accessible via other routes rather than just the 'Manage purchase requests' section. Please could purchase requests that are attached to a title and a POL be added to the 'Other details' section beneath a title record in a repository search? This would allow us to quickly ascertain which titles have purchase requests linked to them.
1 vote -
Add an option to search the repository by "Assign to" cataloger / operator
Currently there is no way to know which records are assigned to a certain user except for the "assigned to" note indication. We need a way to retrieve the records that were assigned in order to restore them back to the users' MDE, in case they dissappeard from the opened records pane. See full usecase in SFC#00957311.
26 votes -
Report list of records changed after abort job
After a user was running a discovery suppression job, and aborted they assumed nothing was changed. It would be very useful if the records that were changed before the abort were reported to the user.
Here's an example showing an abort that occurred and the user running the job assumed since they aborted the job, nothing was changed:18 votes -
Add fields to record historical valuation data
When rare books and other special collections are valued for insurance / exhibition / audit, it would be useful to add this into dedicated fields in the item record for physical inventory or other areas for digital titles. This way, a history of the value of the item can be recorded over time.
2 votes -
490's accompanying 830 field display
When you search titles, Alma currently displays 830 in the Series field when traced (490 with a 1 indicator).
However, 830 depending on 490 means that 490 takes precedence.It must be said that the trace which 830 is, is supposed to be used to be able to view 490 by the cataloguers and librarians.
But currently, when using the trace, 490 is not displayed.When you have a 490 field with several $a, you write several 830s.
For example ISBN: 9784043675043.
245 00 $$a Tō enmei.
490 1# $$a Kadokawa bunko ; $$v 13617. $$a Kadokawa sofia bunko ;…3 votes -
Import Profiles - Match Profile - Adding a Title only match method
The customer would like to add a Title only match method for CNMARC when loading new records via import profiles.
The title field can be set to 200$a.Because when the ISBNs are matched, the book title may be different for some Chinese books. It would be great to be able to match on the 200$a - main title.
13 votes -
Local Authority Automation and Workflow
Currently, Alma requires quite a bit of manual intervention when creating local authority records and linking them to the relevant records in the catalog. In order to relink an authority controlled field (ie. 1XX, 6XX, and 7XX) someone from the library must go through and change the second indicators from 0 to 7 and add a $2 with the local authority profile code. This can be done using normalization rules but it still must be done manually. There are no scheduled jobs that will do this.
An example might be helpful to both show the problem and a possible solution.
…
3 votes -
Ability to create sets from "Manage Deleted Repository" search
We would like the ability to create a set from a "Manage Deleted Repository" search.
Some vendors cannot use the "delete" files currently generated by Publishing Profiles. We would like to create sets (especially logical ones) from a "Manage Deleted Repository" search so that they can be attached to a Publishing Profile and help automate delete processes for these vendors rather than using an external script with the API and analytics.
This way, someone would only have to update the deleted date range of the set periodically, or even better, more search options and filters could be created for "Manage…
14 votes -
Additional Input Parameter Options for Item Description Templates
When creating an Item Description Template it would be very helpful to include additional Input Parameter options such as Permanent Physical Location. We utilize different description orders on our labels dependent upon the different locations items are shelved and there doesn't seem to be a way to distinguish the differing order with the current parameter options. More input parameter options would allow for greater individual institutional nuances and their unique practices.
For example, I could have an unclassed serial shelved in "serials" with material type issue and I want the description to display as:
v.{EnumA} no.{EnumB} {ChronI} {ChronJ}
I could…3 votes -
Reading lists - notification on Alma if an attempt is made to delete an item on a Leganto reading list
We would like there to be a notification on Alma if any attempt is made to delete an item that is on a Leganto reading list, whether it is deleted individually or as part of a batch-job. The deletion could be because the physical item is in poor condition or has been lost by a user, in which case we would need to know to purchase another copy. Alternatively, we may be deleting because we have purchased a newer edition, and would need to make sure that our reading lists are updated. This would apply to both physical and e-resources.…
15 votes -
Search results sorted by record creation date
For the purpose of having an overview of the progress in cataloguing a sorting option for bibliographic records by their creation date in chronological order is necessary.
8 votes -
Having the ability to configure the presence of all available Licensing terms in the Repository Search in Alma
There are a number of License terms that appear in the Advanced Repository search that are not configurable, that is there is no option to stop them appearing as options to search under in a simple or advanced search.
We want to delete some of these terms from Advanced Search. We want to get rid of the terms that we're not using in our current Licensing workflows (they clog up the search). The terms we want to delete from the Advanced Search are not available to configure in the Alma Configuration Menu > Resources > Search Configuration > Search Indexes.
…
1 vote -
error message
when you want to add a title into a collection, if this title already exists in the collection, an error message should appear "title already in the collection". It would be very useful.
1 vote -
Ability to know which set/s a specific record belong to
It would be very useful to have the ability in Alma to know which set or sets a specific record is in. It would be nice to search for an item id (for itemized sets), an mms id (for titles sets) and so on, and get the sets' names those items or mmsids belong to.
6 votes -
Publishing profiles should be able to produce valid MARCXML
The ability to produce valid MARCXML exports from publishing profiles, with the namespace included, would be useful.
Currently the "MARCXML" option produces a file that is not valid MARCXML. It doesn't include a namespace.
The rationale given by ExL Support for not including a namespace was that it would be possible for the user to use norm rules to change the data on export, in which case the data might not be valid, so they didn't want to include a namespace. In some cases it may be necessary for libraries to produce data exports that are not valid, but even…
0 votes -
Raise the exporting capacity from Alma to Excel
It's recently found that there is a limit of 100,000 records when exporting from Alma to Excel. Please consider raising the exporting capacity.
Background information: please refer to Salesforce case # 944923, and this documentation in the knowledge centre:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/The_Alma_User_Interface#Export_to_ExcelThank you!
4 votes -
"Display in Discovery" from any screen in Alma
Make the Display in Discovery action available in any screen/view of a record in Alma, not just in a repository search or in portfolio lists. There is often the need to see how a resource displays in Primo when working in an item, orders, and other areas of records.
60 votes -
Block Deleted Records from Merge Records and Combine Inventory Process
Currently, when a CSV file is loaded into the "Merge Records and Combine Inventory" process in Alma Resource Management, if the preferred bibliographic record is already deleted from the repository, the merged record attaches to a deleted bib, and is deleted, which is not ideal. We would like to have those merges bounce or error and not merge, or at least be noted in the results file when this occurs, so that staff may manually review or fix that error.
11 votes
- Don't see your idea?