Skip to content

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

259 results found

  1. Add a lock feature to prevent selected items from being withdrawn when running a job

    I envisage this as a simple checkbox within an item's record which prevents that item from being accidentally withdrawn. (A parallel exists in many photo editing software packages.)

    I also envisage this as being a property which could be engaged or disengaged on a set of items via a job.

    When running a withdrawal job, any such "locked" items which were not withdrawn should be listed individually in the job report so that the user can determine whether this was correct (in case an item has been accidentally locked by a user, for example).

    A use case is as follows:

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Add an Owning Library facet in Repository searches

    Can we please have the owning library added as a facet in repository searches. At the moment it only appears in Acquisitions based searches as we have four libraries making up our collections this facet would also be very useful in the general searching

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Add the NOT Boolean operator to the Advanced Search in Alma

    Advanced Search in Alma contains currently only AND and OR Boolean operators - it would be very useful to have the NOT operator included, so that we can exclude particular records from Logical Sets, rather than creating 2 Logical sets and then combining them with NOT, resulting always in an Itemized set.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add 775 field in the search index.

    Currently this field is not indexed in the search index. Would you please add it so that it can be searched?

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Make approved Purchase requests searchable in Primo

    By default, Purchase Requests are suppressed from search and discovery in Primo, whatever their status (In review, Approved, Rejected).
    We would like the library to have the possibility to automatically unsuppress Purchase Requests and to make them searchable once they have been Approved.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Ability to browse all call numbers in a single search

    We would like the ability to browse all call numbers, regardless of call number type. In Alma, many of our local Library of Congress, Dewey, and SuDocs call numbers are retrievable only by the call number type Other Scheme. An “all call number” browse would allow us to retrieve a complete shelf list of our call numbers and would be especially helpful when assigning new call numbers.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Brief result display options per Alma login

    Enable Alma users to choose "brief display" options (either very brief or extended information). Many of our Alma users would like to be able to do a search in Alma (in both repository search and course reading lists) and ONLY see a list of titles (e.g., do not display Format, Subject, ISBN, Availability). However, recognize that many Alma users would like to see extended display, so we would like each Alma user to be able to set their display preferences (e.g., brief, title only OR additional information). Ideally, users could choose exactly what data elements to display (e.g., OCLC number,…

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Unclutter index for F3 lookup from field 830 (Series Added Entry - Uniform Title)

    F3 lookup from field 830 is used to verify if a series title has been entered into the database in a standardized form, and, if so, to link the bib record to that title . At present, the index searched by F3 contains a mixture of headings from fields 830 and 490 (where the non-standardized series title is entered) and headings with volume numbers (which refer to a part of a series, not the series as a whole). To best serve its purpose, the index looked up from 830 with F3 should contain and display only the fields $a, $p,…

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Display Collection details on a citation record the same as what you see via an Alma All title display

    Display Collection details on a citation record the same as what you see via an Alma All title display

    We use Collections to group records together to help with our Leganto processing, but you cant see this information from the Citation view. We would like both views to provide the same level of information. The attached screenshot shows what I mean

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Combining multiple itemized sets

    We'd really like the ability to flag multiple sets to be combined to create a single combined set. Several times we've wanted to do this to facilitate data analysis (e.g. on sets created logging weekly data loads), but it's far too time-consuming to combine them two at a time!

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Editing multiple collections from a set in bulk

    We have a lot of historic collection records left over from our migration which we would like to update in bulk, for example, there collections have no portfolios so I would like to be able to add services to them all at once rather than individually. I'd also like to be able to update the "Library" field etc.

    I can create a set of all these collections however, I can't make bulk updates to it. It would be great if there was an ability to run a job to add services and download a spreadsheet of all the fields in…

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Authority linking issue with bibliographic field 240

    We'd request that when Alma links up bib field 240 with a uniform title entered in authority record, it should take into account of bibliographic contents in field 240 PLUS field 100 ALTOGETHER, and link these combined contents with uniform titles entered in authority records.

    Currently, it links up the uniform title in field 240 only with authority record. So, those generic uniform titles e.g. Works, Poetry, etc. will be ambiguous, and do not have proper linking with their authority records established with author's name.

    Details, please refer to Salesforce case # 823121

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Task list customization

    Currently, the task list is automatically configured based on user roles. However, there are many features assigned to a role in Alma that a user may not actually deal with. For example, as electronic resources manager, I do not need to see print order lines to claim for print titles. This is particularly an issue because other departments do not always use the task list in their workflow, so mine can become cluttered with their content. We would like additional customization to be available within the task list, so that we only see relevant tasks.

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Report list of records changed after abort job

    After a user was running a discovery suppression job, and aborted they assumed nothing was changed. It would be very useful if the records that were changed before the abort were reported to the user.
    Here's an example showing an abort that occurred and the user running the job assumed since they aborted the job, nothing was changed:

    https://www.screencast.com/t/PoFqKwEjHIuH

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base