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

184 results found

  1. Show the same note both in Edit service and on Edit collection level

    For a bether overwiev show the note addedd in collection service also under Edit collection. Saves a lot of work.
    Note is a great field.

    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)
  2. Add Day or Week embargo option

    When setting Coverage Information, current embargo options are to enter a number of months or years. Some publishers have a 2 week, or 14 day embargo; we cannot enter embargo information for these. Adding a Day and/or Week option would allow this information to be added.

    43 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. Include parser override values in it's own column in extended export report

    Include parser override values in it's own column in extended export report

    It's not possible to view which portfolios in a collection have parser override values. Currently, the value is included in the parser parameters value in extended export reports.

    It would be helpful with managing portfolios to have a way to see when a portfolio has a parser override value. That way, we could check on those portfolios and make sure the CZ parser value has been corrected.

    Please, include parser override values in it's own column in extended export report or have another way of highlighting when an…

    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)
  4. Ability to delete all parser override values using change portfolio job

    Currently, it's not possible to remove parser override values using the change portfolio job. This would be helpful when clearing those values from a collection of portfolios after the CZ portfolios have been updated by Ex Libris.

    46 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. If e-collection from CZ is already active in NZ, ask for validation

    It is possible to activate electronic collections from the CZ more than once in your NZ. We are aware there are use cases where this is the desired behaviour.

    Yet it would be nice if there was a short dialogue: "The collection is already active in your NZ. Are you sure you want to activate it again?" - just to avoid duplicate activation by mistake.

    23 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. Improve OpenURL generation to remove blanks and duplicates

    Openurls generated could by Alma/Primo be shorted by:

    1. Not sending duplicate parameters.
    2. Not sending empty parameters.

    Background:

    We have noticed that OpenURLs produced by Alma/Primo (which are then sent on to our ILLiad server, which can require redirection to get the patron authenticated) can be VERY long. So long in fact, that they can produce errors for our ILLiad web server. The ILLiad server will end up reporting "Request header is too large", and the user is left with a HTTP Status 400 Bad request error.

    We believe the responsibility here is on the Alma/PRimo side as the urls generated…

    15 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. Electronic Material Types - Need for more options.

    Unlike the Physical Item Material Types, Electronic Material Types are limited because they are hardcoded. However, the list that is provided by Ex Libris does not give us enough granularity. For instance, at our institution, we have senior theses that are deposited into our institutional repository. However, when you create the portfolio and select the Electronic Material Type there is no option for either “Bachelor’s Thesis” or a generic “Thesis”. Instead, they only provide “Dissertation” or “Master Thesis” there is no option for a Bachelor’s of Senior project. Therefore, we are forced to select Book which is inaccurate.

    This would…

    135 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. Add moore options to local portoflio

    Usefull to be able to add moore fields in the "add local portfolio"Moore authors and a publishing year

    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)
  9. Improve the management of license terms in config

    Currently to manage the order and organization of license terms in Alma, we have to number each term we wish to use in order. If we want to add or reorder, we need to carefully renumber the existing terms so we don't accidentally use the same number twice and risk overwriting existing terms. While we've all learned work-arounds for this, given the amount of work it takes to maintain our hundreds of licenses, it seems risky to have this form of ordering. It would be much better to have the functionality that appears elsewhere in Alma that allows for lines…

    56 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. Improve Alma's Licence „Controlled Vocabulary“ functionality

    Background (as it works now):

    Under „Manage License Terms“ a field can be defined as „Controlled Vocabulary“ and the defined CV values can be selected within a License. However, these CV values are only some kind of text module / boilerplate text which are copied into a specific license field. This means: when a CV value is changed or deleted, the content of this specific field in all licenses did not change. The change must be made in each license itself. A deleted CV value is displayed in the license field as: „<CV value> (not listed)“. The CV values functionality…

    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)
  11. Add electronic collection details to the Alma publishing

    Currently both physical and digital collections are published to Primo. Because of this these data elements can be added to the display sections of the Primo UI including the collections facets (courtesy of the Primo back office rules).

    Similarly the collection name is published to Primo Central and therefore can be included in the collections facet and full display Details section.

    Note: The publishing should also include details showing whether the resource is a Community Zone resource or not. (It may be desirable to only include non-Community Zone collections in the Primo displays as the PCI collections is already displayed).

    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)
  12. Improve 'Synchronize from CZ' job reports

    Sometimes, the information in the reports bears no resemblance to what’s in the CZ Updates Task List. For example, the 'portfolio linked to different bibliographic record' information isn't included in the CZ Updates Task List at all so you have to submit a SF case each time if you want to find out which portfolios were moved and which records are involved.

    It would be useful to have clickable counters in the 'Synchronize jobs from CZ’ job reports that take you through to the corresponding changes in the CZ Updates Task List.

    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)
  13. make "test access" work when direct linking is enabled

    The "test access" button in Alma does not work when direct linking is enabled in Primo. When trying to test access for an electronic portfolio, Alma loads a blank page forcing staff to click "display in a new window" in order to proceed. We recommend that this behavior be changed so that test access works the same regardless of whether direct linking is enabled.

    74 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. "Electronic material type originating from Bib" vs "Electronic material type" : a display issue in the Portfolio service editor's list

    In an electronic portfolio, there is a field called "Electronic material type originating from Bib" which can be overloaded by another field called "Electronic material type".
    The Job "Change electronic portfolio information" allows to update the material type of portfolios into the field "Electronic material type" into a set of portfolios.
    If we do so, the material type is not updated into the Portfolio service editor's list... which is confusing.

    our request : when the material type of a portfolio has been updated in the field "Electronic material type", ALMA should only considare this material type and display it in…

    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)
  15. E-Collections: Read-only access to Alma for other institutions

    We wish to provide read-only access to our Alma instance to other institutions in our consortium and vice versa so that we can compare setup more efficiently. The permissions need to be quite restrictive and prohibit access to financial, patron data, etc. but allow us to view E-Collection, Service and Portfolio level screens.

    When comparing set-up of our e-collections we are spending a lot of time discussing via email and sharing screen shots, which is not as efficient as being able to go in with a view privilege and compare in real-time.

    79 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. 49 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. Implement auto holdings for IEEE

    Implement auto holdings (autoholding, auto load, autoload) for IEEE, as is already available for ProQuest, Elsevier, Ovid, and Springer.

    118 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. Display perpetual coverage dates where no other coverage provided

    We now have the ability to log current access dates and perpetual access dates on a portfolio. However there is no way to display the perpetual access dates in Alma or Primo unless looking at the coverage tab of the portfolio.

    It would be good if there was an option to use the perpetual coverage dates as our display dates either by having an additional option for the local, global, local and global section, or just displaying those dates if local only is selected and there is nothing in the local section.

    We have titles that we had current and…

    103 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. Using load portfolios in a collection to update POL link

    We currently use the Load Portfolios tool in the Electronic service to update portfolio information. We have found this won't update the PO Line information in the Acquisition tab of the Portfolio. It is included in the data in an extended export of portfolio information, but does any changes/additions made to this field in the spreadsheet are not reflected in Alma when it is loaded.

    We would like to be able to add/change this information using the Load portfolios tool.

    A recent example of where this would be useful was a number of portfolios were incorrectly deleted from a collection.…

    41 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. Portfolio Bulk Load file limit too small

    The file limit of 10MB is too small. If we're using the Bulk Load, it means we're dealing with very large amounts of portfolios. Having to split those files is cumbersome.

    12 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