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.
118 results found
-
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…
10 votes -
Ability to edit records during import when manual handling required
During the import of records, we sometimes get the "Manual Handling Required" notice, from which we can view the record in question as well as its error.
On that screen you can view the record and we have often found that only a small fix is needed to correct the error, and would be best done at this point in the process rather than getting the original file, making a change, and either reloading the whole thing or extracting the one file to fix and reload it alone.
It would be nice if, along with the ability to simply view…
9 votes -
Overlap Analysis - compare all IZ EXCEPT selected electronic collections (such as non-owned eBooks in EBA, DDA, and ATO collections)
Overlap Analysis would be more useful if we could compare all of our IZ EXCEPT certain selected electronic collections. The use case if that we load vendor records for titles in our Evidence-Based Acquisition, Access to Order, and DDAs. Since we do not yet own these resources, we would like these eliminated from the "all IZ" target sources.
9 votes -
Browse Shelf Listing - straight to edit!
If you click on a record in the list that appears when clicking Browse Shelf Listing (Alt+C) while in MDE, the record immediately opens in MDE for editing. This is not necessary and confusing because for example when you click on a record after clicking Find Matches (Ctrl+M) you get the option of View or Edit. Same should apply to Browse Shelf Listing (Alt+C)
9 votes -
No relation "Replaces/Replaced by" between records due to entry of invalid ISBN (020 $z)
If there are two records in Alma, one that has 020 $a u and another that has 020 $a v and 020 $z u, the both records will be related by the system with the relation: Replaces/Replaced by. The 020 $z is understood as a "cancelled" ISBN and therefore included in the job that calculates the relations.
In the vast majority of cases we know 020 $z is a false/invalid ISBN: a publisher mistakenly(!) uses the same ISBN in two different resources that have nothing to do with each other. However, according to the international rules for describing resources, the…
7 votes -
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 -
Improve the efficiency and accuracy of Check call no.
In the Aleph environment, when a cataloger presses F3 in the MARC tag of call number (050), they can see "all" similar call numbers. This helps them to decide the call number for the record they are working on. The system does not differentiate whether these are physical or electronic resources, or whether they have holdings. However, in the Alma environment, when in the same call number (050) MARC tag, it is not possible to see "all" call numbers of records in the system, especially not for electronic resources. This significantly increases the difficulty for catalogers in deciding the call…
4 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 -
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'.
4 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 -
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 -
Add permission to remove items from sets to more Alma roles
Several of our cataloging workflows are based on multiple catalogers working off of a public Alma set of items to be cataloged. After they catalog an item, they remove it from the set. The ability to remove records from sets created by others requires the Repository Manager role. Currently we have to add the Repository Manager role to catalogers to get the "remove from others' sets" functionality, and we don't want to grant the other advanced permissions along with that role.
Please add the ability to remove items from sets created by others to additional Alma roles that are lower…3 votes -
Add Mintel Global Outlook on Sustainability Reports to CZ
Request to add Mintel reports on Global Outlook on Sustainability to the Community Zone
These are recently released reports in September 2024
3 votes -
Add MMS to title list search options in Collection Resource Editor
When searching the list of titles assigned to a collection, users can only search by title or publisher. It would be helpful if there was also the option to search by MMS ID since this allows for more precise retrieval. See screenshot: https://app.screencast.com/sCZbTHJ39CcHE
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 -
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
- Don't see your idea?