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

5 results found

  1. Add "Which coverage statement will be applied?" option to "Change Electronic portfolio information" job

    The "Change Electronic portfolio information" job includes the task "Remove local coverage" which removes local coverage from all the portfolios in a set so the only coverage remaining is global coverage. I run this in cases where the global coverage was once poor, so we loaded local coverage, but now the global coverage has been fixed and is good, so now we want to remove our local coverage and use the good global coverage. However, "Remove local coverage" does not also change the "Which coverage statement will be applied?" radio button from "Only local" to "Only global."

    It is important…

    87 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Create option to keep CZUTL deleted portfolios active in Institution Zone

    When portfolios are deleted from a non-auto-active electionic collection and notifications for this appear in the Community Zone Updates Task List, the portfolios stay unlinked in your institution zone but are deactivated. Often these are portfolios that represent access that still exists for the institution and we merely reactivate the local portfolio. We would like to be able to select an option to keep these portfolios active in our institution zone. If they are really no longer necessary, we can delete them when we review the CZUTL, but it would save us time if the portfolios were not deactivated automatically.

    161 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Implement auto holdings for Oxford University Press Journals

    Implement auto holdings for Oxford University Press journals as is already done for Springer, Elsevier, Ovid.

    60 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  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…)
  5. Add Access type in the portfolio information update job

    Since Ex Libris has added Access type for individual portfolio, there has to be a job to run to add access type to the portfolios in a collection. Currently, either we have to specify it in each portfolio manually, or we load a spreadsheet matching on portfolio ID. Unfortunately, as of today 1/23/2019, when loading a spreadsheet without the local coverage, e.g. only the access type, the local coverage is overwritten.

    105 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