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

129 results found

  1. 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.

    29 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. Full PCRE Regular Expressions in Normalization rules

    Supporting full PCRE regular expressions would make Normalization rules so powerful. Allow capturing data in one place and re-using it somewhere else, checking for substrings, etc.

    28 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. Make Push Selected to MDE button available for Itemized Sets

    'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…

    28 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. Option to export Alma search results and sets as CSV

    Right now Alma search results and sets can only be exported in XLSX-format. For performance (and other) reasons it would be good to have the option to export in CSV format.

    (Publishing this as an enhancement request was suggested by Ex Libris in public Salesforce case #00825531)

    27 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 active link function to all fields where a URI in subfield u is valid

    Subfield u for uniform resource identifiers has been defined as a valid subfield in many bibliographic fields to provide automated access to electronic resources.
    As noted in the OCLC bibformats: "Subfield ǂu defined as the URI is valid in the following fields: 031, 370, 381, 505, 506, 510, 514, 520, 530, 538, 540, 542, 545, 552, 555, 561, 563, 852, 856, 880, 883, 884, and 956. Additionally, subfield ǂu can be used in fields 901-907 and 945-949, either in accord with its control subfield definition or as a locally-defined subfield" (http://www.oclc.org/bibformats/en/controlsubfields.html#subfieldu).
    Currently, only URIs in 856 subfield u…

    27 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 an option to search the repository by "Assign to" cataloger / operator

    Currently there is no way to know which records are assigned to a certain user except for the "assigned to" note indication. We need a way to retrieve the records that were assigned in order to restore them back to the users' MDE, in case they dissappeard from the opened records pane. See full usecase in SFC#00957311.

    26 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. Add a safety feature to Delete Bibliographic Record Job to include option "Do not delete if ANY PO Line is attached"

    Currently there is only an option to protect Active PO Lines with this job. Acquisitions staff often place orders on bib records representing multi-volume sets. Cataloging staff then decided to use individual bib records for each volume and want to delete the set record and move POLs to the individual records. It would be very helpful to have this feature in place to protect order information.

    26 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. Enable 'recall' option on individual work orders

    At present work order types can be set to recall items or not.

    It would be useful to have this as an option for individual work orders (much as 'do not pick from shelf' is an option).

    This would make work orders more versatile and save having two work order types ('recall' and 'no recall') for essentially the same process.

    25 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. 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)
  10. 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)
  11. 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)
  12. 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)
  13. 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?

    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)
  14. 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)
  15. 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)
  16. 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)
  17. 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)
  18. 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)
  19. 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)
  20. 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)
  • Don't see your idea?

Feedback and Knowledge Base