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.
260 results found
-
Add the ability to search ( and save query ) for holdings with suppressed tag yes
Please add the ability to search ( and save query as a set ) for holdings with suppressed tag yes.
Right now we can search for Holding having Tag Suppressed at Title level. This is not enough and is sometimes misleading (e.g. when a Title has 2 holdings, one suppressed and one not suppressed).We need to identify, save as set and manipulate holdings having tag suppressed at holdings level. This info has been added at Items level in Analytics, and is useful in case of report, but we need to work at Holdings Level in Alma with real time…
15 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 -
Search possibilities as "Received X weeks ago" or "Available X weeks ago"
Libraries sometimes wish to build logical sets from constantly changing data. For example, a logical set of items received in the last 30 days or a logical set of ebook portfolios activated in the last 15 days. The "Receiving date" (Physical items) and "Activation Date" (Electronic portfolios) search indexes only accept a specific date (selectable from a calendar) and only allow the operators "Equals", "Not Equals", "Before", "After", "Is Empty", and "Is Not Empty". It is therefore not possible to build 100% logical sets based on items received in the last 3 weeks and associate them with a collection for…
106 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 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 -
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 -
Customize search labels for local authorities
We would like to configure the search labels for local authorities. We have already checked, but the MARC21 fields used for the corresponding local authorities (084, 600, 651) are not shown in the list of search labels. Unfortunately, the support was not able to help us. They said that index codes to search index labels mapping and expanding the index fields is an enhancement request.
20 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 -
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…12 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 -
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)
50 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
- Don't see your idea?