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.
44 results found
-
Request for Enhancement: Add a search bar and facets to itemized sets in Alma
Description:
In Alma, logical sets let you search inside the set and use facets. This makes them much easier to work with, especially when the set is large.Itemized sets are treated as a static list of records, so they do not support internal search or facets in the same way. Even though this is how they are designed, it makes them harder to use in practice. When a set is large, it becomes difficult to find specific records or understand what is in the set without a lot of manual effort.
Suggestion:
Add a search bar and facets to…27 votes -
Search Authority Headings: Mariano Moreno National Library of Argentina. Import BNA10 - Z39.50 protocol
Implement the import of authority records via Z39.50 from the Mariano Moreno National Library of Argentina. Is not listed in “Authority vocabularies in the Community Zone” https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(Espa%C3%B1ol)/Gesti%C3%B3n_de_metadatos/050Trabajar_con_registros_de_autoridad
Downloading authority records
https://www.bn.gov.ar/bibliotecarios/protocoloZ3950
Z39.50 protocolIP: 200.123.191.9
Port: 9991
Database: BNA10
Authentication: YES
Username: Z39.50
Password: Z39.50
Character set: UTF-8
Format syntax: MARC21
Contact: dpt@bn.gob.arA Proquest case (10586567) was submitted—Search for Authority Headings: Mariano Moreno National Library of Argentina. It was noted that "Alma currently allows the import of bibliographic records from the Mariano Moreno National Library using the BNA01 database. However, the incorporation of the BNA10 database for authority records…
22 votes -
Manage Sets without Repository Manager permissions
It would be nice if we could update and manage repository sets without needing the Repository Manager role. Without it, staff can create sets and run queries, but they can't update any sets that weren't personally created by them, making it so that managers are having to make small updates that could easily be made by staff.
18 votes -
MD editor save marc tags chronologically
Upon save any MARC tags that are in the wrong chronological order are saved in the correct order.
16 votes -
Relationship designators should not be searched in Field 5XX, subfield $a
In Authorities, when relationship designators are used to specify relationships between agents in field 5XX, with subfield $i (relationship information), Alma searchs the relationship designators included in $i instead of searching the agent name included in subfield $a (personal names; corporate names, etc.). The subfield $i is not part of the name of the author or contributor, it is a separate element that denotes a relationship between agents. It is for this reason that we propose that names be indexed by the name included in subfield $a instead of subfield $i.
15 votes -
Display all 035$a values for the Record Number column in Table view of Titles UI
In the new titles search UI, the Record Number field lists only the first listed 035$a value of the record, followed by "and others." This is true for both the record view, where keeping data compact makes sense, and on the table view where one might expect to see more values for repeating data fields.
If the table view showed all of the 035$a values in the record number column, this would increase the utility of this view, as it would allow staff to recognize OCLC and other system numbers among the list without requiring a click and scroll through…
12 votes -
Support Processing System Control Number (035) Updates in Imported Authority Record Updates
Currently, Alma's authority-control jobs do not process updates to MARC21 authority tag 035 (System Control Number) when the update occurs via an authority import profile as the update of an existing record, i.e. there is a match between the existing authority record in Alma and the incoming authority record via the authority import profile. In contrast, the update is processed when there is no match with an existing record, i.e. the record is new to Alma, or, when the authority record has been updated manually via the MDE.
This was clarified by Ex Libris in a support ticket (case 07255325).…
11 votes -
Add Option to Handle Multi-Matches Automatically Based on Brief Level
Alma’s import profile functionality currently includes the option "Do not override/merge a record with lower brief version", which ensures that an incoming record is not loaded if its brief level is lower than that of the matched record in Alma.
We would like to see this functionality extended to enable handling multi-matches automatically. Currently, when an incoming record matches multiple existing records in Alma, the import process still flags this as an multi-match issue, even if all matched records in Alma have a higher brief level than the incoming record. These cases must then be reviewed and resolved manually by…
10 votes -
Enable local extensions on MARC 79X and 89X
OCLC Bibliographic Formats and Standards sets out tags 79X (790-799) and 89X (896-899) as valid for local uses. These ranges should be available for network zone members to use as well. Adopting these ranges will allow catalogers to directly adapt records from WorldCat into a network and add local extensions without having to remap from the OCLC-supported field to a field in Alma, such as a 9XX.
Catalogers primarily use these fields to enter details such as authors with local affiliations (e.g., current faculty members), dissertation advisors or members of dissertation committees, and the college within the institution supervising the…
8 votes -
Post Alert when import job reaches Manual Handling Required
Please add an alert to the Real-Time Notifications list, targeted to users with privileges for running import profiles, when an import job is paused with the status "Manual Handling Required."
Import profiles run manually or on a schedule may reach a paused state with status Manual Handling Required, commonly for multiple matched records that require merges, and sometimes with validation errors. Because these jobs don't run to completion, they don't appear on job history. Because these jobs are paused, they don't appear in the list of running jobs. If a user is not aware that the job is paused, import…
8 votes -
Change the order of the dropdown menu for 'Run a Job'
It would save a lot of time and extra clicks if the first option in the dropdown menu for 'Run a job' was switched to 'Name', rather than 'Description'.
7 votes -
Make Existing Record Primary When Merging via Search Resources
When merging records through Alma’s Search Resources, make the existing Alma record the Primary and the incoming external record the Secondary.
Currently, when bringing in external records, Import and Integration Profiles treat the existing Alma record as Primary, but Search Resources makes the external record Primary. This inconsistency forces libraries to maintain two opposing sets of merge rules, depending on how the record enters Alma.
Making the Alma record Primary in Search Resources would align the behavior with other workflows. This could be configurable or at least opt-in so libraries can adjust their merge rule settings in the External Search…
7 votes -
Add filters and columns to import profiles screens for zone, protocol, scheduling, status
The Import Profiles screen has few options for narrowing the list of profiles if one isn't certain of the profile name, or if descriptions are too similar. Please add filters and columns to the display screen--preferably sortable columns--for fields that distinguish the zone, scheduling, and status for import profiles.
Priority 1, Zone: Users should be able to clearly see whether an import profile is using the network zone or the institution zone for an import profile, as this affects the workflow and processing of records being imported.
Priority 2, Status: While the Active/Inactive status of a profile may be useful…
4 votes -
Add "created by user" and "modified by user" Index in the Alma search
Now that the new relative date search exists in Alma, it would be very helpful to have another index "created by user" and "modified by user" to be able to search for records created or modified by a specific user within a relative date range.
For exemple, a user could be able to review all the records she/he createred the day before in a easy way.3 votes -
Add extra filter operators to date fields in title search
Add the following filter operators to all titles search:
-Is within last (days)
-Is older than (days)
-Is within next (days)to filters in all titles search such as MMS creation date (title) and modification date (title).
These filters are already available in user search.
3 votes -
Collection - report who added title and when
When adding titles to Collections (Resources\Manage Collections) it would be helpful if it reported who and when a title was added to the collection. Report of this via Analytics would be preferable but displaying in Alma would be a start.
3 votes -
ellipses in specific contexts(三点リーダー“…”)
In Japan, we use ellipses in specific contexts.
Please adjust both Cloud App and Alma so that typing three middle dots and converting them results in an ellipsis (“…”) with three dots centered.
*Note: This is not three periods (“...”).I believe this issue is likely caused by the font type, language settings, or similar factors.
Thank you for your cooperation.3 votes -
【NACSIS-CAT/ILL Cloud App】We would like to request that prefix matching search, similar to WebUIP, be implemented in the Cloud App as well.
Unlike Western books, Japanese titles are not displayed word by word, so prefix matching search is frequently used.
Therefore, it would be very helpful if prefix matching search could be enabled, as it is in WebUIP.The following three prefix matches are possible in WebUIP but not in the Cloud App. Could you please adjust the system to enable prefix matching search?
(1) Cloud App “NACSIS-CAT/ILL” > Catalog > Book Bibliography
(2) Cloud App “NACSIS-CAT/ILL” > Catalog > Journal Bibliography
(3) Cloud App “NACSIS-CAT/ILL” > Catalog > Uniform Title AuthorityThank you in advance.
3 votesHello Bukkyo University,
Can you please share more details on the capabilities available in WebUIP as a step by step scenario so it will clear to us what is the exact reqeust?
-
Multiple Logical Sets Attached to Logical Collections in Collection Discovery
I would like to be able to create a Logical Collection in Collection Discovery that combines the results of at least two different logical sets.
CASE EXAMPLE: I have been asked to create "New Book" collections for multiple departments that include both print books and ebooks. For the print books, the fields I need to query on are only available the creation of a Physical Titles search set. For the ebooks, the fields I need to query on are only in an Electronic Titles search set. Since I cannot merge the results into a single logical set, that means I…
1 vote -
Display of Collections in Collections Lobby in Primo VE
Ability to only display digital collections in the Collections Lobby page of the Primo View, whose profile slot includes the collection’s local scope.
Case number 081133401 vote
- Don't see your idea?