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
-
Enable labeling enumeration and chronology fields
It can be difficult to recall the meaning of enumeration and chronology fields, e.g., Enumeration A, Enumeration B, Chronology I, etc.). It would be helpful if general system administrators could change the labels of these that show to staff, for example, change Enumeration A to Year.
42 votes -
Allow to define several local search indexes, including standard MARC fields
Following the partial implementation of idea "Ability to search via free text MARC tag and subfields" (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/17197337-ability-to-search-via-free-text-marc-tag-and-subfi) under NERS 2020 #6795, here is perhaps a more modest suggestion, that hopefully can be more technically feasible and still provide a large chunk of the missing functionality.
Similar to the analytics "Local Param" concept, it would be very helpful if institutions were able to define 5-10 "Local Search Indexes", based on each institution's needs. These indexes should be able to include any MARC field or subfield, whether local or standard (and preferably also field combinations).
Use case: In our institution,…
40 votes -
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…
39 votes -
Add Melingo to ALMA
Hello,
The assimilation of Melingo in Primo for the customers in Israel proved to be a useful solution.
It would be nice if it can also be implemented in ALMA.
If Melingo will indeed be in ALMA, the catalogers will no longer need to add Ktiv Maleh or Ktiv Haser in Hebrew in variant titles.Thanks.
38 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…
36 votes -
Collection Discovery manual title ordering
In collections and sub-collections, please allow adjusting the order of titles manually (and individually - like we change the order of collections by drag-and-drop).
While the ability to change the default sort method is useful, our collections require more granular control over the order in which titles display.
A drag-and-drop system would be ideal. Slightly less useful would be the ability to track and sort by the date that each title was added to a collection.
35 votes -
Index fields 772 $$w and 830 $$w for the Alma Repository Search
As these fields are currently not indexed but would be very useful, we strongly suggest adding them to the search indexes which are available for the Alma Repository Search.
Field 773 $$w is already indexed and we think these two additional fields could be used for similar search queries.(Follow up of support case 6659197)
32 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 -
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.
31 votes -
import profiles -- need the option to leave suppression codes "as is"
When creating an import profile, the “set management tags” option is to either suppress record/s from publish/delivery, or to not suppress. This is for the entire file.
We need a third option to leave the existing suppress status unchanged for replaced and merged records. (We had this option in Voyager, and it worked well)
Rational: All GPO weekly brief Marcive records are loaded suppressed. When the monthly bib records overlay the weekly brief records, the suppress status needs to remain as is. “If” the bib record is suppressed, the cataloger will unsuppress at the point of cataloging
30 votes -
Full PCRE Regular Expressions in Normalization rules
Supporting full PCRE regular expressions would make Normalization rules so powerful. Allow capturing data in one place and re-using it somewhere else, checking for substrings, etc.
28 votes -
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 -
Index field 310 for the Alma Repository Search
It would be useful to be able to search within all records with field 310 not only through the codes in 008 but also via the text in 310. We therefore suggest adding the field to the indexes for the Alma Repository Search.
26 votes -
Option to export Alma search results and sets as CSV
Right now Alma search results and sets can only be exported in XLSX-format. For performance (and other) reasons it would be good to have the option to export in CSV format.
(Publishing this as an enhancement request was suggested by Ex Libris in public Salesforce case #00825531)
26 votes -
Add a safety feature to Delete Bibliographic Record Job to include option "Do not delete if ANY PO Line is attached"
Currently there is only an option to protect Active PO Lines with this job. Acquisitions staff often place orders on bib records representing multi-volume sets. Cataloging staff then decided to use individual bib records for each volume and want to delete the set record and move POLs to the individual records. It would be very helpful to have this feature in place to protect order information.
26 votes -
Make Push Selected to MDE button available for Itemized Sets
'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…
25 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 -
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 votesThank you for submitting this idea. To be sure we fully understand the request, could you please specify which other MARC fields other than 050 and 090 you are asking to be added to the LC call number index? Thank you.
-
Use of parentheses in advanced search
Currently advanced search does not allow the use of parentheses. We'd like to suggest the capability of using parentheses in doing some complicated search logic. This can shorten the search query a lot. Currently, we have to repeat the search queries, and apply a combination of AND/OR search logic. The attachment explains the situation with a screen shot of current search logic.
24 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…24 votes
- Don't see your idea?