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.

How can we improve Alma?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Refine search and Search external resources function

    When using the "Search external resources" function under profiles including several external catalogs, we can only use refine search link on the first tab.

    It would be great if the refine search link was on all tabs rather than on the fisrt tab only.

    68 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Analyse and normalise special characters and diacritics in Alma records

    In order to enable correct and consistent automatic linking between Bib. headings and authority records, Alma's treatment of diacritics needs to be normalised, and made configurable according to the Authority file being used. In addition there are special characters in use (such as quotation marks), that have more than a single graphic representation that should be normalised in order to prevent discrepancies in Almas' match and link mechanisms.
    SFC#00533813, SFC#00375370 relate to the issue.

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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:

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Access detailed error reports for all jobs

    University of South Australia Library would be interested in accessing various error reports for the jobs that we run at the time when we run the jobs.
    We are aware we can check Import errors as per "Resolving Import Issues" but for other type of jobs we cannot check error reports.
    As an example, running a filtering job on a set provides us with a report including a brief information on the number of records that "failed" as in this message:
    "Of the 67201 records processed, 4 records failed. For more information view the report details (or contact Support using…

    85 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 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.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Test mode for jobs

    Allow jobs that change bibliographic records or inventory to be run in a test mode first that shows results that would occur before updating the database, so we can be sure that what we intend to happen is what does happen. Right now we are just hoping it will work as expected.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Fix Call Number Sorting for certain classifications

    Certain call number classifications that don't follow the typical format (LC class code, class number, Cutter code, title code, pub date) aren't sorting correctly in Alma's Browse Shelf Listing or Primo's call number browse.

    One example is from a classification concerned with books about Civil War troop regiments:

    E
    577.5
    24th
    .T55
    2010

    Which should typically sort like this:
    E577.5 1st
    E577.5 2nd
    E577.5 3rd
    E577.5 10th
    E577.5 24th
    etc.

    However, it seems as though the call number normalization isn't set for these specialized classifications and they end up sorting incorrectly, like this:

    E577.5 1st. P48 2004
    E577.5 10th .W35…

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Better control over processing order in import profiles

    When importing records it would be really useful to have an option to control the order of the processing steps involved in the import, and maybe to add additional processing steps.

    We have two use cases where the current order has not worked out for us:

    * When importing records with EOD, the EOD will be created from the original record rather than the normalized record. This was a special use case, where a change in the originating system prevented EOD to be embedded in a correct way. Had we been able to process the records with normalization rules we…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. In Advanced Search, allow filtering OUT specific locations. For example, allow use of the filer: Physical Location "IS NOT" X.

    Many searches do not allow for an "IS NOT" operator, and in some cases it is greatly missed. For example, when trying to assemble large sets of records where you want to exclude just a few locations, or filter out a single library. Please allow for an "IS NOT" operator when doing an advanced search and filtering by location or library. I'm sure there are other search filters also missing the "IS NOT" operator. Please feel free to add more suggestions via a comment! :)

    147 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Add Melingo to ALMA

    Hello,

    The assimilation of Melingo in Primo for the customers in Israel proved to be a useful solution.
    It would be nice if it can also be implemented in ALMA.
    If Melingo will indeed be in ALMA, the catalogers will no longer need to add Ktiv Maleh or Ktiv Haser in Hebrew in variant titles.

    Thanks.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Selecting records to print from search results

    It would be very useful to be able to print select records from Alma search results by checking off records to print. Printing off records is a necessary part of maintaining tangible collections. One can often find superseded SuDoc publications while searching the IZ by SuDoc stem when adding new SuDoc publications. I would like to print records rather than writing down call numbers and OCLC numbers of items to withdraw. An individual printed record would make it easier to find and withdraw superseded or unwanted materials.

    As it is now, one has to create an itemized set from the…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Massive copy of records from the community zone to the local catalog

    In our institution, we have thousands of active electronic records for our institution but belong to the Community Zone. We want to copy massively these records to our catalog without having to do it one at a time.
    Our usual procedure is, from an excel file in which we have the ISBNs or ISSNs of the electronic documents, to upload the portfolios from the electronic collection itself. In this way we bring and activate in our institution the portfolios of the collection, but this does not generate a local copy in our catalog of each of them. So, we have…

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Provide ability to turn off the Related Record functionality for physical items

    Provide ability to turn off Related Record functionality for physical items. I would like to be able to decide for each related field in the MARC record - 773, 774, 777, 786, 800, 810, 811, and 830 whether or not Primo will display the related record information for physical items.

    There are cases where displaying related record information to the user is more confusing then helpful. 830 series fields, for example, will display "related" records that may not relate at all to a users search, especially if the series is general like: "Brill's studies in intellectual history." I would like…

    122 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Add "Search within results" box on a set

    Hello,

    It would be very useful if we had a search box of "Search within results", on a set we created with indication rules.

    Thanks.

    191 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Change "Open Form Editor" short cut key

    Currently the short cut key for "Open Form Editor" is Ctrl + F, and this prevents the user from using Ctrl + F to find text on the page.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Allow suppression of items from Discovery in Primo

    I would like a check-box in the item record that would allow staff to suppress individual items from discovery in Primo. This could be used for libraries that want to use only a single discoverable "dummy" item for placing requests on physical journals in Primo as well as libraries that prefer not to have items discoverable by patrons until they are done with processing and are available on the shelves. In an ideal world, if a holdings record only had suppressed items, the holding record would also not display. Moreover, if all items on all holdings attached to a bibliographic…

    109 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Include Network IDs of linked bib records in quick export of bib records to Excel

    Please include Network IDs of linked bib records in the quick export of bib records to Excel. Currently the export does not contain Network IDs of linked records. If it includes the Network IDs, we can simply copy the Network IDs, and use them to create a set in the NZ, for further global updating. We need the Network IDs to create an NZ set especially when the original repository search criteria are based on some local contents, which do not exist in the NZ environment. In other words, if we want to create an NZ set based on the…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Move Browse bib headings and shelf listings function away from MD Editor

    Currently the Browse functions stick to MD Editor. And this poses too many restrictions to browsing. Please consider making browsing easier, and make it independent from MD Editor, and instead, incorporate browsing into normal simple and advanced repository searching.

    The major disadvantages of doing browsing within MD Editor are:
    1. Space constraint: the MD Editor does not have much space for results display
    2. Too many parameters to choose e.g. vocabulary, IZ vs. NZ

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Make Suppressing a location function the same as suppressing a holding in all publishing jobs

    Currently, the general publishing job exports inventory in locations which are ticked "Suppress from Discovery" in Physical Locations config, when "Excluded Suppressed Locations: is ticked in the Publishing Profile.

    Alma should handle this flag as it does for Publishing to Primo and Publishing to Libraries Australia and ignore suppressed locations, otherwise what's the point of setting this at the location level and then providing an option to Exclude suppressed records. It is extra work to set this value for each individual bib/holdings record.

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Add the 'Not contains', 'Not contains phrase', 'Not equal', 'Is not empty' search logic to Keywords, Creator, Subject etc. search indexes

    Please add the 'Not contains', 'Not contains phrase', 'Not equal', 'Is not empty' search logic to as many search indexes as possible, and particularly to Keywords, Creator, Subject search indexes.

    The 'Not contains', 'Not contains phrase', 'Not equal', 'Is not empty' search logics are very essential to advanced searches.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4 5 9 10
  • Don't see your idea?

Feedback and Knowledge Base