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.
116 results found
-
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 -
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 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 option to import records as standalone upon multi-match
In the "Automatic Multi-Match Handling" section, under the option "Choose a conclusive action in case the above selected criteria result in multiple records," I'd like to be able to select "skip and import record as standalone." I still want the record, but it doesn't know which record I plan to overlay. So, I must manually resolve the issue. It's an extra step to go back into the job's history, download the record it rejected, and reload it as standalone.
3 votes -
Add 2FA for Import profiles
Recent changes to our digital preservation system mean that two factor authentication is now required for API access to the system. This includes OAI Harvest tools.
At present there is no field in the Alma/Primo import profile template I can add the authentication key required to harvest data from our preservation system.
Is it possible to add such a field to the Alma import authentication template? This would benefit not only us, but others who have links to external systems which require two factor authentication.
Information about the change as it relates to us can be found in the following…
3 votes -
Add notes or internal description field to collections
Currently the only place to put information into a (not electronic) collection is the Description, which is visible to the public. It would be very useful to have an internal note or internal description field where we can put in information such as why a collection was created, who wanted it, what criteria to use when adding titles, etc.
3 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 -
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 -
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 -
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 -
Allow multiple Z39.50 to be setup in Alma
Right we use the only Z39.50 setup for Interlibrary Loan's ILLiad. One of our librarians would like to connect a new Z30.50 to search through Endnote to run systematic reviews. We had previously wanted to use another Z39.50 setup to input a more comprehensive search in Search Resources in Alma. If we can get multiple Z30.50s setup in Alma it would help us connect various sources to Alma and make it more robust.
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 -
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 -
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 -
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 -
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
- Don't see your idea?