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
  1. Allow sorting of itemized set members similarly to logical set results.

    In Manage Sets, enable sorting the members of itemized record sets by title, creator, and publication date, similar to the criteria available for sorting results of logical sets. Currently our only option for sorting the members of an itemized set is by exporting to Excel and manipulating the resulting spreadsheet, which doesn't allow for clean sorting by the same criteria.

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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…

    39 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Index the Marc 546 field in Alma Repository Search

    Libraries have expressed the need to search the Marc 546 language note field in Alma repository search. https://www.oclc.org/bibformats/en/5xx/546.html

    Use cases:
    to search for specific languages that do not have a Marc language code in the 041 field.
    Or to search for closed-captioning or subtitle info in the 546 field. (Example: "English, Spanish, French or Mandarin dialogue with optional English for the hearing impaired; closed-captioned."

    https://www.oclc.org/bibformats/en/0xx/041.html

    Like how other 5xx fields are indexed in the Notes search index, could the 546 be indexed as well?

    https://knowledge.exlibrisgroup.com/Alma/ProductDocumentation/010AlmaOnlineHelp(English)/040ResourceManagement/040MetadataManagement/180SearchIndexes/MARC21SearchIndexes

    Voters: If you would like…

    39 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Allow network zone administrators to unlink bibs from member institutions

    In many cases member institutions share records with the NZ that go against the consortium's policy. In these cases the only recourse is to ask the member institution to "copy to catalog", which unlinks the record, allowing the NZ to delete the bib record. This can be cumbersome in a large consortium. It should be possible for the NZ admins to perform this action, i.e. while working in the NZ to unlink a bib from member IZs, as though any institutions holding that bib had selected "copy to catalog".

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Enable labeling enumeration and chronology fields

    It can be difficult to recall the meaning of enumeration and chronology fields, e.g., Enumeration A, Enumeration B, Chronology I, etc.). It would be helpful if general system administrators could change the labels of these that show to staff, for example, change Enumeration A to Year.

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Include MMS ID in Excel output from Manage Sets Results pages

    The MMS ID is essential information when dealing with spreadsheets of records, and yet it is missing from Excel output of lists of sets and search results. Please include the MMS ID in all output Excel spreadsheets of Repository records.

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Community Zone records: subfield t missing in 780 and 785 MARC tags

    In the CZ please add $t (Title of the related resource) to tags 780 (Continues) and 785 (Continued by).

    The lack of $t causes issues in discovery where 780 and 785 tags are set to be displayed, linked and searchable. With no $t this is not possible.

    31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. Allow overlap analysis tool to include print as well as e

    We would find it useful if the overlap analysis tool could also compare against print holdings, as well as electronic. Currently it only allows you to compare overlap within electronic titles, however the functionality of the tool is useful in that you can upload a file containing a list of identifiers, set up the overlap and leave it to run.

    The only way to conduct print and e overlap analysis in Alma at the moment is to use the Title level overlap analysis dashboard in Analytics, which includes various overlap reports and includes both print and electronic. However, we have…

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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)

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. LC call number search and index

    LC call number should support indexing all valid MARC fields as mentioned in http://www.loc.gov/marc/bibliographic/bd050.html and not only 050$a or local 090$a fields.
    It should index also $b and than enable to search for full LC call number, of course this should reflects also in the holdings level (i.e. $h,$i etc)

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. 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…)
  12. Add a mapping structure for normalization/merge rules in MDE

    The numbers of normalization rules is getting quite annoying. When we are in a consortium we also see every rule in the network zone.
    I would like a posibility to create folders like in Analytics.
    This would be helpful to group rules by institution or category.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Allow option to abort import once it has been submitted

    Once an import has been submitted, there should be an option to abort or cancel the import.

    Sometimes mistakes are made. The wrong import profile is chosen, the wrong file is chosen. Often the mistake can be noticed very quickly, but there is no choice but to wait until the entire import file is loaded. And by then the damage is done, it can be very tedious in Alma to undo certain mistakes (portfolios imported to the wrong collection for example).

    Alma offers the action option to "abort" once a job has been submitted. This same option should be available…

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. 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…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. 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.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Add more times to scheduled weekly bibliographic import jobs

    When running import jobs on a schedule Alma only gives us one weekly option (Saturdays at 3:00 a.m.). OCLC WorldShare generally posts new, delete and updated files on Saturday mornings in the early a.m., although not always by 3:00 a.m.
    Since it doesn't make sense to run these import jobs daily since record sets are only delivered weekly, we have them set up to run at 3:00 a.m. on Saturday (the only weekly option that Alma gives us). This causes the following problems:

    1) Files of deleted records are loaded concurrently with files of new records for the same collections…

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 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…)
  19. 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.

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. "Select All" checkbox for In Process Items

    When changing the status of In Process Items there is no “Select All” box at the head of the column, often there are multiple copies and we want to apply the same status change to all the items on the list.

    Instead of having to check the box next to each item in a list we would like to suggest that on this page (and other pages where applicable) that a “Select All” checkbox* be added.

    *as is the case on some lists such as “Patron Loans” and “List of Items”.

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base