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.
133 results found
-
Allow form editing of Metadata Configuration profiles in addition to Extension files
The metadata configuration profiles are currently only editable by uploading XML files, which become invisible upon upload. This can become a nuisance if a library wants to make small additions to existing fields, or wants to add multiple new fields with numerous subfield/indicator definitions. It would be much easier if new values could be added using a form within Alma, via an "add row" link at the top of each page. For example, in the MARC21 bibliographic profile, an "add row" button could add a new MARC field and definition. Within each field would be additional "add row" buttons for…
3 votes -
Add all Enumeration and Chronology fields to the Inventory Information tab of an Import Profile
Currently, only Enumeration A - C and Chronology I - K are listed in the Inventory Information tab of our Import Profiles. Our consortia uses Enumeration A-D; Enumeration D specifically is used for free-text phrases that do not conveniently fit into the category of volume, number or issue; so "index", "part", "box", etc. are all written in EnumD. This is why it is frustrating that this enumeration field cannot be imported via an import profile.
It would be immensely helpful for us if all enumeration fields were listed in the import profile. There is no point in having so many…
55 votes -
Show all holdings in export list in column "availability"
The results list exportet to excel shows only the first three to four holdings followed by “and others”.
So you do not get the complete number/information about the holdings of the record.3 votes -
Allow Correction of MARC21 Field Data in Metadata Configuration List
In Config-->Resources-->Metadata Configuration-->MARC21 Bibliographic, Alma users can add a new MARC21 field not currently included in the suite of out-of-the-box MARC21 fields by using the "Add Extensions" command to upload a XML file that contains field definitions and prescribed indicator and subfield values. The values in that file trigger error warnings in the Metadata Editor if that field contains incorrect indicator values or unauthorized subfields in a given bibliographic record. However, it is currently NOT possible to delete a newly added MARC21 field or upload a revised XML field definition file without deleting the entire extension pack.
What we're requesting…
1 vote -
Show in name of person who created the bibliographic record
When reviewing a bibliographic record in the record information section, the ID of the user who created the record is displayed but not the name.
It would be useful if Alma showed the name of the cataloger (and not the ID) currently it is necessary to search by ID later to know who created or modified a bibliographic record.2 votes -
automated import profiles - create log file with useful information if process fails
We are finding Alma less than helpful in cases where the automated download fails due to a parsing error. Apart from actually creating a log file as suggested here, there would be other ways to improve this experience.
This is what currently happens:
- for automated import profiles, no log file is created when the process fails, the emailed report simply states that the import failed, there is nowhere in alma where I could find any further information
- because of this, we then need to try and run the import manually, so we can see what the issue is…1 vote -
Add Call Number to all Overlap and Collection Analysis Reports that include Print
Add Call Number to all Overlap and Collection Analysis Reports that include Print
The new Title Look Up function that permits comparing a list of print to various electronic collections is excellent. However, the output reports don't include the print call numbers. That would be a significant improvement; staff could then easily use the report to go to the shelves. As it is, we have to do a separate process in Analytics just to get call numbers which seems like a waste of time.
1 vote -
Request for improved functionality "Search bibliographic records matching this value" in Alma's authority repository search.
We request enhancements to Alma's authority repository search function.
Currently, when we click "Search bibliographic records matching this value" from a specific authority record in the search result to move to the bibliographic record list page, we have not be able to back to the authority record list page displayed in the first search.
A Back icon is displayed on the bibliographic record list page, but even if we click it repeatedly, we will not be able to return to the authority list page, and will eventually move to the top screen of Alma.
Returning to the authority record list…14 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.
29 votes -
Index fields 700 $$4 and 710 $$4 for the Alma Repository Search
As 100 $$4 and 110 $$4 are already indexed and can be very useful for cataloguers for searching records in Alma, we strongly suggest having also the relator codes in 700 $$4 and 710 $$4 indexed for the Alma Repository Search.
(Follow up of support case 6659197)
53 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 -
Index field 773 $$g for the Alma Repository Search
Our libraries would like to have subfield $$g in field 773 indexed for searching in Alma, because it would allow to have more precise search queries including e.g. the issue number within a journal collection.
24 votes -
Add a tab to Manage Sets that shows Sets linked to Publishing Profiles
From Admin - Manage Sets we can see My Sets, Public Sets, and All Sets. It would be useful for there to be a way to more easily distinguish and find sets that are used in Publishing Profiles. As more and more integrations with third party services rely on Publishing (HathiTrust, Google Books, RapidILL, BrowZine, Syndetics, etc.) more and more sets need to be created and maintained and occasionally tweaked if locations or libraries are added, removed, or changed, or if new materials within the sets become unshareable for some reason.
The current workflow to find the right set is…
1 vote -
Improve search for ayn diacritic directly after hyphen
In a romanized Hebrew search when an ayn diacritic appears directly after a hyphen, there is zero results with the expected search: "gozeret ha-orot" (no spaces). This very search has the expected result in Primo but not Alma. That search also works in OCLC Connexion. I was told to use a space instead of a hyphen in Alma, which brought up the record but it is not the way one expects to search in this instance.
1 vote -
Make bibliographic references searchable
Make bibliographic references searchable
MARC21
555__ |a
555__ |dImportant for old prints and manuscripts
555 also includes references that cannot be used in 024 7
So far 500 has to be filled out in addition to 555 to make it searchable
6 votes -
Make it possible to add single titles from other sources than the IZ to Collection Discovery
At the moment you may only add titles from your IZ to a collection in collection discovery. It would be nice to have a method also to add titles from the NZ, the CDI and external resources.
63 votes -
More customization for Duplicate Title Analysis job
Request to be able to further customize the Duplicate Title Analysis job in Alma. For example, include/exclude CZ records and specify resource type (physical/electronic, book/journal/map etc).
Additionally, identifying the "preferred" record is extremely limited. Being able to select the preferred record by MARC/DC field and/or subfield would be helpful.
18 votes -
IZ/CZ symbol display in Record View
Could “Record View” display the symbol to show whether the bib record is IZ or CZ? At the moment, you have to click on Edit and go into the MDE to find out which it is, which is annoying and time-consuming if you don’t need the MDE at that point for any other reason. You may have reached Record View from a route other than a search (e.g. activating an e-resource), so may not have seen the IZ/CZ symbol at a previous stage.
2 votes -
Collection Discovery: Allow several libraries to manage a collection
In the Collection Resource Editor > General tab, we would like to be able to add several libraries to a collection (instead of just one).
When the viewtolibrariesforcollection_discovery Customer parameter is set to true, this would allow to display a collection on several Primo views, for example in case of a shared collection in the IZ which does not belong to a specific library.
21 votes -
Replace the search index label "Creator" with "Author"
the label used for the author index in the title search is confusing, implying that it is the creator of the Alma record, as shown in Alma Analytics, and not the author of the title.
19 votes
- Don't see your idea?